Dion Moult

Ideas for the JSON equivalent of STEP anchors and references could be borrowed some one of the hypermedia conventions for JSON like HALJSON or JSON-LD. Just my $0.02 :)

I recall attribute regexes were useful in some of the more annoying situations like LayerSetName vs Name. It also has usecases in schema differences. Why is the cardinality for attributes...

A note that the cardinality may be fixed in the schema, but that's a separate thing to the cardinality in IDS. For example, the cardinality in schema might be optional,...

The cardinality for everything, not just attributes, can either be required, optional, or prohibited only. IDS as far as I'm aware has no scope right now for checking cardinality in...

My proposal is for UUID4, yes. However, this is not my area of expertise, so I would seek more experienced advice before making a decision. I do believe that specifying...

Unfortunately not, hence why some implementers are asking about the behaviour of the null UUID. I've seen implementers also choose to simply increment a number for "on-the-fly" exported IFC objects....

This is a fundamental problem in IFC, not in IDS, I believe. IFC2X3 did not have the EXPRESS rules that restricted the class-pairs to be used for types and occurrences....

If anybody is after a computer map of 2X3 elements to types I produced this after coming across the same problem in IFC2X3: https://github.com/IfcOpenShell/IfcOpenShell/blob/v0.7.0/src/ifcopenshell-python/ifcopenshell/util/entity_to_type_map_2x3.json

Oh right I see, that's a bit of a weird requirement then. What's the original requirement in plain English?

I'm still struggling to see what the practical information requirement is. It sounds a bit academic so far.