W3C home > Mailing lists > Public > public-owl-dev@w3.org > April to June 2007

Re: RDFS compatibility information in OWL-DL documents

From: Alan Ruttenberg <alanruttenberg@gmail.com>
Date: Wed, 18 Apr 2007 13:52:29 -0400
Message-Id: <062D795D-B0A8-496A-B0A6-E557BB36B082@gmail.com>
Cc: Jeremy Carroll <jjc@hpl.hp.com>, public-owl-dev@w3.org, Tim Berners-Lee <timbl@w3.org>, Alistair Miles <a.j.miles@rl.ac.uk>
To: Bijan Parsia <bparsia@cs.man.ac.uk>
This is more complicated than I can easily follow for the moment. In  
case it is helpful,  here's an example of something I was thinking of:

Define: rdfs:imports as new ontology property. This is an instruction  
to rdfs tools that they should include the file specified by the  
property, and that owl reasoners should *not*. Consider the following  
case I suggested in the context of SKOS in some earlier  
correspondence. The idea would be that the extra triple  
"annotationSubPropertyOf a subproperty of subproperty" would be in a  
separate file, say "rdf-extras.rdf", and the test.rdf below would be  
amended so that it contains

<owl:Ontology rdf:about="#"><rdfs:imports resource="rdfs-extras.rdf"/ 

Then rdfs-extras.rdf would have this (instead of the owl file)

   <rdf:Property rdf:about="#annotationSubPropertyOf">
     <rdfs:subPropertyOf rdf:resource="&rdfs;subPropertyOf"/>

Of course, I would like OWL to support reasoning on annotation  
properties in some way, but the above is a little less ambitious and  
might be a good first step.

(there's a little more cleanup that had to be done to completely  
repurpose the example. mylabel and annotationSubPropertyOf need to be  
annotation properties in the OWL, and extras needs to say that  
AnnotationProperty is a subclass of Property.)


> 	From: 	  alanruttenberg@gmail.com
> 	Subject: 	tabulator doesn't understand subproperties of  
> rdfs:subPropertyOf (yet?)
> 	Date: 	January 23, 2007 10:44:18 AM EST
> 	To: 	  timbl@w3.org
> 	Cc: 	  a.j.miles@rl.ac.uk
> This is a prototype for workaround for allowing subproperties of  
> owl annotation properties. The idea is that
> the OWL version doesn't include the triple making  
> annotationSubPropertyOf a subproperty of subproperty. Of course  
> tabulator is smarter than OWL and can handle this (I would like to  
> be able to say).
> I'm thinking about this in the context of skos extensibility within  
> owl dl.
> http://mumble.net/~alanr/test.rdf
> The example:baz in this file should be labeled with "baz label"
> -Alan
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE rdf:RDF [
>   <!ENTITY example "http://example.com/#">
>   <!ENTITY owl "http://www.w3.org/2002/07/owl#">
>   <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
>   <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
>   <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
> ]>
> <rdf:RDF xml:base="&example;"
>          xmlns:example="&example;"
>          xmlns:owl="&owl;"
>          xmlns:rdf="&rdf;"
>          xmlns:rdfs="&rdfs;">
> <!-- Ontology Information -->
>   <owl:Ontology rdf:about="#"/>
> <!-- Annotation Properties -->
>   <rdf:Property rdf:about="#annotationSubPropertyOf">
>     <rdfs:subPropertyOf rdf:resource="&rdfs;subPropertyOf"/>
>   </rdf:Property>
>   <rdf:Property rdf:about="#mylabel">
>     <example:annotationSubPropertyOf rdf:resource="&rdfs;label"/>
>   </rdf:Property>
>   <owl:Thing rdf:about="#baz">
>     <example:mylabel rdf:datatype="&xsd;string">baz label</ 
> example:mylabel>
>     <example:someproperty rdf:datatype="&xsd;string">some property  
> value</example:someproperty>
>   </owl:Thing>
> </rdf:RDF>
Received on Wednesday, 18 April 2007 18:18:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:58:15 UTC