'cardinality' attribute in Presentation Syntax

Jeff wrote in [1]
> 8) The use of cardinality attributes with Restrictions
> that have subelements is confusing. It could be mistakenly
> interpreted to mean the same thing as the use of cardinalityQ
> in DAML+OIL. Perhaps it would be clearer to change the
> cardinality attributes to elements.

[1] http://lists.w3.org/Archives/Public/www-webont-wg/2002Dec/0186.html

I also think it is better to change the cardinality
attributes to child elements in the same manner as the
other restriction content elements, because it makes
all the restriction contents as sibling elements and
improve the consistency in the syntax.


[e.g., current presentation syntax]
  <owl:IndividualRestriction owl:property="child" owl:maxCardinality="1">
    <owl:allValuesFrom owl:class="Person" />
  </owl:IndividualRestriction>

  <owl:IndividualRestriction owl:property="advisor" owl:minCardinality="1">
    <owl:allValuesFrom owl:class="Person" />
    <owl:someValueFrom owl:class="Professor" />
  </owl:IndividualRestriction>

  <owl:DataRestriction owl:property="studentID" owl:cardinality="1">
    <owl:allValuesFrom owl:datatype="xsd:integer" />
  </owl:DataRestriction>


[revised presentation syntax]
  <owl:IndividualRestriction owl:property="child">
    <owl:maxCardinality owl:value="1" />
    <owl:allValuesFrom owl:class="Person" />
  </owl:IndividualRestriction>

  <owl:IndividualRestriction owl:property="advisor">
    <owl:minCardinality owl:value="1" />
    <owl:allValuesFrom owl:class="Person" />
    <owl:someValueFrom owl:class="Professor" />
  </owl:IndividualRestriction>

  <owl:DataRestriction owl:property="studentID">
    <owl:cardinality owl:value="1" />
    <owl:allValuesFrom owl:datatype="xsd:integer" />
  </owl:DataRestriction>


-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 Tuesday, 7 January 2003 13:26:06 UTC