On Fri, 28 Jan 2005 12:07:30 -0500, Bruce D'Arcus <[log in to unmask]> wrote:
> On Jan 28, 2005, at 11:39 AM, Mike Rylander wrote:
> > instead of:
> >
> > <titleInfo type="uniform">
> >   <title>Harry Potter and the prisoner of Azkaban. Spanish</title>
> > </titleInfo>
> Why not:
> <titleInfo lang="es">
>    <title>Harry Potter and the prisoner of Azkaban</title>
> </titleInfo>
> ... ?
> It's easy to use XSLT to attach the word "Spanish" to output based on
> the lang attribute.

Unfortunately, because the definition of 240$I spells out the name of
the language one would need to create a map (translated for every
language) that maps to the ISO639-2b language encodings. That sounds
rather un-fun to me... :)

Perhap I shouldn't have used the tag name "lang" in my example.  To
match the symbolic name from marc more closely perhaps a
<languageOfWork> tag is more appropriate.

The point is that there are displayable fields, such as 240$I, that
could be separated easily, but for whatever reason are not.  I realize
that MODS is meant to be a simplification of marc, and that parsing
out fields such as the <extent> stuff that marc does not separate
isn't really a simplification (even though I'd like that particular
example to happen), but I'm not sure that loosing the ability to keep
descriptive elements (from the end users perspective) separated from
content is worth a few less tags.

Of course, take all of this with a grain of salt, since I'm just a
lowly developer trying to get work done with MODS...

Mike Rylander
[log in to unmask]
GPLS -- PINES Development
Database Developer