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 14:48:32 +0100
To: Steve Harris <steve.harris@garlik.com>
CC: "semantic-web@w3.org" <semantic-web@w3.org>
Message-ID: <05E7708E0001C949A25F16661CC2F6F50394A095AF@ESESSCMS0356.eemea.ericsson.se>
Hi Steve,

Thanks, I see how it works for n-ary relations in RDF. 

However, what I want to achieve is naming of a simple service. And from the name of the service, I should understand what the service is about without the need of fetching an RDF file. 

Regards,

Vincent

-----Original Message-----
From: Steve Harris [mailto:steve.harris@garlik.com] 
Sent: den 4 februari 2011 14:38
To: Vincent Huang A
Cc: semantic-web@w3.org
Subject: Re: URI in a URI

You can describe it using a bnode, or UUID URI, or some such, for example, in Turtle:

[
	:service <http://example.com/sensors/sensor1/services> ;
	:reading <http://sweet.jpl.nasa.gov/2.1/propTemperature> ;
	rdf:value 12.0 ;
] .

This is a common way to express n-ary relations in RDF.

- Steve

On 2011-02-04, at 13:22, Vincent Huang A wrote:

> Hi Andrea,
>  
> Thanks for your reply. What I want to do is to give an identity to a 
> service. I could use 
> http://example.com/sensors/sensor1/services#Temperature
> but, I want to use a well-defined name for the service.
> http://sweet.jpl.nasa.gov/2.1/propTemperature is used as a well-defined name instead of the word "Temperature".
>  
> I can have a sensor RDF with the property inside, then I will not be able to have a URI for the service.
>  
> Regards,
>  
> Vincent
>  
>  
> From: semantic-web-request@w3.org [mailto:semantic-web-request@w3.org] 
> On Behalf Of Andrea Splendiani
> Sent: den 4 februari 2011 14:02
> To: Vincent Huang A
> Cc: semantic-web@w3.org
> Subject: Re: URI in a URI
>  
> Hi,
>  
> Technically yes (but you may have to escape something).
>  
> Design wise, you want to say:
> Sensor (uri) property (uri) value.
> You have a triple.
> So should be your sensor URL returning an rdf doc with the property inside.
>  
> Said that, if you need the composed uri for some other reason... That works.
>  
> Ciao,
> Andrea
> 
> Apologies for typos, sent from an iPad
> 
> Il giorno Feb 4, 2011, alle ore 12:24, Vincent Huang A <vincent.a.huang@ericsson.com> ha scritto:
> 
> 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
>  
> Thanks,
>  
> Vincent
> 

--
Steve Harris, CTO, Garlik Limited
1-3 Halford Road, Richmond, TW10 6AW, UK
+44 20 8439 8203  http://www.garlik.com/
Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Friday, 4 February 2011 13:49:29 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 21:45:41 GMT