There are situations where we want to be able to distinguish between the work and the expressions of a work.
What other works has this person created (I don’t care what they may have translated or edited)?
What languages has this work been translated into?
Which works have as their subject this other work?
Answering these questions without the level of abstraction provided by Work would seem to be a more complex process.
Collection Metadata Standards Manager
Tel: +44(0)1937 546669
ISNI: 0000 0001 1825 6037
Since are talking BIBFRAME, what is the opinion of LC?
What definition of Work will give the best results for the community that actually needs to use this data to actually do something useful?
· Cataloging. Is it really to the benefit of catalogers that the Work be split (or not split)?
· Work information as used by collection management or acquisition
· The rest of the world
From: Bibliographic Framework Transition Initiative Forum
[mailto:[log in to unmask]]
On Behalf Of Simon Spero
Sent: 26 January, 2017 00:44
To: [log in to unmask]
Subject: Re: [BIBFRAME] Work record(s) that have Instances with more than one language
FRBR's treatment of a translation as creating a new FRBR expression of a FRBR work is indeed at variance with the use of the notion of work in copyright law (where a translation is the canonical example of a derivative work in 17 USC 101 and Berne convention).
There is a good case to be made that translations are composite works consisting of the original content together with the intellectual work of the translator; however there is a case to be made that this approach is not optimal for grouping or discovery.
The boundary of work and expression became blurred as the IFLA process ground on. It is probably better to unpack and formalize the concepts rigorously, and only then define any simplified models (which is what I think is meant by indecs abstractions being fuzzy and context sensitive).