Skip to content

naming of data-section #5

@janbrouwer

Description

@janbrouwer

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?

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions