W3C home > Mailing lists > Public > public-xg-lld@w3.org > January 2011

social and emergent uses -- DRAFT -- call for use cases

From: Jodi Schneider <jodi.schneider@deri.org>
Date: Thu, 13 Jan 2011 11:41:08 -0500
Message-Id: <BDA246F0-2C9B-45E8-B47F-3FE270DA215E@deri.org>
To: public-xg-lld@w3.org
Here’s our draft call for use cases for the "social and emergent" cluster:
What listservs should we send this? So far, we envision sending this to:
ASIST, code4lib, public LLD list, AOIR
Is anything confusing?
In particular, do “social” and “emergent” make sense? What do they evoke, for you?
Thanks for any comments!
-Jodi and Uldis

-----------------

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

Call for Use Cases: Library Linked Data -- Social and Emergent Uses

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?

The W3C Library Linked Data Incubator Group is soliciting SOCIAL and EMERGENT use cases for library-related linked data:
How is library and cultural heritage data used 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] 
enhance the use of library-related data in a social context? 
contribute to systems for sharing, filtering, recommending, or machine reading?
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, 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.
Received on Thursday, 13 January 2011 16:42:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 16:42:46 GMT