JTC1/SC22/WG15RIN-N051 JTC1/SC22/WG15-N215 (first part) ISO/IEC JTC1/SC22/WG15 RIN: POSIX Rapporteur Group on Internationalization Minutes of Stockholm meeting Date: Sunday 3rd November 1991 09:30-17:00 Monday 4th November 1991 09:30-17:00 Tuesday 5th November 1991 09:00-12:30 Location: Memory Hotel, Kista (Sunday) Electrum Conference Centre, Kista (Monday, Tuesday) Attendance: Ralph Barker (US) rapporteur Christian Brack (Germany) observer Patric Dempster (Canada) rapporteur Dominic Dunlop (UK) rapporteur John Hill (US) observer Jim Isaak WG15 convenor Akio Kido (Japan) observer Randall Howard (Canada) observer Hal Jespersen (US) observer Yashusi Nakahara (Japan) observer Paul Rabin (US) observer Nobuo Saito (Japan) rapporteur Keld Simonsen (Denmark) Rapporteur Donn Terry (US) observer Shin-ichi Yamada (Japan) observer 1. Opening of meeting. 1.1. Introductions and roll call of technical experts The meeting convened at 10:00. Those attending introduced themselves. (See list above.) Patric Dempster queried whether specific invitations could be issued to rapporteurs to attend RIN meetings, separate from the invitation to the main WG15 meetings, in order that he could justify the need for his attendance to CSA. Donn Terry pointed out that this was a general problem for all rapporteur groups, and should be raised in WG15 plenary. The group agreed. 1.2. Selection of chair, secretary & drafting committee Chair: Keld Simonsen Secretary: Dominic Dunlop Drafting: Ralph Barker, Yashusi Nakahara 1.3. Temporary document number assignment Temporary document numbers from the series SRTN (Stockholm RIN Temporary Number) were assigned to materials provided to those attending the meeting. 1.4. Adoption of agenda and allocation of documents on agenda A working agenda was accepted as appearing in attachment 1 to this document. Further levels of headings have been added in these minutes for ease of reference. Items 4.10 through 4.16 were added to the agenda appearing in N040. 1.5. Approval of minutes The minutes of the May 1991 Rotterdam meeting, as published in WG15 N170r, were accepted as a true record with the exception of these points: Under 1.2, Shigekatsu Nakao was not present. Yashusi Nakahara was on the drafting commitee. Under 3.2.1.5, those present could remember the outcome of the discussion on date formats (see secretary's note in minutes). The issue is discussed again under 4.14 in these minutes. Under 4.1.1, the sentence "Erik van der Poel was strongly against the inclusion of LC_CTYPE in the locale" should read "Erik van der Poel was strongly against the use of the '.codeset' part of XPG3's LANG, i.e. language[_territory[.codeset]]". Also, "Surely, he contended, the issues of character set and locale should be orthogonal" should read "Surely, he contended, the issues of coded character set and locale should be orthogonal" 2. Action item reports Keld Simonsen suggested that the group should have an issues log. There was some discussion of the function of such a log, where it should appear, and of whether the group has any issues suitable for such a log. See 7.3. Keld Simonsen also suggested a list of ongoing actions. Hal Jespersen proposed handling such things with resolutions charging people with particular responsibilities. It was agreed that open actions carried forward from one meeting to the next should not be renumbered, but should appear ahead of all actions resulting from a meeting. See 7.4.1. The group discussed resolutions from the 90-10 meeting which might have appeared in such a list, had one existed at the time: RIN 9010-15: Keld Simonsen: Pass additional materials on collating, such as further papers from Alain LaBonte of CSA, to Greger Leijonhufvud for use in production of future drafts of 1003.2. Complete. Apart from any other consideration, GL is no longer a member of the 1003.2 working group. Any future documents on this topic should be routed through the correct channel -- from WG15 to the US development body. RIN 9010-19: Nobuo Saito: Produce paper on issues of locale production for group. Closed by SRTN1 and SRTN5. Revision and possible merging of these documents may require further actions from this meeting. RIN 9010-20: Donn Terry et al: (Ongoing) Continue work on questionnaire. The minutes notwithstanding, it really was closed last time. See 4.3. RIN 9010-21: Donn Terry: Review following topics, and, where necessary, amend draft questionnaire to solicit specific information... [text omitted] Closed. RIN9105-1 All: critique new draft of questionnaire; respond by 1st August. Closed -- despite a disappointing lack of comment. See 4.3. RIN9105-2 All: Participate in UniForum/X/Open joint internationalization activity if sufficiently interested. Closed. Ralph Barker, Yashusi Nakahara, Keld Simonsen and Donn Terry have joined the e-mail list. Randall Howard also expressed an interest in joining. RIN9105-3 Donn Terry, Erik van der Poel, Yashusi Nakahara: Monitor progress of coordination ad hoc, ensuring that issues pertaining to national profiles are brought to the group's attention where appropriate. Closed. There has been no meeting as yet. The first formal meeting is scheduled for January 1992. Resolution 56 requests the Japanese delegation to act as informal liaison. RIN9105-4 Donn Terry: Circulate revised questionnaire document to group as soon as it becomes available. Closed. RIN9105-5 Donn Terry: Circulate revised tape archive format document to group as soon as it becomes available. Closed. This item has been circulated to e-mail list. RIN9105-6 Donn Terry: Circulate revision (action RIN9105-4 above) of questionnaire document to WG15 members for completion, and pass to Dick Weaver as an expert paper for consideration by WG20. Closed. See 4.3, action RIN9111-3. and resolution 55. RIN9105-7 Erik van der Poel: Circulate materials from PortSoft as they become available. Closed. Resolution 56, in effect, requests the Japanese member body to deliver future materials to RIN. RIN9105-8 Erik van der Poel: Determine whether substitute is necessary to implement Japanese collation. (See also RIN9105-20 below.) Closed. The substitute operation is not required -- see RIN N046. RIN9105-9 Erik van der Poel: Encourage production and contribution of national profiles by PortSoft members. Closed. RIN9105-10 Greger Leijonhufvud, Yashusi Nakahara: Do not require spelling out of ISO 646 invariant character names in locale guidelines; do not suggest in examples that this is necessary. Open. Carried forward as an action on Yashusi Nakahara alone. Hal Jespersen commented that a national body should make a comment to this effect in the CD 9945-2.2 ballot. RIN9105-11 Greger Leijonhufvud: Pass IEEE ballot objections to pax -e to Keld Simonsen for review. Open, pending discussion under 4.10. The action is transferred to Hal Jespersen. RIN9105-12 Keld Simonsen: Circulate organizations on Donn Terry's address list with RIN minutes; require organizations to let RIN know if they want minutes of future meetings; request them to send RIN their minutes. Open. RIN9105-13 Keld Simonsen: Continue collection of national profiles, locales and charmaps in electronic form. Closed. Resolution 57 resulted. RIN9105-14 Keld Simonsen: Formally submit for discussion at November meeting the proposal for 646 invariant character set support in 9945-2. (Already circulated by electronic mail.) Open. However, RIN N047 was circulated later in the meeting, closing this action. RIN9105-15 Keld Simonsen: Informally provide feedback on internationalization-related issues from SC22/WG21 (C++). Closed. See report under 5.2. RIN9105-16 Keld Simonsen: Introduce to WG20 the work done in RIN on short character names. Open. To be closed at WG20 meeting during week of 91-11-11. RIN9105-17 Keld Simonsen: Pass INSTA Swedish contact information to Greger Leijonhufvud. Closed. It is not clear that this has been done, but it has been overtaken by events, as Greger Leijonhufvud requires no futher input on collation. RIN9105-18 Keld Simonsen: Identify and report on activity on internationalization-related topics in SC18 and SC21. Closed. See report under 5.8. RIN9105-19 Keld Simonsen: Update wg15rin and i18n mail lists: add Randall Howard (and others). Closed. See also 4.15. RIN9105-20 Patric Dempster: Clarify, through discussion with Alain LaBonte, whether the CSA ordering standard requires the substitute operation. (See also RIN9105-8 above.) Closed. The substitute operation is not required. RIN9105-21 Patric Dempster: Propose a measurement unit questions which Donn Terry could incorporate in the questionnaire. Closed. See discussion under 4.3. RIN9105-22 Ralph Barker, Yashusi Nakahara: Synchronize the national profile related aspects, including definitions, of 1003.0 with the content of Draft guideline for national profile. Closed. Yashusi Nakahara has delivered comments; Ralph Barker considers that they have been acted upon. Donn Terry commented that the 91-11 WG15 plenary is to decide whether to propose 1003.0 as a DTR. RIN9105-23 Ralph Barker: Circulate copies of the internationalization section of 1003.0. Open. Replaced by action RIN9111-5. RIN9105-24 Ralph Barker: Circulate materials from UniForum/X/Open internationalization group, including problem statements relating to distributed locale and multi-byte support, as they become available. Open. Material on this topic has been posted to the XoJIG mailing list, but not cross-posted to RIN lists. RIN9105-25 Ralph Barker: Coordinate participation (item 5 above). Closed. (This should have read item 2.5 above). RIN9105-26 Ralph Barker: Request that a representative of X/Open Company Ltd. provides a report to RIN either in written form, or in person, at the next meeting of RIN. (Nobuo Saito's former action RIN9010-10) Closed. No public information is available beyond that provided through the joint UniForum / X/Open meetings: all other material, including interrim reports etc., is proprietary, so no report will be forthcoming. Keld Simonsen expressed disappointment at this situation. Hal Jespersen suggested that a written request for specific documents might produce more favourable results. Action RIN9111-14 resulted. RIN9105-27 Yashusi Nakahara: Add section discussing short character names to Draft guideline for national profile. Closed. But see also 4.1. RIN9105-28 Yashusi Nakahara: Add wording to Draft guideline for national profile stating that locales should be written so as to be independent of code set and that use of the codeset part of XPG's LANG specification should be avoided pending a more general solution to the problem of data announcement. Closed. But see also 4.1. RIN9105-29 Yashusi Nakahara: Check allowed format of charmap comments. Closed. ISO 2022 shifts can be used in comments. RIN9105-30 Yashusi Nakahara: If acceptable to national member body, distribute revisions to Japanese profile to mail list both in nroff output and in troff -mm source form. Closed. 3. Balloting activities 3.1. 9945-1 Ballot internationalization issues Donn Terry reported that there were no developments relating to 9945-1. Keld Simonsen queried whether there were any issues relating to date and timezone. Donn Terry and Hal Jespersen replied that the only issues related to these topics belonged to 9945-2. RIN can provide well-finished input to 1003.1A if it wishes. As Donn Terry is no longer US rapporteur, Ralph Barker is likely to take over his reporting role in future. He will also be able to comment on 1003.0, if this becomes an ISO project. A short discussion followed on the probable logistics of progressing 1003.0 to an ISO TR. 3.2. 9945-2 Ballot internationalization issues Hal Jespersen reported that a new 9945-2.2 CD, equivalent to IEEE P1003.2 draft 11, was in ballot until 92-02-14. Draft 12, reflecting ISO input, is likely to appear after 92-05. Provided that CD 2.2 passes ballot, draft 8 of 1003.2a will become a PDAM to DIS 9945-2. There was a discussion of issues of process, and the circulation of internationalization-related comments and ballot objections. Donn Terry proposed that these issues should be raised with the WG15 chair for discussion as to how best to handle them. Action RIN9111-6 resulted. 1003.2b is still under development in the IEEE working group, and is intended for clarifications, interpretations, and any issues coming out of ISO which would seriously slow the progress of 1003.2a if they were incorporated into that document. It will also address three further issues: the complaints of profilers that the optional parts of 1003.2a are too large -- they want a smaller granularity; synchronization with 1003.1a (primarily symbolic links), and possibly with 1003.14 (checkpointing); and pax. Patric Dempster queried the disposition of the programmatic interfaces in 1003.2. Were these to move into 1003.1? Hal Jespersen replied that they remained in 1003.2 for now, pending a TCOS project plan to develop a LIS for them, incorporate them into 1003.16, and so on. At that time, they will be eliminated from 1003.2. 4. New business 4.1. Example national profiles and locales 4.1.1. Japanese national profile Nabuo Saito introduced RIN N046, Japanese national profile, which was developed in parallel with RIN N045, Guidelines for national profiles. This accounts for possible inconsistencies between the current versions of these documents. Akio Kido summarized developments in RIN N046 since the preliminary draft seen by the group at its 91-05 meeting. In particular, the locale is now based around the new JIS X 0212 character set standard and the existing JIS X 0208 and JIS X 0201 sets, the combined repertoire tentatively being named EUJIS. Information about JIS X 0201, an ISO 646 variant, appears only as comments for information. The same applies to JIS X 0212, because not all hardware yet supports it. Mandating such support through the locale definition is a longer-term goal. Keld Simonsen queried this approach, saying that all information could safely be included, as JIS X 0212-related information would be ignored by implementations not supporting that code set. If the information were commented out, implementations supporting JIS X 0212 would not be able to use it. The inclusion of references to a particular code set in a locale does not mandate support for that code set, as references to DIS 10646 in DP 9945-2.2 illustrate. Yashusi Nakahara explained that the locale did not define a collation sequence, because of a lack of consensus in Japan, because of technical issues relating to the handling of the 16-bit-wide Western alphabets of existing code sets, and because of varying approaches to Western alphabets in Asia. Hal Jespersen expressed concern at the size of the Japanese national profile if the intention was to incorporate it into an annex of CD 9945-2. Also, the profile references ISO 9899, which no other part of 9945-2 does. Akio Kido thought that it was too early to include the Japanese profile in 9945-2, although the Danish information should remain there for the moment. It would be better to issue the Guidelines as a TR, with example profiles as annexes to that TR. At this time, Dominic Dunlop proposed, the Danish profile information should be moved from 9945-2 to an annex of the TR. The group agreed. Jim Isaak, who was sitting in at the meeting at that stage, suggested that, in liaison with WG20, WG15 should move forward towards the production of an NP for this TR. Further discussion suggested that two TR's were necessary: Guidelines for Locales, from WG20, and Guidelines for POSIX Profiles from WG15. Creation of a registry for locales through WG20 would be yet a third NP. Ralph Barker was very much against pushing too much work towards WG20, a group which had yet to meet. Dominic Dunlop and Jim Isaak pointed out that WG15 could initiate NPs to SC22, suggesting that either WG15 or WG20 could take responsibility. It would be politically better, however, first to request that WG20 forwards the NP. Resolution 58 and action RIN9111-16 resulted. Yashusi Nakahara introduced RIN N045, Guidelines for national profiles, and ran through the changes had been made relative the draft seen by the group at its 91-05 meeting. He also presented an open issues list: -- Relationship between AEP and National Profile (orthogonal?) -- Content and structure of National Profile document. Suggestion: 1. General 2. Registry of named objects 3. Parameters 4. Options 5. Errors and exceptions 6. Extensions 7. Data interchange Annex A. Informative references Annex B. Notes and rationale On the latter, Hal Jespersen suggested that the structure should follow TR10000 as closely as possible. The group was asked for its opinions on the conformance classes proposed in RIN N045 6.7, which add two new national body conforming classes to the three classes of 9945-1. The group felt that the approach was good and correct. 4.1.2. Guideline for national profiles Keld Simonsen presented RIN N044, Guideline for producing a national POSIX locale. UniForum and X/Open and DKUUG are working initially on providing a collection point for locales. DKUUG also provides ftp and e-mail access to locale definitions. The collection may be thought of as an an informal registry -- a registry not officially recognized by ISO/IEC. Several people considered the word 'registry' to be inappropriate -- the collection could contain alternative locale descriptions for the same locale, and could make no statement about which was definitive. A formal registry is a long-term goal, although it would be likely to be the province of SC22/WG20. Randall Howard queried the name space for locale names (point 7; head of page 3). Because it differs from the 9945-1 portable filename character set, locale names could not directly be used as file names on POSIX-conforming systems. Hal Jespersen also commented that the proposed inclusion of characters which were special to the 9945-2 shell was problematic. Keld Simonsen stated that his document was derived from X/Open deliberations, and ISO conventions, but was prepared to go along with the group's feeling that only the portable filename character set should be used. Action RIN9111-10 resulted. Yashusi Nakahara requested more explicit guidance on points 7-6, 7-9 and 7-10, so as to avoid very verbose names. Randall Howard pointed out that locale names might exceed the 9945-1 14-character minimum maximum filename length. While Ralph Barker wanted short names which would be guaranteed to fit within 14 characters, Dominic Dunlop and others considered this an unreasonable goal. After all, implementations could make more characters available through the use of subdirectories. Nabuo Saito asked about the criteria for deciding which of a number of alternative locale definitions in the collection for a given country or culture should be regarded as definitive. Dominic Dunlop maintained that, while a registry could be prescriptive on such matters, a collection could merely present the alternatives, and allow its users to make their own decisions. Action RIN9111-8 resulted. Resolution 58 is also relevant. It was agreed that item 12, which refered to the possibility of making a charge for the service, should be deleted, pending further research on the manner in which ISO registries are operated. Ralph Barker feared that, if X/Open offered a free service, it would encourage the submission of a very large volume of locale definitions. While this was desirable in that, for example, a large corporation might wish to a number of related locales for its own internal use, it would also be likely to work against harmonization. Yashusi Nakahara requested that more decriptive material be supplied for points 10-6 to 10-8. It was decided to register the document with the status of a discussion paper. DS will continue collecting locales according to its recommendations, pending production of a new draft after input from X/Open and UniForum. 4.1.3. Guideline for national locales The group discussed RIN N043, Operational rules for WG15RIN POSIX locales creation. The first issue raised was whether there was a need for this document to be separate from RIN N045. The group agreed that there was. Donn Terry pointed out that to combine them would provide additional input to SGFS -- input which it was not seeking, and which it might well find confusing. Initially at least, only information on profiles should be passed to SGFS. Randall Howard added that locale-related material could potentially be produced more quickly than solutions to the large problems related to profiling. It made sense to separate the two. Patric Dempster drew attention to the continuing confusion between national profiles and functional profiles. A clear definition of both was needed in order that we do not appear to be diverging from SGFS, and instead can synchronize with relevant aspects of that group's work. There was a need to explain this to SGFS, said Donn Terry, preferably in a one page document produced in time for its 92-06 meeting. Action RIN9111-9 resulted. Keld Simonsen maintained that there were three terms understood in RIN: profiles picking options from some base standard(s), international standardized profiles (ISPs), and national profiles. The group remained unconvinced. Yashusi Nakahara highlighted the importance of national profiles being internationally agreed, in order that the needs of a particular market could be addressed by suppliers from outside that market as well as from inside. Given suitable tools, these profiles could be used as starting points for pragmatic modification by commercial users, added Randall Howard. Hal Jespersen suggested dropping use of 'profile', as the true profiling content of a 'national profile' was small: most of the information is in the national locale definition. The selection of a particular national locale could be be one line of a short ISP. The elements of such a profile which corresponded to particular national interest were minimal or absent, so the concept of a national profile might turn out to be unnecessary. Dominic Dunlop pointed out that the locales could form a series of international standards, in the way that keyboards and the 8859 character sets already are. This would allow for international harmonization, despite the fact that a particular locale is predominently of interest to one country or cultural group. Alternatively, suggested Keld Simonsen, it could be done through a registry. Some did not see how a registry ensured harmonization. Keld Simonsen replied that his proposal covered this issue. There was a discussion of the manner in which locales should be related. Was it better to group locales for cultures having the same spoken language, or locales belonging to a given country? It was agreed that the former was a better idea, as (say) French locales would be likely to have a higher degree of commonality than Canadian locales, and could be created from a base French locale by short lists of differences. There would be a strong incentive to harmonize profiles in order that locales with differing base languages could be used together in a single territory. The group agreed to create the document, and forward it by appropriate channels to SGFS. Discussion then moved to the actual content of WG15RIN-N043, which Keld Simonsen stressed was a draft. He took the group through the document, rehearsing, in response to points raised from the floor, several of the issues raised, and the manners in which they had been addressed. In particular, the perceived benefits of the replace-after statement, defined in RIN-N035, were highlighted. U.S. and Canadian rapporteurs were not convinced -- they preferred that registered locales should be defined in full, rather than as a set of differences from some base locale. If the intention was to reduce the size of locale components, maintained Randall Howard, the group would do better to define ways of breaking complete locales into more manageable pieces, rather than means of defining one locale in terms of another. After all, the base locale modified by some change might not be available to a particular user for some reason: there is no normative requirement that any implementation should provide any particular locale. The process of developing full locales could also be made more tractable through use of the POSIX.2 tools. RIN could advise on this. Hal Jespersen pointed out that replace after was yet another potential change to the 9945-2.2 CD, and could delay progress. This would be highly undesirable. Keld Simonsen said that there was no need for the facility to be in the initial standard. Ultimately, it was agreed that Canada should take action RIN9111-17. Yashusi Nakahara pointed out that Japanese experience was also relevant --although solely character-code based collation was of little relevance to Japanese locales. However, Japan's first priority was RIN-N045, rather than the internal structure of locale definitions. The group agreed that the paragraph at the bottom of page 3 (The WG15RIN locale collection) should be cut down to nothing more than a cross-reference, as it dealt with matters addressed by WG15RIN-N044. Dominic Dunlop suggested that WG15RIN-N043 should be re-entitled Draft guideline for producing a national POSIX profile, as it was clear from discussion that it could not yet be regarded as definitive. With these changes, the document was suitable for registration. Donn Terry raised the issue of whether the intention of the group was to encourage or to discourage the development of a large number of possibly disparate locales. No consensus emerged. Dominic Dunlop queried which version of the 10646 document was being referenced in Collating specification considerations, page 3. Keld Simonsen replied that the Danish locale information in the current CD 9945-2.2 would have to be amended to reflect the new ordering of script types (that is, the relative ordering of Hebrew and Arabic scripts, for example) in the 91-09 DIS 10646. At the end of the discussion, Donn Terry pointed out that the group had spent a lot of time on this agenda item, and that it could not complete its agenda if all other items were discussed at this length. Patric Dempster suggested that discussion of each agenda item should be limited to 45 minutes, after which, if there were no resolution, matters should be referred to member bodies for comment. 4.2. Collection of national locales and profiles 4.2.1. Naming scheme for locales (national/application) Discussion of this item having already taken place in connection with 4.1 above, there was no further discussion. 4.3. Revised questionnaire Patric Dempster stated that research in Canada had revealed that the concept of a measurement locale was important, but potentially so difficult as to be insoluble. Donn Terry agreed. Because of the complexity of the issue, no changes for the existing questionnaire were suggested, however. The group agreed that the issue was in the province of WG20, now that that group existed. Action RIN9111-3 and resolution 55 resulted. 4.4. Invariant ISO 646 support Keld Simonsen noted that RIN-N047, A representation for the shell in ISO 646, had been distributed to the group a considerable time ago. He saw a considerable problem with processing old data encoded in 646 character sets. Hal Jespersen doubted that just fixing the shell, as suggested in the proposal, was sufficient to address the problem. Randall Howard suggested moving the problem of the representation of shell and other 9945-2 language programs using the ISO 646 invariant characters set to the issues list. Donn Terry said that he could accept this only if it was also an issue whether this was to be solved or not. Keld Simonsen accepted this. See 7.3, items 3 and 4. 4.5. Internationalization background paper There having been no feedback on Donn Terry's existing draft (distributed by e-mail), it was agreed that it should be registered on delivery as a RIN document. The group agreed that it should be forwarded to WG20 for information. Resolution 59 resulted. [Secretary's note: the document was subsequently registered as WG15-N214. It is probably no longer necessary to register it as a RIN document.] [RIN N053 resulted] 4.6. Byte terminology RIN-N039, Answers to questions about n-bit-byte and context, provoked the usual debate on the meaning of byte. The ISO 2382 definition of 04.05.07 was considered incorrect; that of 01.02.09 closer to our understanding. The group thought the current DP 9945-2 definition was better, although it required amendment to make it clear that bytes or sequences of bytes could be used to hold codes for control as well as graphic characters. Jim Isaak, looking in on the meeting, suggested that the group formulate resolution 60 for forwarding to WG15. 4.7. Second CD of 9945-2 Hal Jespersen stated that the purpose of this agenda item was to solicit feedback on the national body reviews of the CD. Keld Simonsen indicated that agenda items 4.10 through 4.14 were relevant. Patric Dempster stated that Canada was in two minds on the ballot. On the one hand, it wanted 9945-2 to go ahead; on the other, it was very disappointed that pax -e had been dropped from the draft. Canada's understanding when voting in favour of 9945-1 had been that functionality of this type would be included in 9945-2. There had, Canada considered, been insufficient rationale for its having been dropped. Action RIN9105-10 remains open. Hal Jespersen stated that there had been opposition in IEEE ballots, particularly on the grounds that the option addressed merely one small aspect of a much larger problem. 4.8. Extended identifiers Keld Simonsen introduced RIN042, ident entry in LC_CTYPE section of locales, which proposes the enriching of the set of characters allowed in 9945-2 little languages (shell, awk etc.). Yashusi Nakahara queried the time at which the C language isident(char) function, referenced in the document, will appear in an amendment to ISO 9899, and considered that RIN042 should not exclude the alternative more generic is(char, class) function. WG14 and WG21 had yet to reach consensus on the issue. It would be useful for WG15 to know more of the thinking of these groups. Hal Jespersen maintained that, in the light of historical practice, incorporation of the proposed functionality in 9945-2 little languages would be difficult. Besides, an issue such as this should have been raised during a review and comment period, not after the production of a draft to be balloted. Patric Dempster complained about a lack of information on the proposal, precluding discussion in Canada. Discussion of ISO process ensued. Donn Terry pointed out that isident() might have to cover different sets of characters when called from different languages: '-' is valid in a COBOL identifier, but not in many other languages. Yashusi Nakahara drew the group's attention to TR 10176, Guidelines for the preparation of programming language standards, which addresses the same issue as the current proposal. WG15 should wait until more conventional programming languages converged on a common response to the recommendations of the TR. Dominic Dunlop contended that it was premature to introduce this functionality to 9945-2 at this stage. Without support from any standard implementation language -- most notably from C -- it would not practically be possible to implement the functionality in 9945-2. Ralph Barker agreed. Donn Terry also had the feeling that security could be compromised by dynamic user changes to the set of valid identifier characters, just as security can be compromised by manipulation of the IFS environment variable. The functionality might also preclude the possibility of shell compilers. More investigation was necessary. John Hill, looking in on the meeting, queried whether any of the base documents for the current work of WG15 referred to internationalization requirements such as that proposed by RIN-N042. Keld Simonsen conceded that there were no such base documents. Ultimately, it was agreed to put this issue on the issues list, 7.3 (item 1). There were likely to be further requirements of the same general type which should also be on the list, forming, in effect, a base requirements document. The matter of forwarding a liaison statement to WG20, seeking its input was also discussed, but no action was taken. [Secretary's note: action was subsequently taken in the WG15 meeting of 91-11.] 4.9. Current state of ISO 10646 Keld Simonsen had distributed a brief report to the mail list. The current DIS (91-09-27) is very similar in its base plane to Unicode, the main difference being that there are more precomposed characters than in Unicode. No other planes are populated: there is no separate Japanese plane. At the recent SC22 plenary, a liaison statement from SC22 to SC2 expressed concern that the base plane now contained null (zero) octets, which would cause problems to C and POSIX. SC2's response points out that, in effect, the 10646 base plane uses 16-bit, not 8-bit bytes. Implementations could be upgraded to use the wider bytes. A two- to three-octet transformation mechanism specified in the DIS, offered an alternative solution. (See action RIN9111-7.) The group had reservations about this. John Hill wondered if SC2 realized what a threat this issue posed to the widespread acceptance of the proposed standard. Jim Isaak noted that SC22 had asked for feedback on the impact of the new 10646 DIS on SC22 projects, and as to whether acceptance of the new DIS would be likely to be slower than that of the old DIS. Certainly, the current situation suggested that WG15 experts should bring the problems to the attention of those balloting on DIS 10646 (which is not currently in ballot). Resolution 61 resulted from this discussion. 4.10. pax Keld Simonsen rehearsed the history of pax -e, and the Danish concerns. Patric Dempster also voiced Canadian concerns. Hal Jespersen stated that the option had been dropped from the current CD because of valid technical objections from a number of IEEE balloters. The import of these objections was that the proposed filename exchange solution involving charmap files was inappropriate and incomplete. An alternative proposal, based around ISO tape labels (ISO 1001), will appear in 1003.2b. However, as a considerable technical change, it is doubtful that it could be incorporated into a revision of the DIS. Donn Terry suggested that the Canadians' immediate problem could be solved by requiring support of ISO 8859-1 characters in filenames, rather than the minimum of ISO 646 support specified in the CD. Perhaps, added Dominic Dunlop, the CD could be reworded to give greater prominence to the possibility of making such a requirement. See related action RIN9111-18. In the face of continued complaints from Keld Simonsen, Donn Terry maintained that correct process had been observed, given that 9945-2 is the subject of national body development, and given the current synchronization plan. The pax -e proposal had not been prototyped, and its inclusion in the current CD would have been premature. A discussion of ISO balloting procedures and project timescales ensued. Dominic Dunlop suggested that filename exchange should be on the issues list, 7.3. The group agreed: it appears as item 2. It seemed that a primary reason for issues to get onto this list was the lack of a technology prototype. Ideally, someone should take an action to prototype a solution. Nobody stepped forward to do this. 4.11. Interface routines for locale and charmap Keld Simonsen introduced Danish suggestions for interface routines for locales and charmaps, adding that it was related to work in progress within X/Open. Donn Terry pointed out that, when a well-finished proposal corresponding was forthcoming, it should be accompanied by a statement justifying the requirement for such a facility. Given such justification, the facility appeared to him to be suitable as a component of a revision to 9945-1. 4.12. ISO/IEEE synchronization problems Keld Simonsen stated that DS is not happy with synchronization on 9945-2. Patric Dempster thinks that some of the problems are due to poor communication between WG15, member bodies, and the IEEE. The issue is to be discussed in WG15 plenary. 4.13. strxfrm Randall Howard gave the group background information on some Canadian concerns. The central issue is that Alain LaBonte wants the transformed form of the string produced by strxfrm to be externally visible, and hence the subject of standardization. Actual implementations use such a form internally, but these forms are not portable between implementations. Application portability would be enhanced if they were. Canada sought feedback from the group on whether such a proposal to WG15 would be considered reasonable by RIN. Several people pointed out that the issue was perhaps more related to the C standard than to POSIX -- despite its relationship to POSIX collation. If this were the case, the issue is properly the province of WG14. Keld Simonsen and Donn Terry's initial judgment was that standardization of the transformed format would not be immediately useful, and would meet considerable resistance from implementors. Action RIN9111-19 resulted. 4.14. Format of day field in date Keld Simonsen enumerated the format options to the date command. There was no way of getting out a day of the month or month number without left space fill. Danish orthography required such a format. One solution would be to add yet two more format letters, although he had no proposal. The group agreed that there was a problem. Action RIN9111-14 resulted. 4.15. Mailing list issues The new mailing list address is sc22wg15rin@dkuug.dk. Subscription requests should be sent to sc22wg15rin-request@dkuug.dk. While dkuug has set up ftp-accessible archives for other SC22 mail lists, this has not been done for the RIN list, as, in the past, copyright material (for example, IEEE documents) has appeared on this list. RIN members are allowed to see such documents; others are not. Dominic Dunlop suggested that non-anonymous ftp might be used, but would not be particularly secure. Hal Jespersen stated that the new IEEE copyright notice, which precluded paper or abridged electronic copies, probably covered the case. Actions RIN9111-1, RIN9111-4 and RIN9111-12 resulted. 4.16. Japanese CD 9945-2 concerns. Nabuo Saito presented a draft document, a precursor to a ballot comment on CD 9945-2. As development agency, the US undertook to give detailed consideration to this comment when it was received. The document was not registered because of its preliminary nature. 5. Liaison reports 5.1. Report on IEEE 1003.x internationalization status No discussion. 5.2. Liaison reports: SC22 5.2.1. WG20 (internationalization) This group meets in the week of 91-11-11. Keld Simonsen will attend. 5.2.2. WG21 (C++) The group meets in the week of 91-11-11 (concurrently with WG20). Keld Simonsen and SN will attend. 5.2.3. Special working group on character sets This activity has been moved into WG20. 5.3. TSG1 internationalization activity This group has been wound up. Its internationalization activity is now the responsibility of WG20. 5.4. UniForum / X/Open joint internationalization group The group is working on X Window and distributed locales. Material will be cross-posted to the sc22wg15rin mailing list where appropriate. 5.5. X/Open internationalization SN is no longer associated with this activity. Contact may resume as a result of Keld Simonsen' letter to Mike Lambert. 5.6. PortSoft No report. See, however, RIN-N033. 5.7. Nordic culture Keld Simonsen had nothing specific to report. 5.8. Other internationalization activity Keld Simonsen reported briefly on activity in SC18, including multi-media mail supporting extended character sets. 6. Review and approval of resolutions and action items On behalf of the drafting committee, Ralph Barker presented the draft resolutions. All were accepted with editorial and some substantive changes where appropriate, and appear as attachment 2 to these minutes. Action items are minuted under 7.4. 6.1. Recommendations for WG15 Resolutions 55, 58, 59, 60 and 61 address matters which require action by WG15. The group did not agree to forward any further matters to WG15 by any other route. 7. Closing procedures 7.1. Future meeting considerations -- request for invitations The group will next meet in New Zealand in conjunction with the WG15 meeting. Keld Simonsen considered that 2 1/2 days were needed. Following discussion, it was agreed to limit the meeting to the 1 1/2 days prior to the WG15 plenary, and to adopt procedures which could cut short prolonged discussion of agenda items, and prevent the unlimited extension of the agenda through the addition of new items at the meeting. [Secretary's note: WG15's subsequent decision to meet for four full days in New Zealand invalidates this plan. There is a need to schedule an alternative meeting. This could take place in conjunction with the 92-01 or 92-04 meetings of IEEE TCOS (92-01-13 - 17, Orlando, Florida; 92-04-06 - 10, Dallas, Texas).] Prior to the New Zealand meeting, suggested Yashusi Nakahara, the group should set itself a schedule for the discussion of agenda items by e-mail. See action RIN9111-11. No further meetings were scheduled. 7.2. Permanent document number assignment The following document numbers were assigned: N043 Denmark Operational Rules for the WG15RIN POSIX Locales Creation N044 Denmark Guideline for producing a national POSIX locale N045 Japan Guidelines for for national profiles N046 Japan Japanese national profile N047 Denmark A representation for the shell in ISO 646 N048 US Questionnaire N049 US 10646 issues background paper (see action RIN9111-21) N050 Dominic Dunlop Historical document register N051 Dominic Dunlop Stockholm minutes ) Also numbered N052 Dominic Dunlop Stockholm resolutions ) WG15-N215 N053 US Internationalisation background paper 7.3. Review of issues list It having been agreed at the meeting to create an issues list, the following issues were put on it. [Secretary's note: the group may care to restate these issues in the light of the WG15 recommendations on the format and content of its issues list.] 1. Definition of mechanisms allowing the use of extended character sets in 9945-2 language (sh, awk, make etc.) identifiers. 2. Definition of mechanisms for the interchange of filenames containing characters outside those those defined by the 9945-1 portable filename character set, or the invariant part of ISO 646. 3. Establishment of whether there is a requirement for a means of expressing 9945-2 language (sh, awk, make etc.) programs using only the characters defined by the invariant part of ISO 646. 4. Given that the resolution of issue 3 establishes that there is such a requirement, definition of mechanisms allowing the expression of 9945-2 language (sh, awk, make etc.) programs using only the characters defined by the invariant part of ISO 646. 7.4. Review of action items 7.4.1. Open actions from previous meetings The following existing actions were not considered closed. As a result of a decision taken at the meeting, they are carried forward without renumbering: RIN9105-10: Yashusi Nakahara: Do not require spelling out of ISO 646 invariant character names in locale guidelines; do not suggest in examples that this is necessary. This action was previously assigned to Greger Leijonhufvud as well as Yashusi Nakahara, but the group has taken a decision not to assign actions to those who are unlikely to attend RIN meetings. RIN9105-11: Hal Jespersen: Pass IEEE ballot objections to pax -e to Keld Simonsen for review. This is a reassignment of an action on Greger Leijonhufvud. RIN9105-12: Keld Simonsen: Circulate organizations on Donn Terry's address list with RIN minutes; require organizations to let RIN know if they want minutes of future meetings; request them to send RIN their minutes. RIN9105-14: Keld Simonsen: Formally submit for discussion at November meeting the proposal for 646 invariant character set support in 9945-2. (Already circulated by electronic mail.) This item was closed by action during the meeting: see RIN N047. RIN9105-16: Keld Simonsen: Introduce to WG20 the work done in RIN on short character names. It is likely that this item will be closed at the WG20 meeting of 91-11-11. RIN9105-23: Ralph Barker: Circulate copies of the internationalization section of 1003.0. Open. However, RIN9111-5 replaces this action. RIN9105-24: Ralph Barker: Circulate materials from UniForum/X/Open internationalization group, including problem statements relating to distributed locale and multi-byte support, as they become available. Material on this topic has been posted to the XoJIG mailing list, but not cross-posted to RIN lists or circulated on paper. 7.4.2. New action items RIN9111-1 All: Be aware of the need to include copyright notices where appropriate on material posted to the mail list. RIN9111-2 All: Consider and discuss (by e-mail if possible) the separation of national profile and locale. RIN9111-3 Donn Terry: Pass current copy of questionnaire to Keld Simonsen for forwarding to WG20. (Implements RIN resolution 55.) (Completed during WG15 plenary.) RIN9111-4 Hal Jespersen: Mail new IEEE copyright notice to Keld Simonsen. RIN9111-5 Hal Jespersen: Notify sc22wg15rin mail list when revised version of 1003.0 is available by FTP. RIN9111-6 Keld Simonsen, Yashusi Nakahara: Discuss with WG15 chair mechanisms for the timely circulation of internationalization-related ballot comments, and report back to group. RIN9111-7 Keld Simonsen: Copy SC22 liaison statement to WG2 on new DIS 10646, and SC2 response, to group. RIN9111-8 Keld Simonsen: Explore procedures for starting an ISO registry and report back to group. RIN9111-9 Keld Simonsen: Include on the 92-05 RIN agenda a discussion of contents of a one-page statement on national profiles to SGFS. RIN9111-10 Keld Simonsen: Inform XoJIG that RIN recommends that characters allowed in components of locale names should be confined to the 9945-2 portable filename character set. RIN9111-11 Keld Simonsen: Moderate e-mail discussion of 92-05 agenda items prior to the 92-05 meeting. RIN9111-12 Keld Simonsen: Prepend new IEEE copyright notice to existing IEEE materials in mail archive. RIN9111-13 Keld Simonsen: Publish details of ftp availability of mail archive. RIN9111-14 Keld Simonsen: Submit to IEEE for possible inclusion in 1003.2b a proposal for means of outputing non-space-padded date and month numbers from date command. RIN9111-15 Keld Simonsen: Write to Mike Lambert of X/Open requesting advance copies of X/Open internationalization guidelines as an aid to cooperation. The letter should also ask for contact person to be named, and state that X/Open is welcome to send an observer to any RIN meeting. RIN9111-16 Member bodies: Canvas opinion on need for NPs on national profiles, locales, and a registry, and report back to group. RIN9111-17 Patric Dempster, Randall Howard: Investigate the use of replace after for the production of Canadian locales with reference to the Danish locale in 1003.2 draft 11.2, annex F, and report back on whether they found its merits outweighed its disadvantages. RIN9111-18 Patric Dempster: Consult on acceptability within Canada of suggestion that support of 8859-1 character set in filenames by pax be specified by a Canadian profile as an interim solution to a more general problem; report back to group. RIN9111-19 Patric Dempster: Consult on acceptability within Canada of RIN response on strxfrm issues; report back to group. RIN9111-20 Ralph Barker: Create WG20 liaison statement relating to need for NPs on national profiles, locales, and a registry. (Completed during WG15 plenary.) RIN9111-21 Ralph Barker: Draft background paper on ISO 10646-related issues 7.5. Thanks to host Following a vote of thanks to SIS, the meeting host, the meeting closed at 13:20 on 91-11-05. ISO/IEC JTC1/SC22/WG15 RIN: POSIX Rapporteur Group on Internationalization Resolutions from Stockholm meeting JTC1/SC22/WG15RIN-N052 JTC1/SC22/WG15-N215 (second part) Note: These resolutions adopt a serial numbering scheme. For reference, resolutions from previous meetings may be considered to be renumbered as follows: Location Old nos. New nos. Copenhagen 1-15 1-15 Paris 1-24 16-39 London 1-9 40-48 Rotterdam A-B, W-Z 49-54 55. Forwarding of questionnaire to WG20 Whereas ISO/IEC JTC1/SC22/WG15/RIN has developed a draft internationalization questionnaire, which when completed by national bodies or other representative standards development organizations fully familiar with the IT requirements of a particular culture can assist in determining general internationalization interface and application portability requirements, and Whereas ISO/IEC JTC1/SC22/WG20 has embarked on the development of standards in the area of internationalization, Therefore, ISO/IEC JTC1/SC22/WG15/RIN requests that ISO/IEC JTC1/SC22/WG15 authorize and instruct its liaison to ISO/IEC JTC1/SC22/WG20 to transmit to ISO/IEC JTC1/SC22/WG20 the then current version of ISO/IEC JTC1/SC22/WG15/RIN's draft internationalization questionnaire (ISO/IEC JTC1/SC22/WG15 N217) for review and comment by ISO/IEC JTC1/SC22/WG20 and for their consideration in relation to their scope of work. 56. Informal liaison to PortSoft Whereas various members of the Japanese national delegation to ISO/IEC JTC1/SC22/WG15/RIN attend meetings of and participate in the activities of PortSoft, Therefore ISO/IEC JTC1/SC22/WG15/RIN requests that the Japanese national delegation to ISO/IEC JTC1/SC22/WG15/RIN act as an informal liaison between PortSoft and ISO/IEC JTC1/SC22/WG15/RIN. 57. Collection of locales Whereas ISO/IEC JTC1/SC22/WG15/RIN has determined that it is beneficial to the IT community for national profiles, locales and corresponding charmaps to be collected and made available in electronic form to persons within the IT community and national bodies as samples of such documents, Therefore, ISO/IEC JTC1/SC22/WG15/RIN requests that Keld Simonsen collect national profiles, locales and corresponding charmaps and make same available in electronic form to interested persons or national bodies on an on-going basis, subject to the availability of necessary computer and network resources. 58. Request to WG20: possible new internationalization-related projects Whereas, the Japanese rapporteur to ISO/IEC JTC1/SC22/WG15/RIN, has submitted a draft Guideline for Producing a national POSIX Locale (JTC1/SC22/WG15RIN N045) and various sample national profiles have also been submitted, including the Danish and Japanese national profile (JCT1/SC22/WG15RIN N012, N046), to ISO/IEC JTC1/SC22/WG15/RIN for review and comment and consideration in connection with other ISO/IEC JTC1/SC22/WG15/RIN work, and Whereas ISO/IEC JTC1/SC22/WG15/RIN has determined that publication of said national locales as a Technical Report, and the publication of the Japanese National Profile, the Danish National Profile, together with other national profiles which might be available, as a separate Technical Report would be desirable for the purpose of providing sample national profiles and locales which could act as guidance to other national bodies in the development of their national profiles and locales, or other organizations developing locale definitions, and Whereas ISO/IEC JTC1/SC22/WG15/RIN has determined, in concert with the UniForum and X/Open internationalization working groups, that in order for locales to interoperate properly, particularly in a networked or distributed computing environment, a locale registry procedure would be desirable to assure that a precise definition of a locale that would be known network wide, Therefore, ISO/IEC JTC1/SC22/WG15/RIN requests that ISO/IEC JTC1/SC22/WG15, through its liaison to ISO/IEC JTC1/SC22/WG20, request the following determinations from ISO/IEC JTC1/SC22/WG20: 1) Does ISO/IEC JTC1/SC22/WG20 wish to sponsor an NP for the new work item of the publication of national POSIX locales, including the Japanese national locale and other national locales then available, as a Technical Report, or does ISO/IEC JTC1/SC22/WG20 prefer that such work be sponsored by ISO/IEC JTC1/SC22/WG15? 2) Does ISO/IEC JTC1/SC22/WG20 wish to sponsor an NP for the new work item of the publication of a collection of National Profiles, including the Japanese National Profile, and other national profiles then available, as a Technical Report, or does ISO/IEC JTC1/SC22/WG20 prefer that such work be sponsored by ISO/IEC JTC1/SC22/WG15? 3) Does ISO/IEC JTC1/SC22/WG20 wish to investigate the development of an international locale registry that would satisfy the requirements of national bodies and users, and sponsor any new work item that may result from such investigations, or does ISO/IEC JTC1/SC22/WG20 prefer that such work be done by ISO/IEC JTC1/SC22/WG15? 59. Input to WG20: internalization background paper Whereas ISO/IEC JTC1/SC22/WG15/RIN has developed a technical paper which provides an overview of the technical issues of internationalization, as related to the work of ISO/IEC JTC1/SC22/WG15, and, Whereas ISO/IEC JTC1/SC22/WG20 may find an already existing technical paper which provides an overview of certain of the technical issues involved in internationalization to be useful in their work, ISO/IEC JTC1/SC22/WG15/RIN requests that ISO/IEC JTC1/SC22/WG15 forward the ISO/IEC JTC1/SC22/WG15/RIN background paper on internationalization to ISO/IEC JTC1/SC22/WG20, through the ISO/IEC JTC1/SC22/WG15 liaison to ISO/IEC JTC1/SC22/WG20, for their consideration. 60. Input to SC1: definition of byte Whereas ISO/IEC JTC1/SC22/WG15/RIN has determined that inconsistencies exist between various ISO standards as to the definition of the word byte, and that such inconsistencies may adversely affect the functionality and portability of applications within the POSIX environment, ISO/IEC JTC1/SC22/WG15/RIN requests that ISO/IEC JTC1/SC22/WG15 forward the following liaison statement to ISO/IEC JTC1/SC1: The following is a suggestion for the definition of byte, as a refinement of the definition appearing in ISO DIS 2382-1 (ISO/IEC JTC1/SC1 N1176) together with the one appearing in CD 9945-2.2. We have examined several ISO standards and found inconsistencies with the use of the word, and recommend the following definition which appears to capture all the critical characteristics and is still not too narrow. byte: An individually addressable unit of data storage consisting of a string of a number of bits. It may be used to store a character or a portion of a character; The number of bits within a byte may vary between system implementations. The least significant bit is called the low-order bit; the most significant is called the high-order bit. The definition of byte in the new Part 1 (01.02.09) is generally consistent with this definition but equates byte with character exactly. However, equating bytes and characters disallows the concept of multibyte character that appears in ISO 2022. Some definitions of byte have, in the past, equated it with octet (exactly 8 bits). This does not work on some architectures, as the natural size of a byte may be other than 8 bits and this is acknowledged in newer definition. (For consistency with 9989, 9945-2.2 also sets a minimum size of a byte as 8.) 61. Input to SC2: concern at direction of DIS 10646 Whereas ISO/IEC JTC1/SC22/WG15/RIN has noted significant difficulties involving ISO/IEC 10646, as mentioned in the exchange of liaison statements between ISO/IEC JTC1/SC22 and ISO/IEC JTC1/SC2 mentioned below, Therefore ISO/IEC JTC1/SC22/WG15/RIN requests that ISO/IEC JTC1/SC22/WG15 resolve as follows: Whereas ISO/IEC JTC1/SC22, pursuant to its resolution AY of its September 1991 meeting (Vienna), forwarded a liaison statement to ISO/IEC JTC1/SC2 indicating concerns regarding changes to the then current DIS ISO/IEC 10646, and Whereas ISO/IEC JTC1/SC2 forwarded a response to ISO/IEC JTC1/SC22 in ISO/IEC JTC1/SC2 document N 2301 (October 1991), Therefore WG15 notes that most existing implementations and applications of 9945 (POSIX) will not support the canonical form of ISO 10646 as a coded character set without fundamental modifications. We also expect this to be true of the ISO/IEC 9899 C standard. (The programming language in which most existing POSIX systems are implemented.) Adoption of 10646 with full interoperability between new applications and existing applications will be impossible without, at a minimum, recompilation after at least some modification. Although this modification is expected to be small at the source level, it will result in significantly different object code. Additionally, an assumption on the part of an operating system that 10646 is in use is likely to render existing binary applications unusable. Since users (and consequently vendors) are seriously concerned with the issue of backwards compatibility of both source and binary applications, introduction of 10646 in a form which affects both C and 9945 applications will significantly reduce the likelihood of adoption of 10646 on systems which use either one or both of C and 9945. It is to be noted that insisting that zero octets can be used as part of a coded character in 10646 may simplify some problems, but it appears to be a significant problem for other communities. Further evaluation of the relative costs to the industry and its installed base of users is necessary to evaluate this properly. All national bodies are asked to take this into account, and to determine the relative cost of such decisions as part of that process. 62. Thanks The JTC1/SC22/WG15 Rapporteur Group on Internationalization thanks Ann Flod and other members of the staff at SIS for making the meeting arrangements. The JTC1/SC22/WG15 Rapporteur Group on Internationalization thanks Mr. Keld Simonsen for chairing the meeting. The JTC1/SC22/WG15 Rapporteur Group on Internationalization thanks Mr. Dominic Dunlop for acting as secretary for the meeting. The JTC1/SC22/WG15 Rapporteur Group on Internationalization Mr. Ralph Barker, and Mr. Yasushi Nakahara for participating on the Drafting Committee.