W3C home > Mailing lists > Public > public-ldp@w3.org > September 2014

Re: LDP Patch Format FPWD published

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Mon, 22 Sep 2014 13:31:25 -0400
Message-ID: <54205CED.6000706@openlinksw.com>
To: public-ldp@w3.org
On 9/22/14 12:32 PM, Alexandre Bertails wrote:
> Hi Kingsley,
>
>> On 9/18/14 6:30 PM, Arnaud Le Hors wrote:
>> > Hi all,
>> >
>> > I'm pleased to announce that the LDP WG just published the Linked Data
>> > Patch Format First Public Working Draft:
>> > _http://www.w3.org/TR/2014/WD-ldpatch-20140918/_
>> >
>> > I want to stress that the WG is seeking feedback from the community at
>> > large on the direction being proposed.
>> >
>> > Getting this draft out has not been easy. There are different possible
>> > approaches and none of them is fully satisfying. After a lot of
>> > discussions we settled on the current proposal which is very much a
>> > compromise. So, please, have a look and let us know what you think!
>> >
>> > Thank you.
>> > --
>> > Arnaud  Le Hors - Senior Technical Staff Member, Open Web Standards -
>> > IBM Software Group
>>
>> A little bug. The opening example has:
>>
>> <http://example.org/timbl#> as a URI that idenfies TimBL. That's in
>> accurate. If you want to stick with <dns:example.org> then it would be
>> <http://example.org/timbl#i> .
>
> I am not sure to understand how this is a bug. Because of the fix you
> proposed, I assumed you meant that empty fragments were not allowed in
> RDF, but I couldn't find any specification against that.
>
> Actually, [1] suggests that this is a valid approach.
>
> And it looks like Facebook agrees:
>
> [[
> $ GET -H 'Accept: text/turtle' http://graph.facebook.com/627001044
> ...
> </627001044#>
>     user:id "627001044" ;
>     user:first_name "Alexandre" ;
>     user:gender "male" ;
>     user:last_name "Bertails" ;
>     user:locale "fr_FR" ;
>     user:name "Alexandre Bertails" ;
>     user:username "bertails" .
> ]]
>
> And libraries like Sesame or Jena seem ok too.

Firstly, I am suggesting that if TimBL is to be used as an example, then 
his actual WebID should be used. That bug boils to making up a non 
existent URI for TimBL when he has a functional URI that actually 
demonstrates Linked Data very well.

In regards to:

[[
<http://example.org/timbl#> as a URI that idenfies TimBL. That's in
accurate. If you want to stick with <dns:example.org> then it would be
<http://example.org/timbl#i> .
]]


There are other problems, in regards to the profile data returned by 
Facebook which simply doesn't make them an acceptable example in this 
context. I don't have a preferred WebID style (#, #i, slash etc.., the 
are components of what should be an opaque identifier) , I just want 
them to conform to Linked Data principles [1][2]. I want the examples in 
these specs to make sense and not confuse readers.


Links:

[1] http://bit.ly/NzfyF0 -- my 2011 post about Facebook URIs (which I've 
just noticed has G+ markup issues that I'll fix later)

[2] http://bit.ly/1udMVnD -- Vapor Report on my Facebook WebID (note: 
there is no relation that associates 
<http://graph.facebook.com/kidehen#> with 
<http://graph.facebook.com/kidehen> i.e., we have an implicit rather 
that explicit association, which is no good in regards to Linked Data 
clarity

[3] 3. 
http://bit.ly/timb-personal-uri-vapor-linked-data-compliance-report -- 
The same thing using TimBL's actual WebID and you have the missing 
clarity re. how his WebID and WebID-Profile document are associated .


Kingsley
>
>>
>> Please fix, otherwise the example won't achieve its goal. Ideally, you
>> should use his actual URI <http://www.w3.org/People/Berners-Lee/card#i>
>> which has the added effect of being a live demonstration of what the
>> example is trying to convey.
>
> As for using Tim's WebID directly, we (the editors) thought about it
> and didn't like the idea, because 1. we simply do not own that
> document (obviously), and 2. the example data does not exist there.
>
> Alexandre
>
> [1] https://en.wikipedia.org/wiki/HTTPRange-14#Use_of_.23
>
>>
>> Correction suggestion:
>>
>> [[
>> The following RDF Graph will be used as an example through this
>> specification. It describes the relation between a person named Tim
>> Berners-Lee (denoted by <http://example.org/timbl#>) and two events he
>> attended.
>> ]]
>>
>> becomes
>>
>> [[
>> The following RDF Graph will be used as an example through this
>> specification. It describes the relation between a person named Tim
>> Berners-Lee (denoted by <http://www.w3.org/People/Berners-Lee/card#i>)
>> and two events he attended.
>> ]]
>>
>> or even
>>
>> [[
>> The following RDF Graph will be used as an example through this
>> specification. It describes the relation between a person named Tim
>> Berners-Lee (*identified* by
>> <http://www.w3.org/People/Berners-Lee/card#i>) and two events he 
>> attended.
>> ]]
>>
>> Links:
>>
>> 1.
>> http://bit.ly/fragment-identifiers-as-global-identifier-operators-for-the-web 
>>
>> 2. http://dig.csail.mit.edu/breadcrumbs/node/71
>> 3. http://bit.ly/timb-personal-uri-vapor-linked-data-compliance-report
>>
>> -- 
>> Regards,
>>
>> Kingsley Idehen
>> Founder & CEO
>> OpenLink Software
>> Company Web: http://www.openlinksw.com
>> Personal Weblog 1: http://kidehen.blogspot.com
>> Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
>> Twitter Profile: https://twitter.com/kidehen
>> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
>> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>> Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
>
>


-- 
Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this



Received on Monday, 22 September 2014 17:31:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:16:38 UTC