W3C home > Mailing lists > Public > public-sweo-ig@w3.org > October 2010

Reminder: Call for Use Cases: Library Linked Data

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Thu, 07 Oct 2010 17:13:12 +0200
Message-ID: <4CADE388.2050308@few.vu.nl>
To: SKOS <public-esw-thes@w3.org>, semantic-web@w3.org, dc-general@jiscmail.ac.uk, dc-architecture@jiscmail.ac.uk, ecoterm@npogroups.org, NKOS-L@OCLC.ORG, diglib@infoserv.inist.fr, info-ic@listes.irisa.fr, public-sweo-ig@w3.org, "public-lod@w3.org" <public-lod@w3.org>, dutchsemweb-l@few.vu.nl, public-lld <public-lld@w3.org>
CC: public-xg-lld <public-xg-lld@w3.org>
[apologies for cross-posting]

W3C Library Linked Data Incubator Group - http://www.w3.org/2005/Incubator/lld/

Call for Use Cases: Library Linked Data

Are you currently using linked data technology [1] for library-related data, or
considering doing it in the near future? If so, please tell us more by filling
in the questionnaire below and sending it back to us or to public-lld@w3.org,
preferably before October 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].

We are particularly interested in use cases describing the use of library
linked data for end-user oriented applications. However, we're not ruling
anything out at this stage, and the Incubator Group will carefully consider
all submissions we receive.

On behalf of the Incubator Group, thanks in advance for your time,

Emmanuelle Bermes (Emmanuelle.Bermes_bnf.fr), Alexander Haffner (A.Haffner_d-nb.de),
Antoine Isaac (aisaac_few.vu.nl) and Jodi Schneider (jodi.schneider_deri.org)

[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

================================================================
================================================================

=== 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.
Received on Thursday, 7 October 2010 15:14:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:00 UTC
http://lists.w3.org/Archives/Public/public-sweo-ig/2010Oct/0000.html
lists.w3.org
crawl=CC-MAIN-2015-22
16353
application/http; msgtype=response
sha1:YBZF42A3MF5ET2GAFN3L2ZK65WWUQYGX
<urn:uuid:33318d08-bdde-43f3-aeb1-11adc5769eec>
2015-05-22T21:45:18Z
128.30.52.56
sha1:O7MCFW6FESJFJHRIRHOSALFXLK6BGG6H
<urn:uuid:d243367c-91b6-40ae-8773-ef59fe31e16c>
http://lists.w3.org/Archives/Public/public-sweo-ig/2010Oct/0000.html
response
<urn:uuid:97def443-b421-4ea7-b4f2-26757252ffca>
robots: classic
hostname: ip-10-180-206-219.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2015-22
operator: CommonCrawl Admin
description: Wide crawl of the web for May 2015
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf