W3C home > Mailing lists > Public > public-owl-wg@w3.org > January 2009

RE: ACTION-265 DONE

From: Michael Schneider <schneid@fzi.de>
Date: Wed, 21 Jan 2009 21:42:59 +0100
Message-ID: <0EF30CAA69519C4CB91D01481AEA06A0F988C5@judith.fzi.de>
To: "Bijan Parsia" <bparsia@cs.man.ac.uk>
Cc: "W3C OWL Working Group" <public-owl-wg@w3.org>
Hi!

I would put the "named class" option to the top of the list. I think our
annotation approach can now be pretty well described by: "The objects of
annotations are URIs." And since the "named class" option just introduces
such a URI, it looks to me to be the most obvious of the proposed
workarounds.

Just an idea,
Michael

>-----Original Message-----
>From: public-owl-wg-request@w3.org [mailto:public-owl-wg-request@w3.org]
>On Behalf Of Bijan Parsia
>Sent: Wednesday, January 21, 2009 8:42 PM
>To: W3C OWL Working Group
>Subject: ACTION-265 DONE
>
>
>See: http://www.w3.org/2007/OWL/wiki/LC_Responses/ALR1
>
>Here's the text:
>"""<<LC BOILERPLATE>>
>
>The working group has decided to make no change to OWL 2 in response
>to your comment. While we appreciate the use cases raised in your
>comment, we found that the specification and technical difficulties
>of adding such a feature at this time outweigh the benefits it would
>bring, esp. given the existence of various workarounds. For example,
>
>* One could embed class expressions in literals, i.e., xsd:string or
>XMLLiteral. While you point out that "strings rust", one could
>introduce a named subtype of xsd:string that would allow tools, such
>as Protege 4, to syntax check the expressions.
>* One could introduce a named class for the expression. To avoid
>cluttering the class hierarchy with these classes, one could either
>annotate the axioms, or use a distinguished naming scheme, or make
>them subclasses of a certain class.
>* In OWL Full, this is available in certain forms. So one could use
>OWL Full to guide an extension.
>
>The main issue with such workarounds is, of course, interoperability.
>However, we do feel confident that reasonable interoperability could
>be accomplished by your publishing details of the annotations (or
>naming scheme, or subtype) and having your popular tools support it."""
>
>I guess there's boilerplate afterwards as well, "Please let us know
>if this satisfies you. Blah blah."
>
>Cheers,
>Bijan.
>

--
Dipl.-Inform. Michael Schneider
Research Scientist, Dept. Information Process Engineering (IPE)
Tel  : +49-721-9654-726
Fax  : +49-721-9654-727
Email: schneid@fzi.de
WWW  : http://www.fzi.de/ipe/eng/mitarbeiter.php?id=555

============================================================================
==

FZI Forschungszentrum Informatik an der Universität Karlsruhe
Haid-und-Neu-Str. 10-14, D-76131 Karlsruhe
Tel.: +49-721-9654-0, Fax: +49-721-9654-959
Stiftung des bürgerlichen Rechts
Stiftung Az: 14-0563.1 Regierungspräsidium Karlsruhe
Vorstand: Prof. Dr.-Ing. Rüdiger Dillmann, Dipl. Wi.-Ing. Michael Flor,
Prof. Dr. rer. nat. Dr. h.c. Wolffried Stucky, Prof. Dr. rer. nat. Rudi
Studer
Vorsitzender des Kuratoriums: Ministerialdirigent Günther Leßnerkraus

============================================================================
==


Received on Wednesday, 21 January 2009 20:43:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 January 2009 20:43:42 GMT