W3C home > Mailing lists > Public > public-vocabs@w3.org > May 2014

Re: Are there any plans to develop an OWL version of QUDT?

From: Simon Spero <sesuncedu@gmail.com>
Date: Wed, 7 May 2014 21:41:07 -0400
Cc: W3C Web Schemas Task Force <public-vocabs@w3.org>, Ralph Hodgson <rhodgson@topquadrant.com>
Message-Id: <90C1F4B8-EAA5-4314-94D3-671D22949062@gmail.com>
To: Holger Knublauch <holger@topquadrant.com>
On May 6, 2014, at 8:19 PM, Holger Knublauch <holger@topquadrant.com> wrote:

> +1
> 
> OWL DL is IMHO an academic niche language while most real-world projects that I have seen don't need or want its limitations. I also find it alarming if people argue that we should not use RDF features only because their favorite ontology editor and API cannot handle RDF. Being limited to OWL DL was a design decision that those tools made, while other tools have no problems with RDF.
> 
> Holger

You raise some good points;  as I have often stated (pace pfps) , I consider Description Logics to be rather weak tea, and whilst they are very well suited to a certain class of problem, I greatly prefer non-montonic, higher order systems for general KR problems. 

However, some of the points you make require some caveats.   

Firstly:  
    If a problem falls within the class of problems that OWL 2 DL can handle, it is good to stay within the constraints of DL.  Going to OWL Full should be made on a carefully considered basis of costs vs. benefits.  

Secondly: 
       The mapping from OWL to RDF is explicitly only defined for OWL-DL.  It is not possible always possible to parse an OWL-2 ontology that does not follow some of the DL restrictions.  One can make a best effort, but the mapping from OWL 2 Full to RDF is a one way trip, as the OWL to RDF mapping specifications makes clear in the first paragraph of the first section. 

Thirdly:  
         The vocabularies being discussed were inconsistent at every level of the RDF, RDFS, and OWL chain, and contained basic type errors. I do not know what tools were used to create them, but whatever tool it was could not do basic consistency checking.   

Fourthly:  
      If a vocabulary or tool claims to comply with  standards/(W3C recommendations), it is very important that the vocabulary/tool should comply with those standards. If a vocabulary tool is intended to follow a standard, but is in fact non compliant, then it is a major bug.  

As Ralph said, he considers the problems I reported to be potentially serious issues, and will be looking in to them in detail.

Simon
Received on Thursday, 8 May 2014 01:41:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:41 UTC