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

Re: Social use case ideas

From: Uldis Bojars <captsolo@gmail.com>
Date: Thu, 6 Jan 2011 16:58:20 +0200
Message-ID: <AANLkTikOq33xtF_G2pLoJyEUSxA60X_O_uES1ePO2muM@mail.gmail.com>
To: Antoine Isaac <aisaac@few.vu.nl>
Cc: public-xg-lld <public-xg-lld@w3.org>
Hi Antoine,

Just a quick reply to 3). Will reply to other comments in a follow-up email.

On Wed, Jan 5, 2011 at 6:09 PM, Antoine Isaac <aisaac@few.vu.nl> wrote:

>> 3) Location/ownership info
>>
>> An open publication catalog + information about where these
>> publications can be found.
>>
>> To add a social aspect, let users of this service indicate what
>> publications they have and if / on what conditions they would lend
>> these books. As a result participants would not only be able to find
>> books in nearby collections (presumably covered by the Use Case Find
>> materials in the closest physical collection) but could also enable
>> peer-to-peer book-swapping (though would require a critical mass of
>> users from any given location before it becomes useful for people from
>> that location).
>
> I'm not sure I understand this use case: who are the "users"/"participants"
> who hold publications and could swap them? End users or libraries
> themselves?

Re peer-to-peer book-swapping the intended participants are end users.
They share information about the books they have and an information
system that aggregates this information helps them find books nearby
that they may be interested in.

Jodi suggested an interesting twist to this use case -- to also look
at e-book lending / sharing (e.g., with underlying architecture
ensuring that copyright legislation is complied with -- such as by
expiring a shared ebook after a given period of time).

But there is no reason why libraries should be excluded. End users may
also use information about books that are available in nearby
libraries. (One use case does not exclude the other)

Uldis
Received on Thursday, 6 January 2011 14:59:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 6 January 2011 14:59:37 GMT