search

buildingSMART / NextGen-IFC

61 stars 4 forks source link

Remove the implementer agreements and merge them into the official documentation/spec #42

Open Moult opened 4 years ago

Moult commented 4 years ago

Description of the proposal:

I do not see the reason to have a separate set of implementer agreements - which are essentially meeting notes - as a separate location to see how things must be implemented. I think they can be systematically merged into the documentation text, and if we're lucky in some cases into the spec itself (in EXPRESS, or UML in the future)

Describe how it contributes to the objectives set in https://github.com/buildingSMART/NextGen-IFC/wiki/Towards-a-technology-independent-IFC:

What do we win:

Less confusion. Single source of truth. Less maintenance.

What do we loose

Nothing?

Schema impact:

Case by case based on implementer agreement.

Instance model impact:

Case by case based on implementer agreement.

Backwards compatible:

Case by case based on implementer agreement.

Automatic migration possible:

No.

Additional implications:

- Note that not all points need to be satisfied! Backwards compatibility and file size are not concerns.

TLiebich commented 4 years ago

fully agree with @Moult in order to proceed there should be a git based process to allow for pull requests on the IFC documentation itself, so that implementer agreements can be entered in a well defined and traceable process into the IFC specification.

berlotti commented 4 years ago

According to the principles and decision tree (https://github.com/buildingSMART/NextGen-IFC/wiki/Ten-principles-for-a-future-IFC) this is agreed. Checked with ISG. Proposal accepted.