Karen Coyle said:
>A step related to RDA in which RDA is defined as data elements that can
>be encoded for processing should allow literals for all data elements,
>but should be defined in such a way that non-literals could be used for
>any data element.
Assuming "literal" translates to "transcribed" and "nonliteral"
translates to a pointer such as an ASN or url, then I question that
*any* element may be non-literal. Among those which must be literal
in my view are title as on the item, statement of responsibility as on
the item, series as on the item, and probably imprint as on the item.
Tom Jones may author one work, translate another, and be the criminal
defendant for yet another. Coded relationships (MARC 100$e or $4) do
not replace the infinite variety of possible statements of
responsibility. That transcribed statement of responsibility is
needed, regardless of Mr. Jones being in prime entry as a non-literal
value, with granularity allowing one to display "Tom Jones" in direct
order.
Lubetzky notwithstanding, some redundancy is built into what we do.
__ __ J. McRee (Mac) Elrod ([EMAIL PROTECTED])
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__________________________________________________________
