LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  July 2003

MODS July 2003

Subject:

Re: New schema and citation changes

From:

Doug <[log in to unmask]>

Reply-To:

Metadata Object Description Schema List <[log in to unmask]>

Date:

Thu, 17 Jul 2003 23:29:32 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (58 lines)

Okay, so the documents of the ISO 15924 committee which are bilingual:

<titleInfo>
        <title>Information technology ___ Code for the representation of the names of scripts, FDIS</title>
</titleInfo>
<titleInfo>
        <title>Technologies de l___information ___ Code pour la représentation des noms d___écritures, FDIS</title>
</titleInfo>
<identifier type="uri">http://www.evertype.com/standards/iso15924/document/fdis15924.pdf</identifier>

You know, and I know that one of these is English and the other French. Further, at one level, its beside the point what languages these are! They are simply the two, equally valid, titles of the one work.

But, look at the identifier tag. It is also equally obvious that the identifier is an uri (url). That http:// gives it away every time ;-)
Yet we still include the type, why? Three reasons, I would suggest:
1) tradition, from the early days of digital metadata and metalanguages reduntant information has always been provided when possible, perhaps to encourage,
2) data granularity, what is obvious to one person may not be to another, the more forms or basic elements you can provide for any one piece of data, the more likely it will make sense to the broadest range of people/user agents, and this granularity or redundancy allows,
3) data checking and referential integrity and so on (as well as some level of data backup).

So, in the identifier tag is placed the type attribute information and an user agent may check that the data matches the type attribute and is an uri. Or it may, if http://, gopher://, file:///, mailto: etc is not present, it may still pass the information to a browser, because its been told its an uri. The browser is likely to automatically add the http:// and see what happens.

Or, in the case of the titles... say the title with the attribute xml:lang="fr" comes through and only the tag+attribute (xml:lang="en") comes through of the other title. A search on the French title finds nothing, but with just the attribute information, a search in an English language US library catalogue for "technology, information, code, representation, names, scripts" produces the record. Voila ;-) Information redundancy/granularity has won the day!!!

Far-fetched situation, I know, but illustrative of why language tags are important, at least in certain kinds of works.

Now, in the case of "Siddhartha"... leave out the lang attribute altogether or give it the xml:lang="en" attribute and value to indicate that this is meant as an English title.

In the Andy Warhol example <title xml:lang="de">, <title type="alternative" xml:lang="en">, and <language authority="iso639-2b">eng</language> gives a great summary of the basic ironies of this work!

Any attempt to categorize material, as you know, is fraught with "exceptions" because human data is always more messy and more subtle than any artificial data structure. But just because there are always exceptions doesn't (and shouldn't) stop us from trying. If it did we wouldn't be having this conversation <grin>.

So again, unicode is great. The case I presented with a word in greek script within the title is obvious in a unicode system. The <span> with language/script attributes is not necessary within a fully unicode cataloguing system. But adding this granularity to the data allows the citation software that has downloaded the catalogue record to render all <span> tags with language or script tags in an italic script if called upon in the style manual.

As in all cases, a particular library may choose not to use the language attributes, at all. It will still be legal MODS data. It will save the encoders time (and so the library will save money) and the bibliographers will spend more time adding the attributes! Likewise, the <span> tag could be ignored entirely, but the users of your library will certainly appreciate the additional data when it comes to forming bibliographies. And maybe the library catalogue will become a Rosetta Stone a hundred millenia from now, allowing the reconstruction of dozens of dead languages because all the translations and pieces of other languages are properly labelled!!!!!!!!!!!!!!!!!

Doug (only half kidding)

On Thu, 17 Jul 2003 10:44:50 -0700
Karen Coyle <[log in to unmask]> wrote:

> At 10:33 AM 7/17/2003 -0500, you wrote:
> >But if we are going to rely on unicode alone, then we might as well drop
> >the lang, xml:lang and script attributes completely!
>
> Unfortunately - or otherwise - you are talking to the person (moi) who
> argued against xml:lang in descriptive fields (which are those that are
> copied from the piece, such as author, title, publisher, etc.). What would
> you do with "Italian Cuisine" or "The Tao of Pooh"? What about a book title
> like: "Siddhartha"? I don't think we want folks to have to determine if a
> word that originates in another language is or isn't now considered part of
> English. And I also don't think we can expect people to make these
> distinctions for works in languages other than their own. Do you exclude
> proper nouns? Can you even positively determine what is a proper noun?
> Sometimes this is easy:
> Andy Warhol : Ausstellung der Deutschen Gesellschaft für Bildende Kunst
> Sometimes less so:
> On the effects of gypsum, or plaster of paris, as a manure;
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
November 2023
August 2023
July 2023
June 2023
November 2022
October 2022
September 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
May 2021
November 2020
September 2020
August 2020
July 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager