W3C home > Mailing lists > Public > uri@w3.org > June 2009

Re: URI for abstract concepts (domain, host, origin, site, etc.)

From: Erik Wilde <dret@berkeley.edu>
Date: Sun, 28 Jun 2009 20:43:10 +0200
Message-ID: <4A47B9BE.4000006@berkeley.edu>
To: "uri@w3.org" <uri@w3.org>

Eran Hammer-Lahav wrote:
> Let me try explaining my use case again, this time without any overloaded terminology or proposed solutions.
> XRD is a document format for describing resources. It looks like this:
> <XRD>
> 	<Subject>http://example.com</Subject>
> 	<Type>http://example.org/type/blog</Type>
> 	<Link>
> 		<Rel>author</Rel>
> 		<URI>http://example.com/author</URI>
> 	</URI>
> </XRD>
> Without getting too much into XRD, this short descriptor describes the resource identified by 'http://example.com'. It includes one type indicator (a made up example meant to mean this resource is a blog), and one link to the author's page.
> I want to use this document format to describe rules that apply to all resources which belong to an HTTP host (as defined by 2616: a domain/address and port combination). The problem is, <Subject> requires a URI and currently there is no way to identify this set of resources (http://domain:port/*) as a valid URI.
> What I don't want to do is use an exception such as 'if the URI begins with X, treat it as a rule and not a valid URI'...

given this new description, isn't what you're looking for a URI template 
language for XRD? maybe not exactly the one currently proposed by 
http://tools.ietf.org/html/draft-gregorio-uritemplate-03, but isn't that 
close to what you want? a template notation would also nicely address 
the case mentioned already where the host scope would be too general. 
but then again, a URI template is not a URI, so you could use it in the 
context of XRD, but not as a standalone URI....


erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
        dret@berkeley.edu  -  http://dret.net/netdret
        UC Berkeley - School of Information (ISchool)
Received on Sunday, 28 June 2009 18:44:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:13 UTC