Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
...
Panel | |||||||
---|---|---|---|---|---|---|---|
|
Linked Open Data is one of the fundamental concepts of the Semantic Web. It consists of asking a server for the RDF relating to an individual. If the response includes object properties that link to other individuals, those individuals can be queried also. For more information on Linked Open Data, see Concept: Linked Data.
VIVO accepts standard requests for Linked Open Data and some non-standard ones. The contents of the response are in accordance with those suggested by the in their tutorial How to Publish Linked Data on the Web.
...
Code Block |
---|
@prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix vcard: <http://www.w3.org/2006/vcard/ns#> . @prefix obo: <http://purl.obolibrary.org/obo/> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix vitro: <http://vitro.mannlib.cornell.edu/ns/vitro/0.7#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix vivo: <http://vivoweb.org/ontology/core#> . <http://vivo.mydomain.edu/individual/n3639> a vivo:FacultyMember , foaf:Person , owl:Thing , foaf:Agent , obo:BFO_0000002 , obo:BFO_0000001 , obo:BFO_0000004 ; rdfs:label "Baker, Able "^^xsd:string ; obo:ARG_2000028 <http://vivo.mydomain.edu/individual/n3972> ; obo:RO_0000053 <http://vivo.mydomain.edu/individual/n475> , <http://vivo.mydomain.edu/individual/n7850> ; vitro:mostSpecificType vivo:FacultyMember ; vivo:freetextKeyword "Potrezebie, Chattanooga" ; vivo:hasCollaborator <http://vivo.mydomain.edu/individual/n7429> ; vivo:relatedBy <http://vivo.mydomain.edu/individual/n3401> , <http://vivo.mydomain.edu/individual/n5855> , <http://vivo.mydomain.edu/individual/n2421> ; vivo:researchOverview "Whatever strikes my fancy." ; vivo:scopusId "abaker" . <http://vivo.mydomain.edu/individual/n3972> a vcard:Kind , obo:BFO_0000031 , owl:Thing , obo:ARG_2000379 , obo:IAO_0000030 , obo:BFO_0000002 , obo:BFO_0000001 , vcard:Individual ; obo:ARG_2000029 <http://vivo.mydomain.edu/individual/n3639> . <http://vivo.mydomain.edu/individual/n475> a owl:Thing , obo:BFO_0000023 , vivo:InvestigatorRole , obo:BFO_0000002 , obo:BFO_0000017 , vivo:PrincipalInvestigatorRole , obo:BFO_0000020 , obo:BFO_0000001 , vivo:ResearcherRole ; obo:RO_0000052 <http://vivo.mydomain.edu/individual/n3639> . <http://vivo.mydomain.edu/individual/n7850> a owl:Thing , obo:BFO_0000023 , obo:BFO_0000017 , obo:BFO_0000002 , obo:BFO_0000020 , obo:BFO_0000001 , vivo:LeaderRole ; rdfs:label "Lead Guitarist"^^xsd:string ; obo:RO_0000052 <http://vivo.mydomain.edu/individual/n3639> . <http://vivo.mydomain.edu/individual/n7429> a foaf:Person , vivo:FacultyMember , foaf:Agent , owl:Thing , obo:BFO_0000002 , obo:BFO_0000001 , obo:BFO_0000004 ; rdfs:label "Dog, Charlie" . <http://vivo.mydomain.edu/individual/n3401> a owl:Thing , vivo:Relationship , obo:BFO_0000002 , obo:BFO_0000020 , obo:BFO_0000001 , vivo:Authorship ; vivo:relates <http://vivo.mydomain.edu/individual/n3639> . <http://vivo.mydomain.edu/individual/n5855> a vivo:FacultyPosition , owl:Thing , vivo:Relationship , obo:BFO_0000002 , obo:BFO_0000020 , obo:BFO_0000001 , vivo:Position ; rdfs:label "Functionary"^^xsd:string ; vivo:relates <http://vivo.mydomain.edu/individual/n3639> . <http://vivo.mydomain.edu/individual/n2421> a owl:Thing , vivo:Relationship , obo:BFO_0000002 , obo:BFO_0000020 , obo:BFO_0000001 , vivo:Grant ; rdfs:label "Cosmogenic Lassitude in Phlegmatic Axolotls" ; vivo:relates <http://vivo.mydomain.edu/individual/n3639> . obo:BFO_0000001 a owl:Class ; rdfs:label "Entity" . obo:BFO_0000002 a owl:Class ; rdfs:label "Continuant" . obo:BFO_0000004 a owl:Class ; rdfs:label "Independent Continuant"@en-US . vivo:FacultyMember a owl:Class ; rdfs:label "Faculty Member"@en-US . foaf:Person a owl:Class ; rdfs:label "Person"@en-US . foaf:Agent a owl:Class ; rdfs:label "Agent"@en-US . owl:Thing a owl:Class . <http://vivo.mydomain.edu/individual/n3639/n3639.n3> a foaf:Document ; rdfs:label "RDF description of Baker, Able - http://vivo.mydomain.edu/individual/n3639" ; <http://purl.org/dc/elements/1.1/date> "2014-03-10T11:08:39"^^xsd:dateTime ; <http://purl.org/dc/elements/1.1/publisher> <http://vivo.mydomain.edu> ; <http://purl.org/dc/elements/1.1/rights> <http://vivo.mydomain.edu/termsOfUse> . |
The RDF can be expressed graphically like this:
...
You would need to remove this triple in order for the more restrictive triple to take effect.
VIVO uses the same permissions model to restrict Linked Open Data that it uses to restrict displays or updates. So if you are logged in to VIVO as the root user, and you request Linked Open Data, no restrictions would be applied.
This is consistent with VIVO's authorization model.
An external application could take advantage of this fact to obtain full RDF about individuals. Since there is no authorization parameter on the Linked Open Data request, the client application would need to begin by logging in to VIVO as an administrator, and then retain the session cookie to submit with subsequent requests.
If you ask for Linked Open Data for a non-existent individual, regardless of the form you use, VIVO will return a response code of 404 not found
.
...