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.

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

Relations order of relating and related attributes #77

Open
hlg opened this issue Oct 23, 2020 · 0 comments
Open

Relations order of relating and related attributes #77

hlg opened this issue Oct 23, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@hlg
Copy link

hlg commented Oct 23, 2020

I suggest to unify the order of relating and related attributes in objectified relations, particularly one-to-many relations. Currently we have for example:

  • IfcRelContainedInSpatialStructure with many side first (RelatedElements), one side second (RelatingStructure)
  • IfcRelAggregates with the one side first (RelatingObject), many side second (RelatedObjects)

This is a proposal to 'change' entities in the schema.

This would reduce variations in the schema which could cause confusion.

We would loose direction of the relation. If the relations are meant to be (and stay) uni-directional (or with a main direction), then this proposal would be obsolete. In that case I would still propose to check for consistency in names (subjects -relating- first, objects -related- second).

No impact on schema level, only on instance level. Instances are not forward-compatible. Automatic migration is possible.

@hlg hlg added the enhancement New feature or request label Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant