Re: Identifying OWL 1.1 files & the OWL namespace

Holger Knublauch a écrit :
> But we at least want this to work the other way around, so that OWL 1.1
> aware tools can process "legacy" OWL 1.0 files.  Furthermore, OWL 1.0
> tools can at least partially make sense of OWL 1.1 files.  Therefore I
> don't think that using a completely new namespace is a good solution.

I don't think that recognizing both namespaces (1.0 and 1.1) would be
too difficult to implement.

> The more I think about it, I would vote for a convention such as
> 
>   xmlns:owl="http://www.w3.org/2002/07/owl#"
>   xmlns:owlx="http://www.owlx.org/2006/11/owlx#"  // or similar

IMO, that would make manual editing of OWL 1.1 a real headache! The
distinction between rdf: and rdfs: being not always intuitive or
natural, that would make things even worse.

Or are you trying to ban manual editing in favor of high-level
interfaces like Protégé ? ;->

> Resulting files would contain statements such as
> 
>     <rdfs:subClassOf>
>       <owlx:SelfRestriction>
>         <owl:onProperty>
>           <owl:ObjectProperty rdf:ID="likes"/>
>         </owl:onProperty>
>       </owlx:SelfRestriction>
>     </rdfs:subClassOf>
> 
> This would allow tools and users to more easily recognize that OWL 1.1
> is used, and the owlx namespace declaration would point to the
> corresponding draft version.  For OWL 1.0 tools, the additional
> constructs might just become junk statements but at least they can
> process the vocabulary that they know about.

I'm really not convinced that partially parsing an OWL 1.1 ontology with
by OWL 1.0 agent would be relevant at all...

  pa

Received on Wednesday, 24 January 2007 16:18:31 UTC