Using owl:deprecated

[Liana Kiff]

I am wondering if there is a correct syntax to get the form editor to let me specify  "true" ^^xsd:boolean  as the value of the owl:deprecated property when I add it to a class (or instance) in the editor.  I can force this value into the source code as an rdf statement  [owl:deprecated "true"^^xsd:boolean ;] , but not into the form editor, which expects a fully defined rdf:Resource.  Is there a trick to the syntax I should use in this case, or is there no other way than to switch to Source view?

It seems strange that it should be so hard to add this property and value, when the only reason to add this property in the first place is to specify the value "true."

-Liana

[Holger Knublauch]

Hi Liana,

this goes back to the official OWL 2 vocabulary published at the URL of the OWL namespace. It states

owl:deprecated a owl:AnnotationProperty ;
     rdfs:label "deprecated" ;
     rdfs:comment "The annotation property that indicates that a given entity has been deprecated." ;
     rdfs:domain rdfs:Resource ;
     rdfs:isDefinedBy <http://www.w3.org/2002/07/owl#> ;
     rdfs:range rdfs:Resource . 

which means that the values of owl:deprecated may be anything. For properties with the range of rdfs:Resource, TopBraid assumes that the values are resources, so there is no input widget for xsd:boolean values.

Looking through the spec, it is unclear why they didn't set the range to xsd:boolean, so I guess I'll just make this change to our system vocabulary for the next version, and you'll then get the boolean editor. The only value that this property is ever taking seems to be "true".

Thanks,
Holger

--
You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to topbrai...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Irene Polikoff]

Yes, this looks like an issue with the spec. On one hand, OWL vocabulary says:

owl:deprecated a owl:AnnotationProperty ;

     rdfs:label "deprecated" ;

     rdfs:comment "The annotation property that indicates that a given entity has been deprecated." ;

     rdfs:domain rdfs:Resource ;

     rdfs:isDefinedBy <http://www.w3.org/2002/07/owl#> ;

     rdfs:range rdfs:Resource . 

On the other hand, verbally, the spec says: 

"An annotation with the owl:deprecated annotation property and the value equal to "true"^^xsd:boolean can be used to specify that an IRI is deprecated.”

If so, then the range should be xsd:boolean or may be no range at all so that users can decide if they want a boolean or a resource.

Irene Polikoff

[Liana Kiff]

Thank you for the explanation, and I'll look forward to the "fix."
I agree that the spec seems to be out of alignment with the intended use.