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

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

From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
Date: Mon, 29 Jun 2009 17:14:52 +0900
Message-ID: <4A4877FC.7080803@it.aoyama.ac.jp>
To: Eran Hammer-Lahav <eran@hueniverse.com>
CC: Erik Wilde <dret@berkeley.edu>, "uri@w3.org" <uri@w3.org>
I think the problem is that if there's an easy solution for 'hosts' (by 
whatever definition), and you consider your problem solved, then the 
next week/month/year, somebody else (or it might be you) will come again 
and ask for something similar, only on a slightly different (more 
general or more specific) level.

It is unclear from your example below whether XRD allows more than one 
<Subject> at the same time, but if it does, you are on the right way, 
maybe. It may then be possible to add something like <Prefix> (data 
applying to all URIs with the same prefix),..., and then sooner or 
later, we get to an URI templating language.

I just remembered that the 1999 version of RDF had "aboutEach" and 
containers defined by an URI pattern
(see http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#containers)

As far as I remember, at least the later was discontinued in the 2004 
update, but I might be wrong.

Regards,    Martin.

On 2009/06/29 4:32, Eran Hammer-Lahav wrote:
> Using a URI template is one option being considered (XRD already has a<URITemplate>  element under<Link>  so the syntax is already part of XRD). However, that requires either creating a new element (like<SubjectTemplate>) or changing the XML schema type for<Subject>  which currently does not allow anything but valid URIs.
>
> But before we consider that, I wanted to see if there was an easy solution for describing such resources with a URI.
>
> EHL
>
>> -----Original Message-----
>> From: uri-request@w3.org [mailto:uri-request@w3.org] On Behalf Of Erik
>> Wilde
>> Sent: Sunday, June 28, 2009 11:43 AM
>> To: uri@w3.org
>> Subject: Re: URI for abstract concepts (domain, host, origin, site,
>> etc.)
>>
>> hello.
>>
>> 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....
>>
>> cheers,
>>
>> erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
>>          dret@berkeley.edu  -  http://dret.net/netdret
>>          UC Berkeley - School of Information (ISchool)
>
>
>

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp
Received on Monday, 29 June 2009 08:15:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:42 GMT