search

WDscholia / scholia

Wikidata-based scholarly profiles
https://scholia.toolforge.org
Other
220 stars 78 forks source link

initiate discussion about Scholia APIs #1665

Open egonw opened 3 years ago

egonw commented 3 years ago

Triggered by the discussion around the Bioschemas API (see https://github.com/WDscholia/scholia/pull/1478 and https://github.com/WDscholia/scholia/pull/1663), should Scholia introduce APIs that use content negotiation to serve machine readable content or HTML (or ...), depending on the use. What would this new Scholia design look like? What non-HTML types should be returned? Should we have API methods to return content for individual aspect panels?

WolfgangFahl commented 2 years ago

https://github.com/WolfgangFahl/ProceedingsTitleParser/issues/20 had a similar discussion.

The API is restful and allows to specify the Proceedings Title Parser search parameters via the URL of http://ptp.bitplan.com

We opted for the formats described in PTP Content Negotiation Documentation

wikison is Mediawiki markup that follows rules to make sure the triples in a Semantic Media Wiki are properly created

The other formats csv, xml and json are commonly used vanilla data exchange formats. The idea here is to have a "most natural" representation along the lines of the WikiSon/JSON ideas.