DDDS on URI's

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:

	http://demo.asemantics.com/biz/rdfa/walker.pl?http:// 
www.asemantics.com/

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

	http://demo.asemantics.com/biz/rdfa/walker.pl?urn:foaf: 
areggiori@webweaving.org
versus
	http://demo.asemantics.com/biz/rdfa/walker.pl?urn:foaf: 
Libby.Miller@bristol.ac.uk

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.

Dw.