SC22/WG15 US TAG N295 SC22/WG15 SD-3 Proposed Mar 17, 1992 WG15 Issues List (Draft Proposal) The issues list below is maintained by the meeting Vice Chair for each meeting, in accordance with WG15 Nxxx, which describes the procedures for maintaining it. At this time, no permanent documents have been used to record closed issues. This paragraph will in the future record the permanent document numbers should this occur. 1. RIN input to WG20 [Resolved]. Keywords: RIN, Internationalization, WG20, multi-lingual. Description: Proposed WG on internationalization should have input from RIN, but it isn't formed yet. How to address liaison statements. Originator: RIN (6/90) Alternatives: WG15, 6/90: Wait until group is formed, then send liaison statement. Keep as issue until completed. Arguments: None. Resolution: WG15, 06/91: Send liaison statement to WG20 now that it is formed. History: This issue was raised at the WG15 Paris meeting when the Rapporteur Group on Internationalisation requested WG15 (RIN 027 refers) to advise the new SC22 working group on Internationalisation about the problems of multi-lingual and multi-directional presentation issues, eg numbers in Hebrew text. There was uncertainty on how to proceed this issue at the time. This issue was closed at the Rotterdam meeting, where the issues list was reviewed. It was noted that the problem can be forwarded to SC22/WG20, now that it has been 'formed'. See WG15 resolution 133: 133 Recommendation to WG20 Whereas ISO/IEC JTC1/SC22/WG20 is newly formed for internationalization under ISO/IEC JTC1/SC22, and Whereas a Rapporteur Group for Internationalization (RIN) has been formed in ISO/IEC JTC1/SC22/WG15 with active participation from the National Bodies, and Whereas ISO/IEC JTC1/SC22/WG15 work such as ISO/IEC 9945-2 has introduced a suitable set of internationalization features including, but not limited to, the following: - date and time format - numeric and monetary representation - collation - character map - character classification - national locales - national profiles, and Whereas ISO/IEC JTC1/SC22/WG15 believes that the RIN work also would be useful for the work of ISO/IEC JTC1/SC22/WG20, Therefore ISO/IEC JTC1/SC22/WG15 requests that ISO/IEC JTC1/SC22/WG20 work with ISO/IEC JTC1/SC22/WG15/RIN to agree how to best move work in these areas forward. This action was reviewed at the WG15 meeting, Stockholm, as 9105-08: "Convenor: Forward WG15RIN-N027 to WG20, Internationalisation, and to SC2, SC18, and SC20. (Arises from discussion of issues list item, "multi - lingual, multi - directional presentation", under agenda item 2.2.) Status: Done." 2. Documenting National Profiles. [Open] Keywords: National Profiles, Profiles, internationalization Description: Where should National Profiles be documented: - an annex devoted to Profiles in the Standard, or... - in a separate TR? Originator: WG15 (06/90) Alternatives: Unknown: (06/90) A proposed resolution was to generate an Annex to 9945 which was devoted to profiles. It is unknown whether this solution was formally adopted. Ad-hoc: (05/91) Need a separate document, as all national profiles would be too large a set. Arguments: None Recorded, but see history for background. Resolution: Open. History: The issue was revisited at the Rotterdam meeting, where the following action item was approved: 9010-9: RIN & convenor: POSIX National Profiles. Seek guidance from Rapporteur Group on Internationalization on improvements to the practice of WG15's handling of POSIX National Profiles. (9006-37) Open pending start of activity by SC22/WG20. Becomes 9105-2. An ad-hoc group on (Profile?) Coordination also fed into the Rotterdam WG15 Plenary, where Arnie Powell reported that: "The break-out group was of the opinion that standards documents should not contain copies of all applicable national profiles; there was need of guidance from JTC1/SGFS on the the format of profile standards. (See resolution 117.) Jim Isaak commented that "they will not have any idea what [a national profile] is", so they would have to be fully briefed before being able to deliver useful guidance. Although no specific action arose, Willem Wakker is to coordinate with SGFS. (See also [Rotterdam minutes] 6.3, and actions 9105-7 and 9105-30.)" [Rotterdam also passed resolution 117 on visiting this item in the Issues list, but this is concerned largely with SGFS coordination.] Rotterdam resolution 156 also refers to this issue: 156 Synchronizing National Profiles Whereas ISO/IEC JTC1/SC22/WG15 understands that synchronization problems may arise if National Profiles are included in multiple POSIX standards documents, Therefore ISO/IEC JTC1/SC22/WG15 instructs its Convenor to review this issue and seek comment from the IEEE Standards Department as to how this might be addressed and to report back the findings to ISO/IEC JTC1/SC22/WG15 at the next ISO/IEC JTC1/SC22/WG15 meeting. 3. Disposition of Canadian Comment, 9945-1. [Open] Keywords: 9945-1, Canada, internationalization, interchange. Description: Tar and cpio interchange formats are not adequate for international work. However, normative changes are a problem at this time for 9945-.1 Originator: WG15 (Canada) (06/90) Alternatives: WG15 (6/90): hold as open issue until changes can be addressed. Arguments: None recorded. Resolution: Open, pending technical resolution. History: The disposition of comments (N085) item 6 addressed Canadian comments by suggesting additional text to 9945-1.2 section 10 lines 80-81 and 102-104 (tar) and lines 270-272 (cpio). However, the changes were considered to be normative and therefore could not be endorsed for inclusion in the 9945-1 standard at the time the issue was entered. The proposed resolution was to include the proposed changes in the next amendment to 9945-1. It is unknown whether this solution was formally adopted. 4. Publication of responses to Ballot comments [Resolved] Keywords: ballot responses, NPs Description: A concern about the visibility of responses to ballots returned to SC22, they should be cireculated to WG15 as they become available. Originator: WG15 (05/91) Alternatives: None proposed. Arguments: Resolution: Resolved by SC22 disposition of NPs. History: This issue was first raised at WG15's Rotterdam meeting: Comments in the Rotterdam minutes on this item noted that: "in order that WG15 member's concerns about the visibility of responses to ballots returned to SC22, these responses will be circulated to WG15 as they become available in future." 5. CD 9945-2.2 Document not identified [Resolved] Keywords: CD 9945-2.2 Description: When will 9945-2.2 become available? Originator: WG15 (05/91) Alternatives: US: (05/92) When the IEEE 1003.2 document becomes sufficiently stable. WG15: (05/92) Move to issues list. Arguments: None recorded. Resolution: Closed by SC22 N1063 History: This issue was first raised at WG15's Rotterdam meeting: This was formerly action 9010-7, but was moved to the issues list pending a decision by the US member body that 1003.2 has become stable enough for submission. As well as being required for CD registration, it is also required for liaison with SC2 on character set issues.