On 6/10/13 11:15 AM, Alessio Palmero Aprosio wrote:

 *


For example:
140132    Eukaryote    10
140132    Animal    10
140132    Fish    10
140132    Species    10

becomes:
<http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Eukaryote> . <http://airpedia.org/resource/140132_Eukaryote> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Animal> . <http://airpedia.org/resource/140132_Animal> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Fish> . <http://airpedia.org/resource/140132_Fish> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Species> . <http://airpedia.org/resource/140132_Species> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> owl:sameAs <http://dbpedia.org/resource/Big_skate> . <http://airpedia.org/resource/140132> owl:sameAs <http://ca.dbpedia.org/resource/Raja_binoculata> .

All you do is publish Turtle, and if you want it mega simple folks that grok CSV then simply don't use prefixes (which are too confusing). Thus, you would have:

<http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Eukaryote> . <http://airpedia.org/resource/140132_Eukaryote> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Animal> . <http://airpedia.org/resource/140132_Animal> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Fish> . <http://airpedia.org/resource/140132_Fish> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> <http://airpedia.org/vocab/01/#type> <http://dbpedia.org/ontology/Species> . <http://airpedia.org/resource/140132_Species> <http://airpedia.org/vocab/01/#confidence> "10"^^xsd:int . <http://airpedia.org/resource/140132> <http://www.w3.org/2002/07/owl#sameAs> <http://dbpedia.org/resource/Big_skate> . <http://airpedia.org/resource/140132> <http://www.w3.org/2002/07/owl#sameAs> <http://ca.dbpedia.org/resource/Raja_binoculata> .

Also, if you are going to use URIs like <http://airpedia.org/resource/140132> then I assume you will be using one of the Linked Data heuristics to disambiguate:

<http://airpedia.org/resource/140132> and the document that describes it i.e., you would use an HTTP 303 to redirect to <http://airpedia.org/page/140132>. Alternatively, you could return 200 OK for <http://airpedia.org/resource/140132> and then put <http://airpedia.org/page/140132> in the Content-Location: header in the HTTP response which also delivers the same disambiguation but without the 303 redirection which some implementers of hashless (or slash) based Linked Data URIs don't like.


--

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




Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to