INTERNATIONAL ORGANIZATION FOR STANDARDIZATION

ORGANISATION INTERNATIONALE DE NORMALISATION

ISO/IEC JTC 1/SC 2/WG 2

Universal Multiple-Octet Coded Character Set

(UCS)

ISO/IEC JTC 1/SC 2/WG 2 N1402

1996-08-19


Title: Principles and Procedures for Allocation of New Characters and Scripts and handling of Defect Reports on Character Names (Revised N 1352)



Source: Ad hoc group on Principles and Procedures - Messrs.
V.S. Umamaheswaran, Sven Thygesen, Peter Edberg


References: N 946, N 995 (section 9-a-i.3), N 1002, N 1061, N 1117, N 1118, N 1137 and N 1203 (section 6.1, 6.2 and 10.1.2), N1218, N1352.

Action: To be considered by SC 2/WG 2 and all potential submitters of proposals for new characters to the repertoire of ISO/IEC 10646


Distribution: ISO/IEC JTC 1/SC 2/WG 2, ISO/IEC JTC 1/SC 2 and Liaison Organizations


This document was originally prepared by Mark Davis, Edwin Hart and Sten G. Lindberg, as document N 946 (dated 11 October 1994), based on N 884 (authored by Rick McGowan and Joe Becker). It has been enhanced by an ad hoc group on principles and procedures set up at the San Francisco SC 2/WG 2 meeting no. 26, The result was presented as SC2/WG 2 N1116. At the Geneva SC 2/WG 2 meeting no 27, where some enhancements were proposed. The result was presented as SC2/WG 2 N1202. At the Helsinki SC 2/WG 2 meeting no 28, some enhancements were proposed and adopted. The result was presented as SC2/WG 2 N1252. The document was accepted, following Resolution M28.6 at that meeting.

This document contains a new Annex C: " Description of the UCS work flow and stages in progression from initial proposal to final publication". It was discussed at the meeting in Québec 1996-08-12/16.

Furthermore a new question has been included in the proposal summary form. It reads:

C. Technical - Justification

10. Does the proposal contain characters with any special properties such as control function or similar

semantics? _____________
If YES, describe in detail (include attachment if necessary) _____________




Principles and Procedures

for Allocation of New Characters and Scripts

I. Goals for Encoding New Characters into the Basic Multilingual Plane

A. The Basic Multilingual Plane should contain all contemporary characters in common use:

Generally, the Basic Multilingual Plane (BMP) should be devoted to high-utility characters that are widely implemented in some form of communication system. These include, for example, characters from hard copy typographic systems that are awaiting computerization, and characters recognizable and useful to a large community of customers. The "utility" of a character in a computer or communications standard can be measured (at least in theory) by such factors as: number of publications (for example, newspapers or books) using the character, the size of the community who can recognize the character, etc. Characters of more limited use should be considered for encoding in supplementary planes, for example, obscure archaic characters.

B. The characters encoded into the Basic Multilingual Plane will not cover all characters included in future standards:

It is not necessary, though it may often be desirable, that all characters encoded in future international, national, and industry information technology and communication standards be included in the BMP. The first edition used characters from pre-existing standards as a means of evaluating the established utility as well as ensuring compatibility with existing practice. Characters encoded in future standards may or may not have proven utility, and may or may not establish themselves in common use.

II. Character Categories

SC 2/WG 2 will use the following categories to aid in assessing the encoding of the proposed characters.

A. Contemporary

There exists a contemporary community of native users who produce new printed matter with the proposed characters in newspapers, magazines, books, signs, etc. Examples include Burmese, Maldivian, Syriac, Yi, Xishuang Banna Dai.

B.1 Specialized (Small Collections of Characters)

The characters are part of a relatively small set. There exists a limited community of users (for example, liturgical) who produce new printed material with these proposed characters. Generally, these characters have few native users, or are not in day-to-day use for ordinary communication. Examples include Javanese, Pahlavi...

B. 2 Specialized (Large Collections of Characters)

The characters are part of a relatively large set. There exists a limited community of users (for example, liturgical) who produce new printed material with these proposed characters. Generally, these characters have few native users, or are not in day-to-day use for ordinary communication. Examples include personal name ideographs, Chu Nom, Archaic Han.

