W3C home > Mailing lists > Public > www-tag@w3.org > June 2011

Re: Comments solicited: "Providing and discovering definitions of URIs"

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Mon, 27 Jun 2011 12:55:21 +0100
Message-ID: <4E086FA9.2030308@openlinksw.com>
To: www-tag@w3.org
On 6/27/11 11:35 AM, Leo Sauermann wrote:
> Hi Jonathan,
> (cc Cygri because ... you know... old times)
>
> I and Cygri were editors of:
> http://www.w3.org/TR/cooluris/
>
> The documents overlap, you can reference the cooluris TR for many of 
> the # -vs 303 aspects.
> In fact, you should, because we were in contact with TAG and others 
> back in 2007/2008 when
> we edited the document, and it contains most of the stuff related to 
> httpRange-14
>
>
>
> What misses in tr/cooluris is the predicate connecting a document to 
> its uri
>
> The trick is to have a triple that connects a conceptual thing to a 
> document,
> what you have in point 3.2 in the issue57:
> http://www.w3.org/2001/tag/awwsw/issue57/20110625/#cite-source
>
> Takin the EQ018 example, the trick is to encode the link from #EQ018 
> to the document and vice versa.
> I have no definitive answer, but I have the gut feeling that it needs 
> to be defined on the level of RDFS,
> because rdfs:isDefinedBy is semantically close.
>
> foaf:primaryTopic and foaf:primaryTopicOf are also close.

I agree with the above bar chosen predicate. The predicate to use is: 
wdrs:describedby [1][2]. A URI that Names an Observation Subject also 
needs to be in a relation with a URI that Identifies the Location of the 
Representation of the URIs referent. In much simpler terms: A Object has 
Identity distinct from its Representation. Thus, an Object should be 
endowed with an Identifier (Name) that resolves to the Address of its 
Representation. This Representation takes the from of an EAV/SPO graph 
pictorial where Attribute=Value pairs coalesce around the Observation or 
Description Subject.

Links:

1. http://lists.w3.org/Archives/Public/public-powderwg/2010Nov/0005.html 
-- Phil Archer's fix errata re. wdrs:describeby
2. http://www.mail-archive.com/public-lod@w3.org/msg06723.html -- old 
post I made about this matter
3. http://dbpedia.org/resource/Linked_Data -- Object Name
4. http://dbpedia.org/page/Linked_Data -- an HTML Resource that carries 
(bears) the EAV/SPO graph pictorial that describes #1
5. http://dbpedia.org/data/Linked_Data.nt -- an N3 Resource that does 
same as #2
6. http://dbpedia.org/data/Linked_Data.ntriples -- an N-Triples resource 
that does same as #2
7. 
http://linkeddata.informatik.hu-berlin.de/uridbg/index.php?url=http%3A%2F%2Fdbpedia.org%2Fresource%2FLinked_Data&useragentheader=&acceptheader= 
-- URI Debugger that enables one to look at the data representations and 
critical relations that facilitate "whole data representation" + 
metadata for enabling rich data sources for data centric machine 
understanding and FYN etc..



Kingsley
>
>
>
> so to sum up:
> * try to quote the TR/Cooluris/ as much as you can because it was very 
> heavily peer reviewed by TAG and IvanHerman and others.
> * suggest something for the thing-doc relation, my 2c are above.
>
>
> thats it from me, not more I can contribute.
>
> best
> Leo
>
> It was Jonathan Rees who said at the right time 25.06.2011 18:12 the 
> following words:
>> Comments solicited: "Providing and discovering definitions of URIs"
>>
>> (message being sent to www-tag, bcc: public-lod and semantic-web)
>>
>> As most of you know, the 9-year-old "httpRange-14" turf war is an
>> annoyance and embarrassment in efforts to develop RDF, linked data,
>> the Semantic Web, and Web architecture.
>>
>> As a step toward getting closure I've prepared a document (with
>> the help of the TAG and the AWWSW task group):
>>
>>    http://www.w3.org/2001/tag/awwsw/issue57/20110625/
>>
>> which attempts to record the variety of approaches that have been
>> offered.  I have attempted to record in a neutral way all the main
>> proposals that have been put forth and present them in a way that
>> permits them to be compared.  I'm sure I have failed to be completely
>> neutral, but if so I'm confident you will tell me.
>>
>> How to actually get closure is yet to be determined, but a first step
>> might be to get all the relevant information collected in this
>> document so that we all know what the issues and opportunities are.
>>
>> This document is for informational purposes only and its future is
>> not yet determined. I would have polished it a bit more but given
>> current debate on www-tag and public-lod I felt it was more important
>> to get it out than to tie up loose ends.
>>
>> Please comment on thewww-tag@w3.org  list. I will revise the document
>> based on comments received.
>>
>> If you wish to review the debate please see
>>    http://www.w3.org/wiki/HttpRange14Webography
>>
>> Best
>> Jonathan
>>
>> Abstract
>>
>> The specification governing Uniform Resource Identifiers (URIs)
>> [rfc3986] allows URIs to mean anything at all, and this unbounded
>> flexibility is exploited in a variety contexts, notably the Semantic
>> Web and Linked Data. To use a URI to mean something, an agent (a)
>> selects a URI, (b) provides a definition of the URI in a manner that
>> permits discovery by agents who encounter the URI, and (c) uses the
>> URI. Subsequently other agents may not only understand the URI (by
>> discovering and consulting the definition) but may also use the URI
>> themselves.
>>
>> A few widely known methods are in use to help agents provide and
>> discover URI definitions, including RDF fragment identifier resolution
>> and the HTTP 303 redirect. Difficulties in using these methods have
>> led to a search for new methods that are easier to deploy, and perform
>> better, than the established ones. However, some of the proposed
>> methods introduce new problems, such as incompatible changes to the
>> way metadata is written. This report brings together in one place
>> information on current and proposed practices, with analysis of
>> benefits and shortcomings of each.
>>
>> The purpose of this report is not to make recommendations but rather
>> to initiate a discussion that might lead to consensus on the use of
>> current and/or new methods.
>>
>> (this is TAG ISSUE-57 / ACTION-579)
>>
>
> -- 
> Leo Sauermann, Dr.
> CEO and Founder
>
> mail:leo.sauermann@gnowsis.com
> mobile: +43 6991 gnowsis
>
> Where your things come together,
> Join:http://www.gnowsis.com/about/content/newsletter
> Follow:http://twitter.com/Refinder
> Like:http://www.facebook.com/Refinder
> Learn:http://www.gnowsis.com/about/blog
> Try:http://www.getrefinder.com/accounts/register/
> ____________________________________________________


-- 

Regards,

Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
Received on Monday, 27 June 2011 11:55:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:36 GMT