Andy Ward

It's an invalid file. The RepresentationContext is not defined correctly and none of the items are linked to the context that is available. We could have a look at if...

Probably best bringing @CBenghi in on this as he's more familiar with the Helix/3D batching

I'd expect it to technically pass. Which software are you using? The syntax looks correct. But I'm not sure it'll be checking what you are hoping for... This specification is...

You should definitely be able to do what you're suggesting: use an Attribute Facet as the sole Applicability selector. It's legal IDS syntax. E.g as in the [examples](https://github.com/buildingSMART/IDS/blob/master/Documentation/attribute-facet.md#examples) I'd take...

@stefkeB Looks like you need to rebase your [commit](https://github.com/buildingSMART/IDS/commit/febb5b52978aa3fc3faa47466553bed7a1435d92) before it can be merged?

Thanks Claudio. I've put a PR in for these IDS files. It's mainly just to avoid confusion amongst implementors over what the test case is testing. I've also finally made...

> Another approach would be to add and subtract a very small number. However, this approach also presents the issue of deciding how small the number should be. Regardless, I...

> Here's another proposal: what if the number was rounded to the same number of decimal places as what the IDS author specifies? While I can see the initial logic,...

Agreed, checking for any custom/USERDEFINED predefined type feels useful. This shouldn't preclude implicitly checking the ObjectType. 1. Standard case: _All Doors defined as TrapDoor_ (PredefinedType = TRAPDOOR) Entity Facet: -...

Just ahead of your call a couple of questions: **1. Valid/invalid use cases** > ## PROHIBITED > 3. IDS HAS PSET/PNAME/DATATYPE/VALUE: **This does not sound like a valid use case**...