W3C home > Mailing lists > Public > public-xg-webid@w3.org > January 2012

Re: FOAF SSL success, form windows RDFa (via linked data)

From: Henry Story <henry.story@bblfish.net>
Date: Tue, 10 Jan 2012 11:35:19 +0100
Cc: public-xg-webid@w3.org
Message-Id: <40F7C570-131F-4375-A247-98617565A5A7@bblfish.net>
To: Kingsley Idehen <kidehen@openlinksw.com>

On 10 Jan 2012, at 03:59, Kingsley Idehen wrote:

> 
> For the publisher:
> How do they publish using slash style of HTTP URI, for instance? 

That is explained in the the document we refer to 

HTTP Content Negotiation [SWBP-VOCAB-PUB] can be employed to aid in publication and discovery of multiple distinct serialisations of the same graph at the same URL.

[SWBP-VOCAB-PUB]
Jon Phipps; Diego Berrueta. Best Practice Recipes for Publishing RDF Vocabularies. 28 August 2008. W3C Note. URL:http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828

Ok, so perhaps we should bring this out more clearly in the text, as it is perhaps  a lot more hidden than I had realised.


> How do they publish using a # style of HTTP URI and not be exposed to the legacy libraries, frameworks etc.. that send fragments over the wire? 

That is not an issue. That is for the library implementors to fix. 

> How do they obtain and control HTTP URI based Names? 

I don't think that this is something the spec needs to address. There are many introductory books on how to do that, and many other specs to look that up.

> You are glossing over some serious pragmatic challenges!

You are exaggerating, clearly. But thanks for - unintentionally - making me realise that the reference to the Best Practices document was a bit hidden.

Henry

Social Web Architect
http://bblfish.net/
Received on Tuesday, 10 January 2012 10:35:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 10 January 2012 10:35:56 GMT