- From: Antoine Isaac <aisaac@few.vu.nl>
- Date: Fri, 03 Sep 2010 11:15:49 +0200
- To: public-xg-lld <public-xg-lld@w3.org>
Hi Marcia (forwarding to the list, as it is a relevant question, and the continuation of yesterday's call [1])
> Do you think it is necessary to refer to the 4 principles to avoid
> non-true-LD be included?
> http://www.w3.org/DesignIssues/LinkedData.html
I'd have said that if contributors don't know linked data they would not even think of contributing :-)
Now, we're in the real world, and we'll be sending the call to more general lists. So there could be still completely out-of-scope contributions that we don't want if we don't put such link.
Any objection?
Cheers,
Antoine
[1] http://www.w3.org/2005/Incubator/lld/minutes/2010/09/02-lld-minutes.html#item15
-------- Original Message --------
Subject: Re: Use case mail
Date: Thu, 2 Sep 2010 13:34:39 -0400
From: ZENG, MARCIA <mzeng@kent.edu>
To: Antoine Isaac <aisaac@few.vu.nl>
On 9/2/10 7:14 AM, "Antoine Isaac" <aisaac@few.vu.nl> wrote:
> Dear all
>
> To prepare for our calling for external contributions for (use)
cases, I
> have drafted a first mail at
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Call_Mail
>
> It is heavily adapted from the SKOS Call for use cases at
> http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0036.html
>
> Comments are of course highly welcome. And feel free to directly
fix any
> typo or grammatical mistake you would spot on the text!
>
A note on this: while adapting the SKOS use case mail I felt very
tempted to re-use the introduction at
http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Template (copied
below). I really like that piece of text, and I think it is a good
way to assert that we especially value user-oriented use cases for
our task, even if other cases are welcome as well. However it would
make the mail we send a very long one, even if we shortened it to
half of its current size.
I'd thus suggest to fit this introduction into
http://www.w3.org/2005/Incubator/lld/wiki/UCCuration , which is
communicated to external contributors in the current draft mail.
Maybe we can discuss this on the coming call. But it is now quite
late, and anyway objections or approval by mail are always welcome,
especially from these who have sent regrets :-)
Antoine
-----
The mission of the Library Linked Data Incubator Group is to help
increase global interoperability of library data on the Web by
bringing together people involved in Semantic Web
activities--focusing on Linked Data--in the library community and
beyond, building on existing initiatives, and identifying
collaboration tracks for the future.
Achieving this goal will depend on identifying shared models, modes
of collaboration, and a common understanding of the changing ways
that data is shared on the web.
One approach to this problem is to identify use cases that reflect
expectations of how end-users will exploit library services and
assets, how libraries will make such assets and services available,
and the infrastructure and devices necessary to complete this
connection. It is important, as well, to recognize that libraries
exist within an ecosystem of many information providers and
services, and the interrelationships among all information providers
is an important component of such use cases.
A use case describes what a user can do with a system by specifying
a sequence of interactions between user and system leading to a
desirable outcome. It should not be confused with specifying the
technology itself: a use case may allow for many alternatives to
achieving user needs. While use cases are typically devised
independently of underlying technology (that is, they are intended
to expose functional requirements, rather than to specify the means
by which such requirements are satisfied), the focus of this
Incubator Group is specifically on how linked data approaches might
be brought to bear so as to improve the overall ability to satisfy
user needs. The linked data perspective should therefore be integral
to the use cases.
To help analysis across use cases and to keep a consistent level of
information, each use case should try to follow the template below,
providing something for each non-optional field.
Received on Friday, 3 September 2010 09:16:22 UTC