Support for Linked Data Notifications about orcid-source HOT 4 CLOSED

Thanks! See it in use: https://twitter.com/csarven/status/905422007436795904

from orcid-source.

I assume you mean the content-negotatiated RDF output from ORCID, e.g. from

curl -L -H "Accept: text/turtle" http://orcid.org/0000-0001-9842-9718

which lists the "Websites" URLs depending on their description:

<http://orcid.org/0000-0001-9842-9718>
        a                  foaf:Person , prov:Person ;
        rdfs:label         "Stian Soiland-Reyes" ;
        rdfs:seeAlso       <http://soiland-reyes.com/stian/#me> ;
        prov:alternateOf   <http://soiland-reyes.com/stian/#me> ;
        foaf:homepage      <http://soiland-reyes.com/stian/work/> ;
        foaf:page          <http://www.manchester.ac.uk/research/soiland-reyes/publications> , <https://twitter.com/soilandreyes> , <http://scholar.google.com/citations?user=OeBjonkAAAAJ> , <http://academic.research.microsoft.com/Author/5200832> , <http://uk.linkedin.com/in/stain/> , <https://github.com/stain> , <http://www.slideshare.net/soilandreyes/> .

(Perhaps the description should also be shown in literal somehow.. as an oa:Annotaton?)

The magic for choosing alternate properties than foaf:page is here
in RDFMessageBodyWriter.describeResearcherUrls()

I'm afraid these properties are not described anywhere else.. but adding handling of new "magic" URL description here like "LDP Inbox" and "PIM" would achieve what you want.

However using that (if we document it properly) would also mean showing the LDP Inbox and PIM Space at the normal browser HTML representation, but the LDP/PIM might not have a reasonable HTML representation themselves. So perhaps non-human "Websites" should be hidden from its listing of Websites? (This would include the FOAF I guess)

from orcid-source.

This is a two step process: The simplest thing to start off would be to allow profile owners to add the "Inbox" relation. That way people can use an Inbox of their choice. If ORCID wants to introduce/host Inboxes for profiles, that feature can be implemented separately.

from orcid-source.

I think the inbox (and storage) URLs should be human-visible by default. We can't foresee how inbox representations will be - well, at least available in JSON-LD. We let profile owners and inbox owners decide for themselves, i.e., profile owners choose to link to their Inbox which may or may not have a human-friendly view.

from orcid-source.