ISO/IEC 8825-4:2002/Amd 3:2008
(Amendment)Information technology — ASN.1 encoding rules: XML Encoding Rules (XER) — Part 4: — Amendment 3: PER encoding instructions
Information technology — ASN.1 encoding rules: XML Encoding Rules (XER) — Part 4: — Amendment 3: PER encoding instructions
Technologies de l'information — Règles de codage ASN.1: Règles de codage XML (XER) — Partie 4: — Amendement 3: Instructions de codage PER
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 8825-4
First edition
2002-12-15
AMENDMENT 3
2008-04-01
Information technology —
ASN.1 encoding rules: XML Encoding
Rules (XER) —
AMENDMENT 3: PER encoding instructions
Technologies de l'information — Règles de codage ASN.1: Règles de
codage XML (XER) —
AMENDEMENT 3: Instructions de codage PER
Reference number
ISO/IEC 8825-4:2002/Amd.3:2008(E)
©
ISO/IEC 2008
---------------------- Page: 1 ----------------------
ISO/IEC 8825-4:2002/Amd.3:2008(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2008
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2008 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 8825-4:2002/Amd.3:2008(E)
CONTENTS
Page
1) Introduction. 1
2) Subclause 3.2.3 bis . 1
3) Subclause 8.3.3 bis . 1
4) Subclause 8.3.4 bis . 1
5) Subclauses 10.2.6, 10.2.7 and 10.2.8 . 1
6) Subclause 10.2.10. 2
7) Subclause 11.4. 2
8) Subclause 13.5. 2
9) Subclause 13.7. 2
10) Clause 14. 2
11) Subclauses 14.1.2, 14.1.3, 14.1.4 and 14.1.5 . 2
12) Subclause 14.2.1.2. 3
13) Subclause 14.2.1.17 . 3
14) Subclause 14.2.3.1. 3
15) Subclause 15.1.3 . 4
16) Subclause 15.4.3 . 4
17) Subclause 16.4. 4
18) Subclause 18.1.1 . 4
19) Subclause 18.2.12. 4
20) Subclause 19.1.1 . 4
21) Subclause 19.1.4 . 4
22) Subclause 19.1.6 . 5
23) Subclause 19.2.1 . 5
24) Subclauses 19.2.7-19.2.9. 5
25) Subclause 19.2.10. 5
26) Subclauses 19.3.1-19.3.4. 5
27) Subclause 20.1.1 . 6
28) Subclause 21.1.1 . 6
29) Subclause 22.1.1 . 6
30) Subclause 22.2.3 . 6
31) Subclause 23.1.1 . 6
32) Subclause 23.2.7 . 7
33) Subclause 24.1.1 . 7
34) Subclause 25.1.1 . 7
35) Subclause 25.2.1 . 7
36) Subclause 25.2.7 . 7
37) Subclause 26.1.1 . 7
38) Subclauses 26.2.1 and 26.2.2 . 7
39) Subclause 27.1.1 . 8
40) Subclause 28.1.1 . 8
41) Subclause 29.1.1 . 8
42) Subclause 29.2.1 . 8
43) Subclause 29.2.2 . 9
© ISO/IEC 2008 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 8825-4:2002/Amd.3:2008(E)
Page
44) Subclause 30.1.1 . 9
45) Subclause 31.1.1 . 9
46) Subclause 31.1.4 . 9
47) Subclause 31.2.3 bis. 9
48) Subclause 31.2.5 . 9
49) Subclause 32.1.1 . 10
50) Subclause 32.2.1 . 10
51) Subclause 32.2.5 . 10
52) Subclause 32.3.4 . 10
53) Subclause 33.1.1 . 10
54) Subclause 33.2.6 . 10
55) Subclause 34.1.1 . 10
56) Subclause 34.3.4 . 10
57) Subclause 35.1.1 . 11
58) Subclause 35.2.1 . 11
59) Subclauses 35.2.2.1 and 35.2.2.2 . 11
60) Subclause 35.2.5 . 11
61) Subclause 35.2.7 . 11
62) Subclause 36.1.1 . 12
63) Subclause 36.2.3 . 12
64) Subclause 37.1.1 . 12
65) Subclause 37.2.4 . 12
66) Subclause 38.1.1 . 12
67) Subclause 38.2.7 . 12
68) Subclause 39.1.1 . 12
69) Subclause 39.2.1 . 13
70) Subclause 39.2.2 bis. 13
71) Subclauses 39.3.1 and 39.3.2 . 13
72) Subclauses C.1.6 and C.1.7. 13
73) Subclause C.2.2. 13
iv © ISO/IEC 2008 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 8825-4:2002/Amd.3:2008(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 3 to ISO/IEC 8825-4:2002 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 6, Telecommunications and information exchange between
systems in collaboration with ITU-T. The identical text is published as ITU-T
Rec. X.693 (2001)/Amd.3 (05/2007).
© ISO/IEC 2008 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 8825-4:2002/Amd.3:2008 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
Information technology – ASN.1 encoding rules: XML encoding rules
Amendment 3: PER encoding instructions
Conventions used in this amendment: Original, unchanged, text is in normal font. Deleted text is struck-through, thus:
deleted text. Inserted text is underlined, thus: inserted text.
1) Introduction
In the Introduction, insert "XER" in bullet a) as follows:
Clauses 18 to 39 specify:
a) the syntax of each XER encoding instruction used in a type prefix or an XER encoding control section;
b) restrictions on the XER encoding instructions that can be associated with a particular ASN.1 type
(resulting from inheritance and multiple assignments);
c) modifications to the XER encoding rules that are required in an EXTENDED-XER encoding when an
XER encoding instruction is applied.
2) Subclause 3.2.3 bis
Replace subclause 3.2.3 bis with the following:
3.2.3 bis XER encoding instructions: Notation used to change the EXTENDED-XER encoding of a type (or of a
component of a type).
NOTE – XER eEncoding instructions are included in eitherthat are associated with an ASN.1 type (or with a component of an
ASN.1 type) by assignment to that type (or component) in an XER type prefix (see ITU-T Rec. X.680 | ISO/IEC 8824-1, 30.3) or
an XER encoding control section (see ITU-T Rec. X.680 | ISO/IEC 8824-1, clause 50).
3) Subclause 8.3.3 bis
Replace subclause 8.3.3 bis with the following:
8.3.3 bis The "XMLBooleanValue" specified in ITU-T Rec. X.680 | ISO/IEC 8824-1, 17.3, shall only be
"EmptyElementBoolean" and the "XMLSequenceOfValue" and "XMLSetOfValue" with a component that is a boolean
type shall be "XMLValueList".
4) Subclause 8.3.4 bis
Replace subclause 8.3.4 bis with the following:
8.3.4 bis The "XMLEnumeratedValue" specified in ITU-T Rec. X.680 | ISO/IEC 8824-1, 19.8, shall only be
"EmptyElementEnumerated" and the "XMLSequenceOfValue" and "XMLSetOfValue" with a component that is an
enumerated type shall be "XMLValueList".
5) Subclauses 10.2.6, 10.2.7 and 10.2.8
In subclauses 10.2.6, 10.2.7 and 10.2.8 change "Encoding Control Section" to "encoding control section".
ITU-T Rec. X.693 (2001)/Amd.3 (05/2007) 1
---------------------- Page: 6 ----------------------
ISO/IEC 8825-4:2002/Amd.3:2008 (E)
6) Subclause 10.2.10
Replace subclause 10.2.10 with the following:
10.2.10 Conforming decoders and validators shall accept, but may ignore, the presence of an type identification
attribute from the control namespace in any XML element of an encoding unless its presence and use is as specified in
clauses 37 and 38. Encoders shall not generate such attributes except as specified in clauses 37 and 38.
NOTE – Other XML tools may insert such attributes. In general, an EXTENDED-XER decoder cannot easily determine the
permitted value and meaning of some type identification attributes from the control namespace. Their presence and value may be
of use to an application if (for example) unexpected XML child elements are present that are (as a decoder's option) passed to the
application – rather than being ignored or producing a fatal decoding error.
7) Subclause 11.4
In subclause 11.4, insert:
"[" (see ITU-T Rec. X.680 | ISO/IEC 8824-1, 11.26)
"]" (see ITU-T Rec. X.680 | ISO/IEC 8824-1, 11.26)
after
":" (see ITU-T Rec. X.680 | ISO/IEC 8824-1, 11.26)
8) Subclause 13.5
Replace subclause 13.5 with the following:
13.5 Each use of a "PositiveInstruction" in an XER type prefix or in an XER encoding control section assigns that
XER encoding instruction to the corresponding "Type". Each of the alternatives of "PositiveInstruction" (for example,
"AnyAttributesInstruction") has two alternatives. Only the first alternative of these shall be used in a type prefix.
9) Subclause 13.7
Replace subclause 13.7 with the following:
13.7 An encoding instruction in a type prefix or in an XER encoding control section can be a positive instruction,
used to add or to replace an encoding instruction (use of "PositiveInstruction"), or a negating instruction used to cancel
(use of "NegatingInstruction") one or more associated encoding instructions.
10) Clause 14
In the heading for clause 14, insert "XER" before "encoding control section".
11) Subclauses 14.1.2, 14.1.3, 14.1.4 and 14.1.5
Replace subclauses 14.1.2, 14.1.3, 14.1.4 and 14.1.5 with the following:
14.1.2 The XER "EncodingInstructionAssignmentList" production is:
EncodingInstructionAssignmentList ::=
EncodingInstruction
EncodingInstructionAssignmentList ?
| "[" EncodingInstruction
EncodinginstructionAssignmentList ?
14.1.3 The "EncodingInstruction" production is defined in 13.3. Each alternative of "PositiveInstruction" (for
example "AnyAttributesInstruction") has two alternatives. An XER encoding control section shall contain only one of
the alternatives for "EncodingInstructionAssignmentList". If the first alternative is used, then the first alternative for
each of the alternatives of "PositiveInstruction" shall be used. If the second alternative is used, then the second
alternative for each of the alternatives of "PositiveInstruction" shall be used.
NOTE – Each alternative of "PositiveInstruction" provides two alternative forms. The first is provided for historical reasons. The
second alternative form provides the matching "]" and moves the "TargetList" (if any) to the end of the production. It is provided
for similarity with the syntax used in the "EncodingInstructionAssignmentList" of other ASN.1 encoding rule standards, and for
2 ITU-T Rec. X.693 (2001)/Amd.3 (05/2007)
---------------------- Page: 7 ----------------------
ISO/IEC 8825-4:2002/Amd.3:2008 (E)
readability. The use of the second alternative of the "EncodingInstructionAssignmentList" (and hence the second alternative of
all the alternatives of "PositiveInstruction" within it) is recommended for new specifications.
14.1.4 Each use of an "EncodingInstruction" in an XER encoding control section assigns that XER encoding
instruction to the occurrences of "Type" that are identified in the "TargetList" of the encoding instruction, or to the type
references in an imports list. The "TargetList" production and the targets it identifies are specified in 14.2.
14.1.5 Subclauses 13.4 to 13.14 also apply to encoding instructions in an XER encoding control section. The clauses
defining the detailed syntax for each encoding instruction category are listed in Table 1. Categories of XER encoding
instructions are also listed in Table 1.
12) Subclause 14.2.1.2
In subclause 14.2.1.2, NOTE 2, insert "XE
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.