@11:00, it seems like "broader" should be applied to the ontology, not the instance data right? It would be inferred from the ontology to determine that "BMW X2" is a specific type of "BMW" through relationships within the ontology rather than the instances directly. Is there a pro/con to defining this relationship on the instance data vs the ontology?
regarding your definition of knowledgegraph, I can say the same about rdf, because rdf does not a hierarchical structure in his data model. Different case are rdfs and owl. Thus, I wonder: it makes sense to use the name: knowldegegraph?
@11:00, it seems like "broader" should be applied to the ontology, not the instance data right? It would be inferred from the ontology to determine that "BMW X2" is a specific type of "BMW" through relationships within the ontology rather than the instances directly. Is there a pro/con to defining this relationship on the instance data vs the ontology?
regarding your definition of knowledgegraph, I can say the same about rdf, because rdf does not a hierarchical structure in his data model. Different case are rdfs and owl. Thus, I wonder: it makes sense to use the name: knowldegegraph?
Please double check Exercise 15 of the tutorial materials (PDF). I think the range and domain of "isBaseof" is switched in the video.