Use Case Crosslinking Environment Data and the Library
Back to Use Cases & Case Studies page
- 1 Name
- 2 Owner
- 3 Background and Current Practice
- 4 Goal
- 5 Target Audience
- 6 Use Case Scenario
- 7 Application of linked data for the given use case
- 8 Existing Work (optional)
- 9 Related Vocabularies (optional)
- 10 Problems and Limitations (optional)
- 11 Related Use Cases and Unanticipated Uses (optional)
- 12 References (optional)
Crosslinking Environment Data and the Library
Thomas Bandholtz firstname.lastname@example.org
Background and Current Practice
The Federal Environment Agency, Germany, (UBA)  has a long tradition in knowledge organization using a library along with many Web-based information systems presenting observation data and results of analysis. The backbone of this information space is a classification system enhanced by a reference vocabulary which consists of a thesaurus, a gazetteer and a chronicle. Until today, the library and the data representations are kept separately.
We want to cross-link bibliographical information with related environmental observation data, and both with the reference vocabulary. Linked data technology provides means to (URI-) reference specific data records, not only Web pages.
- General information for the public, but they may not be so interested in the data behind the reports.
- Professionals who are working on environmental topics, such as eco-audits.
- Academic people, both students and researchers.
Use Case Scenario
User A is searching the OPAC for some environmental topic and finds an article which is based on observation data. Along with the bibliographic record he sees a link to a Web representation of this observation data itself. So he can make his own analysis on the same data. User B is exploring some environmental information system which gives access to observation data. He makes his selection and retrieves a specific timeline or spatial distribution. Along with the data representation he finds links pointing to bibliographic records of publications which discuss this data. User C is exploring the reference vocabulary (SNS, ) and finds back-links pointing both to bibliographic records and data representations which are tagged with a concept.
For human users, the use case scenario works even with HTML Web pages if they are well structured and linked. Linked data technology provides a more fine-grained linkage. It simplifies the process of cross-linking, as both the OPAC and the data are referencing concept URIs instead of terms. It provides access for machine agents.
Existing Work (optional)
Since 2003, Semantic Network Service (SNS)  makes three reference vocabularies accessible: the thesaurus of the library, a gazetteer, and a chronicle. There is a Web representation of each concept, and there are web services (including automatic classification of Web pages) which return XML Topic Maps representations of concepts. In 2010 we started a Linked Environment Data initiative . So far we migrated the thesaurus to a linked data RDF representation based on iQvoc , including linkage to GEMET . At the same time we developed a linked data representation of the Environmental Specimen Bank (ESB)  and a species catalog to be linked to EUNIS . In 2011 we will bring this into production, migrate the gazetteer and the chronicle to linked data technology as well and establish detailed linking between ESB and SNS. The ESB Website includes many specific publications which are linked to data representations, but there is no integration of the OPAC catalogue  so far. There are plans for RDFying the OPAC catalog of the library as well, but no schedule so far.
Related Vocabularies (optional)
- SKOS  for the classification and the reference vocabularies
- elements of the Geonames Ontology  for the gazetteer
- elements of the Event Ontology  for the chronicle
- Dublin Core terms  for bibliographic records
- elements of Darwin Core  for the species
- Statistical Core Vocabulary (SCOVO)  for observation data of the ESB. SCOVO will be replaced by the Data Cube vocabulary .
Problems and Limitations (optional)
The most prominent obstacle is the lack of a dedicated funding for this initiative. There are some projects of the participating systems that draw up some of their budget for pieces of the puzzle, but there is no overall plan of the agency so far.
- the lack of stable RDF vocabularies. SKOS and Dublin Core may be called mature, but the others are moving targets. There is no established property such as “relatedDataRecord” and “relatedPublication”.
- open source editions of triple stores are very difficult to handle, missing support for content negotiation based on user designed URI patterns, and they may not scale well.
- As we are developing Web applications with Ruby-on-rails, there is no usable RDF support in Ruby (compared to active record).
Related Use Cases and Unanticipated Uses (optional)
As the use case is not yet implemented, we cannot anticipate unanticipated uses ;-)
There may be some overlap with Authority Data Enrichment. There is also some overlap with the FAO use cases (Use Case FAO Authority Description Concept Scheme, Use Case AGRIS, and Use Case AGROVOC Thesaurus), as the FAO and the UBA both participate in the Ecoterm initiative .
 Linked Environment Data, see http://www.w3.org/egov/wiki/Linked_Environment_Data
 Bandholtz, T.; Schulte-Coerne, T.; Glaser, R.; Fock, J.; Keller, T. (2010) iQvoc – Open Source SKOS(XL) Maintenance and Publishing Tool. 6th Workshop on Scripting and Development for the Semantic Web. Heraklion 2010 http://www.semanticscripting.org/SFSW2010/