Re: Avoiding exposed content in DAM+OIL

From: Stefan Decker ([email protected])
Date: 12/27/00

• Next message: Frank van Harmelen: "parseType="daml:collection""
• Previous message: Frank van Harmelen: "Re: Avoiding exposed content in DAM+OIL"
• Maybe in reply to: Frank van Harmelen: "Avoiding exposed content in DAM+OIL"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

OPS,

after checking with the RDF Spec I discovered another bug.
While my last email contained valid RDF, the value of XML attributes
are treated like strings, not resources.
#father, however, is a resource - so Ian's suggestion does unfortunately 
not work.

The following productions taken from the RDF Spec are relevant here:
<quote >
   [16] propAttr       ::= propName '="' string '"'
                           (with embedded quotes escaped)
   [17] typedNode      ::= '<' typeName idAboutAttr? propAttr* '/>'
                         | '<' typeName idAboutAttr? propAttr* '>'
                               property* '</' typeName '>'
</quote>
the value of propAttr is a String.

The following would work:

    <restrictedBy>
      <Restriction cardinality="1">
          <onProperty rdf:resource="#father"/>
       </Restriction>
    </restrictedBy>

but isn't as nice...

Sorry,

     Stefan

• Next message: Frank van Harmelen: "parseType="daml:collection""
• Previous message: Frank van Harmelen: "Re: Avoiding exposed content in DAM+OIL"
• Maybe in reply to: Frank van Harmelen: "Avoiding exposed content in DAM+OIL"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

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