This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
In the aviation Ontology we've been reviewing thus far, flights and delays are represented as distinct object types. This decision was made in light of at least one alternative: to include delay information as a property of each flight object. See the image below for an illustration of the trade-off.
How should these trade-offs and design decisions be made?
📚 Recommended Reading (~10 min read)
Ontologies can be updated once deployed, but starting out with a well-reasoned framework will reduce the time it takes to derive value in Foundry. Review the following Foundry article that describes how the Object Model should be created in response to the functional requirements of the use case.
By now it should be clear that an optimal Ontology requires an optimal backing pipeline, which is one reason data engineers are so critical in the Ontology development and maintenance lifecycle. Through the rest of this tutorial, you'll use your experience in this training track to build and improve a set of Ontology object and link types.