pasi-paasiala

Add an option to not add newlines after each line in the properties file

1

New lines after every line are a bit problematic for us, since we are manipulating the properties files also by external tools used by external translators. In this process the...

How requirements on enumerated properties should be interpreted

3

This is related to the following files: [IDS](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/property/fail-any_matching_value_in_an_enumerated_property_will_pass_3_3.ids) [IFC](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/property/fail-any_matching_value_in_an_enumerated_property_will_pass_3_3.ifc) The IDS requires that the enumerated value has simple value "EXISTING". The actual value of the property contains two values "EXISTING"...

Remove the outdated "implementation agreement" comment lines from the schema

4

The lines starting from here should be removed, since they're outdated. https://github.com/buildingSMART/IDS/blob/master/Development/ids.xsd#L67 Here are still the lines, if the line number mentioned above doesn't work due to changes to the...

Remove sample that is checking wall types

2

It is not advisable to target type classes in IFC, since: 1. The users may not be aware of them 2. The users may not have control over them in...

Remove cardinality checks for attributes

14

It is possible to specify cardinality for attributes as shown in [this](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/ids/pass-specification_optionality_and_facet_optionality_can_be_combined.ids) example. The specific requirement I'm talking about is this: ``` Description Foobar ``` The interpretation of this is...

Make system name mandatory for classification requirement

2

According to [this](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/classification/fail-a_classification_facet_with_no_data_matches_any_classification_1_2.ids) example it is possible to create a classification requirement that is accepted if an object has any classification. That is, it is possible to have this kind...

Relation names do not match the schema

1

The relation names in version afb04a10ff8cd9178f1665ce5a64198bed87e81a do not match the schema. The relation names should be all upper case. IFCRELASSIGNSTOGROUP instead of IfcRelAssignsToGroup.

Clarify relation recursion and cardinality

4

Currently the partof facet seems to be recursive by default as suggested by these [IDS](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/partof/pass-an_aggregate_entity_may_pass_any_ancestral_whole_passes.ids) and [IFC](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/partof/pass-an_aggregate_entity_may_pass_any_ancestral_whole_passes.ifc) files. This isn't very clear for example in the case when there's an...

#190 Relation names made all caps.

Add instructions to entity

2

All other RequirementsTypes have instructions. Entity should have as well.