Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

naming of data-section #5

Open
janbrouwer opened this issue May 30, 2020 · 1 comment
Open

naming of data-section #5

janbrouwer opened this issue May 30, 2020 · 1 comment
Assignees
@pipauwel @janbrouwer @dennisrshelden @kafsari

Comments

@janbrouwer
Copy link
Collaborator

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?
@pipauwel
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pipauwel pipauwel

@janbrouwer janbrouwer

@dennisrshelden dennisrshelden

@kafsari kafsari

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pipauwel @janbrouwer @dennisrshelden @kafsari