Data validity / inference #28
Replies: 3 comments 2 replies
-
I don't think it's reasonable to expect all receiving applications to implement an Ontology Reasoner/Inferrer, so I think we need the sender to provide all the links (including inverse links). This gives us the most robust implementation of the standard: allowing an application to start from any point and traverse the ontology data in different directions, which supports the widest range of the use cases. |
Beta Was this translation helpful? Give feedback.
-
@RaggedStaff @simonLouvet I think we can close here, right? Do we need to document this somewhere? |
Beta Was this translation helpful? Give feedback.
-
Transfered to issue #34 |
Beta Was this translation helpful? Give feedback.
-
What we do when data is not “completed” = with the correct backlinks or inverse links (ex: CatalogItem:references / DefinedProduct:referencedBy).
is the responsibility of the sender to link data (inferences) or the receiver?
Use Case : When prototype imported data from Socleo, the link between supply and product (dfc-b:offers) was missing but inverse link exists (dfc-b:offeredThrough). When offers ui try to display product from offers it isn't possible. Prototype have to implement specific rules or make inferences from the OWL file to obtain dfc-b:offers predicate.
Beta Was this translation helpful? Give feedback.
All reactions