brinxmat
Rurik Greenall
This isn't what the open web is about: Please don't register #ORCID, let it die because of membership support.orcid.org/knowledgebase/…
acka47
Adrian Pohl
@brinxmat Will you also need a membership for using the Query API? dev.orcid.org/docs/query-api #ORCID @Orcid_ORg
@brinxmat Will you also need a membership for using the Query API? dev.orcid.org/docs/query-api #ORCID @Orcid_ORg
acka47
Adrian Pohl
@brinxmat Only tried examples, e.g. curl -H 'Accept: application/orcid+xml' 'devsandbox.orcid.org/search/orcid-b…' Hope it'll work for the rest soon. #ORCID
@brinxmat Only tried examples, e.g. curl -H 'Accept: application/orcid+xml' 'devsandbox.orcid.org/search/orcid-b…' Hope it'll work for the rest soon. #ORCID
gbilder
Geoffrey Bilder
@brinxmat @acka47 Try: curl -H 'Accept: application/orcid+xml' 'pub.orcid.org/search/orcid-b…'
@brinxmat @acka47 Try: curl -H 'Accept: application/orcid+xml' 'pub.orcid.org/search/orcid-b…'
brinxmat
Rurik Greenall
@gbilder @acka47 pub.orcid.org isn't a uri I have seen before ;-) QAm getting expected responses; where can I see licensing details
@gbilder @acka47 pub.orcid.org isn't a uri I have seen before ;-) QAm getting expected responses; where can I see licensing details
acka47
Adrian Pohl
@brinxmat @gbilder Didn't know pub.orcid.org as well. Documentatio could be better...
@brinxmat @gbilder Didn't know pub.orcid.org as well. Documentatio could be better...
brinxmat
Rurik Greenall
@acka47 @gbilder If the license terms are agreeable, we could wrap this as RDF and make it usable :)
@acka47 @gbilder If the license terms are agreeable, we could wrap this as RDF and make it usable :)
acka47
Adrian Pohl
@brinxmat @gbilder "Future versions of the ORCID API may support additional formats, for example application/rdf+xml." de.slideshare.net/ORCIDSlides/or…
@brinxmat @gbilder "Future versions of the ORCID API may support additional formats, for example application/rdf+xml." de.slideshare.net/ORCIDSlides/or…
gbilder
Geoffrey Bilder
@acka47 @brinxmat Yes, I would’t waste time creating RDF representations. ORCID will be doing that soon anyway.
@acka47 @brinxmat Yes, I would’t waste time creating RDF representations. ORCID will be doing that soon anyway.
gbilder
Geoffrey Bilder
@brinxmat @acka47 Possibly. But, surprisingly, RDF is least popular representation asked for in DOI content negotiation. Go figure.
@brinxmat @acka47 Possibly. But, surprisingly, RDF is least popular representation asked for in DOI content negotiation. Go figure.
ostephens
ostephens
@gbilder @acka47 @brinxmat but is the most popular the first one that was available?
@gbilder @acka47 @brinxmat but is the most popular the first one that was available?
gbilder
Geoffrey Bilder
@ostephens @acka47 @brinxmat RDF was available at launch of CN. The *last* we added- the CSL representations- are the most popular.
@ostephens @acka47 @brinxmat RDF was available at launch of CN. The *last* we added- the CSL representations- are the most popular.
brinxmat
Rurik Greenall
@gbilder @ostephens @acka47 no surprise there, I'd guess CSL is used in clients like Zotero etc. RDF resources need to be aligned, ergo my q
@gbilder @ostephens @acka47 no surprise there, I'd guess CSL is used in clients like Zotero etc. RDF resources need to be aligned, ergo my q
gthorisson
Gudmundur Thorisson
@brinxmat cannot be totally free - need to get revenue to cover operating costs. Memb. fee scheme could be better, but will evolve.
@brinxmat cannot be totally free - need to get revenue to cover operating costs. Memb. fee scheme could be better, but will evolve.
brinxmat
Rurik Greenall
@gthorisson Seems to be a publisher-driven anyway; I guess that I have no comment on their revenue model. Member's clubs aren't open though
@gthorisson Seems to be a publisher-driven anyway; I guess that I have no comment on their revenue model. Member's clubs aren't open though
gthorisson
Gudmundur Thorisson
@brinxmat Many key API integration scenarios essentially require a trust relationship, which implies client app registration <-- membership
@brinxmat Many key API integration scenarios essentially require a trust relationship, which implies client app registration <-- membership
brinxmat
Rurik Greenall
@gthorisson Sure, I see the arguments. Will shut up until I see a copy of a license for the data
@gthorisson Sure, I see the arguments. Will shut up until I see a copy of a license for the data
gthorisson
Gudmundur Thorisson
@brinxmat OK. Fair enough. In the meantime, check out Principles which mention data & code licensing about.orcid.org/about/what-is-…
@brinxmat OK. Fair enough. In the meantime, check out Principles which mention data & code licensing about.orcid.org/about/what-is-…
brinxmat
Rurik Greenall
@gthorisson Nice principles, but no explicit license for API data. Am I missing something?
@gthorisson Nice principles, but no explicit license for API data. Am I missing something?
gthorisson
Gudmundur Thorisson
@brinxmat Very good point. Clear licensing info is one key feature that's needed, let me add this to the ToDo list on support.orcid.org
@brinxmat Very good point. Clear licensing info is one key feature that's needed, let me add this to the ToDo list on support.orcid.org
gbilder
Geoffrey Bilder
@brinxmat #ORCID has free API too. They are committed to releasing data under CC-0 and source under MIT lic.. How is that not open?
@brinxmat #ORCID has free API too. They are committed to releasing data under CC-0 and source under MIT lic.. How is that not open?
gbilder
Geoffrey Bilder
@brinxmat Yes. Anything that has been made public by researcher. See #ORCID principles here: goo.gl/u8Wy0
@brinxmat Yes. Anything that has been made public by researcher. See #ORCID principles here: goo.gl/u8Wy0
brinxmat
Rurik Greenall
@gbilder In order to interact with the data, I need the key ####-####-####-#### which isn't part of the researcher's data, but ORCID
@gbilder In order to interact with the data, I need the key ####-####-####-#### which isn't part of the researcher's data, but ORCID
gbilder
Geoffrey Bilder
@brinxmat The identifiers themselves are *always* public, hence in CC0 dump. You can also use public API to search via public data #orcid
@brinxmat The identifiers themselves are *always* public, hence in CC0 dump. You can also use public API to search via public data #orcid
brinxmat
Rurik Greenall
@gbilder OK, where do I find the dump? The API fails because I'm not authenticated
@gbilder OK, where do I find the dump? The API fails because I'm not authenticated
gbilder
Geoffrey Bilder
@brinxmat You don’t need to authenticate to use public API. Just point queries at pub.orcid.org
@brinxmat You don’t need to authenticate to use public API. Just point queries at pub.orcid.org
brinxmat
Rurik Greenall
@gbilder I should not be so obtuse: Without the IDs, the API is worthless…so, yes…
@gbilder I should not be so obtuse: Without the IDs, the API is worthless…so, yes…