VIVO-256 migrate orcid to URI reference

This commit is contained in:
brianjlowe 2013-09-11 10:17:32 -04:00
parent 17b90964d0
commit 745a4a26e8
6 changed files with 27 additions and 21 deletions

View file

@ -0,0 +1,11 @@
PREFIX vivo: <http://vivoweb.org/ontology/core#>
PREFIX owl: <http://www.w3.org/2002/07/owl#Thing>
CONSTRUCT {
?s vivo:orcidId ?orcidURI .
?orcidURI a owl:Thing .
} WHERE {
?s vivo:orcidId ?orcidString
FILTER(isLiteral(?orcidString))
BIND(IRI(concat("http://orcid.org/", str(?orcidString))) AS ?orcidURI)
}

View file

@ -9,12 +9,6 @@ CONSTRUCT {
_:primaryTelephone a v:Voice .
_:primaryTelephone a v:Work .
_:primaryTelephone v:telephone ?primaryPhoneNumber .
_:name v:hasTelephone _:fax .
_:fax a v:Telephone .
_:fax a v:Fax.
_:fax v:telephone ?faxNumber .
_:name v:hasAddress _:address .
_:address v:streetAddress ?streetAddress .
} WHERE {
?s arg:ARG_2000028 ?vcard .
?s vivo:primaryPhoneNumber ?primaryPhoneNumber

View file

@ -8,8 +8,6 @@ CONSTRUCT {
_:fax a v:Telephone .
_:fax a v:Fax.
_:fax v:telephone ?faxNumber .
_:name v:hasAddress _:address .
_:address v:streetAddress ?streetAddress .
} WHERE {
?s arg:ARG_2000028 ?vcard .
?s vivo:faxNumber ?faxNumber

View file

@ -0,0 +1,9 @@
PREFIX vivo: <http://vivoweb.org/ontology/core#>
PREFIX owl: <http://www.w3.org/2002/07/owl#Thing>
CONSTRUCT {
?s vivo:orcidId ?orcidString .
} WHERE {
?s vivo:orcidId ?orcidString
FILTER(isLiteral(?orcidString))
}

View file

@ -1830,19 +1830,6 @@ use one freetextKeyword assertion for each keyword or phrase.</obo:IAO_0000112>
<!-- http://vivoweb.org/ontology/core#orcidId -->
<owl:DatatypeProperty rdf:about="http://vivoweb.org/ontology/core#orcidId">
<rdfs:label xml:lang="en">orcid id</rdfs:label>
<obo:IAO_0000112 rdf:datatype="http://www.w3.org/2001/XMLSchema#string">We can&apos;t yet assume that we will only have a single ORCID id for a person.
source: http://en.wikipedia.org/wiki/ORCID .
We wanted this property to be visible so that people would be aware that we intend to carry ORCID ids in VIVO for cross-reference. I don&apos;t believe any ORCID ids have been minted yet, but it&apos;s hard to imagine they would need to be private since the goal of having them is to disambiguate author references internationally. However, this and the researcherId and scopusId (also with domain foaf:Person) can stay as visible to self-editors for now as they will probably be used mostly in data ingest. It might be nice in the future to let people make their own decision about whether these are visible.</obo:IAO_0000112>
<rdfs:subPropertyOf rdf:resource="http://vivoweb.org/ontology/core#identifier"/>
</owl:DatatypeProperty>
<!-- http://vivoweb.org/ontology/core#outreachOverview -->

View file

@ -2069,6 +2069,13 @@ there is a measurement process p that has specified output m, a measurement datu
</owl:ObjectProperty>
<!-- http://vivoweb.org/ontology/core#orcidId -->
<owl:ObjectProperty rdf:about="http://vivoweb.org/ontology/core#orcidId">
<rdfs:label xml:lang="en">orcid id</rdfs:label>
<obo:IAO_0000112 rdf:datatype="http://www.w3.org/2001/XMLSchema#string">This is now an object property where the object value is a resource of the form &lt;http://orcid.org/NNNN-NNNN-NNNN-NNNN&gt;. This is to support connecting VIVO and ORCID in the linked data web. Note: a person can have multiple ORCID iDs.</obo:IAO_0000112>
</owl:ObjectProperty>
<!-- Generated by the OWL API (version 3.3.1957) http://owlapi.sourceforge.net -->