- From: Boris Motik <boris.motik@comlab.ox.ac.uk>
- Date: Mon, 16 Jun 2008 21:14:31 +0100
- To: <public-owl-wg@w3.org>
Hello, As required by my ACTION-160, I've extended the specification with keys. Here are the diffs: Structural specification: http://www.w3.org/2007/OWL/wiki/index.php?title=Syntax&diff=8647&oldid=8591 Semantics: http://www.w3.org/2007/OWL/wiki/index.php?title=Semantics&diff=8664&oldid=8596 RDF Mapping: http://www.w3.org/2007/OWL/wiki/index.php?title=Mapping_to_RDF_Graphs&diff=8655&oldid=8581 XML Schema: http://www.w3.org/2007/OWL/wiki/index.php?title=OWL_XML_Schema&diff=8648&oldid=7939 Profiles: http://www.w3.org/2007/OWL/wiki/index.php?title=Profiles&diff=8662&oldid=8601 This was one of the more complex changes to the documents, so it is quite possible that there are bugs out there. Should you find any, please let me know. Just as a heads up, contrary to Bijan's suggestion, I haven't introduced a nonterminal production KeyPropertyExpression that would be a superclass for ObjectPropertyExpression and DataPropertyExpression. Introducing another class seemed like quite a bit of overhead, particularly that you need to syntactically distinguish object from data property expressions in the semantics and in various other places. Instead, in the RDF mapping and semantics document, I chose to refer to the axiom as KeyFor( OPE1 ... OPEm DPE1 ... DPEm CE ). Although this seems to suggest that all object properties should come before all data properties, this is not the intended meaning; in fact, the syntax allows for interleaving object and data properties. Regards, Boris
Received on Monday, 16 June 2008 20:16:05 UTC