Main Page

From CETAF Identifiers Wiki
Revision as of 14:13, 11 April 2019 by Fabian Reimeier (Talk | contribs) (Added corrected example)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

CETAF ISTC Stable Identifier Initiative

CETAF Stable Identifiers are globally unique, consistent and reliable identifiers for specimens in natural and botanical collections. These identifiers are used in the world wide web to redirect users and systems to images, websites and metadata of the physical objects and to integrate them with the semantic web.

How do CETAF Stable Identifier look like?

Example for the syntax of a CETAF Stable Identifier.

The CETAF identifier system is based on HTTP-URIs and Linked Data principles. It is simple and future-proof. Each collection object as well as its associated information resources (e.g. multimedia, RDF, webpages) are identified by stable HTTP-URIs that will never change. The URI Syntax for the objects is chosen and maintained by the institution owning them. This flexibility is one of the main advantages of the CETAF Stable Identifier system as it allows e.g. to include branding and local scope identifiers into the CETAF Stable Identifier URI. There are however some best practices for stable URIs. Examples are:

How are CETAF Stable Identifiers resolved?

Resolving URI-based collection identifiers using standard HTTP-redirection mechanisms.

A CETAF Stable Identifier allows the access of information about the corresponding collection object in various ways. If a human user tries to access a collection object by typing it’s CETAF Stable Identifier into a web-browser, he will be redirected to a human-readable representation (e.g. html web-page) of it. If a software-system tries to access the collection object via the same identifier, it will be redirected to a machine-processable RDF-encoded metadata record. The identifier is therefore integrated with the semantic web and can also be used in other RDF representations to link to the belonging collection object.

What can CETAF Stable Identifiers be used for?

As described above, CETAF Identifiers can first of all be used to redirect users and systems to images, websites and metadata of the physical objects they belong to. They can also be used to precisely reference specimens needed in scientific studies and serve as basis for data retrieval, integration and reproducibility of data experiments. Additionally, the stable identifiers enable new applications in the semantic web domain. An example for this is the Biology Pilot. The Botanic Garden and Botanical Museum Berlin, Meise Botanic Garden and other collections annotated thousands of specimens with the HUH and WikiData IDs of their collectors. The CETAF Stable Identifiers of the annotated specimens are available on GBIF and a server is crawling the identifiers to organize the RDF information in a Blaze Graph triple store. This graph enables us to search for specimen by their collector HUH or WikiData ID, which is invariant to the different spelling variants the individual institutions may be using. The query will return all relevant specimens available in the joined set of specimens regardless of their origin institution. If the number of institutions using stable identifiers grows and the amount of machine readable annotations increases, this technology could be used to basically create a “google for specimens”.

How can I implement CETAF Stable Identifiers for my collection?

The CETAF Stable Identifiers can be implemented in three levels. They are described in detail here. Following conditions have to be met to reach the corresponding implementation levels:

Level 1

  • you assigned a stable URI to each object of your collection, which will be never changed and preferably follows the best practices for stable URIs
  • there exists a human-readable representation (web-page) for each of your collection objects
  • a user trying to access a collection object by typing the stable URI of it into a web-browser will be redirected to the human-readable representation (web-page) of the object (you can test this by using the CETAF URI Tester)

Level 2

  • you reached level 1
  • there exists a machine-readable RDF metadata record for each of your collection objects
  • a machine trying to access a collection object via its identifier with 'application/rdf+xml' header will be redirected to the objects machine-readable RDF metadata record (you can test this by using the CETAF URI Tester)

Level 3

  • you reached level 2
  • the machine-readable RDF metadata record of each of your collection objects encodes application specific data (e.g. is compliant to the CETAF Specimen Preview Profile (CSPP))

Useful Links

Further reading