Skip to content

Document why compound measures are absent from DataTypes (#297) #455

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BIMvoice wants to merge 1 commit into
base: development
Choose a base branch
from
Open

Document why compound measures are absent from DataTypes (#297) #455

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions Documentation/ImplementersDocumentation/DataTypes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -402,6 +402,8 @@ Columns of the table determine the validity of the type depending on the schema

Please note that [IFCSTRIPPEDOPTIONAL](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcStrippedOptional.htm) is a special data type that should never be instantiated, but it is listed here for schema tolerance reasons.

`IFCCOMPOUNDPLANEANGLEMEASURE` and `IFCCOMPLEXNUMBER` are intentionally absent from this table. Unlike every other measure, both are declared as aggregates in the IFC schema (`IfcCompoundPlaneAngleMeasure` is a `LIST [3:4] OF INTEGER` holding degrees, minutes, seconds and optionally millionths of a second; `IfcComplexNumber` is an `ARRAY [1:2] OF REAL`), so neither reduces to the single scalar value an `xs:restriction` requires and no `xs:base` type applies. Their data type can still be required on a property facet, for example `dataType="IFCCOMPOUNDPLANEANGLEMEASURE"`, to assert that a property exists with the correct IFC type. Only value level restriction is unsupported for these two.

## XML base types

The list of valid XML base types for the `base` attribute of `xs:restriction`, the associated regex expression to check for the validity of string representation, and the allowed nodes inside the `xs:restriction` are as follows:
Expand Down
Loading