W3C home > Mailing lists > Public > public-webid@w3.org > October 2013

Re: messed up sentence in Webid-TLS spec

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Mon, 28 Oct 2013 08:41:14 -0400
Message-ID: <526E5B6A.2080107@openlinksw.com>
To: public-webid@w3.org
On 10/28/13 7:50 AM, Roman Evstifeev wrote:
> At first i thought it was some copy-paste error os the like. But now i got this.
> I still see sentence as not-so-clear:
>
> For WebIDs .., the URI ...
>
> Here "the URI" does seem like it is "THE URI" that was mentined
> earlier, but i can hardly guess how it is related to the context
> before comma.
> This is not because "WebID is URI" link is not clear to the reader (to
> me at least), this is because the wording used.

Clarity is the challenge. It has been the challenge since forever.

A URL is a kind of HTTP URI that's used to denote ("refer to") HTTP 
accessible Documents.
A WebID is a kind of HTTP URI that used to denote ("refer to") Agents.

Using Linked Data principles, you can construct WebIDs that resolve to 
HTTP accessible Profile Documents.

Links:

[1] 
https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/img/WebID-overview.png -- 
illustrating application of Linked Data principles to a WebID (the blue 
rectangle outlines a Profile Document URL while the red rectangle 
outlines a WebID; in both cases, we are working with different kinds of 
HTTP URIs) .

[2] http://bit.ly/15tk1Au -- illustrating Linked Data URIs and the 
indirection they facilitate re. Name->Address mapping .

Kingsley
>
> On Sun, Oct 27, 2013 at 8:40 PM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>> On 10/27/13 8:55 AM, Roman Evstifeev wrote:
>>> Ok, i think i got it, but this was really hard. Wording may be better,
>>> like:
>>> <<If WebID contains fragment identifier (e.g. #me), the Profile
>>> Document itself is denoted by the same url without fragment
>>> identifier>>
>>>
>>> On Sun, Oct 27, 2013 at 4:47 PM, Roman Evstifeev
>>> <someuniquename@gmail.com> wrote:
>>>> https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/tls-respec.html
>>>> Section 1.2, Terminology:
>>>> Paragraph 1, WebID:
>>>> <<For WebIDs with fragment identifiers (e.g. #me), the URI without the
>>>> fragment denotes the Profile Document.>>
>>>> This sentence says what?
>>>
>> Roman
>>
>> The basics:
>>
>> 1. HTTP URIs denote things (entities)  -- Web Documents and anything else
>> 2. HTTP URLs (a kind of URI) denote HTTP accessible Documents, specifically
>> 3. HTTP URIs that denote an Agent (a kind or entity/thing) are WebIDs .
>>
>> All we have to do is find ways to make this clear in our material.
>>
>> --
>>
>> Regards,
>>
>> 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
>>
>>
>>
>>
>>
>


-- 

Regards,

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 Monday, 28 October 2013 12:41:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:05:52 UTC