Tag for AsymmetricProperty

[M Carter]

Has anyone been successful in documenting Asymmetric Object Properties? The ODM does not list it but RDF does. There is an RDF tag for Symmetric Object Property, that uses True/False. A True annotate as a symmetric property, a false does not annotate as a asymmetric property.

The RDF forms correctly for symmetric but does not even reference asymmetric. InverseFunctional does not work for me due to multiple asymmetry elements.

[Helmut Ortmann]

Hi,

I didn't get the picture.

Could you explain more specific what you expect from EA or..

Helmut

[M Carter]

Helmut,

The objective is to document an object property in standard OWL 2 syntax.

hasAssessment      
Annotations      
   description:   A asymmetric object property provides a specific association of the assessment element. It implies a subordinate/superior relationship.
   label:   hasAssessment
   version:   0.0.1
Properties      
   type: AsymmetricProperty
                 ObjectProperty

The problem is, the ODM implementation does not allow for explicit stating of isAsymmetric. There is an isSymmetric statement that is Boolean. But a false value does not state an Asymmetric object property.  Asymmetric is not the same as inverseFunctional.

Does that make sense?

[Glassboy]

It makes perfect sense.  Hopefully we'll see better OWL/RDF support in future versions.

[Paolo F Cantoni]

[SNIP]
The problem is, the ODM implementation does not allow for explicit stating of isAsymmetric. There is an isSymmetric statement that is Boolean. But a false value does not state an Asymmetric object property.  Asymmetric is not the same as inverseFunctional.
[SNIP]

Did you mean: "Asymmetric is not the same as inverseSymmetric."

AFAIK there are four terms in symmetry for relationships:  Symmetric, Antisymmetric, Asymmetric and Nonsymmetric - none of which are inverses to another.

Paolo

[M Carter]

Semantics...semantics.

The OWL2 specification states:

"An object property asymmetry axiom AsymmetricObjectProperty( OPE ) states that the object property expression OPE is asymmetric — that is, if an individual x is connected by OPE to an individual y, then y cannot be connected by OPE to x."

"An object property symmetry axiom SymmetricObjectProperty( OPE ) states that the object property expression OPE is symmetric — that is, if an individual x is connected by OPE to an individual y, then y is also connected by OPE to x."

The ODM specification states:

"A symmetric property is a property for which holds that if the pair (x, y) is an instance of P, then the pair (y, x) is also an
instance of P. Syntactically, a property is defined as symmetric by making it an instance of the built-in OWL class
owl:SymmetricProperty, a subclass of owl:ObjectProperty."

ODM 1.1 states:

"isAsymmetric: Boolean [0..1] – An asymmetric property is a property for which the triple (x, P, y) implies NOT(y, P, x)."  This is negates the use of functionalInverse properties, that have specific cardinality restrictions.

Now that we have defined the terms, the question still stands, has anyone found a workaround in EA for this particular issue.

What I see is that the specification used for ODM in EA is version 1.0 and not version 1.1.  For a customer trying to document an ontology specification, this is an issue.