Re: evaluating DAML+OIL vs. WebOnt requirements


This looks great!  A few comments:

1) Extending your recipe for strings, can't one express
unique URI naming of objects using

    a daml:UnambiguousProperty;  # each uniqueName denotes 1 object
    a daml:UniqueProperty.       # each object has only 1 uniqueName

2) For ontology management language features, I'd add that
DAML+OIL supports the use of other properties (such as
Dublin Core) with ontologies, but doesn't give them meaning.

3) For B solution to "tagging/grouping" problem, I think
we've overloading the term "tagging".  Some of us use the
term "tagging" for the use of statement IDs (e.g.
associating a statement with its source); DAML+OIL inherits
this ability from RDF, but doesn't give it meaning.  We
might want to split this into 2 requirements.


Received on Tuesday, 29 January 2002 20:05:15 UTC