C. Major Extinct (Small Collections of Characters)

The characters are part of a relatively small set. There exists a relatively large body of literature using these characters, and a relatively large scholarly community studying that literature. Examples include Etruscan, Linear B.

D. Attested Extinct (Small Collections of Characters)

The characters are part of a relatively small set. There exists a relatively limited literature using these characters and a relatively small scholarly community studying that literature. Examples include Samaritan, Meroitic.

E. Minor Extinct

The characters are part of a relatively small set. The utility of publicly encoding these characters is open to question. Examples are Khotanese, Lahnda.

F. Archaic Hieroglyphic or Ideographic

These characters are part of a large set (for example, 160 or more characters) of hieroglyphic or ideographic characters. A large character set is almost by definition obscure, since it is difficult to obtain information or agreement on the precise membership of the set. Examples include Lolo, Moso, Akkadian, Egyptian Hieroglyphics, Hittite (Luwian), Khitan, Mayan Hieroglyphics, Nuchen.

G. Obscure or Questionable Usage Symbols

The characters are part of a small or large collection that is not yet deciphered, or not completely understood, or not well-attested by substantial literature or the scholarly community. Or they are symbols that are not normally used in in-line text, that are merely drawings, that are used only in two-dimensional diagrams, or that may be composed (such as, a slash through a symbol to indicate forbidden). Examples include logos, pictures of cows, circuit components, weather chart symbols.

III. Procedure for Encoding New Characters and Scripts

The following defines a procedure with criteria for deciding how to encode new characters in ISO/IEC 10646. This procedure shall be used for new scripts only after thorough research into the repertoire and ordering of the characters within the script.

See submitter's responsibilities and the attached Proposal Summary Form in Annex A.

SC 2/WG 2 Evaluation Procedure

In assessing the suitability of a proposed character for encoding, SC 2/WG 2 shall evaluate the credibility of the submitter and then use the following procedure:

1. Do not encode.

a) If the proposed character is a (shape or other) variation of a character already encoded in ISO/IEC 10646 and therefore may be unified, or

b) If the proposed character is a presentation form (glyph), variant, or ligature, or

c) If the proposed character may be better represented as a sequence of ISO/IEC 10646 encoded characters.

2. Suggest use of the Private Use Area

a) If the proposed character has an extremely small or closed community of customers, or

b) If the proposed characters are part of a script that is very complex to implement and the script has not yet been encoded in ISO/IEC 10646 (the private use area may be used for test and evaluation).

3. Encode on a supplementary plane

a) If the proposed character is used infrequently, or

b) If it is part of a set of characters for which insufficient space is available in the Basic Multilingual Plane.

4. Encode on the Basic Multilingual Plane

a) If the proposed character does not fit into one of the previous criteria (1, 2, or 3), and

b) If the proposed character is part of a well-defined character collection not already encoded in ISO/IEC 10646, or

c) If the proposed character is part of a small number of characters to be added to a script already encoded in the Basic Multilingual Plane of ISO/IEC 10646 (for example, the characters can be encoded at unallocated code positions within the block or blocks allocated for that script).

Principles and Procedures

for Handling Defect Reports on Character Names

In principle, the Character Names in the standard are not to be changed. However, there may be situations where changes, deletions or annotations to names of characters may be warranted. Requests for changing of Character Names may be issued as defect report. The principles of dealing with such defect reports by SC 2/WG2 are described in Annex B.


Annex A

INFORMATION ACCOMPANYING SUBMISSIONS

The process of deciding which characters should be included in the repertoire of ISO/IEC 10646 by SC 2/WG 2 depends on the availability of accurate and most comprehensive information about any proposed additions. SC 2/WG 2, at its San Francisco meeting 26, designed a form (template) that will assist the submitters in gathering and providing the relevant information, and will assist SC 2/WG 2 in making more informed decisions. This form is included in the following pages of this annex.

Each new submission must be accompanied by a duly completed proposal summary form to assist SC 2/WG 2 to better evaluate the requirements and towards a speedier acceptance of the submission. Submitters are also requested to ensure that a proposed character does not already exist in ISO/IEC 10646.

