W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2009

Re: DESCRIBE ENDPOINT

From: Axel Polleres <axel.polleres@deri.org>
Date: Tue, 30 Jun 2009 18:23:32 +0100
Message-ID: <4A4A4A14.9000005@deri.org>
To: 'RDF Data Access Working Group' <public-rdf-dawg@w3.org>
Paul Gearon wrote:
> On Tue, Jun 30, 2009 at 10:05 AM, Axel Polleres<axel.polleres@deri.org> 
> wrote:
>  > just to pick up the discussion on "option 6" in today's telecon which was
>  > mentioned in a rush in the end of the telecon...
>  >
>  > I didn't get clear how
>  >
>  > DESCRIBE ENDPOINT
>  > or
>  > SELFDESCRIBE
>  >
>  > are different from
>  >
>  > DESCRIBE <endpoint-URI>
>  >
>  > Can someone elaborate?
> 
> A service may not necessarily know it's own endpoint URI so the latter
> may not be possible. That's also why Steve raised the issue of
> relative URIs.

So that could be DESCRIBE <.>

then?

> On a slightly separate note, the "DESCRIBE <endpoint-URI>" form may be
> capable of referring to descriptions on other endpoints. May that's
> something we want to consider (or to exclude).

yeah, that makes it look appealing somehow.

Axel

> Regards,
> Paul
> 


-- 
Dr. Axel Polleres
Digital Enterprise Research Institute, National University of Ireland,
Galway
email: axel.polleres@deri.org  url: http://www.polleres.net/
Received on Tuesday, 30 June 2009 17:24:12 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:39 GMT