How to enforce application-specific constraints? #731
Replies: 4 comments
-
|
In GitLab by @yoavnash on Jan 9, 2020, 16:48 changed the description |
Beta Was this translation helpful? Give feedback.
-
|
In GitLab by @yoavnash on Jan 9, 2020, 16:51 Advantages of modules:
Advantages of data models:
|
Beta Was this translation helpful? Give feedback.
-
|
In GitLab by @urbanmatthias on Mar 11, 2020, 08:21 I think it should be possible to add constraints to already defined entities using owl ontologies / modules. |
Beta Was this translation helpful? Give feedback.
-
|
Another idea: https://www.w3.org/TR/shacl/ |
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions