Andy Ward
Andy Ward
WPF is now supported in .NET core. We should future proof the Xplorer app by supporting the new runtimes and updating libraries we use to latest supported versions. (e.g. Helix,...
Most of the existing [test cases](https://github.com/buildingSMART/IDS/tree/master/Documentation/testcases) (which are really useful BTW) seem to exercise the Requirements scenarios over the Applicability side of things. I'm presuming that's since Requirements are the...
Most of the testcases in the [IDS folder](https://github.com/buildingSMART/IDS/tree/development/Documentation/testcases/ids) (10 out of 12 in development) seem to have an ifcVersion inconsistent with their corresponding test IFC file. i.e. they have an...
Updated now we've made xbim IDS validator public
Fixes #273 ifcVersion discrepancy
The test case IFC file [material/fail-an_optional_material_fails_if_no_value_matches.ifc](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/material/fail-an_optional_material_fails_if_no_value_matches.ifc) seems to be syntactically invalid. The IFCMATERIAL entity name should be in single quotes. i.e. `#2=IFCMATERIAL('No match',$,$);` rather than `#2=IFCMATERIAL("No match",$,$);` I'm guessing this...
Related to #175 it seems that both applicability and requirements are defined as a **xs:sequence** of the facets rather than an **xs:any**, which means if multiple facets need to be...
The Property facet specifies the Property Set and Name are both required parameters - which initially makes sense to avoid ambiguity etc. However it's relatively common to find EIR specifications...
According to the [docs](https://github.com/buildingSMART/IDS/blob/development/Documentation/facet-configurations.md#properties), `dataType` is a required field when specifying a `value`. The implication of this is that the IDS author must know the correct IFC dataType expected for...
A couple of issues discovered in the tolerance test cases when implementing the latest 1.0 logic: **1. Test values outside the precision of a double** _fail_comparison_tolerance_for_floating_point_negative_high_number_lower_bound.ids_ is testing that. `-1000001.0000010001...