> For the complete documentation index, see [llms.txt](https://docs.dfc-standard.org/dfc-standard-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dfc-standard.org/dfc-standard-documentation/appendixes/technical-decisions/data-validity-and-inferences.md). # Data validity and inferences What we do when data is not **completed** = with the correct backlinks or inverse links (e.g. `CatalogItem:references` / `DefinedProduct:referencedBy`). **Is it the responsibility of the sender to link data (inferences) or the receiver?** It isn't reasonable to expect all receiving applications to implement an Ontology Reasoner/Inferrer, so 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. ## Decision * When transmitting data via the DFC standard any and all inverse relations (that exist in the ontology) MUST be provided for each transferred property. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dfc-standard.org/dfc-standard-documentation/appendixes/technical-decisions/data-validity-and-inferences.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.