ifcJSON icon indicating copy to clipboard operation
ifcJSON copied to clipboard

naming of data-section

Open janbrouwer opened this issue 4 years ago • 1 comments

We had a discussion some time ago about the "data" section in IFCJSON, and if it was necessary. I believe we made the choice that it was optional for snippets and transactional exchanges, but is needed when header data is present. I think we need to pick a definitive one before it gets difficult to change. Options:

  • data; like is done in STEP
  • objects; very general
  • features; like is done in GeoJSON, good example, but not a good choice here because it refers more to "landschape-features"
  • entities; currently my favorite, because every object in this list is defined as "entity" in the IFC schema
  • any others?

janbrouwer avatar May 30 '20 07:05 janbrouwer

no particular preference really. Except for features, which I think is really a geospatial term.

pipauwel avatar May 30 '20 10:05 pipauwel