W3C home > Mailing lists > Public > semantic-web@w3.org > February 2011

RE: URI in a URI

From: Vincent Huang A <vincent.a.huang@ericsson.com>
Date: Fri, 4 Feb 2011 15:24:22 +0100
To: Hugh Glaser <hg@ecs.soton.ac.uk>, "<nathan@webr3.org>" <nathan@webr3.org>
CC: "semantic-web@w3.org" <semantic-web@w3.org>
Message-ID: <05E7708E0001C949A25F16661CC2F6F50394A09600@ESESSCMS0356.eemea.ericsson.se>
Thanks Hugh,

It really helps. The examples give me more understanding on how URI is constructed. 

I think this is a very useful feature to name emerging services.



-----Original Message-----
From: Hugh Glaser [mailto:hg@ecs.soton.ac.uk] 
Sent: den 4 februari 2011 15:08
To: <nathan@webr3.org>
Cc: Vincent Huang A; semantic-web@w3.org
Subject: Re: URI in a URI

A very useful question.
It is an important issue for the emerging services accessing the semantic web.

Yes in general using a # is a bad thing.
It is likely the server will never see the fragment after the #.

I don't know if it is written anywhere, but there seems to me a bit of a consensus around this.
And it is folded into the RESTful stuff.
So for example
describes a typical service invocation with a URI as argument as:

We do something similar in http://sameas.org/ http://sameas.org/about.php describes in detail, with things like:
http://sameas.org/?uri=http://dbpedia.org/resource/London (the NIR) and http://sameas.org/rdf?uri=http://dbpedia.org/resource/London (an IR) etc.
and also in the rkbexplorer services things like http://www.rkbexplorer.com/network/?uri=http://southampton.rkbexplorer.com/id/person-00021&type=person-person&format=tsv
as well as with two URIs

So you could use

Unless someone wants to tell us that is crazy?
This is the sort of thing it is useful to have some best practice emerge on..
Or can anyone point us at where it is written?


On 4 Feb 2011, at 12:41, Nathan wrote:

> Vincent Huang A wrote:
>> Can I have a URI in another URI definition?
>> For example, if I want to give a name to a temperature service coming from a sensor, can I say:
>> http://example.com/sensors/sensor1/services#http://sweet.jpl.nasa.gov
>> /2.1/propTemperature
> well now, that's just one, valid, URI :) so long as it conforms to the syntax restrictions then you're fine.
> note: be clear on the fact that it's only one URI though, not two URIs, or a "URI in a URI", and that #fragments have certain restrictions (see [1]), as in you can't have a '#' in a fragment.
> [1] http://tools.ietf.org/html/rfc3986#section-3.5
> Best,
> Nathan

Hugh Glaser,  
              Intelligence, Agents, Multimedia
              School of Electronics and Computer Science,
              University of Southampton,
              Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652 http://www.ecs.soton.ac.uk/~hg/
Received on Friday, 4 February 2011 14:25:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:42:25 UTC