RFD: contents.rdf Spec v0.1

Howdy.  I'm cross-posting this because I hope both projects can start 
using the same decisions and perhaps software.

Below is a revised version of the contents.rdf file in 
twingle/content/sampledata.oscomorg.rdf.  I'd like to have some 
discussion on it, as I'm sure everyone is tired of the format changing. 
  Once we have some agreement, I can check in the file.

At the end of the RDF is an XML comment with some questions that need 
to be discussed.  Feel free to scroll down to that area and provide 
some responses.

Note that this file validates against the W3C validator with no 
warnings or errors.

--Paul

<?xml version="1.0"?>
<rdf:RDF xmlns:nc="http://home.netscape.com/NC-rdf#"
	 xmlns:dc="http://www.purl.org/dc/1.1#"
	 xmlns:oscom="http://www.oscom.org/rdf#"
	 xmlns:D="http://www.webdav.org/rdf#"
	 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<rdf:Description rdf:about="urn:twingle:sites:oscomorg">
   <nc:subitems>
     <rdf:Seq>
       <rdf:li rdf:resource="http://www.oscom.org/index.html"/>
       <rdf:li rdf:resource="http://www.oscom.org/conferences/"/>
     </rdf:Seq>
   </nc:subitems>
</rdf:Description>

<rdf:Description rdf:about="http://www.oscom.org/index.html">
   <dc:title>OSCOM Homepage</dc:title>
   <dc:creator>paul</dc:creator>
   <dc:description></dc:description>
   <dc:subject></dc:subject>
   <oscom:resourcetype rdf:resource="urn:oscom:resourcetypes:article"/>
   <D:getlastmodified>Monday, 12-Jan-03 09:25:56 GMT</D:getlastmodified>
   <oscom:previewurl>http://oscom.org/</oscom:previewurl>
   <oscom:saveurl>http://oscom.org/index.html</oscom:saveurl>
</rdf:Description>

<rdf:Description rdf:about="http://www.oscom.org/conferences/">
   <dc:title>Conferences</dc:title>
   <dc:creator>paul</dc:creator>
   <dc:description></dc:description>
   <dc:subject></dc:subject>
   <oscom:resourcetype rdf:resource="urn:oscom:resourcetypes:folder"/>
   <D:getlastmodified>Monday, 28-Jan-03 09:25:56 GMT</D:getlastmodified>
   <oscom:saveurl></oscom:saveurl>
   <oscom:previewurl></oscom:previewurl>
   <nc:subitems>
     <rdf:Seq>
       <rdf:li 
rdf:resource="http://www.oscom.org/conferences/index.html"/>
       <rdf:li rdf:resource="http://www.oscom.org/conferences/zurich/"/>
       <rdf:li 
rdf:resource="http://www.oscom.org/conferences/berkeley/"/>
       <rdf:li rdf:resource="http://www.oscom.org/conferences/harvard/"/>
     </rdf:Seq>
   </nc:subitems>
</rdf:Description>


<!--

Notes

0) Note that about and resource are now rdf:about and rdf:resource, to
get the W3C online validator to stop complaining.

1) The URN scheme is now simply URLs.  It isn't worth explaining the
difference.  For a folder, use a URL ending in a "/".

2) The URN is now the same as the source URL.  We will likely get rid
of the oscom:sourceurl property as it is redundant.

3) Previously, the dc:creator was an rdf:resource, meaning a reference
to a separately-defined, globally-unique resource.  I think that's too
hard for servers to support right now, so simply use a string.

4) The URN for the top-most resource must match the oscom:siteurn
identifier given in the RSD file.  Otherwise you won't see anything in
the tree.

5) dc:description will be visible as tooltiptext in Twingle/Moztop.

6) Servers can also put resourcetype resources in their contents.rdf
response, if they define any resourcetypes that aren't part of
Twingle/Moztop.

7) dc:creator, dc:description, and dc:subject should be considered
optional.

8) The value of a resource's urn attribute is now the "source" URL.
Meaning, this is the URL that should be used to fetch the original,
unrendered data for the page.

9) oscom:saveurl is the place an HTTP PUT will be issued to save the
data on the server.  For many systems this will be the same as the
value of the urn.

10) We need to have a debate about "article" vs. "document" (or
"page") for the name of the resourcetype across systems.

11) Do we need an encoding attribute in the XML declaration?

-->

</rdf:RDF>