Devon Sparks

I just stumbled on this same problem in a different context using rdflib==7.0.0 and get the same results @svenschneider does using the original example. What additional regression testing is recommended...

Thanks @GeorgDangl. Is it right to think that the Documents API intends to be a minimal interface over backend document databases that supports: 1. Asking the system for a "bucket"...

Hey @ykulbak - thanks for the notes. Makes sense. Webdav does support resource metadata through PROPFIND and PROPPATCH methods. It's not clear to me one way or the other whether...

Just one other thought for consideration: I'd agree the entity IDs are an artifact of the STP serialization and not a requirement of IFC proper. That said, if IFC is...

Hey @Moult I was thinking along these lines too. Considering the group has been targeting JSON Schema, I thought HyperJSON Schema might be a possible option here. An *almost* backwards...

@NickNisbet I'm curious: why wouldn't using the Header section to store a persistent ID for the exchange file solve the problem? As @pasi-paasiala notes, it at least has the benefit...

Thanks both. The challenges with using the IfcProject GUID for file identity make sense (e.g., @ykulbak's mention of parts-models and templates). I can't reason why Header attributes would suffer the...

I've wondered about this too. Consulting [Schenck](https://academic.oup.com/book/40825), substituting the string-based where rules with enumerations appears to be semantically consistent, because we're still defining a dedicated `TYPE`. There are a few...

+1. This looks like a straightforward fix. Minimizing the content surface between IFC "base types" (like IfcInteger) and EXPRESS primitives by using IFC's type definitions everywhere we can directly supports...