LISTSERV mailing list manager LISTSERV 16.0

Help for ISOJAC Archives


ISOJAC Archives

ISOJAC Archives


ISOJAC@LISTSERV.LOC.GOV


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

ISOJAC Home

ISOJAC Home

ISOJAC  August 2007

ISOJAC August 2007

Subject:

Re: First round of changes for ISO 639-3 review period over REPLIES REQUESTED

From:

Milicent K Wewerka <[log in to unmask]>

Reply-To:

ISO 639 Joint Advisory Committee <[log in to unmask]>

Date:

Wed, 1 Aug 2007 11:25:52 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (253 lines)

Would it be possible to rename the element grc as pre-modern Greek? That would encompass the forms of the language that are currently using that code element. In a sense this would be broadening the denotation as Peter mentioned below. Of course that might mean that ISO639-3 would need two additions--one for medieval (gkm) and another that is specifically restricted to the ancient time period. How exact do we need to be in defining the time periods?

Milicent Wewerka, Library of Congress
 

>>> "Patton,Glenn" <[log in to unmask]> 08/01/07 10:58 AM >>>
I agree with Peter's concern about 'grc'. For bibliographic records
(and I looked at a bunch this morning), I believe we'd be faced with a
situation in which it would often be difficult to determine (based on
the data in the records) what the correct coding should be. For
example, I saw a number of microforms of manuscripts created in the 12th
century. It seems to me that one could not automatically assume that
the correct coding would become "gkm" because the text of the manuscript
might reflect the characteristics of the earlier form of Greek. A
cataloger might be able to make the determination at the point of
cataloging but one could only guess if a conversion of existing records
were undertaken.
 
--Glenn

________________________________

From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]] On Behalf
Of Peter Constable
Sent: Tuesday, July 31, 2007 11:20 PM
To: [log in to unmask]
Subject: Re: [ISOJAC] First round of changes for ISO 639-3 review period
over REPLIES REQUESTED



Broadening the denotation of an ID is not a breaking change, in the
sense that existing records tagged with (e.g.) "eus" continue to be
correctly and as-optimally tagged after the merger.

 

It is narrowing of a denotation that would be a breaking change; e.g.,
splitting Ancient Greek in a way that narrows the time-depth varieties
over which "grc" applies would mean that some unknown number of records
tagged with "grc" would suddenly become incorrectly tagged when the
change takes place.

 

 

Peter

 

From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]] On Behalf
Of Joan Spanne
Sent: Tuesday, July 31, 2007 12:42 PM
To: [log in to unmask]
Subject: Re: First round of changes for ISO 639-3 review period over
REPLIES REQUESTED

 


Peter and Milicent responded to my memo of 9 July, but no one else has
commented. I think I answered their specific issues, but my answers also
pointed out where discussion is still needed.

Action is awaiting on:

2006-080 <http://www.sil.org/iso639-3/chg_detail.asp?id=2006-080>

bej

Beja

Add Bedawiyet

2006-090 <http://www.sil.org/iso639-3/chg_detail.asp?id=2006-090>

ile

Interlingue

Add Occidental


(these are both 639-2 code elements, where these changes came about
through interaction with -3 code elements)

and on these:
2006-118 <http://www.sil.org/iso639-3/chg_detail.asp?id=2006-118>
bsz Souletin Basque Merge Merge into [eus] Basque
2006-119 <http://www.sil.org/iso639-3/chg_detail.asp?id=2006-119>
bqe Navarro-Labourdin Basque Merge Merge into [eus]
Basque
I did not ask for JAC input on this before, as both code elements being
retired are only in 639-3, but on further consideration, I decided to
bring it up, since [eus] is in 639-2, and this could be considered
broadening the denotation of [eus] Basque, based on the interpretations
taken for the three code elements when 639-3 was drafted.

And the two tough ones:

2006-084 <http://www.sil.org/iso639-3/chg_detail.asp?id=2006-084>

gkm

Medieval Greek

add code element


this affects [grc] Classical Greek, in particular. See Peter and
Milicent's memos for discussion (split / macrolanguage / collection are
the readily apparent possible answers).

2006-129 <http://www.sil.org/iso639-3/chg_detail.asp?id=2006-129>

cat

Catalan

Catalan

Catalan (macrolanguage)

2006-129

cat

Catalan

Individual language

Macrolanguage

2006-129

cln

Catalan (individual language)

2006-129

vac

Valencian


I have not heard anything favorable toward Valencian as a separate code
element from the JAC, and I also think Valencian does not warrant a code
element on linguistic grounds, and the sociolinguistic landscape is too
uneven to grant one on sociolinguistic grounds. Is that the JAC
concensus? If so, how is the response to be made? (The decision to
consider Valencian at all was based on the recommendation they were
given last year when their request to 639-2 was denied.)

For those of you away from the office but able to briefly reply, when
will you be returning to work to take up these questions?

-Joan




Milicent K Wewerka <[log in to unmask]>
Sent by: ISO 639 Joint Advisory Committee <[log in to unmask]>

2007-07-23 12:32 PM

Please respond to
ISO 639 Joint Advisory Committee <[log in to unmask]>

To

[log in to unmask]

cc


Subject

Re: First round of changes for ISO 639-3 review period over

 






I have two comments on the changes to ISO639-3 as proposed in your
document.

Request 2006-084 for a new code element for Medieval Greek (gkm):
Adopting this addition will make it necessary to revised the captions
for identifiers grc and ell/gre. Those identifiers are part of ISO
639-2.

Request 2006-127 for a new code element for Katso (kaf): This may be
the same language as Kaduo (ktp).


Milicent Wewerka, Library of Congress


>>> Joan Spanne <[log in to unmask]> 07/09/07 5:54 PM >>>
Hello All,

The first round of change requests for ISO 639-3 underwent review from
April 1 - June 30. As expected, not many received any comments, though
the
Valencian request received 43 comments alone (5 other change requests
received one comment each), about 1/4 opposed and 4/5 in favor
(including
a form letter sent in by 9 people).

I am attaching a document that is my report on the changes, with
summaries
and recommendations. Three code elements affected are in both Part 2 and

Part 3. The changes to these are summarized first in the report. The
rest
of the report contains summaries of all other changes (those affecting
only Part 3).

Obviously action on the three code elements in both parts will require
agreement of the JAC. In addition, though, I would appreciate a review
of
the other proposed changes, as it is just possible that one or more of
them might have some effect on Part 2 that I had not foreseen.

To see the actual change request documentation, use this pattern for the

link:

http://www.sil.org/iso639-3/chg_detail.asp?id=2006-129
where the parameter at the end is the change request number.

In order to minimize delay in posting the results of the requests (at
least for those only pertaining to part 3), I would appreciate a
response
by July 18th, if possible. Debate on the Valencian - Catalan matter may
take longer, of course. For more on that matter, please see my message
dated 13 Apr 2007.

Thanks,

Joan Spanne
ISO 639-3/RA
SIL International
7500 W Camp Wisdom Rd
Dallas, TX 75236
[log in to unmask]

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

April 2021
January 2021
November 2020
June 2020
May 2019
February 2019
September 2018
April 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
May 2016
April 2016
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
October 2013
September 2013
August 2013
July 2013
May 2013
April 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
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 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
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 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
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
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager