W3C home > Mailing lists > Public > www-rdf-interest@w3.org > January 2000

Re: Peering over the edge of the RDF cliff

From: Perry A. Caro <caro@Adobe.COM>
Date: Wed, 05 Jan 2000 12:58:33 -0800
Message-ID: <3873B079.AD867E23@corp.adobe.com>
To: Jeff Sussna <jeff.sussna@quokka.com>
CC: "'www-rdf-interest@w3.org'" <www-rdf-interest@w3.org>
Well, gee, if you're willing to abandon the syntax altogether, you won't
mind some hacks that are at least compatible with the RDF syntax, if not the

One option I've considered for this problem is to make the resource URL be a
literal, and then qualify the value to let people know that I really meant
it to be a resource:

<rdf:Description ...>
	<Property rdf:ID="author" rdf:parseType='Resource'>

Acutally, if you mean for Property to be a type, a typedNode might be

<Property rdf:ID="author" rdf:value="foo.html" valueType="resource"/>

This really makes your Property first class, and only creates one "object".

Another option is to use the parseType='Literal' escape-hatch and encode
whatever you want in the value:

<rdf:Description ...>
	<Property rdf:ID="author" rdf:parseType='Literal'>
		<subject resource='foo.html'/>
		<object resource='Fred'/>

This means that inferencing based on the pure unextended RDF model won't
work, but heck, it wouldn't work on your custom syntax anyway.  By hacking
the model but sticking with the RDF syntax, you at least maintain some
amount of interoperability.

Received on Wednesday, 5 January 2000 15:58:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:28 UTC