Avoiding exposed content in DAM+OIL

From: Frank van Harmelen (Frank.van.Harmelen@cs.vu.nl)
Date: 12/25/00

Dear joint-everybody,

While working on the DAML+OIL annotated example (aka the "walkthru"), I noticed the following point. I would be interested in your opinion:

One place where DAML+OIL annotations might live is inside .html files. We would want browsers to be undisturbed by the DAML+OIL annotations (ie, display nothing of these annotations). I believe this is called "avoiding exposed content" in the RDF M&S spec. I understand that RDF was explicitly designed to make this possible (see section 7.7 of http://www.w3.org/TR/REC-rdf-syntax/). 

Our current DAML+OIL syntax does very well in this respect. Besides some semantics-less tags like <versionInfo> and <comment>, all of DAML+OIL avoids exposed contents, WITH THE SINGLE EXCEPTION OF CARDINALITY CONSTRAINTS! An expression like 

      <onProperty rdf:resource="#father"/>

will display as "1" in a browser, which is unfortunate. Can this be avoided? 


This archive was generated by hypermail 2.1.4 : 04/02/02 EST