-
Notifications
You must be signed in to change notification settings - Fork 12
How to enforce application-specific constraints? #229
Copy link
Copy link
Closed
Labels
💬 discussionThe idea is not mature enough to result in an implementation, and needs further discussion.The idea is not mature enough to result in an implementation, and needs further discussion.⚡ breaking changeSolution introduces incompatible API changes, MAJOR version number update. See https://semver.org.Solution introduces incompatible API changes, MAJOR version number update. See https://semver.org.data model
Description
Metadata
Metadata
Assignees
Labels
💬 discussionThe idea is not mature enough to result in an implementation, and needs further discussion.The idea is not mature enough to result in an implementation, and needs further discussion.⚡ breaking changeSolution introduces incompatible API changes, MAJOR version number update. See https://semver.org.Solution introduces incompatible API changes, MAJOR version number update. See https://semver.org.data model
In GitLab by @yoavnash on Jan 9, 2020, 16:42
Two alternatives:
A module is an ontology fragment in which context-specific constraints are enforced by subclassing of classes in common ontology classes.
A data model is written in a separate file in YAML format. Its main use is to enforce context-specific constraints whenever data is pushed is to the dataspace. It is not allowed to create new classes in a data model file, only to strengthen existing constraints or provide new ones.