Andy Ward

Thanks, guess the main point was that it would be handy to codify this in some test cases so we don't get ambiguity. Just on the point of ambiguity, from...

Agreed, feels like the audit tool should warn when using an entity type this is 'inferable' this way. At the moment this IDS will throw an error in the Audit...

> How does the test case contradict this? My reading is the test cases treat Prohibited specifications as a logical NOT of Required specifications. e.g. [ids/pass-prohibited_specifications_fail_if_at_least_one_entity_passes_all_requirements_2_3.ids](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/ids/pass-prohibited_specifications_fail_if_at_least_one_entity_passes_all_requirements_2_3.ids) compared to [ids/pass-required_specifications_need_at_least_one_applicable_entity_1_2.ids](https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases/ids/pass-required_specifications_need_at_least_one_applicable_entity_1_2.ids) With...

Really feels like we need to clarify which of these algorithms spec cardinality should follow... 1. Spec Cardinality defines the expected number of matches from the applicability facets - regardless...

Totally get the use case, @CBenghi and indeed have both seen and built EIR requirements where applicability and requirement are split, and linked together via a relationship. If you're changing...

Fixed by #240 I believe, when introducing _cardinality_ attribute on Requirement facets

WIP at https://github.com/xBimTeam/XbimWindowsUI/pull/196

> As a human it is very hard to get your head around the fact that XMLSchema-instance is used to verify XML instead of an XSD +1 - the use...

@SteveLockley can you take a look while you're in the GE area? I had a quick investigation of #412 as well and determined: * Opens in v4 Geometry Engine *...

@Belrius Let me check up with Steve. @guenter1holzeder Version 6 is nearly there - final few bit of regression testing to do. It's a major update in that it: 1....