- From: Monica Duke <m.duke@ukoln.ac.uk>
- Date: Thu, 08 Jul 2010 14:07:38 +0100
- To: Antoine Isaac <aisaac@few.vu.nl>
- CC: public-xg-lld <public-xg-lld@w3.org>
Antoine Isaac wrote: > Hi everyone, > > > > Which relates a bit to my own remark on the dimensions at [1]. Would it > be appropriate to add something like "documenting" (the verb) or "adding > information" in the user needs, and "user-generated information" in the > information assets? +1 Or possibly 'annotate' as an alternative description for the user interaction. 'Cite' fits in here too. Is there also a need for a distinction between "comment on" (document, annotate) and "submit" (add information)? They are slight variations of user-generated information. Monica > > Cheers, > > Antoine > > [1] http://www.w3.org/2005/Incubator/lld/wiki/Dimensions > > >> All >> >> Again after a first pass, note that IFLA (International Federation of >> Library Associations and Institutions) has developed sets of user tasks >> in relation to bibliographic metadata, as part of the Functional >> Requirements family (the three models cited below - work on consoliding >> these into a single functional requirements model has already begun, >> although FRSAD has not yet been finalised): >> >> From Functional Requirements for Bibliographic Records (FRBR) >> (http://www.ifla.org/en/publications/functional-requirements-for-bibliographic-records): >> >> >> >> to find [bibliographic] entities that correspond to the user’s stated >> search criteria (i.e., to locate either a single entity or a set of >> entities in a file or database as the result of a search using an >> attribute or relationship of the entity); >> >> >> >> to identify an entity (i.e., to confirm that the entity described >> corresponds to the entity sought, or to distinguish between two or more >> entities with similar characteristics); >> >> >> >> >> >> to select an entity that is appropriate to the user’s needs (i.e., to >> choose an entity that meets the user’s requirements with respect to >> content, physical format, etc., or to reject an entity as being >> inappropriate to the user’s needs); >> >> >> >> >> >> to acquire or obtain access to the entity described (i.e., to acquire an >> entity through purchase, loan, etc., or to access an entity >> electronically through an online connection to a remote computer). >> >> From Functional Requirements for Authority Data (FRAD) >> (http://www.ifla.org/en/publications/functional-requirements-for-authority-data): >> >> >> Functional Requirements for Bibliographic Records FRBR (Conceptual >> model) IFLA Study Group on the Functional Requirements for Bibliographic >> Records 12.00 Normal 0 false false false EN-GB X-NONE X-NONE >> MicrosoftInternetExplorer4 >> >> Find an entity or set of entities corresponding to stated criteria >> (i.e., to find either a single entity or a set of entities using an >> attribute or combination of attributes or a relationship of the entity >> as the search criteria); or to explore the universe of bibliographic >> entities using those attributes and relationships. >> >> Identify an entity (i.e., to confirm that the entity represented >> corresponds to the entity sought, to distinguish between two or more >> entities with similar characteristics) or to validate the form of name >> to be used for a controlled access point. >> >> >> >> >> >> >> Contextualise: Place a person, corporate body, work, etc., in context; >> clarify the relationship between two or more persons, corporate bodies, >> works, etc.; or clarify the relationship between a person, corporate >> body, etc., and a name by which that person, corporate body, etc., is >> known (e.g., name used in religion versus secular name). >> >> >> >> >> >> >> >> >> >> Justify*:* Document the authority data creator’s reason for choosing the >> name or form of name on which a controlled access point is based. >> >> From Functional Requirements for Subject Authority Data (FRSAD) >> (http://www.ifla.org/en/node/1297) >> >> >> >> >> >> >> Find one or more subjects and/or their appellations, that correspond(s) >> to the user’s stated criteria, using attributes and relationships; >> >> >> >> >> >> >> >> Identify a subject and/or its appellation based on their attributes or >> relationships (i.e., to distinguish between two or more subjects or >> appellations with similar characteristics and to confirm that the >> appropriate subject or appellation has been found); >> >> >> >> >> >> >> >> >> >> >> >> >> >> Select **a subject and/or its appellation appropriate to the user’s >> needs (i.e., to choose or reject based on the user's requirements and >> needs); >> >> >> >> >> >> >> >> Explore **relationships between subjects and/or their appellations >> (e.g., to explore relationships in order to understand the structure of >> a subject domain and its terminology). >> >> >> >> Cheers >> >> Gordon >> >> >> >> >> >> >> On 07 July 2010 at 20:50 Karen Coyle <kcoyle@kcoyle.net> wrote: >> >> > After a quick first pass... I'd like to see an expansion of users from >> > "persons who are library users" to users like Amazon and LibraryThing, >> > who make use of bibliographic data for non-library purposes. (When >> > talking about LLD, I have taken to say that the "machine" is the Web, >> > the user is anyone on the web.) >> > >> > kc >> > >> > Quoting Emmanuelle Bermes <manue.fig@gmail.com>: >> > >> > > Dear all, >> > > >> > > In order to prepare tomorrow's meeting, I invite you to check the >> work >> > > that has been carried out by our little subgroup (mainly by Stu, >> > > actually !) regarding understanding the UC approach better. >> > > It would be nice to have an opportunity to discuss these >> categories or >> > > dimensions during the call, using the wiki page as a starting point. >> > > >> > > >> > > Cheers >> > > Emmanuelle >> > > >> > > [1]http://www.w3.org/2005/Incubator/lld/wiki/Dimensions >> > > >> > > >> > >> > >> > >> > -- >> > Karen Coyle >> > kcoyle@kcoyle.net http://kcoyle.net >> > ph: 1-510-540-7596 >> > m: 1-510-435-8234 >> > skype: kcoylenet >> > >> > > > >
Received on Thursday, 8 July 2010 13:08:14 UTC