|
|
|
|
|
by zozbot234
955 days ago
|
|
It's generally more interesting to apply validation to data than ontologies themselves. OWL makes this harder, because it rejects two assumptions that are commonly used in real-world modeling: (1) Unique Name Assumption; every object in the domain is described by a single entry in your data model. By contrast, OWL will always try to conflate different entries in order to solve logical consistency issues that arise from your model; (2) Closed-World assumption on relations. OWL rejects this and assumes that your data about the relations or properties in any given model is always incomplete. Its reaction to issues that crop up with your modeling is to enforce logical consistency by adding "inferred" property instances to your data, as opposed to simply flagging the issue for validation. Real-world technologies like SHACL and ShEx work on very similar logical principles, such as description logic https://news.ycombinator.com/item?id=31890041 but avoid these pitfalls. |
|