As part of the VIAF project, we spend massive amounts of time trying to
parse names.  They are *not* broken into separate fields.  Last name?
One part, two part, more parts to that last name?  Is it Beethoven or
van Beethoven?  Names in some cultures are *really* complicated, but
they are all jammed into a single subfield with some minimal punctuation
to separate them.  Good enough for a card and usually good enough for a
display, but really tough for smart machine processing.

That's just the most common composed field.  There are many others.
Break them apart.


-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum
[mailto:[log in to unmask]] On Behalf Of Trail, Nate
Sent: Tuesday, January 29, 2013 10:00 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] Punctuation

If it's in a MARC record, there's no need to guess, because the
subfields are already parsed parts. Title proper is 245$a, subtitle is
245$b, etc.

Nate Trail
Network Development and MARC  Standards Office Technology Policy Mail
stop 4402 Library Services Library of Congress
[log in to unmask]

-----Original Message-----
From: J. McRee Elrod [mailto:[log in to unmask]]
Sent: Monday, January 28, 2013 5:22 PM
To: Trail, Nate
Cc: [log in to unmask]
Subject: Re: [BIBFRAME] Punctuation

>Maybe I'm missing something, but if we capture each subelement in it's 
>own property, there'd be no need to parse a long string with ISBD 
>punctuation.You'd know exactly what was in each, even if you didn't 
>have a display system.

If it is in Chinese characters,  I don't know where the place ends and
the publisher begins, nor where the title proper ends and subtitle
begins.  I only got up the 300 characters and gave up.

   __       __   J. McRee (Mac) Elrod ([log in to unmask])
  {__  |   /     Special Libraries Cataloguing   HTTP://
  ___} |__ \__________________________________________________________