Re: Call for Use Cases: Social uses and other new uses of Library Linked Data - from W3C Library Linked Data Incubator Group

Many thanks, Thomas!

It's now on our wiki at:
http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Crosslinking_Environment_Data_and_the_Library
and we'll take a closer look as we work further on the social/new uses cluster.

Best,
Jodi

On 14 Feb 2011, at 11:35, Thomas Bandholtz wrote:

> Hi Jodi,
> 
> here is a use case (below),
> 
> Best regards,
> Thomas
> 
> 
> Call for Use Cases: Social uses and other new uses of Library Linked
> Data - from W3C Library Linked Data Incubator Group
> 
> === Name ===
> 
> Crosslinking Environment Data and the Library
> 
> 
> === Owner ===
> 
> Thomas Bandholtz
> thomas.bandholtz@innoq.com
> 
> === Background and Current Practice ===
> 
> 
> The Federal Environment Agency, Germany, (UBA) [1] 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.
> 
> === Goal ===
> 
> 
> 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.
> 
> === Target Audience ===
> 
> 
> (1) General information for the public, but they may not be so
> interested in the data behind the reports.
> (2) Professionals who are working on environmental topics, such as
> eco-audits.
> (3) 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.
> 
> === Application of linked data for the given use case ===
> 
> 
> 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) [2] 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 [3]. So far we
> migrated the thesaurus to a linked data RDF representation based on
> iQvoc [4], including linkage to GEMET [5]. At the same time we developed
> a linked data representation of the Environmental Specimen Bank (ESB)
> [6] and a species catalog to be linked to EUNIS [7]. 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 [8] so far. There are plans for RDFying the OPAC catalog
> of the library as well, but no schedule so far.
> 
> === Related Vocabularies (optional) ===
> 
> 
> * SKOS [9] for the classification and the reference vocabularies
> * elements of the Geonames Ontology [10] for the gazetteer
> * elements of the Event Ontology [11] for the chronicle
> * Dublin Core terms [12] for bibliographic records
> * elements of Darwin Core [13] for the species
> * Statistical Core Vocabulary (SCOVO) [14] for observation data of the
> ESB. SCOVO will be replaced by the Data Cube vocabulary [15].
> 
> === 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.
> Technological obstacles: (1) 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”. (2) 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. (3) 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, as the FAO and the
> UBA both participate in the Ecoterm initiative [16].
> 
> === References (optional) ===
> 
> [1] http://www.umweltbundesamt.de
> [2] http://www.semantic-network.de/home.html?lang=en
> [3] Linked Environment Data,
> see http://www.w3.org/egov/wiki/Linked_Environment_Data
> [4] 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/
> [5] http://www.eionet.europa.eu/gemet,
> see also: http://ckan.net/package/gemet
> [6] http://www.umweltprobenbank.de/
> [7] http://eunis.eea.europa.eu . EUNIS is in the LOD-cloud:
> http://ckan.net/package/eunis
> [8] http://doku.uba.de
> [9] http://www.w3.org/2004/02/skos/
> [10] http://www.geonames.org/ontology
> [11] http://motools.sourceforge.net/event/event.html
> [12] http://dublincore.org/documents/dcmi-terms/
> [13] http://rs.tdwg.org/dwc/terms/
> [14] http://sw.joanneum.at/scovo/schema.html
> [15]
> http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html
> [16] http://ecoterm.infointl.com/
> 
> 
> 
> Am 19.01.2011 09:00, schrieb Jodi Schneider:
>> ================================================================
>> Call for Use Cases: Social uses and other new uses of Library Linked Data
>> The W3C Library Linked Data Incubator Group
>> -<http://www.w3.org/2005/Incubator/lld/>http://www.w3.org/2005/Incubator/lld/
>> Requested by February 15th, 2010
>> ================================================================
>> Do you use library-related data -- like reading lists, library materials
>> (articles, books, videos, cultural heritage or archival materials, etc),
>> bookmarks, or annotations -- on the Web and mobile Web?
>> 
>> Are you currently using social features in library-related information
>> systems or sites, or plan to do so in the near future? We are
>> particularly interested in uses that are related to or could benefit
>> from the use of linked data [1].
>> 
>> 
>> The W3C Library Linked Data Incubator Group is soliciting SOCIAL and
>> EMERGENT use cases for library-related linked data:
>> 
>>    * What new or innovative uses do you see (or envision) integrating
>>      library and cultural heritage data into applications on the Web
>>      and in social media?
>>    * How are social features used in library-related information systems?
>>    * What are the emergent uses of library-related data on the Web and
>>      mobile Web?
>>    * How could linked data technology [1]
>>          o enhance the use of library-related data in a social context?
>>          o contribute to systems for sharing, filtering, recommending,
>>            or machine reading?
>>          o support new uses we may not have envisioned or achieved yet?
>>    * Some examples have been discussed in this thread [4]. 
>> 
>> 
>> 
>> Please tell us more by filling in the questionnaire below and sending it
>> back to us or to public-lld@w3.org <mailto:public-lld@w3.org>,
>> preferably before February 15th, 2010.
>> 
>> 
>> 
>> The information you provide will be influential in guiding the
>> activities the
>> Library Linked Data Incubator Group will undertake to help increase global
>> interoperability of library data on the Web. The information you provide
>> will
>> be curated and published on the group wikispace at [3].
>> 
>> We understand that your time is precious, so please don't feel you have to
>> answer every question. Some sections of the templates are clearly marked as
>> optional. However, the more information you can provide, the easier it
>> will be
>> for the Incubator Group to understand your case. And, of course, please
>> do not
>> hesitate to contact us if you have any trouble answering our questions.
>> Editorial guidance on specific points is provided at [2], and examples are
>> available at [3].
>> 
>> At this time, we are particularly interested in use cases describing the
>> social media and emergent uses for library linked data.The Incubator
>> Group will carefully consider all submissions we receive.
>> 
>> On behalf of the Incubator Group, thanks in advance for your time,
>> 
>> Jodi Schneider (jodi.schneider_deri.org) and Uldis Bojārs
>> (uldis.bojars_gmail.com)
>> 
>> [1]http://www.w3.org/DesignIssues/LinkedData.html
>> [2]http://www.w3.org/2005/Incubator/lld/wiki/UCCuration
>> [3]http://www.w3.org/2005/Incubator/lld/wiki/UseCases
>> [4] http://lists.w3.org/Archives/Public/public-xg-lld/2011Jan/0006.html
>> 
>> ================================================================
>> 
>> === Name ===
>> 
>> A short name by which we can refer to the use case in discussions.
>> 
>> === Owner ===
>> 
>> The contact person for this use case.
>> 
>> === Background and Current Practice ===
>> 
>> Where this use case takes place in a specific domain, and so requires
>> some prior
>> information to understand, this section is used to describe that domain.
>> As far
>> as possible, please put explanation of the domain in here, to keep the
>> scenario
>> as short as possible. If this scenario is best illustrated by showing
>> how applying
>> technology could replace current existing practice, then this section
>> can be used
>> to describe the current practice. Often, the key to why a use case is
>> important
>> also lies in what problem would occur if it was not achieved, or what
>> problem
>> means it is hard to achieve.
>> 
>> === Goal ===
>> 
>> Two short statements stating (1) what is achieved in the scenario without
>> reference to linked data, and (2) how we use linked data technology to
>> achieve
>> this goal.
>> 
>> === Target Audience ===
>> 
>> The main audience of your case. For example scholars, the general
>> public, service
>> providers, archivists, computer programs...
>> 
>> === Use Case Scenario ===
>> 
>> The use case scenario itself, described as a story in which actors
>> interact with
>> systems. This section should focus on the user needs in this scenario.
>> Do not
>> mention technical aspects and/or the use of linked data.
>> 
>> === Application of linked data for the given use case ===
>> 
>> This section describes how linked data technology could be used to
>> support the
>> use case above. Try to focus on linked data on an abstract level, without
>> mentioning concrete applications and/or vocabularies. Hint: Nothing library
>> domain specific.
>> 
>> === Existing Work (optional) ===
>> 
>> This section is used to refer to existing technologies or approaches
>> which achieve
>> the use case (Hint: Specific approaches in the library domain). It may
>> especially
>> refer to running prototypes or applications.
>> 
>> === Related Vocabularies (optional) ===
>> 
>> Here you can list and clarify the use of vocabularies (element sets and
>> value
>> vocabularies) which can be helpful and applied within this context.
>> 
>> === Problems and Limitations (optional) ===
>> 
>> This section lists reasons why this scenario is or may be difficult to
>> achieve,
>> including pre-requisites which may not be met, technological obstacles
>> etc. Please
>> explicitly list here the technical challenges made apparent by this use
>> case. This
>> will aid in creating a roadmap to overcome those challenges.
>> 
>> === Related Use Cases and Unanticipated Uses (optional) ===
>> 
>> The scenario above describes a particular case of using linked data.
>> However, by
>> allowing this scenario to take place, the likely solution allows for
>> other use
>> cases. This section captures unanticipated uses of the same system
>> apparent in the
>> use case scenario.
>> 
>> === References (optional) ===
>> 
>> This section is used to refer to cited literature and quoted websites.