devonsparks / ifc-ld Goto Github PK

Hi Devon

I was wondering what language you are planning to develop or if the pipeline is already under development and if you are looking for help/contributions for the p21 -> json-ld converters.

I assume initially you're looking at consuming or exporting packages? Rather than a technical implementation of slots etc....

Happy to try and lend support if I can support the implementation.

Hi Devon sorry a couple of other questions I thought might be best separated; happy to amalgamate if preferred.

Why use a Package vs a MVD label can those be consolidated as the same concept? Or are you considering these like a merge or save event?

Can slots have slots? I think if an Entity can have 1:N slots, then each slot can be 'tagged' then you don't need to manage a single version of ifc you can store all versions of slots by different parties and when you want to get the data out get the relevant slots by tags and or date. You might need to reconcile changes if there are duplicates, but it should be reasonably simple.

At the same

Is a slot a single data point or can it be a group of attributes? Can it be both or is the idea you refer to IfcObjectDefinition for example as a slot or entity?

Slot naming for single attributes?
Rather then using ie "ifc4:person/4" a change to "ifc4:person/givenname" for a single attribute makes more sense.
This makes is more readable when looking at an individual item (don't need to look other references) and doesn't rely on ordered lists which is problematic.

Is the idea of Contents just to isolate the json relevant for ifc so it can be parsed back to STEP or others as required?