W3C home > Mailing lists > Public > www-tag@w3.org > December 2011

evolution, mime, registration document posted

From: Larry Masinter <masinter@adobe.com>
Date: Mon, 19 Dec 2011 16:16:04 -0800
To: Jonathan A Rees <rees@mumble.net>
CC: "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D06121B5793@nambxv01a.corp.adobe.com>
I put the document I've been working on (evolution, registries and MIME), into TAG space.

           http://www.w3.org/2001/tag/2011/12/evolution/evolution-mime-registries.html

the document isn't stable (I'm editing it every day). 


Looking at 
http://www.w3.org/2001/tag/2011/12/uddp/


I would align the two documents with this formulation (which won't make sense if you haven't read 'evolution'):

RDF is an extensible (abstract) language for making assertions, and for which there are several concrete languages which encode and use the abstract framework.

 RDF chose "use URI" as the extensibility method for identifiers in RDF's subject, predicate, and object protocol elements (when those are not blank or literals.)  
The protocol element is called 'uriRef' in RDF, and I'll refer to it as the "RDF#uriRef" protocol element.

UDDP supplies  methods  for supplying additional information can be associated with (some) RDF#uriRefs, and for accessing that information, in the form of a document.

(The methods in the document posted are available for RDF#uriRefs which use a scheme that is based on HTTP and thus has status codes, or those that have a fragment identifier and a stem which can be used to retrieve a representation for which the fragment identifier is meaningful.)

Other languages and protocols (besides the RDF based ones above) may choose to use the RDF#uriRef protocol element in a compatible way.

RDF#uriRef as a protocol element shares many of the concerns discussed within the section labeled "Web Evolution: References between Specifications". 
Since the reference associated with a uriRef may change over time, and as to the decision as to the applicability of the document obtained using UDDP at a later date is left to the implementation.

Larry
Received on Tuesday, 20 December 2011 00:17:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:44 GMT