Comments on Annotated DAML Ontology Markup, rev 1.6, date 2000/10/07

Hi,

I read the first release of DAML-ONT (http://www.daml.org/2000/10/daml-ont.daml
).
I have some questions/comments. I would appreciate 
clarification wrt to the questions. 

With best regards,
Grit Denker

Dr. Grit Denker
Computer Science Laboratory, M/S EL284   tel: +1 650 859-6058
SRI International                        fax: +1 650 859-2844 (dept. fax)
333 Ravenswood Ave.                      email: denker@csl.sri.com
Menlo Park, CA 94025, USA                web: www.csl.sri.com/~denker




Questions/comments on http://www.daml.org/2000/10/daml-ont.daml :
-----------------------------------------------------------------

o I found it confusing that in some places one can find
  
   <domain resource="#Class"/>

  and in others 
 
   <domain resource="http://www.w3.org/2000/01/rdf-schema#Class"/>  

  just to find out at the end of the document that
 
   <Class ID="Class">
     <equivalentTo resource="http://www.w3.org/2000/01/rdf-schema#Class"/> 
   </Class>

o Typo:
    <Property ID="disjointUnionOf">
      ...
      <comment>
  
       for disjointUnionOf(X,Y)  read: ...
           !!!!!!!!

o  Typo:
    <Property ID="intersectionOf">
      <comment>
  
       for intersectionOf(X,Y)  read: ...
           !!!!!!!!

o Typo:
    <Property ID="item">
       <comment> for item(L,I) read : I is an item in L; 
                          !!!!
                 either first(L,I) or item(R,I) where...
                                           !!!!

    {because <domain resource="#List"/>}

o I was wondering whether all the facets of properties 
  (e.g., cardinality, maxCardinality, ...) should have
   
    <domain resource="#Property"/>

  Is that the default? 
  Did I miss something?
   
  Moreover, shouldn't there also be <range ...> definitions for
  all of them? For instance,
  
  <property ID="inverseOf">
     <range resource="#Property"/>
     ...
  </property>

  (and similar numbers for the cardinality properties?)


o Typo: 
    <Property ID="toValue">
       ....
       <comment>for toValue(R, V), read: ...
                               !!!

o Why is there no range constraint for the "toClass"  property, like
  <Property ID="toClass">
    ...
    <range resource="#Class"> ? 
   
   Is that default?

o Typo:
    <Property ID="qualifiedBy">
      ...
      <comment> for qualifiedBy(C, Q), read: ...
                                  !!!

o Typo:
    <Property ID="hasValue">
      ...
      <comment> for hasValue(Q, C), read: ... qualification to C.</comment>
                                                              !!!

o Assertion by reference, importing

  The comment for the "imports" property reads

    "X asserts the content of Y by reference"
    "if imports(X, Y) and you believe X and Y says something, then you
     should believe it"

  What does "asserts" and "believe" mean in this context?
  Is there any semantics that explains this?

o There were alternative IDs suggested for the property "equivalentTo":
  equals, equiv, renames

  I do not understand the semantics of this property. 
  Are there any implications/restrictions that assertions defined for any of
  the properties hold true for both of them? 
  Depending on the semantics one should choose the name of that property.

  Personally, I do associate with "equals" a syntactical equality.
  The term "equiv" in my view implies some kind semantic
  correspondence/equality . 
  "Renames" is the term which has fewest implications on the semantics.

Received on Wednesday, 11 October 2000 01:08:07 UTC