If a submission has already been made prior to the existence of the proposal summary form, the submitter(s) is requested to re-evaluate the submission for completeness using the form as a template, and either provide reference(s) to existing information or provide additional information.

Submitter's Responsibilities

The national body or liaison organization (or any other organization or an individual) proposing new character(s) or a new script shall provide:

1. Proposed category for the script or character(s), character name(s), and description of usage.

2. Justification for the category and name(s).

3. A representative glyph(s) image on paper:
if this glyph image is similar to a glyph image of a previously encoded ISO/IEC 10646 character, then additional justification for encoding the new character shall be provided.

4. Mappings to accepted sources, for example, other standards, dictionaries, accessible published materials

5. Computerized/camera ready font:
prior to the preparation of the final text of the next version of the standard a suitable computerized font (camera ready font) will be needed. Camera ready copy is mandatory for final text of any pDAMs before the next revision. Ordered preference of the fonts: True Type, PostScript or 96x96 bit-mapped format. The minimum design resolution for the font is 96 by 96 dots matrix, for presentation at or near 22 points in print size.

6. List of all the parties consulted.

7. Equivalent glyph images:
if the submission intends using composite sequences of proposed or existing combining and non-combining characters, a list consisting of each composite sequence and its corresponding glyph image shall be provided to better understand the intended use.


ISO/IEC JTC 1/SC 2/WG 2
PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS
FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646

Please fill Sections A, B and C below. Section D will be filled by SC 2/WG 2.

A. Administrative


1. Title:




2. Requester's name:


3. Requester type (Member body/Liaison/Individual contribution):


4. Submission date:


5. Requester's reference (if applicable):


6. (Choose one of the following:)
This is a complete proposal: ; or,
More information will be provided later:


B. Technical - General


1. (Choose one of the following:)

a. This proposal is for a new script (set of characters):
Proposed name of script:

b. The proposal is for addition of character(s) to an existing block:
Name of the existing block:


2. Number of characters in proposal:


3. Proposed category (see section II, Character Categories):


4. Proposed Level of Implementation (see clause 15, ISO/IEC 10646-1):
Is a rationale provided for the choice?
If Yes, reference:


5. Is a repertoire including character names provided?:

a. If YES, are the names in accordance with the 'character naming guidelines' in Annex K of ISO/IEC 10646-1?
b. Are the character shapes attached in a reviewable form?


6. Who will provide the appropriate computerized font (ordered preference: True Type, PostScript or 96x96 bit-mapped format) for publishing the standard?

If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools used:


7. References:
a. Are references (to other character sets, dictionaries, descriptive texts etc.) provided?

b. Are published examples (such as samples from newspapers, magazines, or
other sources) of use of proposed characters attached?


8. Special encoding issues:

Does the proposal address other aspects of character data processing (if applicable) such as input, presentation, sorting, searching, indexing, transliteration etc. (if yes please enclose information):


C. Technical - Justification



1. Has contact been made to members of the user community (for example: National Body, user groups of the script or characters, other experts, etc.)?

If YES, with whom?
If YES, available relevant documents?


2. Information on the user community for the proposed characters (for example: size,
demographics, information technology use, or publishing use) is included?
Reference:


3. The context of use for the proposed characters (type of use; common or rare)
Reference:


4. Are the proposed characters in current use by the user community?
If YES, where? Reference:


5. After giving due considerations to the principles in N 1352 must the proposed
characters be entirely in the BMP?
If YES, is a rationale provided?
If YES, reference:


6. Should the proposed characters be kept together in a contiguous range (rather than
being scattered)?


7. Can any of the proposed characters be considered a presentation form of an existing
character or character sequence?
If YES, is a rationale for its inclusion provided?
If YES, reference:


8. Can any of the proposed character(s) be considered to be similar (in appearance or function) to an existing character?
If YES, is a rationale for its inclusion provided?
If YES, reference:


9. Does the proposal include use of combining characters and/or use of composite sequences (see clause 4.11 and 4.13 in ISO/IEC 10646-1)?
If YES, is a rationale for such use provided?
If YES, reference:

Is a list of composite sequences and their corresponding glyph images (graphic symbols) provided?
If YES, reference:


