Hi Jörg,

I don't wanna go into the details of how our crawling works, but machine tags in general are for a special audience and often represent state for the authority that issued them. I would recommend you not to rely on any of our machine tags. The structure and use patterns might change as we need them.

The safest way to find out the conceptual schemas is to investigate the endpoints directly using the native protocols.

The endpoint lacking a URI is interesting and likely a bug. Ive created a jira to be followed up by us: http://dev.gbif.org/issues/browse/POR-2355

If you wanna know more about the current crawling let us know and we try our best once staff is back from holidays ;)

Thanks, Markus

On 17 Jul 2014, at 11:18, Holetschek, Jörg j.holetschek@bgbm.org wrote:

Hi Markus,

Great to have the final version of the API available! I used it to find out metadata about datasets from the registry and I found some odd datasets.

For BioCASe/DiGIR/TAPIR endpoints, the conceptualSchema usually can be found in the machineTags of the respective endpoint, or in the machineTags of the dataset (e.g. http://api.gbif.org/v1/dataset/88b04a08-f762-11e1-a439-00145eb45e9a).

But I came across many BioCASe/DiGIR/TAPIR endpoints with no according machineTag, for example http://api.gbif.org/v1/dataset/82c788c2-f762-11e1-a439-00145eb45e9a (BioCASe) http://api.gbif.org/v1/dataset/85275ce6-f762-11e1-a439-00145eb45e9a (DiGIR) http://api.gbif.org/v1/dataset/0e6799d0-13e6-11de-b2e1-b8a03c50a862 (TAPIR)

Is that intended? How is it possible to find out the conceptualSchema for these endpoints?

(I also found one endpoint that lacks the ‘url’ field, but I guess that’s just a freak: http://api.gbif.org/v1/dataset/3c7d6270-9681-11dc-8149-b8a03c50a862)

Cheers, Jörg

Von: api-users-bounces@lists.gbif.org [mailto:api-users-bounces@lists.gbif.org] Im Auftrag von Markus Döring Gesendet: Freitag, 11. Juli 2014 15:19 An: api-users@lists.gbif.org Betreff: [API-users] GBIF API v1.0 live

Dear GBIF API users,

sorry for the far too long downtime today, but the good news is that version 1.0 of the API is finally live now! http://api.gbif.org/v1/

You can find the updated documentation here as usual: http://www.gbif.org/developer

The previous v0.9 API URL will still be running up to the end of August, serving the exact same content.

Hope you enjoy it. with best wishes,

your GBIF dev team

Version 1.0 changes:

• remove all underscores from URLs and replace them with camelCase (mainly species & metrics API)
• dataset.owningOrganizationKey renamed to dataset.publishingOrganizationKey
• use of lists instead of simple strings for email, phone, homepage, position and address for contacts, organization and node in the registry
• include issue column in dwca download
• search facets use country iso 2letter codes
• species & dataset suggest returns minimal information now: http://api.gbif-uat.org/v0.9/species/suggest?q=Dracul
• remove reverse geocode & mendeley GBIF articles from our API