Make GBIF API compatible with semantic web a.k.a. Linked Open Data (LOD) about gbif-api HOT 1 OPEN

For now, I studied the /occurrence and /species API's.
My proposal could turn the gbif.org API into a regular citizen of the Web of Data (a.k.a. Linked Open Data).
This is, web client programs will be able to get RDF triples from the existing URL's from gbif.org API , and recursively the triples obtained will refer to URL's that also return RDF triples.
See famous Tim Berners Lee 5 stars mug page : https://www.w3.org/DesignIssues/LinkedData.html

There are 3 scenarios for using JSON-LD in gbif.org API .

1. not changing anything, but be add this in documentation and be aware of the possibilities by external JSON-LD processors and discuss use cases and the big picture (LOD versus frictionlessdata.io, etc)
2. just add at root an @context key
3. in addition add @id and @type (see below)

The @context key could point to my work-in-progress JSON-LD in github.com/jmvanel/rdf-convert/gbif.org , or more probably to a properly versioned URL :

"@context" : "https://raw.githubusercontent.com/jmvanel/rdf-convert/master/gbif.org/context.jsonld"

For a concrete proposal, here are key - value pairs for @id and @type that could be added to
https://api.gbif.org/v1/occurrence/1258202889 .
This would make more visible the URI, which could a be problem for API users (?) . But this would simplify the @context . Note that the existing ID's being integers, wich is not taken in account by JSON-LD API recommendation at the moment, will be soon not a problem , I made an issue for that .

"@id" : "1258202889"
"@type" : "dwc:PreservedSpecimen"

For your understanding of JSON-LD , given above @context , this is equivalent to

"@id" : "https://api.gbif.org/v1/occurrence/1258202889"
"@type" : "http://rs.tdwg.org/dwc/terms/PreservedSpecimen"

from gbif-api.