W3C home > Mailing lists > Public > public-vocabs@w3.org > April 2014

Re: Socialnetworks of a person or organization

From: Adrian Giurca <giurca@tu-cottbus.de>
Date: Thu, 10 Apr 2014 16:37:12 +0200
Message-ID: <5346AC98.4030509@tu-cottbus.de>
To: Kingsley Idehen <kidehen@openlinksw.com>, public-vocabs@w3.org
Hello,
Sorry I did not scroll down until the bottom of the page and I did not 
look into the HTML source. I was not interested by the HTML 
representation of that resource but by its semantic representation.
So an application should look inside the HTML answer to get the semantic 
representation...
It was simpler to me to query with a specific accept header.
When the resource updates I guess the alternate representations are 
updated too.

All the best,
Adrian


On 4/10/2014 4:15 PM, Kingsley Idehen wrote:
> On 4/10/14 6:18 AM, Adrian Giurca wrote:
>>>
>>> Again, I urge you all to regard schema.org as an interface to Web 
>>> developers' minds and the data they control, not as a beautiful 
>>> all-purpose category system for the human race as a whole.
>> Thanks Martin !
>> This is exactly how should be. Many already process this data not 
>> only search engines.
>> Moreover,  would not be bad if http://dbpedia.org accepts headers 
>> such as application/json+schema or text/plain on all resources.
>> Then a request to the URL http://dbpedia.org/page/John_Lennon will 
>> offer what people looks for :)
>>
>> We only need the URI (in this case 
>> http://dbpedia.org/resource/John_Lennon ) which will identify both 
>> the resource and the "page". This can be achieved quite easy... 
>
> Adrian,
>
> Re., DBpedia when you deference an Entity Description Page Identifiers 
> (HTTP URLs) e.g., <http://dbpedia.org/page/John_Lennon> you have 
> hyperlinks in the page footer and <link/> relations in the <head/> of 
> the HTML that describe the page in question.
>
> At the HTTP Level you have also have similar descriptions via "Link:" 
> header relations:
>
> curl -I http://dbpedia.org/page/John_Lennon
> HTTP/1.1 200 OK
> Date: Thu, 10 Apr 2014 12:12:40 GMT
> Content-Type: text/html; charset=UTF-8
> Content-Length: 386981
> Connection: keep-alive
> Vary: Accept-Encoding
> Server: Virtuoso/07.10.3207 (Linux) x86_64-redhat-linux-gnu  VDB
> Accept-Ranges: bytes
> Expires: Thu, 17 Apr 2014 12:12:40 GMT
> Link: <http://dbpedia.org/data/John_Lennon.rdf>; rel="alternate"; 
> type="application/rdf+xml"; title="Structured Descriptor Document 
> (RDF/XML format)", <http://dbpedia.org/data/John_Lennon.n3>; 
> rel="alternate"; type="text/n3"; title="Structured Descriptor Document 
> (N3/Turtle format)", <http://dbpedia.org/data/John_Lennon.json>; 
> rel="alternate"; type="application/json"; title="Structured Descriptor 
> Document (RDF/JSON format)", 
> <http://dbpedia.org/data/John_Lennon.atom>; rel="alternate"; 
> type="application/atom+xml"; title="OData (Atom+Feed format)", 
> <http://dbpedia.org/sparql?default-graph-uri=http%3A%2F%2Fdbpedia.org&query=DESCRIBE+<http://dbpedia.org/resource/John_Lennon>&format=text%2Fcsv>; 
> rel="alternate"; type="text/csv"; title="Structured Descriptor 
> Document (CSV format)", 
> <http://dbpedia.org/data/John_Lennon.ntriples>; rel="alternate"; 
> type="text/plain"; title="Structured Descriptor Document (N-Triples 
> format)", 
> <http://dbpedia.org/sparql?default-graph-uri=http%3A%2F%2Fdbpedia.org&query=DESCRIBE+<http://dbpedia.org/resource/John_Lennon>&output=application%2Fmicrodata%2Bjson>; 
> rel="alternate"; type="application/microdata+json"; title="Structured 
> Descriptor Document (Microdata/JSON format)", 
> <http://dbpedia.org/sparql?default-graph-uri=http%3A%2F%2Fdbpedia.org&query=DESCRIBE+<http://dbpedia.org/resource/John_Lennon>&output=text%2Fhtml>; 
> rel="alternate"; type="text/html"; title="Structured Descriptor 
> Document (Microdata/HTML format)", 
> <http://dbpedia.org/sparql?default-graph-uri=http%3A%2F%2Fdbpedia.org&query=DESCRIBE+<http://dbpedia.org/resource/John_Lennon>&output=application%2Fld%2Bjson>; 
> rel="alternate"; type="application/ld+json"; title="Structured 
> Descriptor Document (JSON-LD format)", 
> <http://dbpedia.org/resource/John_Lennon>; 
> rel="http://xmlns.com/foaf/0.1/primaryTopic", 
> <http://dbpedia.org/resource/John_Lennon>; rev="describedby", 
> <http://mementoarchive.lanl.gov/dbpedia/timegate/http://dbpedia.org/page/John_Lennon>; 
> rel="timegate"
>
>
> Re., the DBpedia Entity Identifiers (HTTP URIs) you have:
>
> curl -I http://dbpedia.org/resource/John_Lennon
> HTTP/1.1 303 See Other
> Date: Thu, 10 Apr 2014 12:14:49 GMT
> Content-Type: text/html; charset=UTF-8
> Content-Length: 0
> Connection: keep-alive
> Server: Virtuoso/07.10.3207 (Linux) x86_64-redhat-linux-gnu  VDB
> Accept-Ranges: bytes
> Location: http://dbpedia.org/page/John_Lennon
>
> Basically, redirection to the page that describes the referent of the 
> DBpedia Entity Identifier.
>
> [1] http://bit.ly/1bD2eZs -- Identifier definition, from my glossary 
> of terms doc
> [2] http://bit.ly/1fqJ5yv -- Denotation
> [3] http://bit.ly/1kv6UdE -- Vapour Report that starts with entity 
> identifier <http://dbpedia.org/resource/John_Lennon> (illustrating how 
> the name and de-reference characteristics of Linked Data enable 
> looking-up the document that describes what 
> <http://dbpedia.org/resource/John_Lennon> refers to at: 
> <http://dbpedia.org/resource/John_Lennon> .
>
> Conclusion:
>
> The basis have been covered for a long time re., DBpedia. I don't see 
> what applying "application/json+schema" or "text/plain" on all 
> resources brings to the table, bar ambiguity and the resultant 
> out-of-band processing which is antithetical to the fundamental goals 
> of Linked Open Data.
>
Received on Thursday, 10 April 2014 14:38:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:39 UTC