LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


MODS@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  November 2002

MODS November 2002

Subject:

Re: language attributes for MODS element.

From:

Karen Coyle <[log in to unmask]>

Reply-To:

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

Date:

Sat, 9 Nov 2002 15:37:59 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (52 lines)

Zhang, referring to your points below, (which are very clear, thank you) I
do need to ask something. My own knoweldge of the languages we refer to in
US library work as "CJK" (Chinese, Japanese, Korean) is practically nil but
I've read the descriptions of how they were rendered in Unicode and was
given the impression that:

1) You can tell what language group you are in based on the Unicode hex
value range in the data. So for a given field, you can tell whether it is
Chinese or Japanese, for example. Is this not true?

2) That there is some ambiguity with a set of characters called the "CJK
unified ideographs" or "Han" segment of Unicode. This segment is used in
all three languages although the meanings of the ideographs depends on the
context of the language using it. The display of the glyphs, however, is
the same in all three languages. But you seem to be saying that this isn't
the case (your #3).

I'm trying to think of situations with Western European languages where
either indexing or display would depend on knowing which language I was
processing. The only thing I can think of is sorting, since I've heard that
some languages use different sort orders for accented characters. Are there
other instances where knowing the language is key to processing?

kc

At 10:06 AM 11/8/2002 -0800, you wrote:
>Why we need so many language indicator for the metadata?
>
>1, for the user you intended to serve: for people who do not understand
>Japanese or Chinese, how can they know what data is in what language for
>those field inside of the  record?
>
>2. For search to work correctly: how the system index those data correctly?
>Index Chinese data with Japanese or index Japanese data with Chinese will
>only produce incorrect search result.
>
>3. for library system to work correctly: if you put Chinese data in Japanese
>font, or Japanese data in Chinese font, you will offend either side of
>users, it is incorrect and is culture sensitive issues. It will tell user
>how poor is this system being designed.
>
>4. most importantly, for globe information access: the same material should
>be matched up by any metadata search that carry the original vernacular
>representation no matter where the metadata is being made. (This issue is
>very close to the topic of next year IFLA)

*********************************************
Karen Coyle           [log in to unmask]

            http://www.kcoyle.net
**********************************************

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

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
https://listserv.loc.gov/cgi-bin/wa?A2=ind0211&L=MODS&P=13057
listserv.loc.gov
crawl=CC-MAIN-2020-10
56240
application/http; msgtype=response
sha1:AV62UZDCBYXDOZIFWAAR7NC6IRW6QBL5
<urn:uuid:29fe89e0-354f-4e35-9592-da6142652a7a>
2020-02-18T17:20:24Z
140.147.55.47
text/html
sha1:NOHQG3DDBKEOKSQ2Y3BZUC7BQKH7HPGG
<urn:uuid:ba407954-b199-47ef-8e61-ec1cd1a6eaa6>
https://listserv.loc.gov/cgi-bin/wa?A2=ind0211&L=MODS&P=13057
response
<urn:uuid:3babec5a-d502-4bd1-85d1-ed973f2de932>
isPartOf: CC-MAIN-2020-10
publisher: Common Crawl
description: Wide crawl of the web for February 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-52.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/