ISO/IEC JTC 1/SC34 N0xxx

ISO/IEC JTC1/SC34/WG2 N256

ISO/IEC JTC 1/SC34

Information Technology --
Document Description and Processing Languages

TITLE: SC34 Secretariat's report on the discussion for dual-numbered publication
SOURCE: SC34 Secretariat
PROJECT: ID: is9541-4
PROJECT EDITOR:
STATUS: Document for the SC34/WG2 meeting in Boston
ACTION: For information
DATE: 2006-12-03
DISTRIBUTION: SC34, SC34/WG2 and Liaisons
REFER TO:
REPLY TO: Dr. James David Mason
(ISO/IEC JTC 1/SC 34 Chairman)
Y-12 National Security Complex
Bldg. 9113, M.S. 8208
Oak Ridge, TN 37831-8208 U.S.A.
Telephone: +1 865 574-6973
Facsimile: +1 865 574-1896
Network: masonjd@y12.doe.gov
http://www.y12.doe.gov/sgml/sc34/
ftp://ftp.y12.doe.gov/pub/sgml/sc34/

Mr. G. Ken Holman
(ISO/IEC JTC 1/SC 34 Secretariat - Standards Council of Canada)
Crane Softwrights Ltd.
Box 266,
Kars, ON K0A-2E0 CANADA
Telephone: +1 613 489-0999
Facsimile: +1 613 489-0995
Network: jtc1sc34@scc.ca


SC34 Secretariat's report on the discussion for dual-numbered publication

