IFC4.3.x-development

IFC4.3.x-development copied to clipboard

Relationship of IfcGradientCurve.EndPoint, IfcSegmentedReferenceCurve.EndPoint with zero-length segment

4

As noted by @RickBrice https://github.com/IfcOpenShell/IfcOpenShell/pull/3982/files#diff-be0a3e3e00f8d8a24a29c355bd022eb663c4310e27251191374b9aa6d05ab4b4R100 This seems redundant. > If the geometry definition is also present, then each of the zero-length segments shall have a [IfcCurveSegment](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcCurveSegment.htm) counterpart - of length...

aothms

`IfcPostalAddress` used in concept template `Site attributes`

1

`IfcPostalAddress` is deprecated, but still used by the concept template `Site attributes`: https://github.com/buildingSMART/IFC4.3.x-development/blob/935c8a22db7379f04ee037ce2de9ba7b91eb99e2/docs/templates/Object%20Attributes/Object%20Occurrence%20Attributes/Spatial%20Element%20Attributes/Site%20Attributes/README.md?plain=1#L16-L25 Request to revise the concept template. I have no idea, where does the concept template come from...

pjanck

There is a typo in property name FlowMeterOurpose (should be FlowMeterPurpose) on page https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/Pset_FlowMeterOccurrence.htm (I just followed the "Let us know" link). _Originally posted by @HoKolo82 in https://github.com/buildingSMART/IFC4.3.x-development/issues/371#issuecomment-1802317218_

aothms

Ambiguity on whether or not object aggregates can have a body

3

According to the [element decomposition concept](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/concepts/Object_Composition/Aggregation/Element_Decomposition/content.html) it says: > By default the following constraints apply to an element being decomposed by Element Decomposition: > > Body Geometry — composite is...

Moult

I suggest adding to the section Pset_Distribution Port Type Cable.Connection Subtype recommendated subtype "Screw block terminal". Full portType definition will be like ElectricalConnectionType.**CRIMP** and ConnectionSubtype.**Screw_terminal** https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/property/ConnectionSubtype.htm

noskovvy

I found some descriptions containing random `\n` in them, should probably remove all of them: > 'Allows for specification of user defined roles beyond the\nenumeration values provided by Role attribute...

atomczak

Don't allow to arbitrarily mix IfcCurveSegment and IfcCompositeCurveSegment. Enforce as an express rule? From: @rickbrice https://github.com/IfcOpenShell/IfcOpenShell/pull/3945 @peterrdf @SergejMuhic @pjanck Thoughts?

aothms

IfcLinearPlacement.RelativePlacement and -.CartesianPosition lack description

7

cc @pjanck @SergejMuhic I think the main potential point of confusion that needs to be clarified is on `CartesianPosition`. I assume this the equivalent transform expressed as a non-linear explicit...

aothms

The changelog for [IfcElectricApplianceTypeEnum](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcElectricApplianceTypeEnum.htm) mentions that the PRINTER and SCANNER TypeEnums have been moved to [IfcCommunicationsApplianceTypeEnum](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcCommunicationsApplianceTypeEnum.htm). Why did PHOTOCOPIER remain in IfcElectricalApplianceTypeEnum, and not move over to IfcCommunicationsApplianceTypeEnum as well?

BenHuijskes

Pset_ConstructionOccurence and Pset_InstallationOccurrence both have InstallationDate. Both properties have the same description of "Date on which the element is installed" Both Psets are applicable to IfcElement. Proposal 1: remove from...

Moult