search

ror-community / ror-roadmap

Central information about what is happening at ROR and how to contribute feedback
10 stars 2 forks source link

Content negotiate a resource. #177

Open fils opened 1 year ago

fils commented 1 year ago

If I do

curl  https://ror.org/03102fn17

or

curl -XGET  --header "Accept: application/ld+json" https://ror.org/03102fn17

I get back a gzip compressed version of the HTML page.

Would it be proper to allow the ror ID resolve to a metadata representation of that resource using a voc like Schema.org or other?

lizkrznarich commented 1 year ago

Hi @fils - as you've noticed, we currently don't support content negotiation, however this is something we could consider for future, so I'm moving this issues to our general roadmap project in https://github.com/ror-community/ror-roadmap. In the meantime, you can get a ROR record in JSON using our API, ex:

curl https://api.ror.org/organizations/03102fn17
curl https://api.ror.org/organizations/ror.org/03102fn17
curl https://api.ror.org/organizations/https://ror.org/03102fn17

See REST API documentation at https://ror.readme.io/docs/retrieve-a-single-ror-record