10. Does the proposal contain characters with any special properties such as control function or similar semantics?
If YES, describe in detail (include attachment if necessary)


D. SC 2/WG 2 Administrative (To be completed by SC 2/WG 2)


1. Relevant SC 2/WG 2 document numbers:


2. Status (list of meeting number and corresponding action or disposition):


3. Additional contact to user communities, liaison organizations etc:


4. Assigned category and assigned priority/time frame:



ISO/IEC JTC 1/SC 2/WG 2
PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS
FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646


An Example: Fictitious summary form filled in for illustration of the use of the form.

Please fill Sections A, B and C below. Section D will be filled by SC 2/WG 2.

A. Administrative


1. Title: Braille


2. Requester's name: Kohji Shibano, Japan


3. Requester type (Member body/Liaison/Individual contribution): Individual Contribution


4. Submission date: 1994-10-10


5. Requester's reference (if applicable): J2-94-xy


6. (Choose one of the following:)
This is a complete proposal: ; or, More information will be provided later:
Yes


B. Technical - General


1. (Choose one of the following:)

a. This proposal is for a new script (set of characters): Yes
Proposed name of script: Braille

b. The proposal is for addition of character(s) to an existing block: No
Name of the existing block:


2. Number of characters in proposal: 448


3. Proposed category (see section II, Character Categories): A


4. Proposed Level of Implementation (see clause 15, ISO/IEC 10646-1): 1
Is a rationale provided for the choice? No
If Yes, reference:


5. Is a repertoire including character names provided?: Yes


a. If YES, are the names in accordance with the 'character naming guidelines' in Annex K of ISO/IEC 10646-1? No (will provide)
b. Are the character shapes attached in a reviewable form? Yes


