ISO
ISO/IEC 9075-5:1999/Cor 2:2003
(Corrigendum)Information technology — Database languages — SQL — Part 5: Host Language Bindings (SQL/Bindings) — Technical Corrigendum 2
Information technology — Database languages — SQL — Part 5: Host Language Bindings (SQL/Bindings) — Technical Corrigendum 2
Technologies de l'information — Langages de base de données — SQL — Partie 5: Liants de langage d'hôte (SQL/Liants) — Rectificatif technique 2
General Information
Status
Withdrawn
Publication Date
04-Jun-2003
Withdrawal Date
04-Jun-2003
Technical Committee
Drafting Committee
Current Stage
9599 - Withdrawal of International Standard
Completion Date
07-Nov-2005
Relations
Effective Date
06-Jun-2022
Effective Date
15-Apr-2008
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9075-5:1999
TECHNICAL CORRIGENDUM 2
Published 2003-06-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Database languages — SQL —
Part 5:
Host Language Bindings (SQL/Bindings)
TECHNICAL CORRIGENDUM 2
Technologies de l'information — Langages de base de données — SQL —
Partie 5: Liants de langage d'hôte (SQL/Liants)
RECTIFICATIF TECHNIQUE 2
Technical Corrigendum 2 to ISO/IEC 9075-5:1999 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.
ISO/IEC 9075-5:1999/Cor. 2:2003 cancels and replaces ISO/IEC 9075-5:1999/Cor. 1:2000.
Statement of purpose for rationale:
A statement indicating the rationale for each change to ISO/IEC 9075 is included. This is to inform the users of
that standard as to the reason why it was judged necessary to change the original wording. In many cases the
reason is editorial or to clarify the wording; in some cases it is to correct an error or an omission in the original
wording.
Notes on numbering:
Where this Corrigendum introduces new Syntax, Access, General and Conformance Rules, the new rules have
been numbered as follows:
Rules inserted between, for example, Rules 7) and 8) are numbered 7.1), 7.2), etc. [or 7) a.1), 7) a.2), etc.]. Those
inserted before Rule 1) are numbered 0.1), 0.2), etc.
Where this Corrigendum introduces new Subclauses, the new subclauses have b een numbered as follows:
Subclauses inserted between, for example, Subclause 4.3.2 and 4.3.3 are numbered 4.3.2a, 4.3.2b, etc.
Those inserted before, for example, 4.3.1 are numbered 4.3.0, 4.3.0a, etc.
ICS 35.060 Ref. No. ISO/IEC 9075-5:1999/Cor.2:2003(E)
© ISO/IEC 2003 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
Contents
Page
4.6.1 Clas ses of SQ L-stateme nts . . . . . . 3
4.6.4 Embeddable SQL-statement . . . . . 3
4.6.5 Prepa rable and im mediately e xecutable SQL-state ments . . . . 4
4.6.6 Direc tly executab le SQL-s tatements . . . . . 4
5.1 an d . . . . . 5
8.1 . . . . . 5
10.5 . . . . . 6
11.1 . . . . . . . 6
11.2 Calls to an . . . . . 6
11.3 . . . . . 6
12.0 . . . . . 7
12.1 . . . . . 8
12.2 . . . . . 8
14.3 . . . . . 8
15.1 Description of SQL descriptor areas . . . . 9
15.2 . . . . . 9
15.3 . . . . . 9
15.4 . . . . . 10
15.5 . . . . . 10
15.6
. . . . . 10
15.8 . . . . . 11
15.9 . . . . . 11
15.10 . . . . . 12
15.13 . . . . . 12
15.14 . . . . . 12
16.1 . . . . . 13
16.2 . . . . . 1 6
16.3 . . . . . 16
16.4 . . . . 1 7
16.5 . . . . . 1 8
16.6 . . . . . 1 9
16.7 . . . . . 1 9
16.8 . . . . . 20
16.9 . . . . . 21
17.1 . . . . . 22
17.2 . . . . . 22
18.1 . . . . . 23
20.1 SQLSTATE . . . . . . . 2 3
Annex A SQL Co nformance Su mmary . . . . . 24
Annex B Implem entation-de fined eleme nts . . . . 26
Annex E Incompatibilities with ISO/IEC 9075:1992 . . . . . 2 7
Annex F SQL fea ture and package taxonomy . . . . . 2 7
2 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
Information technology — Database languages — SQL —
Part 5:
Host Language Bindings (SQL/Bindings)
TECHNICAL CORRIGENDUM 2
4.6.1 Classes of SQL-statements
1. Rationale: Clarify the semantics of SQL-data access indication.
nd
Replace the 2 paragraph with:
Insert this paragraph There are at least four additional ways of classifying SQL-statements:
— According to whether or not they may be embedded.
— According to whether they may be dynamically prepared and executed.
— According to whether or not they may be directly executed.
— According to whether they do not possibly contain SQL, possibly contain SQL, possibly read SQL-
data, or possibly modify SQL-data.
4.6.4 Embeddable SQL-statement
1. Rationale: Correct the classification of SQL-statements.
th st
Insert the following sub-bullet to the 7 bullet of the 1 paragraph:
•
2. Rationale: Correct the classification of SQL-statements.
th st
Replace the 8 bullet of the 1 paragraph with:
— The following SQL-control statements:
•
•
© ISO/IEC 2003 – All rights reserved 3
---------------------- Page: 3 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
4.6.5 Preparable and immediately executable SQL-statements
1. Rationale: Correct the classification of SQL-statements.
th st
Delete the following sub-bullet from the 4 bullet of the 1 paragraph:
•
2. Rationale: Correct the classification of SQL-statements.
nd
Insert the following bullet to the 2 paragraph:
—
4.6.6 Directly executable SQL-statements
1. Rationale: Correct the classification of SQL-statements.
st
Insert the following bullet to the 1 paragraph:
— The following SQL-control statements:
•
• 2. Rationale: Clarify the semantics of SQL-data access indication.
Insert the following Subclause after Subclause 4.6.6, “Directly executable SQL-statements”:
4.6.6a SQL-statements and SQL-data access indication
Insert this paragraph The following are the other SQL-statements that possibly contain SQL:
— SQL embedded exception declaration
Insert this paragraph The following are the other SQL-statements that possibly read SQL-data:
— SQL-d ynamic sta tements
4 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
5.1 and
1. Rationale: Editorial - Correct reserved and non-reserved word lists.
In the Format, in the production for add the alternatives:
| NESTING
| SCOPE_CATALOG
| SCOPE_NAME
| SCOPE_SCHEMA
| USER_DEFINED_TYPE_CATALOG
| USER_DEFINED_TYPE_NAME
| USER_DEFINED_TYPE_SCHEMA
2. Rationale: Editorial. Co rrect reserv ed word list.
In the Format, in the production for , delete the texts:
| DYNAMIC
| NESTING
8.1
1. Rationale: has also to be handled according to the Syntax Rules of
Subclause 9.1, “Retrieval assignment” in Bindings.
Replace Syntax Rule 1 with:
1) Replace SR 8) c) i) 4) A) If A is a o r an i
specification>, then P shall be assignable to A , according to the Syntax Rules of Subclause 9.1,
i i
‘‘Retrieval assignment’’, with A and P as TARGET and VALUE, respectively.
i i
2. Rationale: The current handling of output parameter in routine invocation is incomplete. It does not cover
all alternatives of .
Insert the following General Rule:
1) Replace GR 10 ) b) i) If TS is a o r an i
specification>, then CPV is assigned to TS according to the rules of Subclause 9.1, ‘‘Retrieval
i i
assignment’’.
© ISO/IEC 2003 – All rights reserved 5
---------------------- Page: 5 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
10.5
1. Rationale: Clarify the semantics of SQL-data access indication.
Replace Syntax Rule 1) with:
1) Insert before SR 18) c) It is implemen tation-defined whether th e shall no t contain
an .
11.1
1. Rationale: Consistent use of terminology.
Replace General Rule 1) with:
1) Augments GR 5) After the last time that an SQL-agent performs a call of an procedu re>, follow ing the effectiv e executio n of a or a , a
that specifies
DEALLOCATE DESCRIPTOR D
is effectively executed, where D is the of any SQ L descripto r area that is curre ntly
allocated w ithin an SQ L-session associated with the SQ L-agent.
11.2 Calls to an
1. Rationale: Editorial.
In Syntax Rule 1) replace the following constraints:
DYNAMIC_SQL_ERROR_UNDEFINED_DATA_TARGET:
constant SQLSTATE_TYPE := "0700D";
DYNAMIC_SQL_ERROR_UNDEFINED_LEVEL_VALUE:
constant SQLSTATE_TYPE := "0700E";
with:
DYNAMIC_SQL_ERROR_INVALID_DATA_TARGET:
constant SQLSTATE_TYPE := "0700D";
DYNAMIC_SQL_ERROR_INVALID_LEVEL_VALUE:
constant SQLSTATE_TYPE := "0700E";
11.3
1. Rationale: Editorial.
In the Format, replace the production for with:
::=
!! All alternatives from ISO/IEC 9075-2
|
|
6 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
|
|
|
2. Rationale: Consistent use of terminology.
In the Format replace the production of with:
::=
|
|
|
|
|
|
In the Format replace the production of with:
::=
|
|
|
12.0
1. Rationale: Add missing Syntax and General Rules for .
Add a new Subclause as follows:
12.0
Function
Position a cursor on a specified row of a table and retrieve values from that row.
Format
No additional Format items.
Syntax Rules
1) Add after SR 6) b) iii) For each TS2 that is an , the
Syntax Rules of Subclause 9.1, “Retrieval assignment”, apply to each TS2 and the corresponding
column of table T, as TARGET and VALUE, respectively.
General Rules
1) Add after GR 7) b) ii) If TV is an , then the General Rules of Subclause
9.1, “Retrieval assignment” are applied to TV and SV, as TARGET and VALUE, respectively.
© ISO/IEC 2003 – All rights reserved 7
---------------------- Page: 7 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
12.1 1. Rationale: Replace in correct no n-termina l. Replace Syn tax Rule 1). 1) Insert after SR4) For each TS that is an , then the Syntax Rules of Subclause 9.1, “Retrieval assignment”, shall apply to TS and the corresponding element of the , as TARGET and VALUE, respectively.
2. Rationale: Remove redundant and incorrect rule.
Delete Genera l Rule 1).
3. Rationale: Replace in correct no n-termina l.
Replace Ge neral Rule 2).
2) Insert after GR5) For each TS that is an ,
the corresponding va lue in the row of Q is assigned to TS according to the General Rules of Subclause
9.1, “Retrieval assignment”, as VALUE and TARGET, respectively . The assign ment of va lues to targets
in the is in an implemen tation-dependent order. 12.2 1. Rationale: Editorial - Typographical error. In the Format, replace the production for with: ::= !! All alternatives from ISO/IEC 9075-2 | 14.3 1. Rationale: Specify explicitly the implication that F451, "Character set definition" depends on F461, "Named characte r sets" . Replace Conformance Rule 1) with: 1) Without Feature F761, “Session management” and Feature F461, “Named character sets”, conforming SQL language shall not contain any . 8 © ISO/IEC 2003 – All rights reserved ---------------------- Page: 8 ---------------------- ISO/IEC 9075-5:1999/Cor.2:2003(E) 15.1 Description of SQL descriptor areas 1. Rationale: Correct definition of the length of s. Replace Syntax Rule 6) n) with: 6) n) TYPE indicates REF, LENGTH is the length in octets for the REF type, and USER_DEFINED _TYPE_CATA LOG, USER_DE FINED_TYPE_SC HEMA, and USER_DEFINED _TYPE_NAM E are a valid qualified user-defined type name, and SCOPE_CAT ALOG, SCOPE _SCHEMA , and SCOPE_NAM E are a valid qualified table name. 15.2 1. Rationale: Consistent use of terminology. Replace General Rule 2) with: 2) Case: a) If an SQL descriptor area whose name is V and whose scope is specified by the immediately contained in is already currently allocated, then an exception condition is ra ised: invalid SQL descriptor name. b) Otherwise, allocates an SQL descriptor area whose name is V and whose scope is specified by the immediately contained in . The SQL descriptor area will have at least number of SQL item descriptor areas. The value of LEVEL in each of the item descriptor areas is set to 0 (zero). The values of all other fields in the SQL descriptor area are initially undefined. 15.3 1. Rationale: Consistent use of terminology. Replace General Rule 1) with: 1) Case: a) If an SQL descriptor area is not currently allocated whose name is the value of the specification> immediately contained in and whose scope is specified by the immediately contained in , then an exception condition is raised: invalid SQL descriptor name. b) Otherw ise, deallocates an SQL descriptor are a whose name is the value of the immediately contained in and whose scope is specified by the immediately contained in . © ISO/IEC 2003 – All rights reserved 9 ---------------------- Page: 9 ---------------------- ISO/IEC 9075-5:1999/Cor.2:2003(E) 15.4 1. Rationale: Consistent use of terminology. Replace General Rule 1) with: 1) If a identifies an S QL des criptor area tha t is not currently a llocated w hose nam e is the value of the immediately contained in and whose scope is specified by the immediately contained in , then an exception condition is ra ised: invalid SQL descriptor name. 15.5 1. Rationale: Consistent use of terminology. Replace General Rule 1) with: 1) If a identifies an S QL des criptor area tha t is not currently a llocated w hose nam e is the value of the immediately contained in and whose scope is specified by the immediately contained in , then an exception condition is ra ised: invalid SQL descriptor name. 15.6 1. Rationale: handle s for . Insert the following General Rule: 6) a) vii.1) If DP is either X1, X2 or X3 in a o f the form "SUB STRING ( X1 SIMILAR X2 ESCAPE X3 )" then 1) Case: a) If the declared type of X1 is CHARACTER , CHARACT ER VARY ING or CHA RAC TER L ARG E OBJ ECT, the n let CS be the character set of X1. b) If the declared type of X2 is CHARACTER , CHARACT ER VARY ING or CHA RAC TER L ARG E OBJ ECT, the n let CS be the character set of X1. c) If the declared type of X3 is CHARACTER , CHARACT ER VARY ING or CHA RAC TER L ARG E OBJ ECT, the n let CS be the character set of X1. d) Otherw ise, the chara cter set CS is undefined 2) If CS is defined, then a) If DP is X1 or X2, then DT is CHARACTER VARYING (ML) with character set CS. b) If DP is X3, then DT is CHA RAC TER (1 ) with chara cter set CS. 10 © ISO/IEC 2003 – All rights reserved ---------------------- Page: 10 ---------------------- ISO/IEC 9075-5:1999/Cor.2:2003(E) 2. Rationale: Use correct keywords for parameter modes. Replace General Rule 7) a) iii) with: 7) a) iii) For each D contained in some A , 1 k (one) £ k £ n : 1) D is an input if the of the k-th SQL param eter of SR is IN or INOUT. 2) D is an output if the of the k-th SQL param eter of SR is OUT or INOUT. 15.8 1. Rationale: Consistent use of terminology. Replace General Rule 4) with: 4) If an SQL descriptor area is not currently allocated whose name is the value of the specification> immediately contained in and whose scope is that specified by the immediately contained in , then an exception condition is raised: invalid SQL descriptor name. 2. Rationale: Correct definition of the length of s. Replace General Rule 8) d) ix) with: 8) d) ix) If TYPE indicates a , then USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA, USER_DEFINED_TYPE_NAME, SCOPE_CAT ALOG, SCOPE _SCHEMA , and SCOPE_NAM E are set to the type name> of the referenced type and qualified name of the referenceable base table; LENGTH and OCTET_LENGTH are set to the length in octets of the . 15.9
1. Rationale: Consistent use of terminology.
Replace General Rule 1) with:
1) If is specified and an SQL descriptor area is not currently allocated whose
name is the value of the and whose scope is that specified by the option> immediately contained in immediately contained in ,
then an ex ception co ndition is raised : invalid SQL descriptor name.
2. Rationale: Editorial.
Replace Conformance Rule 2) with:
2) Without Feature B031, ‘‘Basic dynamic SQL’’, conforming SQL language shall not contain any using clause>.
© ISO/IEC 2003 – All rights reserved 11
---------------------- Page: 11 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
15.10
1. Rationale: There is no syntax rule to contain either a or an variable specification>.
Insert the following Syntax Rule:
1) The immediately contained in shall be either a specification> or an .
2. Rationale: Consistent use of terminology.
Replace General Rule 1) with:
1) If is spec ified and an SQL de scriptor area is n ot currently allo cated wh ose nam e is
the value of the immediately contained in and whose
scope is that specified by the immediately contained in , then an
exception condition is ra ised: invalid SQL descriptor name.
15.13
1. Rationale: Editorial - typographical errors.
Replace Conformance Rule 6) with:
6) Without Feature B031, “Basic dynamic SQL”, and Feature F431 "Read-only scrollable cursors", and
Feature F8 31, “Full curs or update” , if an of FOR UPDA TE with o r without a
is specified, then shall not be specified.
2. Rationale: Editorial - typographical errors.
Replace Conformance Rule 8) with:
8) Withou t Feature B 031, “Ba sic dynam ic SQL” , and Feature F431 "R ead-only s crollable curs ors", a
shall not specify .
15.14
1. Rationale: Ensure that the cursor is positioned in same place in returned result set as last set in the called
procedure.
Replace General Rule 4) g) with:
4) g) Cursor CR is placed in the open state
Case:
i) If CR is scrollable the n, let CRCN be the of CR in P. The position of CR in T is
before the row that would be retrieved if the following SQL-statement were executed in P:
12 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
FETCH NEXT FROM CRCN INTO .
ii) Otherwise, the position o f CR is before the first row of T.
16.1
1. Rationale: Delete redundant syntax alternative.
In the Format, replace the production for with:
::=
|
|
|
|
|
|
|
|
2. Rationale: Correct use of undefined BNF term.
Replace Syntax Rule 9) with:
9) Case:
a) If is not specified, then an specification> containing a with a GS for
each that has an associated user-defined type UDT, but is not a user-
defined locator variable is implicit. The of GS is impleme ntation-defin ed and its
is UDT.
b) If contains a with a
GN, then an c ontaining a group specification> with a GS for each that has
an associated user-defined type UDT, but is not a user-defined type locator variable is implicit. The
of GS is GN and its is UDT.
c) If contains a MGS, then
an containing a that
contains MGS extended with a GS for each that
has an associated user-defined type UDT, but is not a user-defined locator variable and the defined type name > of UDT is not contained in any contained in MGS is
implicit. The of GS is implementation-defined and its is UDT.
3. Rationale: Correct use of undefined BNF term.
Replace Syntax Rule 10) with:
10) The implicit or explicit precedes in the text of the
every .
© ISO/IEC 2003 – All rights reserved 13
---------------------- Page: 13 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
4. Rationale: Remove redundant rules that refer to a non-existent BNF term.
Delete Syntax R ules 15) and 16).
5. Rationale: Clarify assignable and comparable.
Replace Syntax Rule 22) h) ii) 1) C) with:
22) h) ii) 1) C) Let the declared type of the sing le SQL param eter of TSF be TPT. PT shall be
assignable to TPT.
Replace Syntax Rule 22) k) i) 6) H) with:
22) k) i) 6) H) For every j, 1 (one) £ j £ a, apply the Syntax Rules of Subclause 10.17,
"Determination of a to-sql function", with TUI and GNI as TYPE and GROUP,
j j
respectively. There shall be an applicable to-sql function TSFI identified by j
name> TSIN . Let TTI be the data type of the single SQ L parameter of TSFI . TSI shall
j j j j
be assignable to TTI .
j
Replace Syntax Rule 22) k) i) 6) I) with:
22) k) i) 6) I) For every l, 1 (one) £ l £ c, apply the Syntax Rules of Subclause 10.17,
"Determination of a to-sql function", with TUIO and GNIO as TYPE and Subclause
l l
7.9, “”, respectively. There shall be an applicable to-sql function
TSFIO identified by TSION . Let TTIO be the data ty pe of the sing le
l l l
SQL param eter of TSFIO . TSIO shall be assignable to TTIO .
l l l
Replace Syntax Rule 22) k) i) 6) J) with:
22) k) i) 6) J) For every k, 1 (one)£ k £ b, apply the Syntax Rules of Subclause 10.15,
"Determination of a from-sql function", with TUO and GNO as TYPE and GROUP,
k k
respectively. There shall be an applicable from-sql function FSFO identified by
k
FSON . Let TRO be the result data type of FSFO . TRO shall be
k k k k
assignable to TSO .
k
Replace Syntax Rule 22) k) i) 6) K) with:
22) k) i) 6) K) For every l, 1 (one) £ l £ c, apply the Syntax Rules of Subclause 10.15,
"Determination of a from-sql function", with TUIO and GNIO as TYPE and GROUP,
l l
respectively. There shall be an applicable from-sql function FSFIO identified by
l
shall be
FSION . Let TRIO be the result data type of FSFIO . TRIO
l l l l
assignable to TSIO .
l
6. Rationale: Editorial.
Replace Syntax Rule 22) k) i) 6) G) with:
22) k) i) 6) G) Let GNI , 1 (one) £ j £ a, be the s corresponding to the j
type name> o f TUI contained in the contained in j
transform g roup spec ification>. Le t GNO , 1 (one) £ k £ b, be the s
k
corresponding to the < user-defined type nam e> of TUO contained in the k
specification > containe d in . Let GNIO , 1 (one)
l
14 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
£ l £ c, be the s corresponding to the of TUIO
l
contained in the contained in specification>.
7. Rationale: Editorial.
Replace Syntax Rule 22) k) i) 8) with:
22) k) i) 8) The of PS is:
BEGIN ATOMIC
DECLARE SVI TUI ;
1 1
.
.
.
DECLARE SVI TUI ;
a a
DECLARE SVO TUO ;
1 1
.
.
.
DECLARE SVO TUO ;
b b
DECLARE SVIO TUIO ;
1 1
.
.
.
DECLARE SVIO TUIO ;
c c
SET SVI = TSIN ( CAST ( PNI AS TTI ));
1 1 1 1
.
.
.
SET SVI = TSIN ( CAST ( PNI AS TTI ));
a a a a
SET SVIO = TSION ( CAST ( PNIO AS TTIO ));
1 1 1
1
.
.
.
SET SVIO = TSION (CAST ( PNIO AS TTIO ));
c c c c
NES;
= CAST ( FSON ( SVO )AS TSO );
SET PNO
1 1 1 1
.
.
.
SET PNO = CAST ( FSON ( SVO )AS TSO );
b b b b
SET PNIO = CAST ( FSION ( SVIO )AS TSIO );
1 1 1 1
.
.
.
SET PNIO = CAST ( FSION ( SVIO )AS TSIO );
c c c c
END;
8. Rationale: Remove rule referring to a non-existent feature.
Delete Genera l Rule 2).
9. Rationale: Specify explicitly the implication that F451, "Character set definition" depends on F461, "Named
characte r sets" .
Replace Conformance Rule 2) with:
2) Withou t Feature F4 61, “Nam ed charac ter sets”, an shall no t contain
© ISO/IEC 2003 – All rights reserved 15
---------------------- Page: 15 ----------------------
ISO/IEC 9075-5:1999/Cor.2:2003(E)
an ...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.