Unanswered Questions/Problems

Copyright General Electric Company 2005, 2006

This page documents currently unresolved issues about how to represent domain knowledge in OWL.

1. In the Vantage construct of pvf.owl, a Vantage has a set of relevant WorkDomainInformationObjects. A WorkDomainInformationObject is defined as an Abstract object which isRelevantTo a Vantage. The inverse property is hasRelevantInformation. Since neither is a FunctionalProperty, this allows a many-to-many relationship between Vantages and WorkDomainInformationObjects. The problem is that a WorkDomainInformationObject which isRelevantTo more than one Vantage can have a different degree of relevance for each Vantage. This seems like an attribute of the relationship, not of either WorkDomainInformationObject itself. But Properties can't have attributes in OWL, right? So how do we represent this?
2. As a more generalized version of the previous, how can we label edges in the graph?
3. Properties of Class: how can we associate an Individual with a Class definition? e.g., associate a particular action (Individual) to a general Class such as Frame.
4.