6. Who will provide the appropriate computerized font (ordered preference: TrueType, PostScript or 96x96 bit-mapped format) for publishing the standard? Japan
If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools used: IBM Japan (ftp://ifi.jp/pub/font)


7. References:
a. Are references (to other character sets, dictionaries, descriptive texts etc.)
provided?
ISO TC 173

b. Are published examples (such as samples from newspapers, magazines, or
other sources) of use of proposed characters attached?
No (will provide)


8. Special encoding issues:

Does the proposal address other aspects of character data processing (if applicable) such as input, presentation, sorting, searching, indexing, transliteration etc. (if yes please enclose information): ______________________________________________________________________________


C. Technical - Justification


1. Has contact been made to members of the user community (for example: National Body, user groups of the script or characters, other experts, etc.)? No

If YES, with whom?
If YES, available relevant documents?


2. Information on the user community for the proposed characters (for example: size,
demographics, information technology use, or publishing use) is included?
Reference:
People with impaired vision (info will be provided)


3. The context of use for the proposed characters (type of use; common or rare) Common
Reference: on-line database services for Braille-translated text (e.g. www: braille.dknet.dk)


4. Are the proposed characters in current use by the user community? Yes
If YES, where? Reference: Worldwide


5. After giving due considerations to the principles in N 1352 must the proposed
characters be entirely in the BMP?
Yes
If YES, is a rationale provided?
If YES, reference:


6. Should the proposed characters be kept together in a contiguous range (rather than
being scattered)?
Yes


7. Can any of the proposed characters be considered a presentation form of an existing
character or character sequence?
No
If YES, is a rationale for its inclusion provided?
If YES, reference:


8. Can any of the proposed character(s) be considered to be similar (in appearance or function) to an existing character? No
If YES, is a rationale for its inclusion provided?
If YES, reference:


9. Does the proposal include use of combining characters and/or use of composite sequences (see clause 4.11 and 4.13 in ISO/IEC 10646-1)? No
If YES, is a rationale for such use provided?
If YES, reference:

Is a list of composite sequences and their corresponding glyph images (graphic symbols) provided?
If YES, reference:


10. Does the proposal contain characters with any special properties such as control function or similar semantics? No
If YES, describe in detail (include attachment if necessary)


D. SC 2/WG 2 Administrative (To be completed by SC 2/WG 2)


1. Relevant SC 2/WG 2 document numbers:


2. Status (list of meeting number and corresponding action or disposition):


3. Additional contact to user communities, liaison organizations etc.:


4. Assigned category and assigned priority/time frame:


ISO/IEC JTC 1/SC 2/WG 2
PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS
FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646


An Example: Fictitious summary form filled in for illustration of the use of the form.

Please fill Sections A, B and C below. Section D will be filled by SC 2/WG 2.

A. Administrative


1. Title: Addition of two Latin characters


2. Requester's name: Danish Standards Association


3. Requester type (Member body/Liaison/Individual contribution): NB


4. Submission date: 1995-03-10


5. Requester's reference (if applicable):


6. (Choose one of the following:)
This is a complete proposal:
Yes ; or, More information will be provided later:


B. Technical - General


1. (Choose one of the following:)

a. This proposal is for a new script (set of characters): No
Proposed name of script:

b. The proposal is for addition of character(s) to an existing block: Yes
Name of the existing block: Table 4 - Row 01: Latin Extended-B


2. Number of characters in proposal: 2


3. Proposed category (see section II, Character Categories): A


4. Proposed Level of Implementation (see clause 15, ISO/IEC 10646-1): 1
Is a rationale provided for the choice?
If Yes, reference:



5. Is a repertoire including character names provided?: Yes

a. If YES, are the names in accordance with the 'character naming guidelines'in Annex K of ISO/IEC 10646-1? Yes
b. Are the character shapes attached in a reviewable form? Yes


6. Who will provide the appropriate computerized font (ordered preference: True Type, PostScript or 96x96 bit-mapped format) for publishing the standard?
Michael Everson, Everson Gunn Teoranta
If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools used:
Michael Everson, Everson Gunn Teoranta


7. References:
a. Are references (to other character sets, dictionaries, descriptive texts etc.)
provided?
Yes

b. Are published examples (such as samples from newspapers, magazines, or
other sources) of use of proposed characters attached?
Yes


8. Special encoding issues:

Does the proposal address other aspects of character data processing (if applicable) such as input, presentation, sorting, searching, indexing, transliteration etc. (if yes please enclose information): Specifications enclosed


C. Technical - Justification


1. Has contact been made to members of the user community (for example: National Body, user groups of the script or characters, other experts, etc.)? Yes

If YES, with whom? Irish National Body, Oxford University
If YES, available relevant documents? Enclosed

2. Information on the user community for the proposed characters (for example: size,
demographics, information technology use, or publishing use) is included?
Yes
Reference: The Community of Gothic and Medieval English Literature


3. The context of use for the proposed characters (type of use; common or rare) Rare
Reference:


4. Are the proposed characters in current use by the user community? Yes
If YES, where? Reference: Scholar Communities


5. After giving due considerations to the principles in N 1352 must the proposed
characters be entirely in the BMP?
Yes
If YES, is a rationale provided? Yes
If YES, reference: Enclosed


6. Should the proposed characters be kept together in a contiguous range (rather than
being scattered)?
No


7. Can any of the proposed characters be considered a presentation form of an existing
character or character sequence?
No
If YES, is a rationale for its inclusion provided?
If YES, reference:


8. Can any of the proposed character(s) be considered to be similar (in appearance or function) to an existing character? No
If YES, is a rationale for its inclusion provided?
If YES, reference:


9. Does the proposal include use of combining characters and/or use of compositesequences (see clause 4.11 and 4.13 in ISO/IEC 10646-1)? No
If YES, is a rationale for such use provided?
If YES, reference:

Is a list of composite sequences and their corresponding glyph images (graphic symbols) provided?
If YES, reference:


10. Does the proposal contain characters with any special properties such as control function or similar semantics? No
If YES, describe in detail (include attachment if necessary)


D. SC 2/WG 2 Administrative (To be completed by SC 2/WG 2)


1. Relevant SC 2/WG 2 document numbers:


2. Status (list of meeting number and corresponding action or disposition):


3. Additional contact to user communities, liaison organizations etc.:


4. Assigned category and assigned priority/time frame:


Annex B

Handling of Defect Reports on Character Names

Since the publication of ISO/IEC 10646-1 in May 1993, several defect reports requesting changes to character names have been received by WG 2. In principle, the names in the standard are not to be changed. However, there may be situations where changes, deletions or annotations to names of characters may be warranted. The following paragraphs describe the principles of dealing with such defect reports:

a. Explanatory information in Annex Q , "Additional Information on Characters"

If WG 2 decides that the request is justified, WG 2 will first consider accommodating the request by adding explanatory text to Annex Q, "Additional Information on Characters", of the Standard ISO/IEC 10646-1.

b. Non-normative parenthetic annotation of the name

If WG 2 considers that the request falls within the guidelines of Rule 12 in Annex K - Character naming guidelines in the standard, then an appropriate annotation will be added to the character name.

In instances where a name change causes a potential problem for compliance by implementations of existing standard, and if the concern expressed in the defect report may be handled with a simple explanatory note, a note may be added.

c. Deprecation

If WG 2 considers that the character identified in the defect report should not have been in the standard, for reasons such as duplication, or incorrect inclusion in a block, then that coded character will be marked with the annotation "(deprecated character)" after its name.

d. Technical Corrigendum

If WG 2 considers that the character identified in the defect report has indeed been incorrectly named, based on the evidence provided in the defect report, a Technical Corrigendum to correct the name will be prepared and forwarded to the SC 2 secretariat for further processing.

e. Reject

In all other situations, where WG 2 considers that the request is not sufficiently justified or a name change is not warranted, the defect report will not be entertained (will be rejected).

Some Guidelines for Submitters of Defect Reports:

As a supplement to the above information on dealing with defect reports, the submitters can assist the working group by following the guidelines given below:

a) report all defects associated with characters from the same block or set of characters as a single defect report (for example, use a single one for all defects from within a character block such as Malayalam), instead of one for each character.

