Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Harry Halpin
On Thu, Jan 20, 2011 at 11:15 AM, Nathan wrote: > Alan Ruttenberg wrote: >> >> On Wed, Jan 19, 2011 at 4:45 PM, Nathan wrote: >>> >>> David Wood wrote: On Jan 19, 2011, at 10:59, Nathan wrote: > ps: as an illustration of how engrained URI normalization is, I've > capitalize

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Alan Ruttenberg
On Thu, Jan 20, 2011 at 5:15 AM, Nathan wrote: > As far as I can see, that's only for a URI reference used within a > namespace, and does not govern usage or normalization when you join the URI > reference up with the local name to make the full URI. > > Out of interest, where is that process def

Re: Standardizing linked data - was Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Nathan
Nathan wrote: Dave Reynolds wrote: All this presupposes some work to formalize and specify linked data. Is there anything like that planned? In some ways Linked Data is an engineering experiment and benefits from that freedom to experiment. On the other hand interoperability eventually needs

Standardizing linked data - was Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Nathan
Dave Reynolds wrote: Okay, I agree, and I'm really not looking to create a lot of work here, the general gist of what I'm hoping for is along the lines of: RDF Publishers MUST perform Case Normalization and Percent-Encoding Normalization on all URIs prior to publishing. When using relative URIs

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Dave Reynolds
Hi Nathan, I largely agree but have a few quibbles :) On 20/01/2011 2:29 PM, Nathan wrote: Dave Reynolds wrote: The URI spec (rfc3986[1]) does allow this usage. In particular Section 6 Normalization and Comparison says: """URI comparison is performed for some particular purpose. Protocols or

Re: How to declare in a web app's interface which kind of app/version/features and or interfaces or formats it exposes

2011-01-20 Thread Thomas Steiner
Hi Olivier, Do you know http://LinkedOpenServices.org/? This might be what you're looking for (assuming your website is your API, where website reads like Web app). Cheers, Tom Thank God not sent from a BlackBerry, but from my iPhone On 20.01.2011, at 18:37, Olivier Berger wrote: > Le jeudi 2

2nd CfP: USEWOD2011 - 1st International Workshop on Usage Analysis and the Web of Data

2011-01-20 Thread Knud Hinnerk Möller
Just a quick reminder that the deadline for USEWOD2011 is approaching fast! === Second Call for Papers === Workshop on: USAGE ANALYSIS AND THE WEB OF DATA (USEWOD2011) & USEWOD DATA CHALLENGE Workshop at WWW 2011 – Hyderabad, India, 28 or 2

Re: How to declare in a web app's interface which kind of app/version/features and or interfaces or formats it exposes

2011-01-20 Thread Olivier Berger
Le jeudi 20 janvier 2011 à 15:50 +, Michael Hausenblas a écrit : > Olivier, > > > I'm considering the different options that could help embed (with > > slightest modifications possible) in the in HTML interface of a Web app, > > a description of which app it is and/or which interfaces it expos

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Nathan
Martin Hepp wrote: On 20.01.2011, at 15:40, Nathan wrote: David Booth wrote: On Thu, 2011-01-20 at 13:08 +, Dave Reynolds wrote: [ . . . ] To make sure that dereference returns what I expect, independent of aliasing, then I should publish data with explicit base URIs (or just absolute URI

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Martin Hepp
Hi: On 20.01.2011, at 15:40, Nathan wrote: David Booth wrote: On Thu, 2011-01-20 at 13:08 +, Dave Reynolds wrote: [ . . . ] To make sure that dereference returns what I expect, independent of aliasing, then I should publish data with explicit base URIs (or just absolute URIs). Publishi

Re: How to declare in a web app's interface which kind of app/version/features and or interfaces or formats it exposes

2011-01-20 Thread Michael Hausenblas
Olivier, > I'm considering the different options that could help embed (with > slightest modifications possible) in the in HTML interface of a Web app, > a description of which app it is and/or which interfaces it exposes, so > that this would be "discoverable" and lead to exploitation of such da

How to declare in a web app's interface which kind of app/version/features and or interfaces or formats it exposes

2011-01-20 Thread Olivier Berger
Hi. I'm considering the different options that could help embed (with slightest modifications possible) in the in HTML interface of a Web app, a description of which app it is and/or which interfaces it exposes, so that this would be "discoverable" and lead to exploitation of such data by SemWeb a

Re: Nice domain name for the take

2011-01-20 Thread Rinke Hoekstra
Hi all, Thanks for the responses! This call for applicants is now closed ;) Cheers, Rinke PS Did I say geni.com? Surely I meant gandi.net ... On 20 jan 2011, at 13:13, Rinke Hoekstra wrote: > Hi all, > > Last year, Christophe Gueret and I registered the domain name > "linkeddatamarketplace

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread William Waites
* [2011-01-20 14:29:35 +] Nathan écrit: ] RDF Publishers MUST perform Case Normalization and Percent-Encoding ] Normalization on all URIs prior to publishing. When using relative URIs ] publishers SHOULD include a well defined base using a serialization ] specific mechanism. Publishers a

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Nathan
David Booth wrote: On Thu, 2011-01-20 at 13:08 +, Dave Reynolds wrote: [ . . . ] It seems to me that this is primarily a issue with publishing, and a little about being sensible about how you pass on links. If I'm going to put up some linked data I should mint normalized URIs; I should use t

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread David Booth
On Thu, 2011-01-20 at 13:08 +, Dave Reynolds wrote: [ . . . ] > It seems to me that this is primarily a issue with publishing, and a > little about being sensible about how you pass on links. If I'm going to > put up some linked data I should mint normalized URIs; I should use the > same spelli

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Nathan
Hi Dave, Generally I agree, will address a few specific points in line (just to address them) then summarize my intended goals at the end (being the substance of the mail). Dave Reynolds wrote: The URI spec (rfc3986[1]) does allow this usage. In particular Section 6 Normalization and Compari

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Dave Reynolds
On Wed, 2011-01-19 at 21:45 +, Nathan wrote: > David Wood wrote: > > On Jan 19, 2011, at 10:59, Nathan wrote: > >> ps: as an illustration of how engrained URI normalization is, I've > >> capitalized the domain names in the to: and cc: fields, I do hope the mail > >> still come through, and h

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Kingsley Idehen
On 1/19/11 11:27 PM, Alan Ruttenberg wrote: On Wed, Jan 19, 2011 at 11:11 AM, Kingsley Idehen mailto:kide...@openlinksw.com>> wrote: On 1/19/11 10:59 AM, Nathan wrote: htTp://lists.W3.org/Archives/Public/public-lod/2011Jan/ - Personally I'd hope that any statements made using th

Nice domain name for the take

2011-01-20 Thread Rinke Hoekstra
Hi all, Last year, Christophe Gueret and I registered the domain name "linkeddatamarketplace.com", thinking we might find the time to set up a market place for ... eh... linked data. The idea was to bring together publishers and users of data (along the lines of http://www.datamarketplace.com).

Re: URI Comparisons: RFC 2616 vs. RDF

2011-01-20 Thread Nathan
Alan Ruttenberg wrote: On Wed, Jan 19, 2011 at 4:45 PM, Nathan wrote: David Wood wrote: On Jan 19, 2011, at 10:59, Nathan wrote: ps: as an illustration of how engrained URI normalization is, I've capitalized the domain names in the to: and cc: fields, I do hope the mail still come through, a

Workshop: Why, Where and How?" of Linked Data

2011-01-20 Thread John Goodwin
Hi all, The DNF Expert Group is pleased to announce the publication of the agenda for the "Why, Where and How?" of Linked Data workshop being run in conjunction with UK Location and the Chartered Institute of IT. Registration is now open through this site at http://www.dnf.org/events/regis