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

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

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Tue, 10 Jan 2012 07:12:46 -0500
Message-ID: <4F0C2B3E.4020702@openlinksw.com>
To: public-xg-webid@w3.org
On 1/10/12 5:35 AM, Henry Story wrote:
> 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 
> <https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/index-respec.html#bib-SWBP-VOCAB-PUB>] 
> can be employed to aid in publication and discovery of multiple 
> distinct serialisations of the same graph at the same URL.
>     Jon Phipps; Diego Berrueta. Best Practice Recipes for Publishing
>     RDF Vocabularies.
>     <http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828> 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.

The implications for slash URIs is hidden. It should be more visible so 
that publishers understand upfront the implications of different HTTP 
URIs style when using the HTTP scheme.

>> 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.

If you say so, but then please make the spec audience profile clear. For 
instance, this isn't for consumer/commodity Web users. It's an 
implementation spec for developers of:

1. certificate generators
2. verifiers.

>> 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.

As long as we get there, a graph has many paths even if they are all 
directed :-)

> Henry
> Social Web Architect
> http://bblfish.net/



Kingsley Idehen	
Founder&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Tuesday, 10 January 2012 12:15:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:39:54 UTC