W3C home > Mailing lists > Public > www-tag@w3.org > March 2012

Re: Middle ground change proposal for httpRange-14 -- submission

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Tue, 27 Mar 2012 07:27:07 -0400
Message-ID: <4F71A40B.2060806@openlinksw.com>
To: David Booth <david@dbooth.org>
CC: www-tag@w3.org
On 3/26/12 2:37 PM, David Booth wrote:
> Hi Kingley,
>
> On Mon, 2012-03-26 at 09:01 -0400, Kingsley Idehen wrote:
> [ . . . ]
>> @prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#>  .
>> <http://example/toucan>  rdfs:isDefinedBy<http://example/toucan>  .
>>
>> Should be:
>>
>> @prefix wdrs:<http://www.w3.org/2007/05/powder-s#>  .
>> <http://example/toucan>  wdrs:describedby<http://example/toucan>  .
> To my mind, wdrs:describedby means something different, as I think it is
> important to be able to distinguish between a URI definition and other
> data that involves the target URI.  Here's how I explained it in the
> proposal:
> http://www.w3.org/wiki/UriDefinitionDiscoveryProtocol#3.2.2_Link_header
> [[
> Note that the "definedby" relation [which corresponds to
> rdfs:isDefinedBy] does not mean the same thing as the "describedby"
> relation defined in Powder[powder]. In particular, under this
> specification the following hypothetical HTTP response:
>
>    200 OK
>    Link:<http://example.com/other-uri-description>; rel="describedby"
>
> does *not* imply that a representation retrieved from
> http://example.com/other-uri-description is a URI definition for the
> target URI. The reason for this difference is that the URI owner may
> well wish to point clients to additional useful information involving
> the target URI, without implying that such information constitutes the
> URI owner's URI definition for the target URI. For example, it could be
> ancillary (but non-definitional) information about the identified
> resource, or it could be an alternate definition authored by a third
> party.
> ]]
>
>
David,

You are saying:
200 OK
Link: <http://example.com/uri-definition>; rel="definedby"

Is better than:
200 OK
Link: <http://example.com/other-uri-description>; rel="describedby"

And en route to utilization we have to deal with:

ISSUE 7: The "definedby" relation needs to be registered per 
RFC5988[rfc5988] as corresponding to rdfs:isDefinedBy[rdfs].

Putting the wdrs: namespace aside for a second, why is "definedby" a 
better predicate than "describedby" when the semantics in question boils 
down to indicating that a resource (a document) is a descriptor (bearer 
of description representation) for the referent of a hashless HTTP URI ?

A 'definition' is a specific kind of  'description'. Web resources don't 
typically describe anything, they tend to 'mention' many things, 
typically loose references to other resources (documents) via URIs. RDF 
adds the description dimension via descriptor resources. Thus, we need 
an appropriate relation to express the semantics of the descriptor 
document and descriptor subject relation. That isn't a definition in my 
eyes. That's a description.

Links:

1. 
http://www.differencebetween.com/difference-between-description-and-vs-definition/ 
.
2. http://goo.gl/DRvQM - work in progress post about Data, Resources, 
Identifiers etc.. (note the diagrams attached to the post).

-- 

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 Tuesday, 27 March 2012 11:27:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:43 UTC