Re: Improviong the ORCID RDF

FYI: Minutes from the ORCID RDF telcon with Tom Demeranville (ORCID)
and Phil Archer (W3C):

https://gist.github.com/stain/abaf89cf40df2823dde1



On 23 November 2015 at 16:16, Stian Soiland-Reyes
<soiland-reyes@cs.manchester.ac.uk> wrote:
> Hi Phil,
>
>
> I saw you wrote up our earlier ORCID RDF discussion on
>
> http://www.w3.org/2015/03/orcid-semantics
>
> Thanks!
>
>
> I generally agree with the improvements suggested, and apologize for
> my quick "trick" in using the trailing /.
>
>
> I would however not add #person - as it has been agreed since 2013
> that an URI like http://orcid.org/0000-0003-0782-2704 identifies the
> person, not just a person with the reserarcher role, or the
> researcher's academic profile or anything like that.
>
> Adding a second #-based identifier for the person in RDF would be
> quite confusing as it means RDF then only gets a second-rate
> identifier for the person, which doesn't match the identifier for the
> person used in any other systems.
>
>
> Getting rid of the / I fully agree on, however. The problem here is
> with FOAF which has forced a particular solution to HTTP Range 14 by
> having a distinct feature of a foaf:PersonalProfileDocument which is
> an information resource, thus it shouldn't have a # URI.
>
> (Of course we are not required to say anything about the
> PersonalProfileDocument - but it was a nice way to give the PROV info
> about when the ORCID profile was last updated)
>
>
> Currently the ORCID URI content-negotiates and redirect to
> https://pub.orcid.org/experimental_rdf_v1/0000-0003-0782-2704, so this
> URI can safely be used as <> for the foaf:PersonalProfileDocument
> (which would then still be correct when/if "experimental" goes)
>
>
> For the foaf:OnlineAccount I agree that #account would work best. The
> URI for the account is not really that important as long as it is
> different from the person, and if it goes to a page the user can read,
> that is great.
>
>
> I'm arranging a Skype call (or equivalent) with Tom Demeranville
> (CCed) from ORCID to discuss this next week, perhaps if Phil and
> others who care about ORCID's RDF have availability you could join for
> a quick chat?
>
> If you are interested, please mark your availability in the doodle poll at:
>
> http://doodle.com/poll/shmnn9nc3g5i84zr
>
> Thanks!
>
> On 10 March 2015 at 17:40, Phil Archer <phil@philarcher.org> wrote:
>> Thanks very much everyone and thanks especially to Stian for being so
>> responsive.
>>
>> I'm trying to write some recommendations for ORCID and this thread has been
>> extremely useful.
>>
>> I don't want to have the whole discussion here - and I would have to drown
>> several small furry animals if this turned into yet another HR14 discussion
>> - but this is, perhaps, the heart of it:
>>
>> “ORCID provides a persistent digital identifier that distinguishes you from
>> every other researcher and, through integration in key research workflows
>> such as manuscript and grant submission, supports automated linkages between
>> you and your professional activities ensuring that your work is recognized”
>>
>> Thus ORCIDs are defined in terms of what they *do*, not what they
>> *represent*.
>>
>> Add that to what Stian has told us in terms of what will and won't wash at
>> ORCID HQ, plus the fact that the IDs are already widely deployed (most
>> notably in CrossRef) and it's clear that the options for improving the
>> semantics are constrained by practicality - which might go against semantic
>> purity.
>>
>> Hmmm... a two pipe problem (but not three I don't think).
>>
>> Thanks again,
>>
>> Phil.
>>
>>
>>
>>
>> On 10/03/2015 14:36, Stian Soiland-Reyes wrote:
>>>
>>> Suggested line to fix:
>>>
>>>
>>> https://github.com/ORCID/ORCID-Source/blob/master/orcid-pub-web/src/main/java/org/orcid/api/t1/server/T1OrcidApiServiceImplBase.java#L198
>>>
>>> On 10 March 2015 at 12:38, Michal Politowski <m.politowski@icm.edu.pl>
>>> wrote:
>>>>
>>>> Yeah, I know. But as long as it is not 303 it still means in the light
>>>> of httpRange-14 that the person is also an information resource - with at
>>>> least
>>>> an HTML and a Turtle representation.
>>>> Which a person may object to.
>>>>
>>>> On Tue, 10 Mar 2015 11:33:54 +0000, Stian Soiland-Reyes wrote:
>>>>>
>>>>> You would need to content-negotiate:
>>>>>
>>>>> * Connected to orcid.org (174.143.185.160) port 80 (#0)
>>>>>>
>>>>>> GET /0000-0003-0782-2704 HTTP/1.1
>>>>>> Host: orcid.org
>>>>>> Accept: text/turtle
>>>>>>
>>>>> < HTTP/1.1 307 Temporary Redirect
>>>>> < Content-Type: text/turtle; qs=3;charset=UTF-8
>>>>> < Date: Tue, 10 Mar 2015 11:30:54 GMT
>>>>> < Location:
>>>>> https://pub.orcid.org/experimental_rdf_v1/0000-0003-0782-2704
>>>>>
>>>>>> GET /experimental_rdf_v1/0000-0003-0782-2704 HTTP/1.1
>>>>>> User-Agent: curl/7.37.1
>>>>>> Host: pub.orcid.org
>>>>>> Accept: text/turtle
>>>>>>
>>>>> < HTTP/1.1 200 OK
>>>>> < Content-Type: text/turtle; qs=3;charset=UTF-8
>>>>> < Content-Length: 2314
>>>>> <
>>>>> @prefix gn:      <http://www.geonames.org/ontology#> .
>>>>> @prefix rdfs:    <http://www.w3.org/2000/01/rdf-schema#> .
>>>>> @prefix prov:    <http://www.w3.org/ns/prov#> .
>>>>> @prefix foaf:    <http://xmlns.com/foaf/0.1/> .
>>>>> @prefix pav:     <http://purl.org/pav/> .
>>>>> @prefix owl:     <http://www.w3.org/2002/07/owl#> .
>>>>> @prefix xsd:     <http://www.w3.org/2001/XMLSchema#> .
>>>>> @prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
>>>>>
>>>>> <http://orcid.org/0000-0003-0782-2704/>
>>>>>        a       foaf:PersonalProfileDocument , foaf:OnlineAccount ;
>>>>> ...
>>>>>
>>>>>
>>>>> Perhaps better would be to use
>>>>> <https://pub.orcid.org/experimental_rdf_v1/0000-0003-0782-2704> as the
>>>>> name of the PersonalProfileDocument.
>>>>>
>>>>> I could not get them to do 303 instead of 307 and do the Vary header
>>>>> (this is done by some web-proxy frontend) - but perhaps you could
>>>>> request that.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 9 March 2015 at 09:25, Michal Politowski <m.politowski@icm.edu.pl>
>>>>> wrote:
>>>>>>
>>>>>> On Fri,  6 Mar 2015 16:00:45 -0500, Simon Spero wrote:
>>>>>>>
>>>>>>> http://www.range-14.com/ .
>>>>>>>
>>>>>>> Err, I mean;
>>>>>>> http://www.w3.org/2001/tag/group/track/issues/14
>>>>>>
>>>>>>
>>>>>> If we want to visit httpRange-14
>>>>>> then the fact that ORCID is claiming that:
>>>>>>
>>>>>>          <http://orcid.org/0000-0003-0782-2704> a foaf:Person .
>>>>>>
>>>>>> while their webserver is saying that
>>>>>> http://orcid.org/0000-0003-0782-2704
>>>>>> has a HTML representation:
>>>>>>
>>>>>>          HTTP/1.1 200 OK
>>>>>>          Content-Type: text/html;charset=UTF-8
>>>>>>
>>>>>> seems rather confusing.
>>>>
>>>>
>>>> --
>>>> Michał Politowski
>>>>
>>>
>>>
>>>
>>
>> --
>>
>> Phil Archer
>> http://philarcher.org/
>> +44 (0)7887 767755
>> @philarcher1
>
>
>
> --
> Stian Soiland-Reyes, eScience Lab
> School of Computer Science
> The University of Manchester
> http://soiland-reyes.com/stian/work/    http://orcid.org/0000-0001-9842-9718



-- 
Stian Soiland-Reyes, eScience Lab
School of Computer Science
The University of Manchester
http://soiland-reyes.com/stian/work/    http://orcid.org/0000-0001-9842-9718

Received on Wednesday, 2 December 2015 12:01:50 UTC