W3C home > Mailing lists > Public > www-rdf-interest@w3.org > March 2004


From: Dirk-Willem van Gulik <dirkx@asemantics.com>
Date: Tue, 2 Mar 2004 12:36:02 +0100
Message-Id: <C88F7BAC-6C3D-11D8-A0F6-000A95CDA38A@asemantics.com>
To: www-rdf-interest@w3.org

Not for any other reason that 'because you can' and triggered by  
Patrick Stickler comment
during the workshop that he does not want the URI its resource - but  
information ABOUT the
resource - give:


a spin. Just for fun and general knowledge perusal. Not as any thing  
serious or as
a construct towards any proposal on the table.

It uses the NAPTR record which is in http.uri.arpa as the starting  
point for a DDDS
walk; which ultimately result in 3 URLs (for this case); one with the  
resource itself  (i2r),
one with information about the resource (i2c) and one with the location  
of the resource (i2l).

Note that as we use uri.arpa. as a starting point for this DDDS walk  
(rfc 3401) we do not
get any of the nice 'fallback' options you see in


as the 'http.uri.arpa' space does not have that property. Note also  
that there is nothing
to stop a certain community to define its OWN ddds starting-point  
(which can even be
hardcoded in their software, does not need to be in DNS or have IANA  
blessing) to
do much the same - but with appropriate fallbacks, failures or 'well  
known ports of
call' without much loss of generality.

Received on Tuesday, 2 March 2004 06:36:25 UTC

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