*********************************************************************************************** From: "G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager" <jtc1sc34 at scc.ca> To: "Lisa A.Rajchel" <lrajchel at ansi.org>; "Keith Brannon" <brannon at iso.org> Cc: "Yushi Komachi" <komachi at y-adagio.com>; "Dana Holmes" <dholmes at ansi.org>; <scott.jameson at hp.com>; "James D. Mason" <masonjd at y12.doe.gov> Subject: Status of joint 9541-4 and 14496-22 progress Date: 2006-11-27, 0:20 Hello Lisa and Keith, I hope this note finds you well. The next meeting of SC34/WG2 is coming up in a week's time, and I still am not in a position to advise WG2 regarding the progress of the joint work of two projects from two committees: 1) JTC 1/SC 34/WG 2 - 9541-4 - Information technology - Font information interchange - Part 4: Open Font Format 2) JTC 1/SC 29/WG 11 - 14496-22 - Information technology -- Coding of audio-visual objects -- Part 22: Open Font Format We have received two pieces of conflicting instruction regarding how we are to progress. On February 9[1] we were given the clearance to progress 9541-4 as a dual-numbered standard joint with 14496-22 under a single title. This was sent to all SC34 members on February 20 and accepted with only a comment from Canada that this was unusual and possibly the source of confusion. With the support of other SC34 members, however, we decided to proceed. On March 27[2] and April 27[3] and June 13[4] we asked for direction, and on June 25[5] we were informed that we could not continue 9541-4 as a dual-numbered standard joint with 14496-22 under a single title. I replied the following day June 26[6] that in fact these do not have different scopes and they are the same document, but this has not been replied to yet. I have asked for guidance on this September 5[7] and October 31[8] without any response. So, we have heard that we can and that we cannot proceed as has been agreed by SC34 members. How can I advise SC 34/WG 2 to progress their work next weekend at their upcoming meeting? Thank you for any help you can be. . . . . . . . . . . Ken [1] >From: Lisa Rajchel <lrajchel at ansi.org> >To: "'G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretary'" <jtc1sc34 at scc.ca>, > Dana Holmes <dholmes at ansi.org> >Cc: "James D. Mason" <masonjd at y12.doe.gov>, > Yushi Komachi > <komachi at y-adagio.com> >Subject: RE: Initiating a project for a dual-numbered standard >Date: Thu, 9 Feb 2006 12:32:20 -0500 > >Ken, > >Your proposed approach is fine. > >Regards, > >Lisa > >-----Original Message----- >From: G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretary [mailto:jtc1sc34 at scc.ca] > >Sent: Thursday, February 09, 2006 9:17 AM >To: Lisa A.Rajchel; Dana Holmes >Cc: James D. Mason; Yushi Komachi >Subject: Initiating a project for a dual-numbered standard > >Good morning Lisa and Dana, I hope this finds each of you well. > >To accommodate a situation where two subcommittees have similar >objectives, we intend to begin a subdivision of 9541 to introduce >9541-4 to be the SC34 name for a single dual-numbered standard that >SC29 names 14496-22, both under the identical title "Open Font >Format" (since it is, indeed, a single document). > >Are there any special procedures, or do we just follow Directives >9.3? Because it is just a subdivision on our part, could we simply >follow Directives 6.2.2, add it to our programme of work and submit >the subdivision to JTC1 for approval? > >We would like to do this immediately rather than wait for our next >plenary session, so we will okay the subdivision at the SC34 level by >asking P-members to vote on the subdivision using an SC34 document >with an SC34 resolution that I'll distribute to members and ask for a >response (should be quicker than a formal NP). > >Weighing the above, I'll go ahead with the document resolution and >P-member vote, instead of a formal NP, unless you advise otherwise. > >Thanks for any guidance and clarification! > >. . . . . . . . . . . . . . Ken >-- [2] >Date: Mon, 27 Mar 2006 08:04:10 -0500 >To: Atlab <atlab at iso.org> >From: "G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretary" <jtc1sc34 at scc.ca> >Subject: RE: JTC 1 N 8040 & N 8041 >Cc: "'Brannon Keith'" <brannon at iso.org>, "'Dana Holmes'" <dholmes at ansi.org> > >Thank you, Ali! >... >I note that our count of active projects in our respect records >matches, except for the new challenge of recording the new >subdivision of 9541. This is a project that will produce a >dual-numbered document. > >The work was initiated in SC29 and found to be in overlap with SC34 >and the compromise reached was to have a project from each >subcommittee reference the work to assist people in each domain to >independently find the work. > >I'm not sure if I should just point our 9541-4 in SC34 to the >database record #43466 for 14496-22 in SC29, or if we should >duplicate the information for 14496-22 in a new record for 9541-4. > >Thanks for any guidance! > >. . . . . . . . . . . Ken [3] >Date: Thu, 27 Apr 2006 09:38:26 -0400 >To: Maho Takahashi <takahashi at iso.org>, "'G. Ken Holman - ISO/IEC >JTC 1/SC 34 Secretary'" <jtc1sc34 at scc.ca> >From: "G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretary" <jtc1sc34 at scc.ca> >Subject: Re: JTC 1/SC 34 Project --- POSSIBLE AUTOMATIC CANCELLATION >(2 and 5 YEAR RULES) >Cc: Atlab <atlab at iso.org>, brannon at iso.org, Takahashi Maho ><takahashi at iso.org>, Steve Pepper <pepper at ontopia.net>, James D. >Mason <masonjd at y12.doe.gov> >... >We maintain our programme of work at: > > http://www.jtc1sc34.org/document/secretariat_temp.html#pow > >You can see perusing this list that the only project for which we do >not have an ISO database entry number is the SC34/WG2 joint >9541/14496-22 project done in conjunction with SC29/WG11. [4] >Date: Tue, 13 Jun 2006 23:12:24 -0400 >To: Abdelali Atlab <atlab at iso.org> >From: "G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager" ><jtc1sc34 at scc.ca> >Subject: Programme of work items for SC34 >Cc: Keith Brannon <brannon at iso.org>, Maho Takahashi <takahashi at iso.org> > >Hello Ali, Keith and Maho! > >Regarding our programme of work, I have some maintenance questions >and we have a new project amendment. > >First, the amendment is 9541 Amd. 4: > > http://www.jtc1sc34.org/document/secretariat_temp.html#is9541-1a4 > >Next, how do we update the ISO catalogue with the new dual-numbered >standard ... for now I'm just pointing 9541-4 to the database entry >for 14496-22: > > http://www.jtc1sc34.org/document/secretariat_temp.html#is9541-4 > >http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43466&scopelist=PROGRAMME > > >Lastly, how do I go about producing a Technical Corrigendum to 19757-2/Amd 1? > >Thanks for your guidance! > >. . . . . . . Ken [5] >Date: Sun, 25 Jun 2006 14:27:35 +0200 >From: Brannon <brannon at iso.org> >Subject: RE: Programme of work items for SC34 >To: "'G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager'" > <jtc1sc34 at scc.ca>, > Projects <projects at iso.org> >Reply-to: brannon at iso.org >Organization: ISO > >Ken, >Ihave noted the new Amd 4 to ISO/IEC 9541 and am copying this to projects >for inclusion in the database. >Concerning your other question no IS carries two project numbers.Both are >separate projects even if the content is similar.You also need to have >different scopes. >Regards >Keith [6] >Date: Mon, 26 Jun 2006 18:35:49 -0400 >To: brannon at iso.org, Projects <projects at iso.org> >From: "G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager" ><jtc1sc34 at scc.ca> >Subject: RE: Programme of work items for SC34 >... >>Concerning your other question no IS carries two project numbers. > >But this was the action indicated to us by Lisa ... below is the >email in February and we have been working on this premise ever since. > >My only question now is how to reflect this in the ISO database. > >>Both are >>separate projects even if the content is similar.You also need to have >>different scopes. > >They do not have different scopes. This is one document that is to >be considered both a project of SC34/WG2 and SC29/WG11. > >Below the message from Lisa is the message from Jim to Scott and >Lisa bringing this issue up. > >Thanks, Keith. > >. . . . . . . . . Ken [7] >Date: Tue, 05 Sep 2006 15:28:02 +0200 >From: Hops <hops at iso.org> >Subject: RE: REMINDER - ISO/IEC CD 18048 >To: "'G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager'" > <jtc1sc34 at scc.ca> >Cc: takahashi at iso.org, brannon at iso.org >Reply-to: hops at iso.org > >Dear Ken, > >Thanks for the prompt reply.I'm afraid I cannot help in sorting this ou >without Keith, who is now on holiday to return on 28 Sept. I am putting a >print-out of this email on his desk to draw his attention on return. > >Best regards. > >Brenda >******************************* > >-----Original Message----- >From: G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager >[mailto:jtc1sc34 at scc.ca] >Sent: 2006-09-05 15:12 >To: hops at iso.org >Cc: brannon at iso.org; takahashi at iso.org >Subject: Re: REMINDER - ISO/IEC CD 18048 > >Hello Brenda, >... >p.s. and we are still unaware of the CS handling of the situation indicated >by JTC 1 for the joint publishing of 9541-4 and 14496-22 as instructed by >the JTC 1 secretariat [8] >Date: Tue, 31 Oct 2006 11:00:26 -0500 >To: brannon at iso.org >From: "G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager" ><jtc1sc34 at scc.ca> >Subject: Re: FW: extensions jtc1 sc 34 >Cc: James D. Mason <masonjd at y12.doe.gov>, Steve Pepper ><pepper at ontopia.net>, Yushi Komachi <komachi at y-adagio.com>, Martin >Bryan <martin at is-thought.co.uk> > >Good morning, Keith, >... >BTW, not mentioned in your summary is the situation we find >ourselves in with respect to 9541-4 and 14496-22 ... we received >authorization from JTC 1 Secretariat that we progress this work as a >jointly-numbered standard and have been working that way for quite a >while ... correspondence from you indicated this was not possible, >yet we have already been working this way. I still do not have >clear direction on how to proceed. > >Thanks again, Keith! > >. . . . . . . . . . Ken -- G. Ken Holman Crane Softwrights Ltd. ISO/IEC JTC 1/SC 34 Secretariat Standards Council of Canada Committee correspondence: mailto:jtc1sc34 at scc.ca Committee website: http://www.jtc1sc34.org Corporate correspondence: mailto:gkholman at CraneSoftwrights.com Corporate website: http://www.CraneSoftwrights.com/a/ *********************************************************************************************** From: "Lisa Rajchel" <lrajchel at ansi.org> To: "G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager" <jtc1sc34 at scc.ca>; "Keith Brannon" <brannon at iso.org> Cc: "Yushi Komachi" <komachi at y-adagio.com>; "Dana Holmes" <dholmes at ansi.org>; <scott.jameson at hp.com>; "James D. Mason" <masonjd at y12.doe.gov> Subject: RE: Status of joint 9541-4 and 14496-22 progress Date: 2006-11-27, 4:34 Keith, Please reply. Lisa -----Original Message----- From: G. Ken Holman - ISO/IEC JTC 1/SC 34 Secretariat Manager [mailto:jtc1sc34@scc.ca] Sent: Sunday, November 26, 2006 10:19 AM To: Lisa A.Rajchel; Keith Brannon Cc: Yushi Komachi; Dana Holmes; scott.jameson@hp.com; James D. Mason Subject: Status of joint 9541-4 and 14496-22 progress ***********************************************************************************************