W3C home > Mailing lists > Public > www-webont-wg@w3.org > January 2003

Explicit Constraint on SubPropertyOf in Presentation Syntax

From: Masahiro Hori <HORIM@jp.ibm.com>
Date: Sun, 5 Jan 2003 23:31:41 +0900
To: www-webont-wg@w3.org
Message-ID: <OFCD4BDDA8.34BF0300-ON49256CA5.0033E655@LocalDomain>

In the current XML presentation syntax Schema [1],
'SubPropertyOf' does not impose any constraints
on the varieties of propertyIDs. This will be
a problem for creating an XSLT stylesheet that
transforms presentation syntax to RDF/XML
syntax, which is an action item raised during
Dec. 19th telecon [2].

[1]
http://lists.w3.org/Archives/Public/www-webont-wg/2002Dec/att-0295/01-OWL-XML-Schemas.html
[2] http://lists.w3.org/Archives/Public/www-webont-wg/2002Dec/0272.html

# For the following proposal, I want to have
# comments especially from Jerome (who is working
# for the XSLT stylesheet) as well as Peter.


In the examples below, 'owls' is used as a
namespace prefix for the presentation syntax,
while 'owl' for RDF/XML syntax.  Currently,
owls:SubPropertyOf is used in the following
manner using the XML presentation syntax.

  <owls:SubPropertyOf owls:super="p2" owls:sub="p3" />

In this expression, variety of property IDs
('p2' and 'p3') cannot be made explicit, namely,
either as DatatypeProperty or ObjectProperty.
However, in the RDF/XML syntax, subPropertyOf
must be specified with a property type:

  <owl:ObjectProperty rdf:ID="p2">
    <rdfs:subPropertyOf rdf:resource="#p3" />
  </owl:ObjectProperty>


In order to alleviate this limitation, I would
like to propose the following changes in the XML
presentation syntax.

  <owls:SubPropertyOf>
    <owls:DatatypeProperty owls:super="p2" owls:sub="p3" />
  </owls:SubPropertyOf>

  <owls:SubPropertyOf>
    <owls:IndividualProperty owls:super="p2" owls:sub="p3" />
  </owls:SubPropertyOf>


I'm afraid the above markups may not necessary
be the best, but the changes are minimum and allow
to reflect the Abstract Syntax of SubPropertyOf.

  <axiom> ::= SubPropertyOf( <datavaluedPropertyID>  <datavaluedPropertyID>
)
  <axiom> ::= SubPropertyOf( <individualvaluedPropertyID>
<individualvaluedPropertyID> )


In addition, the same approach can be applied
to make the distinction of property IDs explicit
for EquivalentProperties in the presentation
syntax.

--(Current 'EquivalentProperties')------

  <owls:EquivalentProperties>
    <owls:property owls:name="p1" />
    <owls:property owls:name="p2" />
    <owls:property owls:name="p3" />
  </owls:EquivalentProperties>

--(Reviesed 'EquivalentProperties')------

  <owls:EquivalentProperties>
    <owls:DatatypeProperty owls:name="p1" />
    <owls:DatatypeProperty owls:name="p2" />
    <owls:DatatypeProperty owls:name="p3" />
  </owls:EquivalentProperties>

  <owls:EquivalentProperties>
    <owls:ObjectProperty owls:name="p1" />
    <owls:ObjectProperty owls:name="p2" />
    <owls:ObjectProperty owls:name="p3" />
  </owls:EquivalentProperties>
-----------------------------------------

As results, the EquivalentProperties
element in the presentation syntax
can also reflect the following Abstract
Syntax on EquivalentProperties.

<axiom> ::= EquivalentProperties( <datavaluedPropertyID>
{<datavaluedPropertyID>} )
<axiom> ::= EquivalentProperties( <individualvaluedPropertyID>
{<individualvaluedPropertyID>} )



-Masahiro

Masahiro Hori, Ph.D.
Group Leader, Programming Models & Tools,
IBM Tokyo Research Laboratory
Tel: +81-46-215-4667 / Fax: +81-46-274-4282
Email: horim@jp.ibm.com
Received on Sunday, 5 January 2003 09:31:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:57:56 GMT