b) avoid including defective characters from different character blocks or sets in the same report.

c) please check if the defect has already been processed by a national body or considered before by WG 2. Copies of the disposition of prior defect reports can be obtained from the SC 2 Secretariat.

d) if one or more new character(s) - with their own new name and glyph - is proposed to be added in conjunction with a defect report, please submit the addition requests separate from the defect report along with the Proposal Summary Form for them.

Annex C

Description of the UCS work flow and stages in progression from initial proposal to final publication

The UCS work flow

UCS work can simplified be illustrated as follows:

Table 1, WG 2 document flow

The stages of work:

Any new proposal for addition of new characters will pass a number of stages from initial proposal to finalized publication. The stages are:

This terminology indicates the stage of maturity of the proposal and the WG's confidence in the proposal.

In process within WG 2
Further progression


Stages

Item

Initial proposal
Provisional acceptance
Final acceptance (allocation of bucket)
Hold for ballot
Progression/ Publication status
SC2

Ballot
JTC 1 Ballot
ITTF

Publica-tion
A
B
C
D
E
F
G
1*
Char. shapes
A1
B1
2*
Char. names
A2
B2
3*
Code position allocation
A3
B3
4*
Text to be included in the standard
A4
B4
5*
Font**
A5
B5
6
Other items from proposal summary form
A6
B6

* Mandatory for entering "final acceptance" stage

** Camera ready copy is mandatory for stage G. It is expected that the quality of the fonts will improve to camera ready quality as the proposal progress trough the various stages. For information on the format of the font see the "Proposal summary form".

The stages A-C may contain provisionally allocated code positions. When a proposal enters stage D the code positions are final.

The content of the Buckets are reviewed at every meeting to decide whether the content shall progress for balloting (stage D).

The progress of the proposals are recorded in the document Summary of WG2 work (the excel spread sheet).

When a proposal reach the D-stage its status is included in List of character names and code positions allocated.

Examples:

List of character names and code positions allocated:

Code positionStatus ReferenceCharacter name
...
20ABF N1092DONG SIGN
...
012C LATIN CAPITAL LETTER I WITH BREVE
...
00E6G N1128LATIN SMALL LETTER AE (ash)
01FDG N1128LATIN SMALL LETTER AE WITH ACUTE (ash)
01E3G N1128LATIN SMALL LETTER AE WITH MACRON (ash)
...
1E9BF N1132LATIN SMALL LETTER LONG S WITH DOT ABOVE
...
FFFCB N1365OBJECT REPLACEMENT CHARACTER
....

Summary of WG2 work items:



STATUS/STAGE: