Peering over the edge of the RDF cliff

I am on the verge reimplementing the semantics of RDF on top of its syntax,
as in the following example:

	<Asset ID="foo.html"/>

	<Property ID="author">
		<subject resource="foo.html"/>
		<object resource="Fred"/>
	</Property>

I really don't want to do this, but it seems to be the only really clean way
I can find to treat RDF properties as first-class objects in a uniform way.
The constraint against having both ID and resource attributes of a property
appears to be the final straw. 

Please, please, please, someone convince me this is unnecessary. I really do
need properties to be first-class objects. I've thought of only doing so in
cases where I know I need them, but I fear stumbling into situations where I
need them but didn't realize it when I created the schema. 

Jeff

------------------------------------------------------------------------
Jeffrey E. Sussna
Chief Architect
Quokka Sports, Inc.
Digital Sports Entertainment

128 Spear St. Suite 200
San Francisco, CA 94105 USA
+1 415 369 4286

http://www.quokka.com
jeff.sussna@quokka.com