ISOIEC JTC 1SC 32 N 1714 by ert634

VIEWS: 73 PAGES: 168

									                                                  ISO/IEC JTC 1/SC 32 N 1714
                                                                                  Date: 2008-04-12
                                                                                   REPLACES: —



                                      ISO/IEC JTC 1/SC 32

                            Data Management and Interchange

                        Secretariat: United States of America (ANSI)
                      Administered by Farance Inc. on behalf of ANSI



DOCUMENT TYPE              Disposition of comments
TITLE                      Disposition of comments on 32N1593 - FCD 15944-7 Information technology -
                           Business operational view Part 7: e-Business Vocabulary
SOURCE                     WG1 - David Clemis & Jake Knoppers - project editors
PROJECT NUMBER             1.32.31.01.07.00
STATUS                     Disposition of the comments reported in 32N1670 (summary of voting on FCD
                           15944-7 ballot 32N1593). This accompanies FDIS 15944-7 sent to ITTF for
                           ballot
REFERENCES
ACTION ID.                 FYI
REQUESTED
ACTION
DUE DATE
Number of Pages            168
LANGUAGE USED              English
DISTRIBUTION               P & L Members
                           SC Chair
                           WG Conveners and Secretaries

Dr. Timothy Schoechle, Secretary, ISO/IEC JTC 1/SC 32
Farance Inc *, 3066 Sixth Street, Boulder, CO, United States of America
Telephone: +1 303-443-5490; E-mail: Timothy@Schoechle.org
available from the JTC 1/SC 32 WebSite http://www.jtc1sc32.org/
*Farance Inc. administers the ISO/IEC JTC 1/SC 32 Secretariat on behalf of ANSI
                                                                ISO/IEC JTC 1/SC 32/WG1 N       0364R




                                                                                      2008-04-08


Telcordia Technologies, Inc.
                                                           ISO/IEC JTC 1/
                                                             SC32/WG 1
1 Telcordia Drive


Piscataway, NJ 08854
                                                              eBusiness
USA
Direct Line : +1 732 873-8496
Direct Fax : +1 732 296-0834
E-mail: plevine@patmedia.net




TITLE:              Disposition of comments on ISO/IEC JTC 1 SC 32 N1670, Summary of
                    Voting on 32N1593 ISO/IEC FCD 15944-7 Information technology -
                    Business Agreement Semantic Descriptive Techniques Part 7: e-
                    Business Vocabulary
SOURCE:             SC 32/WG 1 Convenor (and Project Co-Editors)
STATUS:             Comment resolution to accompany submission of the FDIS ballot of
                    ISO/IEC 15944-7 Information technology - Business Operational View
                    Part 7: e-Business Vocabulary
ACTION:             Comment resolution for record
Notes:              1. All the SC32/WG1 Ballot resolutions on FCD ballot comments which
                       have been accepted by SC36/WG1 have been implemented.
                    2. The version of SC32/WG1 N364R contains in Columns 7 those made
                       by the Project Co-Editors with respect to ensuring that all the
                       SC32/WG1 decisions with respect to resolution of FCD ballot
                       comments have been implements. Such added notes in column 7 are
                       identified by being preceded by “PCEN” ( = Project Co-Editors’ Notes)
                       .
                    3. In addition, it is noted that as a result of implementing SC32/WG1
                       ballot resolutions on the FCD document for Part 7 that the Project Co-
                       Editors made editing changes from a readability perspective.




                                                                                                    1
 1           2                 (3)           4                                    5                                                              (6)                                     (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                     Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                 on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

CA01   all                              ge        Canada votes Approve with comments.                             Canada fully supports the completion of the 15944-      So noted
                                                                                                                  7 document. Adoption of comments will improve
                                                  Many of the comments made below pertain to a re-                quality and understanding of Part 7.                    PCEN: Done via a revised
                                                  ordering of the sub-clauses in Clause 5.                                                                                Clause 5 (as well as in Clause 6,
                                                                                                                                                                          7 & 8 as per other P-member
                                                  Other comments are of a nature of draft text in                                                                         body comments noted below)
                                                  response to Project Editors’ Notes.                                                                                     .

CA2    all                              ed        Lack of consistency in spelling of “eBusiness”.                 Ensure that all occurrences are modified to read        Accepted
                                                  “eBusiness” spelt with no hyphen and a capital B, is a          “eBusiness” where applicable.
                                                  defined term.                                                                                                           PCEN: Implemented in FDIS
                                                                                                                                                                          document (and also “eAffaires”
                                                                                                                                                                          in French)

CA3    all                              ed        The word “utilize” (and utilized, utilizing, etc.) are used     Ensure that all occurrences of “utilize” and its        Accepted
                                                  incorrectly. The word use,(uses, using, etc.), should be        variants are changed to “use” and its variants,         PCEN: Implemented in FSDIS
                                                  employed instead                                                where applicable.
CA4    Project        lines 45-107,     ge        Remove Project Editors’ Notes and implement notes 5,            (1) remove all Project Editors’ Notes for FDIS          Accepted
       Editors’       pp. 4-5                     6, and 7.                                                       version                                                 PCEN: implemented in FDIS
       Notes                                                                                                      (2) Prepare FDIS document in A4 formal and make         document and done throughout
                                                                                                                  other formatting/presentation changes to comply         the FDIS document
                                                                                                                  with ISO/IEC JTC1 Directives;
                                                                                                                  (3) Assign numbers to all “Rules” “nnn” in
                                                                                                                  sequential order.
CA5    Project        p.4               ed        Canada notes that due to JTC1/SC32 change in the                Canada requests that the Project Editors undertake      Accepted
       Editors’                                   date for its 2007 Plenary meeting upset the SC32/WG1            a due diligence in correcting all minor edits of this
       Notes # 8)                                 schedule for development of Part 7 of ISO/IEC 15944.            nature in the preparation of the FDIS document.         PCEN: implemented in FDIS
                                                  As a result, Canada notes that the FCD document,                                                                        document
                                                  32N1593 contains a number of corrections of minor
                                                  editing nature, (e.g., typos, punctuation, upper/lower
                                                  case, spellings, etc. Canada is of the opinion that minor
                                                  edits of this nature will be corrected by the Project
                                                  Editors in the preparation of the FDIS document.
CA6    Table of       pp 7-8            ed        The Canadian comments below include those of a                  Project Editors to amend Table of Contents as per       Accepted
       Contents                                   nature which, if accepted, will change the Table of             resolution of ballot comments to be corrected in the
                                                  Contents. In addition, there are some minor edits.              Table of Contents.                                      PCEN: implemented in FDIS
                                                                                                                                                                          document
CA7    Foreword       lines 44-45, p.   ge        Text is incomplete                                              Update to summarize the Annexes as agreed to by         Accepted (similar to GB
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                           1
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2                 (3)              4                                 5                                                              (6)                                    (7)

MB1     Clause No./        Paragraph/      Type           Comment (justification for change) by the MB                          Proposed change by the MB                     Secretariat observations
        Subclause         Figure/Table/     of                                                                                                                               on each comment submitted
            No./               Note        com-
          Annex           (e.g. Table 1)   ment2
         (e.g. 3.1)

                      9                                                                                           FCD Ballot Resolution meeting, i.e., make specific       comment)
                                                                                                                  reference to Annex E “Russian” (if provided” and
                                                                                                                                                                           PCEN: implemented in FDIS
                                                                                                                  Annex F “Chinese”, etc.
                                                                                                                                                                           document
CA8    Clause 0.1     line 61              ed       Need to provide reference to the many sources of              At end of “… business transaction”, add a footnote       Accepted
                                                    requirements.                                                 which reads as follows:
                                                                                                                                                                           PCEN: implemented in FDIS
                                                                                                                  See further Clause 0.1.2 and Figure 3 in ISO/IEC         document
                                                                                                                  15944-1:2002 for the various sources of
                                                                                                                  requirements on the business operational view
                                                                                                                  (BOV) aspect of Open-edi which are need
                                                                                                                  integrated and/or taken into account in the multipart
                                                                                                                  ISO/IEC 15944 eBusiness standard.
CA9    Clause 0.1     line 89              ed       A summary sentence providing the key purpose is               At end of line 89, add the following sentences:          Accepted
                                                    missing.
                                                                                                                  A key purpose therefore of Part 7 is to present in a     PCEN: implemented in FDIS
                                                                                                                  single document a consolidated set of all the terms      document
                                                                                                                  and definitions found in the ISO/IEC 14662 “Open
                                                                                                                  edi Reference Model”, and all the parts of the
                                                                                                                  multipart ISO/IEC 15944 eBusiness standard.

                                                                                                                  Another purpose of this standard is to support and
                                                                                                                  facilitate an IT-enabled approach to the creation
                                                                                                                  and maintenance of human interface equivalents
                                                                                                                  (HIEs) for al the eBusiness terms and definitions in
                                                                                                                  multiple languages.
CA10   Clause 0.3     166-169              ed       Remove line 168 and insert added text needed to               At line 166 insert the following text:                   Accepted
                                                    complete Clause 0.3
                                                                                                                  An essential element of any standard is that of          PCEN: implemented in FDIS
                                                                                                                  having clearly and explicitly stated definitions for     document
                                                                                                                  the concepts which it uses or introduces.
                                                                                                                  Definitions capture the key concepts of a standard
                                                                                                                  and form the essential foundation for any standard.
                                                                                                                  As such, it is important that definitions be explicit,
                                                                                                                  unambiguous and precise with respect to the
                                                                                                                  semantics conveyed. At times in order to ensure
                                                                                                                  that the concept being defined is not confused with
                                                                                                                  other related concepts (or words that have common
                                                                                                                  or possible different meanings), international
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                           2
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                    (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                     Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                 on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                  standards introduce, i.e., “invent” new terms as
                                                                                                                  labels for these concepts. This is also because the
                                                                                                                  use of “synonyms” is not allowed in definitions in
                                                                                                                  international standards. The same approach has
                                                                                                                  been taken in this multipart ISO/IEC 15944
                                                                                                                  standard. {See further below Clause 5.3.2}
CA11   Clause 0.3     lines 187-192     ed        The text in lines 187-192 is more of the nature of a            Make the current text in lines 187-192 a footnote to     Accepted
                                                  footnote to Clause 0.3                                          the title for Clause 0.3 (at line 164)
                                                                                                                                                                           PCEN: implemented in FDIS
                                                                                                                                                                           document
CA12   Clause 0.4     line 216          ed        Formatting in the footnote 6                                    Insert “bullets” for the six characteristics.            Accepted
                                                                                                                                                                           PCEN: implemented in FDIS
                                                                                                                                                                           document
CA13   Clause 0.6     line 282          ed        Remove Project Editors’ Notes” and insert missing text          Project Editors to complete text similar to that from    Accepted
                                                                                                                  this Clause in Parts 1, 2, 4 and 5 for the
                                                                                                                  preparation fro the text for the FDIS for this Part 7.   PCEN: implemented in FDIS
                                                                                                                                                                           document
CA14   Clause 1       lines 302-305     ed        Remove Project Editors’ Notes                                   Apply                                                    Accepted
CA15   Clause 1       line 310          ed        Based on the assumption that at the Hangzhou meeting            Change “… Parts 1, 2, 4 and 5” to “… Parts 1, 2, 4,      Accepted
                                                  that Part 6 will go to the FDIS equivalent state amend          5, 6, and 7” and amend footnote 10 accordingly.
                                                  text and footnote. Also Part 7 itself needs to be                                                                        PCEN: implemented in FDIS
                                                  referenced.                                                                                                              document
CA16   Clause 1.2     line 329          ed        Amend to include reference to Part 6                            apply                                                    Accepted
                                                                                                                                                                           PCEN: implemented in FDIS
                                                                                                                                                                           document
CA17   Clause 1.3     line 343          te/ed     It is important to state at the beginning of Clause 1.3         Canada recommends that prior to current line 343,        Accepted
                                                             st
                                                  that this 1 edition of Part 7: (1) focuses on the more          the following text be inserted:
                                                  primitive (or high level) rules and aspects; and, (2) that                                                               PCEN: implemented in FDIS
                                                  more detailed rules, as identified as user requirements          “1) the more detailed level of rules (and possible      document
                                                  via written contributions to JTC1/SC32/WG1 will serve           more detailed level of granularity) for the essential
                                                                                            nd
                                                  as inputs into the development of the 2 edition of this         elements of “eBusiness Vocabulary” entry, as
                                                  standard.                                                       currently specified in Clause 5.3 of this standard”.

                                                  Further, the more detailed aspects of change                    and that the current entries 1), 2), 3) and 4) for
                                                  management of the eBusiness Vocabulary are not                  Clause 1.3 be re-numbered as 3), 4), 5) and 6)
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                           3
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                     (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                    Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)
                                                                       st
                                                  addressed in this 1 edition. It is expected that these          respectively.
                                                  will be similar in nature to those for change
                                                  management for the registration of business objects as          (2) The more detailed level of rules for change
                                                  stated in Clause 6.5 “Registry Status” in ISO/IEC               management of the eBusiness Vocabulary. It is
                                                                                                                                                                    nd
                                                  15944-2:2006.                                                   most likely that these will be addressed in the 2
                                                                                                                  edition (and will be based on or harmonized with
                                                                                                                  the rules in Clause 6.5 “Registration Status” of
                                                                                                                  ISO/IEC 15944-2:2006.
CA18   Clause 1.3     line 346          ed        spelling                                                        change “or” to “of”.                                   Accepted
CA19   Clause 1.3     line 352          ed        In footnote 11 the title of 24751-8 is missing                  insert title for ISO/IEC 24751-8                       Accepted
CA20   Clause 1.3     line 357          ed        If there are no additions to Clause 1.3, delete “5)             Apply.                                                 Accepted
                                                  others?”
CA21   Clause 1.3     line 357          ed        If no other P-member body identifies additional user            To be discussed and decided upon by                    Noted
                                                  requirements for changes to the contents of Clauses 5,          JTC1/SC32/WG1 at Hangzhou, China ballot
                                                                                   nd                                                                                    PCEN: To be carried out by
                                                  6, 7 and/or 8 of Part 78, for a 2 edition during the next       resolution meeting.
                                                  3 years, then JTC1/SC32 should consider Clauses 5, 6,                                                                  Sc32/WG1 Convenor and Part
                                                  7 and 8 of this Part 7 to be “stable”.                                                                                 7 Project Co-Editors during the
                                                                                                                                                                         next three years.
CA22   Clause 2       lines 373-388     ed        Review of Annex A Part 7 reveals that there are no new          (1) Remove Project Editors’ Notes.                     Accepted (references to ITU
                                                  Normative References introduced in Part 7.                      (2) Remove footnote.                                   should be changed to ITU-T
                                                  Consequently, the footnote is no longer needed but the          (3) Remove current text for line 385 and replace by    throughout)
                                                  information it contains needs to be stated in Clause 2          the following text”
                                                  itself.                                                                                                                PCEN: implemented in FDIS
                                                                                                                  The complete set of all normative references, i.e.,    document. Note ITU-R is also
                                                                                                                  ISO/IEC, ISO, and ITU-T standards as well as           referenced. Clauses 2 and
                                                                                                                  “Referenced Specifications” which are applicable to    Annex A have been amended
                                                                                                                  this Part 7 of ISO/IEC 15944 are found in Annexes      accordingly.
                                                                                                                  A.1 “ISO/IEC and ITU-T”, and A.2 “Referenced
                                                                                                                  Specifications” of the Annex A “(Normative)
                                                                                                                  Consolidated list of normative references for the
                                                                                                                  eBusiness Vocabulary”.

CA23   Clause 3       lines 406-550     ed        (1) Remove Project Editors’ Notes in Clause 3                   (1) Apply for FDIS                                     Accepted
                                                  (2) ensure that definitions in Clause 3 are incorporated        (2) Apply for FDIS
                                                  in Annexes B, C and D                                           (3) Apply based on resolution of comments on           PCEN: implemented in FDIS
                                                  (3) remove those definition/term pairs which are not            Clauses 0 - 8                                          document. Only concepts and
                                                  used in Clauses 5-8.                                                                                                   their definitions introduced for

1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                              4
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                     5                                                             (6)                                    (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                            Proposed change by the MB                   Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                                                                         the first time in Part 7 are
                                                                                                                                                                         included in Clause 3. Most of
                                                                                                                                                                         these were taken from existing
                                                                                                                                                                         ISO standards. All the entries in
                                                                                                                                                                         Clause 3 have been integrated
                                                                                                                                                                         into Annexes B, C, D, E, and F.
CA24   Clause 3       line 419          ed        Change references “Clauses 0-7” to “Clauses 0-8”                Apply                                                  Accepted
CA25   Clause         line 464          ed        “commitment” should be in bold                                  Apply                                                  Accepted
       3.05
CA26   Clause         line 465          ed        “electronic” should be in bold                                  Apply                                                  Accepted
       3.05
CA27   Clause         line 509          ed        Date for ISO 12620 should be “1999”                             Correct date                                           Accepted
       3.08
CA28   Clause 4       lines 552-570     ed        (1) Delete Project Editors’ Notes                               (1) Apply.                                             Accepted
                                                  (2) Since Annex B contains the complete and                     (2) Canada recommends that the text to Clause 4
                                                  consolidated set of symbols and abbreviations, there is         simply contain a reference (pointer) to Annex B        PCEN: implemented in FDIS
                                                  little use in presenting a partial set in Clause 4.             similar in nature to that found in Clause 2 and its    document
                                                                                                                  reference (pointer) to Annex A. For example, draft
                                                                                                                  text as follows:

                                                                                                                  The complete set of symbols and abbreviations
                                                                                                                  which are used in this Part 7 as well as in Parts 1,
                                                                                                                  2, 4, 5 and 6 of ISO/IEC 15944 and ISO/IEC
                                                                                                                  14662, i.e., the eBusiness Vocabulary, are found in
                                                                                                                  “Annex B (normative) Consolidated list of symbols
                                                                                                                  and abbreviations”.

CA29   Clause 5       lines 571-908     ed        Review by Canadian experts of Clause 5 and its sub-             (1) Re-order the sub-clauses in 5.3 as follows:        Accepted
                                                  clauses indicated a need for re-ordering of the sub-
                                                  clauses in 5.3. In addition, some of the rules and text in              5.3.5 now Clause 5.3.1;                       PCEN: implemented in FDIS
                                                  current Clause 5.3.5 belong more appropriately in                       leave current Clause 5.3.2 as Clause          document. All other FCD ballot
                                                  Clause 5.2.                                                              5.3.2;                                        comments pertaining to
                                                                                                                        leave current Clause 5.3.3 as Clause            restructuring of Clause 5 have
                                                                                                                           5.3.3;                                        also been implemented in the
                                                                                                                        leave Clause 5.3.4 as Clause 5.3.4;             FDIS document.
                                                                                                                        make current Clause 5.3.1 as Clause
                                                                                                                           5.3.5.
                                                                                                                  (2) Focus Clause 5.3.5 (now 5.3.1) on the structural
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                          5
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                    (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                     Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                 on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                  aspects of the presentation of a definition, the use
                                                                                                                  of NOTES and EXAMPLES and move other rules
                                                                                                                  and text in current Clause 5.3.5 into Clause 5.2.

CA30   Clause 5       lines 571-908     ed        Canada has made comments on specific elements in                Based on resolution of ballot comments on Clause        Accepted
                                                  Clause 5 and its sub-clauses, which if accepted, will           5, Canada requests the Project Editors to develop
                                                  lead to a restructured and improved Clause 5. In                a revised Clause 5 for the FDIS version.                PCEN: implemented in FDIS
                                                  making its comments on Clause 5 and in providing                                                                        document {See above CA29}
                                                  proposed revised draft text in Attachments A, B and C,
                                                  it is not possible to know ahead of time which of the
                                                  Canadian comments on Clause 5 will be accepted as is,
                                                  in a revised form or not accepted..
CA31   Clause 5.1     line 587          ed        It is important to note that all HIEs provided will be          At end of line 587 add footnote with text as follows:   Accepted
                                                  based on international standards for character sets,
                                                  scripts, transliteration/transcription, etc., for languages.    All HIEs of terms and definitions are to be based on    PCEN: implemented in FDIS
                                                                                                                  international standards for character sets, scripts,    document, particularly in a
                                                                                                                  transliteration, transcription, etc., for languages.    revised Clause 3, 6 & 7. Done
                                                                                                                                                                          via ftnts 19 & 20. Note that
                                                                                                                  The applicable international standards of this          further development work here
                                                                                                                                                                                                      nd
                                                                                                                  nature which apply are found in Annex A.                is to be done a part of a 2
                                                                                                                                                                          edition for this standard.
CA32   Clause 5.1     line 590          ed        re: footnote 15. The FCD contains no Annexes of this            Change text of footnote to read:                        Accepted
                                                  nature. Revise footnote.
                                                                                                                  There are more detailed aspects which can be            PCEN: implemented in FDIS
                                                                                                                                                          nd
                                                                                                                  addressed. This should be done in the 2 edition         document in Clause 5.1 & ftnt
                                                                                                                                                    st                    20.
                                                                                                                  based on feedback on use of this 1 edition.
C33    Clause 5.2     lines 595-640     te/ed     As noted above, current Clause 5.3.5 contains rules             Revise Clause 5.2 by:                                   Accepted
                                                  and text which more properly belongs in Clause 5.2.
                                                                                                                           moving existing text in Clause 5.3.5 into     PCEN: implemented in FDIS
                                                  In addition, Clause 5.2 is missing rules and text                         Clause 5.2;                                   document. {see also CA 029}
                                                  necessary for the understanding of Clause 5.2. Some                      add text and rules to provide Clause 5.2
                                                  of this is found in Clause 5.3.5.                                         which the Project Editors noted in Lines
                                                                                                                            602-604 is “under development”.

CA34   Clause 5.2     line 595          ed        Clause 5.2 focuses on Principles and Rules. The title           Change “criteria” to “rules”.                           Accepted
                                                  should reflect this.
CA35   Clause 5.2     lines 600-612     ed        Remove Project Editors’ Notes                                   Apply                                                   Accepted


1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                            6
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                   (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                   Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                               on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

CA36   Clause 5.2     line 621          ed        There is a need to qualify “circularity” with some added        Amend by adding an additional sentence as             Accepted
                                                  text.                                                           follows:
                                                                                                                                                                        PCEN: implemented in FDIS
                                                                                                                  They should be dealt with as a holistic whole, and    document. In addition the project
                                                                                                                  thus be built on each other. Care must therefore      Co-Editors made a concerted
                                                                                                                  be taken in using existing terminology and            effort to ensure that that is no
                                                                                                                  definitions.                                          “circularity” in the complete set
                                                                                                                                                                        of definitions as stated in Annex
                                                                                                                                                                        D.
CA37   Clause 5.2     line 632          ed        An example of the application of this rule is needed.           Add the following text:                               Accepted

                                                                                                                  For example, the concept of “business” inherits,      PCEN: implemented in FDIS
                                                                                                                  i.e., incorporates, the concepts (and their           document. Further ftnt 35 added
                                                                                                                  behaviours) of “process”, “Person”, and “recorded     on “inheritance in Clause 5.3.1”.
                                                                                                                  information”.

CA38   Clause 5.2     line 635          ed        An example of the application of this rule is needed.           Add the following text:                               Accepted

                                                                                                                  For example, the concept (and its definition) of      PCEN: implemented in FDIS
                                                                                                                  “business transaction” forms part of many other       document. Incorporated in the
                                                                                                                  concepts (and their definitions) including “agent”,   rules of now Clause 5.2 & Rule
                                                                                                                  “business event”, “business object”, “business        003.
                                                                                                                  transaction identifier (BTI)”, “constraint”,
                                                                                                                  “consumer”, “vendor”, “unambiguous”, “third party”,
                                                                                                                  “Open-edi scenario (OeS)”, etc.
CA39   Clause 5.2     line 640          te/ed     Remove line 640 and move relevant text and rules form           Apply. Use Attachment B which contains rules and      Attachment B accepted. Add
                                                  Clause 5.3.5 into 5.2                                           text taken from Clause 5.3.5 which should form part   footnote referencing ISO 1087
                                                                                                                  of Clause 5.2 as well as some added text to           and ISO 5127 as sources for
                                                                                                                  improve clarity.                                      this clause. This clause
                                                                                                                                                                        integrates ISO 1087, ISO 5127
                                                                                                                                                                        and ISO Directives toward the
                                                                                                                                                                        development of definitions.
                                                                                                                                                                        PCEN: implemented in FDIS
                                                                                                                                                                        document
CA40   Clause 5.2     line 640          ed        Delete line 640 and replace with existing text and rules        In Attachment B (see below), Canada has provided      Accepted, see CA 39 resolution
                                                  from Clause 5.3.5 which more properly belongs in                draft text and rules to be inserted here.
                                                  Clause 5.2. Add other text and rules to make this                                                                     PCEN: implemented in FDIS

1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                         7
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                         (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                         Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                     on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                  Clause more understandable, i.e. by placing in the              Canada has also noted in Clause 5.3.5 which of the          document
                                                  context of this document.                                       existing FCD text and rules it recommends be
                                                                                                                  moved into Clause 5.2
CA41   Clause 5.3     lines 647 -       ed        The order of the elements needs to be revised to reflect        Change the order of the current five elements to            Accepted
                      655                         the restructuring of Clause 5.                                  read as follows (with current footnotes included):
                                                                                                                                                                              PCEN: implemented in FDIS
                                                                                                                       1)   the definition (of the concept)                   document as per CA29 {See
                                                                                                                       2)   the term (representing the concept)               further Clause 5.3, Rule 006}
                                                                                                                       3)   the abbreviation for the concept (as
                                                                                                                            applicable)
                                                                                                                       4)   the gender code for the term
                                                                                                                       5)   the composite identifier (for the concept)

CA42   Clause 5.3     lines 644+        ed        It is important to make clear the essential characteristics     Insert the definition for controlled vocabulary in          Accepted
                                                  of a “controlled vocabulary”. The definition for                Clause 5.3 and state how it is applied in Part 7.
                                                  controlled vocabulary is stated in Annex D but it should                                                                    PCEN: implemented in FDIS
                                                  also be included under Clause 5.3. Further, it is useful        Canada has provided draft text in support of this           document (as per CA29).
                                                  to provide text on how the concept/definition of                comment as Attachment C, i.e., at line 645.
                                                  controlled vocabulary is applied in this Part 7.
CA43   Clause 5.3     line 657          ed        With the text in Clause 5.3.5 becoming part of Clause           Here is draft text to be inserted at line 657.              Accepted
                                                  5.2, the re-ordering of the 5 essential elements in lines
                                                  651-655 and the deletion of Clause 5.3.5, there is a            “The sub-clauses which follow provide the rules             PCEN: implemented in FDIS
                                                  need to include “bridging” text at the end of the 5.3           governing each of these essential elements.                 document (as per CA29).
                                                  Introduction.                                                   (Those pertaining to the development of a definition
                                                                                                                  for a concept are already stated above in Clause
                                                                                                                  5.2).
CA44   Clause         lines 659-701     ed        Change Clause 5.3.1 to Clause 5.3.5 and restructure             Apply                                                       Accepted
       5.3.1                                      document accordingly
CA45   Clause         lines 703-738     ed        Change Clause 5.3.2 to Clause 5.3.1 and restructure             Apply                                                       Accepted
       5.3.2                                      document accordingly.
CA46   Clause         line 704          ed        text missing                                                    Insert text from Attachment A below before           line   Accepted
       5.3.2                                                                                                      704
CA47   Clause         line 711          ed        Spelling. Change re-sue” to “re-use”                            Apply                                                       Accepted
       5.2.2
CA48   Clause         lines 741-753     ed        Change Clause 5.3.5 to Clause 5.3.2 and restructure             Apply                                                       Accepted
       5.3.3                                      document accordingly
CA49   Clause         line 754          ed        Need for some additional guidance on abbreviations              Add text as follows:                                        Accepted
       5.3.3
                                                                                                                                                                              PCEN: implemented in FDIS
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                                8
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                    (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                     Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                 on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                  Guideline nnnG1:                                        document {See further Clause
                                                                                                                  In the choice of an abbreviation, care should be        5.3.3 and Guideline 020G1}.
                                                                                                                  taken not to devise an abbreviation which
                                                                                                                  already exists, and especially one which is in
                                                                                                                  widespread use.

CA50   Clause         lines 756-782     ed        Change Clause 5.3.4 to Clause 5.3.3 and restructure             Apply                                                   Accepted
       5.3.4                                      document accordingly
CA51   Clause         lines 758-759     ed        The text in these two lines belongs to the previous             Move text to end of existing Clause 5.3.3               Accepted
       5.3.4                                      Clause
CA52   Clause         lines 785-869     ed        Move contents of Clause 5.3.5 to Clause 5.2 and                 Apply                                                   Accepted
       5.3.5                                      integrate into Clause 5.2 as per Attachment B and
                                                  delete current Clause 5.3.5
CA53   Clause         lines 787- 870    ed        The text here more properly belongs in Clause 5.2               Move current 5.3.5 text to 5.2 as per Attachment B      Accepted
       5.3.5
CA54   Clause 5.4     lines 874-883     ed        Delete Project Editors’ Notes and use them to add               Add the following text to the start of Clause 5.4.      Accepted
                                                  introductory text to Clause 5.4.
                                                                                                                  “The rules and text in this Clause focus on the most
                                                                                                                  primitive, i.e., essential aspects only”.
CA55   Clause 5.4     line 895          ed        The notion of “as is” is important and should be noted.         Underline as is and add a footnote, with an             Accepted
                                                                                                                  example, as follows:
                                                                                                                                                                          PCEN: implemented in FDIS
                                                                                                                  “The use of the phrase “as is” indicates that the       document {See further Guideline
                                                                                                                  unique combination of characteristics of the            027G1 & ftnt 44}
                                                                                                                  concept apply but the context of use is not (exactly)
                                                                                                                  the same.

                                                                                                                  The convention in ISO/IEC standards is to indicate
                                                                                                                  such adaptations by indicating the same in the
                                                                                                                  term, (e.g., as in applicant (for an OeRI), “code (in
                                                                                                                  coded domain”) “identifier (in business
                                                                                                                  transaction)”, “information (in information
                                                                                                                  processing), etc.”

CA56   Clause 5.4     line 902          ed        Change (E.g,) to (e.g., )                                       Apply                                                   Accepted
CA57   Clause 5.4     line 906          ed        (1) Spelling in footnote 29, second paragraph, change           Apply                                                   Accepted
                                                  “identification” to “identification”
                                                  (2) Also put titles of Annexes in italics.
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                           9
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                  (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                  Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                              on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

CA58   Clause 6.1     line 912          ed        Left justify title of 6.1                                       Apply here (and elsewhere) as required.              Accepted
CA59   Clause 6.1     line 926          te/ed     It is important that text be added to recognize the fact        Apply.                                               Accepted
                                                  that languages have differing writing systems, scripts,         Need to add a new Clause 9 “Template” to cover
                                                  etc. Here follows possible draft text:                          key elements for specifying a HIE eBusiness          Project Editors requested to
                                                                                                                  Vocabulary.                                          develop a new Clause 9
                                                  “It is noted that human interface equivalents (HIEs) can                                                             “Template” and circulate to WG
                                                  and do exist in languages other than those written in           To be discussed with the Project Editors at the      1 members for review.
                                                  romanized forms, i.e. those of a non-Latin writing              SC32/WG
                                                                                                                                                                       PCEN: Based on resolution of
                                                  system.                                                         1 Hangzhou meeting.
                                                                                                                                                                       other comments the possibility
                                                                                                                                                                       of a Clause 9 “Template” has
                                                  In addition, the legal requirements to be able to support                                                                                    nd
                                                                                                                                                                       been deferred to the 2 edition
                                                  “individual accessibility” requirements may well require
                                                                                                                                                                       for this Part 7. {See Clause 1.3
                                                  HIEs of a Bliss symbols, Braille, sign language, audio,
                                                                                                                                                                       “10}”. However the text in this
                                                  etc., nature.
                                                                                                                                                                       comment has been inserted in
                                                                                                                                                                       Annex G under Rule G06.
                                                  While it is outside of the scope of this standard to
                                                  address and resolve “individual accessibility”
                                                  requirements, its “template” {see Clause 9} is structured
                                                  to be able to support “individual accessibility”
                                                  requirements, i.e. where the buyer in a business
                                                  transaction is an “individual” and those “individual
                                                  accessibility” requirements apply.”

CA60   Clause 6.2     lines 930-934     ed        Delete Project Editors’ Notes                                   Apply                                                Accepted
CA61   Clause 6.2     line 936          ed        Insert the acronym “(HIEs)” after the text.                     Apply                                                Accepted
CA62   Clause 6.2     line 937          ed        Change “P-member” to “P-members”                                Apply                                                Accepted
CA63   Clause 6.2     line 949          ed        Change “included” to “added                                     Apply                                                Accepted
CA64   Clause 6.2     line 963          ed        It is important that any jurisdictional domain submitting       To be discussed at SC32/WG1 Hangzhou meeting.        Accepted
                                                  its (official) set of HIE equivalents to the eBusiness
                                                  Vocabulary as an Annex to be added to Part 7 of this            If accepted, one would add the following rule and    PCEN: implemented in FDIS
                                                  standard do so using a new Clause 9 “template”. This            text to Clause 6.2, 6.3, and 6.4 amending the rule   document as per CA59. The
                                                  Canadian comment also applies to current Clauses 5, 6,          below accordingly.                                   intend of a Clause 9 Template
                                                                                                                                                                                                   st
                                                  7 and 8.                                                                                                             has been replaced in this 1
                                                                                                                  Rule nnn:                                            edition into Annex G (Normative)
                                                                                                                  Any submission by an ISO/IEC, ISO, IEC and/or        and the intend of this and similar
                                                                                                                  ITU P-member body of an Annex of HIEs to this        comments have been captured
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                      10
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                     (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                      Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                  on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                  standard shall use the template of Clause 9 to           in Rules 003 -> 008, as well as
                                                                                                                  specify the criteria governing the presentation          in amended text for Clauses 7 &
                                                                                                                  of the eBusiness Vocabulary in that language.            8.

CA65   Clause 6.3     lines 969-973     ed        Delete Project Editors’ Notes                                   Apply                                                    Accepted
CA66   Clause 6.3     lines 982-984     ed        The grammar of the rule has some errors also its                Change text of rule to read:                             Accepted
                                                  readability needs to be improved.
                                                                                                                  Rule nnn:                                                PCEN: implemented in FDIS
                                                                                                                  Any UN member may submit, via its National               document via Clause 6.3 and
                                                                                                                  Standards body, a new Annex to this standard             Rule 031.
                                                                                                                  of the eBusiness Vocabulary in the official
                                                                                                                  language(s) of its jurisdictional domain”.

CA67   Clause 6.3     lines 969-973     ed        Delete Project Editors’ Notes                                   Apply                                                    Accepted
CA68   Clause 6.3     line 985          ed        IT is important to make provision for those UN member           To be discussed at theSC32/WG1 Hangzhou                  Accepted
                                                  states which may not have a “National Standards body”           meeting.
                                                  to be able to submit an Annex of the eBusiness                                                                           PCEN: implemented in FDIS
                                                  Vocabulary in the language(s) of that country. Here the         Possible solution is to add a Guideline the draft text   document via Clause 6.3 and
                                                  UN ambassador is a common focal point for the                   for which is:                                            Guideline 031G1.
                                                  submission of eBusiness Vocabulary in that language.
                                                                                                                  Guideline nnnG1:
                                                                                                                  Any UN member state, which does not have a
                                                                                                                  National Standards body, may submit, via its
                                                                                                                  UN Ambassador, a new Annex of the eBusiness
                                                                                                                  Vocabulary in the official language(s) of that
                                                                                                                  jurisdictional domain.

CA69   Clause 6.4     lines 1001-       ed        Current points “3)” and “”4)” are actually sub-points of        Change “3)” to “2.1)” and “4)” to “2.2)” and             Accepted
                      1009                        “2)”.                                                           restructure text accordingly.
CA70   Clause 6.4     line 1011         ed        Delete “5)” Other?”                                             Apply                                                    Accepted
CA71   Clause 6.4     line 1030         ed        Footnote 31, delete “Temporary Note”. Leave rest of             Apply                                                    Accepted
                                                  text as is.
CA72   Clause 6.4     lines 1034-       ed        Readability would be improved by inserting a “(1)” and          Apply                                                    Accepted
                      1035                        “(2)” so that the existing text would read as follows:
                                                                                                                                                                           PCEN: implemented in FDIS
                                                  “The following matrix provides examples of the use of:                                                                   document. {See further revised

1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                        11
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                     (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                      Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                  on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                                                                           Clause 6.4}
                                                  (1) the same abbreviations for both the ISO English and
                                                  ISO French terms; and,

                                                  (2) differing abbreviations in ISO English and ISO
                                                  French for the same term”.

CA73   Clause 6.4     line 1039         ed        Delete line                                                     Apply                                                    Accepted
CA74   Clause 7       lines 1056-       ed        The existing Project Editors’ Notes should be converted         Canadian comments on Clause 7 do this. Delete            Accepted
                      1070                        into text where applicable in Clause 7 itself.                  Project Editors’ Notes
                                                                                                                                                                           PCEN: implemented in FDIS
                                                                                                                                                                           document not only for Clause 7
                                                                                                                                                                           but likewise for other Clauses
                                                                                                                                                                           where applicable.
CA75   Clause 7       line 1106         ed        Readability. Change “as stated” to “as presented”               Apply                                                    Accepted
CA76   Clause 7       line 1110         ed        Left justify “Rule nnn”                                         Apply                                                    Accepted
CA77   Clause 7       lines 1129-       te/ed     Project Editors’ Notes pertain to the development of a          To be discussed and decided upon at the                  Accepted
                      1144                        “template” of the nature found in the other Parts of            SC32/WG1 Hangzhou meeting.
                                                  15944. Canada supports the addition of a Clause 9                                                                        PCEN: implemented in FDIS
                                                  which would contain such a template.                            Canada is willing to assist the Project Editors in the   document as per CA59 and via
                                                                                                                  drafting of such a new Clause 9.                         Annex G. The matter of the
                                                                                                                                                                           development of a new Clause 9
                                                                                                                                                                           “Template” has been deferred to
                                                                                                                                                                                nd
                                                                                                                                                                           the 2 edition for Part 7 {See
                                                                                                                                                                           also Clause 1.3}
CA78   Clause 8       lines 1150-       ed        Delete Project Editors’ Notes                                   Apply                                                    Accepted
                      1161
CA79   Clause 8       line 1184         ed        Readability. After “… Vocabulary”, insert “as an”.              Apply                                                    Accepted
CA80   Clause 8       line 1190         ed        Readability, clarity. Change “shall take the form” to           Apply                                                    Accepted
                                                  “shall be maintained in the form”.
CA81   Clause 8       line 1191         te/ed     It is necessary to state who is responsible for the             To be discussed and decided upon at the                  Not accepted. (Similar to
                                                  maintenance of the database containing the “eBusiness           SC32/WG1 Hangzhou meeting.                               decision on UK comment below
                                                  Vocabulary Repository”. Canada assumes that this will                                                                    “GB01”.)
                                                  be the Secretariat for SC32/WG1. It is also possible            Possible draft text for line 1191+ could be:
                                                  that the SC32/WG1 Secretariat may designate some                                                                         At present regular
                                                  organization to do this on its behalf.                          “The Secretariat for JTC1/SC32/WG1 (or its               maintenance procedures apply.
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                        12
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                  (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                  Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                              on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                  successor) shall be responsible for the              Aspects of a Registration
                                                                                                                  maintenance of the eBusiness Vocabulary, i.e.,` as   Authority and making
                                                                                                                  the master repository and as a computer database.    standards available as a
                                                                                                                  The SC32/WG1 Secretariat (or SC32/WG1 itself)        database to be considered for
                                                                                                                  may designate an organization to maintain the        the second version of this
                                                                                                                  eBusiness Vocabulary on its behalf.                  standard. At such time,
                                                                                                                                                                       registration procedures would
                                                                                                                                                                       be followed by a Registration
                                                                                                                                                                       Authority according to ISO/IEC
                                                                                                                                                                       15944-2.
CA82   Clause 8       lines 1192-       te/ed     The comments here are Canada’s response to the                  Canada recommends the addition of a new Clause       WG 1 agreed on the following
                      1219                        “Project Editors’ Notes. Canada supports the                    8.3 which captures the Project Editors’ Notes.       form for the identifier:
                                                  eBusiness Vocabulary Identifier be made a permanent
                                                  identifier, i.e., as an eBVID. Canada also supports the         Canada has prepared draft text for Clause 8.3        ISO/IEC 15944-7::120
                                                  suggestion that it be a composite identifier consisting of      based on these Project Editors’ Notes as
                                                                                                                                                                       WG 1 instructs the Project
                                                  the unique designation “EBVID” (or something like that)         Attachment D.
                                                                                                                                                                       Editors accordingly for use in
                                                  plus a three or four digit number.                                                                                   Clause 8
                                                                                                                  Attachment D to be reviewed, discussed, and
                                                                                                                  decided upon at the SC32/WG1 Hangzhou                PCEN: implemented in FDIS
                                                                                                                  meeting.                                             document. A 3-digit number is
                                                                                                                                                                       being used in Annexes C, D, E
                                                                                                                                                                       and D. Here the “Dnnn” serves
                                                                                                                                                                       as an internal Part 7 reference
                                                                                                                                                                       only. The use of the composite
                                                                                                                                                                       identifier of the form on
                                                                                                                                                                       “ISO/IEC15944-7::120” as an
                                                                                                                                                                       alternative for external purposes
                                                                                                                                                                       is stated in Guideline 026G01.
CA83   Annex A        lines 1230-       ed        Delete Project Editors’ Notes and add in A.1 references         Apply                                                Accepted
                      1250                        to Part 6 and 7 with dates as well as to Parts 3 and 8 as
                                                  “under development”.                                                                                                 PCEN: implemented in FDIS
                                                                                                                                                                       document
CA84   Annex A        lines 1235-       ed        formatting of title needs adjusting                             Left justify title and “wrap” appropriately.         Accepted
                      1236
CA85   Annex A        lines 1238-       ed        Canada supports the Project Editors’ Notes and                  Apply and delete Project Editors’ Notes              Accepted
                      1248                        requests the Project Editors to include in Annex A any
                                                  standards stated as Normative References in Part 3, 6,                                                               PCEN: implemented in FDIS
                                                  or 7, which is not yet included in Annex A.                                                                          document
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                      13
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                  (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                   Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                               on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)


                                                  Canada requests the Project Editors to do this.
CA86   Annex A.1      line 1263         ed        Left justify title and add “ITU” so that the title for A.1      Apply.                                                Accepted
                                                  now reads as:
                                                  “A.1 ISO/IEC, ISO, and ITU”. Ensure also that the
                                                  Table of Contents reflects this change.
CA87   Annex A.1      line 1264         ed        add “ITU” in title                                              Apply                                                 Accepted
CA88   Annex A.1      line 1344         ed        ISO 10241 is missing                                            insert reference to ISO 10241 here.                   Accepted
CA89   Annex A.1      line 1376         ed        Insert references for Parts 4, 5, 6, and 7 of ISO/IEC           Apply                                                 Accepted
                                                  15944
CA90   Annex A.2      line 1394         ed        (1) Left-justify entry                                          (1) apply                                             Accepted
                                                  (2) Amend this sentence in footnote 38 to make it more          (2) Change end of first sentence to read “… those
                                                  specific to Part 7                                              referenced in the ISO/IEC eBusiness standards,
                                                                                                                  namely ISO/IEC 14662 and Parts 1, 2, 3, 4, 5, 6, 7,
                                                                                                                  and 8 of ISO/IEC 15944.
CA91                                                                                                                                                                    Accepted
CA92   Annex B        lines 1438-       ed        Project Editors are requested to implement the Project          Apply. Canada is willing to assist in completing      Accepted
                      1460                        Editors’ Notes in the preparation of the FDIS document.         and updating the Annex B List of Symbols and
                                                                                                                  Abbreviations into an E/F side-by-side format.        PCEN: Implemented in FDIS
                                                                                                                                                                        with French language
                                                                                                                                                                        acronyms being included only
                                                                                                                                                                        where they differ from those in
                                                                                                                                                                        English being included {See
                                                                                                                                                                        further also Clause 5.3.3}.
CA93   Annex B        line 1461         ed        Several acronyms used in Annex D are missing from               Insert the following acronyms (with their             Accepted
                                                  this Annex. They need to be added.                              appropriate descriptions)
                                                                                                                                                                        PCEN: implemented in FDIS
                                                                                                                           DMA Interface                               document. Other acronyms are
                                                                                                                           IRBOI                                       also added in what is now
                                                                                                                           OeBTO                                       Annex B.
                                                                                                                           OeRA
                                                                                                                           pRS
                                                                                                                           OeRD
                                                                                                                           OeRI
                                                                                                                           OeR


1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                      14
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                 (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                 Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                             on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

CA94   Annex B        line 1461         ed        “SRI – Set of Recorded Information” should be lower             Change “Set of Recorded Information” to “set of     Accepted
                                                  case                                                            recorded information”.
CA95   Annex C        lines 1467-       ed        (1) Based on successful completion of ballot comments           (1) Apply                                           Accepted
                      1662                        on Part 6, Annex C should be amended accordingly,               (2) Apply
                                                  i.e., include added references in the matrix and Dnnn                                                               PCEN: implemented in FDIS
                                                  entries should there be added definition/term pairs.                                                                document.
                                                  (2) The definitions in Clause 3 of Part 7 should be
                                                  incorporated into the matrix.
CA96   Annex D        lines 1520-       ed        (1) Definitions and terms included in Part 7, i.e., as          (1) Apply;                                          Accepted
                      1662                        found in Clause 3, or Clauses 5-8 (or 9), which are not         (2) Apply
                                                  yet included in Annex D need to be inserted in the              (3) To be resolved at SC32/WG1 Hangzhou             PCEN: implemented in FDIS
                                                  appropriate place in both Annex D.4 and Annex D.5               meeting as part of discussion on Attachment D and   document. All definitions have
                                                  and also assigned a new ID number, i.e., 259+.                  its draft text for Clause 8.3                       been integrated into a single
                                                                                                                                                                      numeric series ending at 271.
                                                  (2) Definitions and terms included in Part 6 which are                                                              This has been done for Annex
                                                  not yet included in Annex D of Part 7 need to be                                                                    D.2 and D.3 as well as in
                                                  inserted in the appropriate place in both Annex D.4 and                                                             Annexes E and F. This means
                                                  D.5 and also assigned a new ID number, i.e., 259+.                                                                  that additional definitions when
                                                                                                                                                                      incorporated (e.g. from
                                                  (3) Based on the results of the discussions on the new                                                              completion of Part 3 and Part 8)
                                                  Clause 8.3 {See Attachment D} the “D” in Column (1) in                                                              will be numbered as 271+
                                                  Annex D.4 and in Column (1) in Annex D may be
                                                  replaced by “eBVID” (or something else).

CA97   Annex E        lines 1665-       ed        Canada looks forward to Russia submitting the contents          To be discussed at the SC32/WG1 Hangzhou            Draft Annex E containing the
                      1674                        for Annex E. Canada requests Russia to consider also            meeting.                                            Russian text received and to
                                                  providing prior to or part of FCD ballot meeting as part                                                            be incorporated.(See below
                                                  of Annex E a matrix similar to D.4, i.e., the eBusiness                                                             “draft text for Annex E provided
                                                  Vocabulary terms sorted in Russian “alphabetic” order”.                                                             by Russia”.)
                                                                                                                                                                       Final Annex E to be
                                                                                                                                                                      harmonized with Annex D and
                                                                                                                                                                      agreed upon structure for
                                                                                                                                                                      Annex F. Possibility of Annex E
                                                                                                                                                                      having as a chapter, i.e. sub-
                                                                                                                                                                      clause, a “List of eBusiness in
                                                                                                                                                                      Russian (Cyrillic) alphabetical
                                                                                                                                                                      order:.

1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                     15
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                        (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB        Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                    on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                                                             (see resolution of CA98 below)
                                                                                                                                                             PCEN: implemented in FDIS
                                                                                                                                                             document. The Annex E was
                                                                                                                                                             submitted by Russia and forms
                                                                                                                                                             part of the FCD ballot
                                                                                                                                                             comments. Any editing
                                                                                                                                                             corrections to Annex D.2 will
                                                                                                                                                             also be made to Annex E in
                                                                                                                                                             consultation with the Russian
                                                                                                                                                             participants.
CA98   Annex F        lines 1688-       ed        Canada looks forward to China submitting the contents           To be discussed at the SC32/WG1 Hangzhou   Draft Annex F containing
                      1696                        for Annex F. Canada requests China to consider also             meeting.                                   Chinese text received and to
                                                  providing prior to or part of FCD ballot meeting as part                                                   be incorporated. (See below
                                                  of Annex F a matrix similar to D.4, i.e., the eBusiness                                                    “draft text for Annex F provided
                                                  Vocabulary terms sorted in Chinese “alphabetic” order”.                                                    by China”.) Structure for
                                                                                                                                                             Annexes F and E to be
                                                                                                                                                             amended as per the resolution
                                                                                                                                                             of the Chinese ballot
                                                                                                                                                             comments. This includes
                                                                                                                                                             Annex F having as a chapter,
                                                                                                                                                             i.e. sub-clause, a “List of
                                                                                                                                                             eBusiness terms in the order of
                                                                                                                                                             Chinese Bopomofo
                                                                                                                                                             (Hanyupinyin) order”.
                                                                                                                                                             Project Editors to develop a
                                                                                                                                                             “draft” common approach to
                                                                                                                                                             structuring and presentation of
                                                                                                                                                             Annexes F and E, review and
                                                                                                                                                             finalize it with China and
                                                                                                                                                             Russia, and incorporate the
                                                                                                                                                             resulting agreed upon
                                                                                                                                                             approach in the FDIS
                                                                                                                                                             document. Also contents of
                                                                                                                                                             Annexes F & E to be updated
                                                                                                                                                             as per changes to Annex D
                                                                                                                                                             (e.g. to incorporate Part 6).

1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                           16
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1           2               (3)             4                                    5                                                              (6)                                    (7)

MB1     Clause No./     Paragraph/       Type            Comment (justification for change) by the MB                           Proposed change by the MB                    Secretariat observations
        Subclause      Figure/Table/      of                                                                                                                                on each comment submitted
            No./            Note         com-
          Annex        (e.g. Table 1)    ment2
         (e.g. 3.1)

                                                                                                                                                                         (see also below, resolution of
                                                                                                                                                                         China comment CN03.)
                                                                                                                                                                         PCEN: implemented in FDIS
                                                                                                                                                                         document. Chinese Annex F
                                                                                                                                                                         forms part of this ballot
                                                                                                                                                                         document (see below). Any
                                                                                                                                                                         editing corrections made to
                                                                                                                                                                         Annex D.2 will also be made to
                                                                                                                                                                         Annex F in consultation with the
                                                                                                                                                                         Chinese Project Co-Editors.
                                                                                                                                                                         Annex F.3 contains the “List of
                                                                                                                                                                         eBusiness Vocabulary terms in
                                                                                                                                                                         ISO Chienese alphabetical order
                                                                                                                                                                         – Chinese Pinyin order”.
CA99   Annex Z        line 1708         ed        Delete “to be completed”                                        Apply                                                  Accepted
CA10   Annex Z        lines 1708-       te/ed     Canada notes that Annexes A, B, C, and D are all of a           To be discussed and decided upon at the                Accepted
0                     1720                        “Consolidated” nature. Canada suggests that                     SC32/WG1 Hangzhou meeting.
                                                  SC32/WG1 consider making Annex Z also                                                                                  Canadian assistance
                                                  “Consolidated” in nature, i.e., it would contain all the        If this recommendation is accepted, Canada is          appreciated
                                                  Bibliographical References” as found in ISO/IEC 14662,          willing to provide assistance to the Project Editors
                                                                                                                                                                         PCEN: implemented in FDIS
                                                  and Parts 1, 2, 4, 5, 6, and 7 of ISO/IEC 15944.                in developing the contents for such an Annex Z.        document
CA10   Annex Z        line 1709         ed        A Reference added in Attachment B is missing. It is             Insert the following reference to this Bibliography:   Accepted
1                                                 used in Clause 5.2.
                                                                                                                  Knoppers, J.V.Th. Draft Definition for “Open-edi
                                                                                                                  Business Transaction Ontology (OeBTO)”.
                                                                                                                  Prepared for ISO/IEC JTC1/SC32/WG1, May,
                                                                                                                  2002. [Document WG1N0220R]




1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                       17
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
Attachment A – Insert before Line 704

It is important to ensure that the “label i.e., term, assigned to a concept being defined is not confused with other
related concepts (or words) that have a common meaning or many possible different meanings), international
                                                                       1
standards introduce, i.e., invent, a new label as term for a concept” .
                                                                                                     2
Given the fact that this multipart standard integrates operational and legal requirements , the definitions and their
associated terms play a key role in ensuring an integrated and harmonized approach. However, an integrated and
                                                                                                  3
harmonized set of terms and definitions is essential to the continuity of this multipart standard
-----------------

Attachment B –

In the context of the international standards of the ISO, “concept” is defined as:

           concept: unit of knowledge created by a unique combination of characteristics

           NOTE Concepts are not necessarily bound to particular languages. They are, however, influenced by the
           social or cultural background which often leads to different categorizations

           [ISO 1087-1:2000 (3.2.1)]

A “characteristic” in turn is defined as:

           characteristic: abstraction of a property of an object or of a set of objects


1
  In most languages, new words are invented on an on-going basis as new concepts are introduced. For example, according to
the Oxford English Dictionary (OED), over 100 new concepts were added to the English language during the period December,
2006 to September, 2007, as reflected in the addition of new entries in the OED. Merriam-Webster also adds about 100 new
words a year.

Here it is noted that the entries for the OED (or most other dictionaries) include all parts of speech, including proper names,
while standards are limited to nouns and verbs. The entries also include new meanings to existing words/entries, (e.g., lawyer
as a verb).

The concept of “word” is defined as:

         word:        smallest linguistic unit conveying a specific meaning and capable of existing as a separate unit in a
         sentence.

         [ISO 5127:2001 (1.1.2.07)]

A key purpose of a dictionary is to provide all the meanings associated with a “word” in the use of that word in the language of
that dictionary. A “term” on the other hand is defined as:

         term:        designation of a defined concept in a special language by a linguistic expression.

         NOTE A term may consist of one or more words, i.e., simple term, or complex term or even contain symbols.

         [ISO 1087:2000 (5.3.1.2)]

Here each ISO standard, a multipart standard, or a family of standards such as ISO/IEC 14662 and ISO/IEC 15944, are of the
nature of a special language

The same factors which lead to the creation of new concepts, words, etc., in a language also apply to standards development
where new terms are often “invented” to ensure that a new or different concept is not confused with, and differentiated from,
existing terms or labels for a related concept.


2
 See further Clause 0.12 ISO/IEC 15944-1:2002 “Business Agreement Semantic Descriptive Techniques”, and in particular it’s
Figure 2 “Integrated View – Business Operational Requirements: External Constraints Focus”.
3
  The ISO/IEC 14662 “Open-edi Reference Model” and the ISO/IEC 15944 eBusiness standard purposely introduced new
labels, i.e., as “terms” for its concepts and their definitions in order to ensure that these are unique and will not be confused with
the various possible concepts/definitions and their terms which may currently be in use but with differing meanings, i.e.,
semantics.


                                                                                                                                   18
             NOTE Characteristics are used for describing concepts.
                                          4
             [ISO 1087-1:2000 (3.2.4)]

Consequently, the first principle (for the development of a definition of a concept) is the requirement of identifying
the essential characteristics of the concept to be defined. Here, one or more of these characteristics may very well
                                                                      5
themselves be of the nature of concepts which are already defined . Application of this principle is also necessary
to ensure and support interoperability among standards.

The second principle is that the use of concepts already defined in existing international standards must be
                                                          6
maximized, i.e. when and wherever applicable or relevant .

The third principle is that only after the unique combination of characteristics of a concept has been agreed to by
those participating in the development of the standard, that one can (or should) start drafting a definition for that
concept.

The fourth principle is the need to distinguish between the daily common (possibly multiple meanings) of a concept
as found in a dictionary for a “word” versus that of a specific meaning in the context of the standard, i.e., as a
      7
“term” . This principle is of particular relevance to eBusiness standards which apply to many different sectors of
economy, i.e., are cross-sectoral in nature.

Rule nnn:
The characteristics (and their unique combination) of a (new) concept shall be identified and agreed to
prior to the drafting of a definition for that concept.

It is advised that the above rule be implemented through the preparation of a short document or working paper
                                   8
which provides such information. Such documents also serve as useful references and provide a useful reference
and provide a useful explanation of the formation of the definition of a concept, choice of the appropriate
associated term, etc.

Rule nnn:
In the identification of the unique combination of characteristics for a concept, one shall maximize use of
those already defined in existing international standards, i.e., where and whenever applicable or relevant.

Rule nnn:




4
    See further Annex D of ISO/IEC 15944-7 for the definitions for the concepts of “property” and “object”.
5
 For example, concept “NEW” may very well consist of (1) a unique combination of already defined concepts “A”, “E”, and “Q”.
and/or, (2) “(1)” plus one or more added characteristics.
6
  The key objective here is that of “do not re-invent the wheel”, “use what exists”. It is also very unlikely that a new” concept is
totally new.
7
  The purpose of a dictionary is to capture in a single document and in alphabetical order all the meanings (one or more)
associated with a character or unique combination of characters, i.e., “words” in that language. Consequently, where a “word”
in a language has more than one (common use) meaning, one needs to specify in a standard, i.e., as an entry in its Clause 3,
which of the multiple common use meanings of that concept apply in the context of that standard. This is done by having a
“term/definition in Clause 3.
8
  For examples of how this rule has already been applied in the development of the multipart ISO/IEC 15944 eBusiness
standard see the following examples in JTC1/SC32/WG1 documents:

          Pereira, M.J.; Knoppers, J.V.Th. Languages and Jurisdiction: "Natural", "Special", "Official", "Artificial", "Indexing",
           "Programming,” etc. Prepared for ISO/IEC JTC1/SC32/WG1. February, 2002. [Document WG1N210R]

          Knoppers, J.V.Th.; Pereira, M.J. What is a "Principle"? What is a "Rule"?: Need for Definitions. Prepared for ISO/IEC
           JTC1/SC32/WG1. February, 2002. [Document WG1N211R]

          Knoppers, J.V. Th. Draft Definition for “Open-edi Business Transaction Ontology (OeBTO)”. Prepared for ISO/IEC
           JTC1/SC32/WG1, May, 2002. [Document WG1N0220R]



                                                                                                                                      19
Any concept requiring a definition for the clarity of the understanding and use of the ISOIEC JTC1
international eBusiness standards shall be included in that standard.

This means that the concept is: (1) central to the understanding of the standard; (2) is used at least twice in the
                                          9
standard; and, (3) is not self-explanatory .

An essential, if not most important, element of any standard is the identification of the concepts on which it is
based. The primary purpose of a “definition” is to serve as a descriptive statement to differentiate one concept
from another. Thus definitions capture the key concepts of a standard and form the foundation of any standard.
As such, it is important that definitions be explicit, unambiguous with respect to the concept to which it pertains and
the semantics to be conveyed.

An essential aspect of electronic data interchange in support of a business transaction is that it includes the making
of commitments among autonomous Persons as parties to a business transaction means that the definition in the
eBusiness Vocabulary must integrate operational legal requirements.

Explicit and unambiguous definitions play a key role in ensuring an integrated and harmonized approach in
specifying BOV aspects. They also serve as a bridge to standards in the field of information and communication
technologies (ICT) as well as to other sectors.

The Directives of ISO/IEC JTC1 place great emphasis on ensuring that definitions be as clear, explicit and
unambiguous as possible. As such, the following rules apply.

Rule nnn:
There must be 1) a business case and rationale for the need to introduce a (new) concept into an
                                                                      10
international standard with its resulting definition and assigned term ; and, 2) such a business case and
rationale must maximize re-use and integration of existing international standards, i.e. those of ISO, IEC,
                   11
ISO/IEC and/or ITU .

Rule nnn:
The descriptive statement comprising a definition must be clear, explicit and unambiguous and stated in
the form of a single sentence.

The primary reason for the need for the descriptive statement comprising the definition of a concept to be
“unambiguous” is because the use of the definition in an eBusiness context , of whatever nature and for whatever
commonly agreed upon goal among the parties involved in a business transaction, is because the use of the
concept and its definition pertains to the making of “commitments” among the parties involved and the resulting
legal obligations (including those of the applicable jurisdictional domains).

Rule nnn:
Only a concept with a single definition shall be included and both the definition and associated term shall
be stated in the singular.

At times, a “NOTE” (or NOTES) is used to provide additional information, qualification, criteria, exceptions, to assist
in the understanding and use of the concept. Also, at times EXAMPLE(S) is included where deemed useful.

Rule nnn:
Any definition of an eBusiness concept must be developed with two or more human interface
equivalencies (HIEs) in order to maximize its unambiguity and subsequent use in support of any and all
commitments made among parties to a business transaction.

The development of two or more HIEs for each term and definition should be considered to be of an “ISO 9000’
and/or “ISO 14000” nature, i.e. as a necessary quality and integrity control check. It is only in the development of

9
  It is noted that often a commonly used word, (e.g., chip), has multiple definitions in a dictionary. eBusiness is cross-sectorial in
nature. It includes both (1) the field of information and communication technologies (ICT), as well as, (2) the many other fields
(or industry sectors) and public sector activities. As such, it is important not only to have any concept defined explicitly and
unambiguously but also to choose a label as a “term” which meets the same criteria among all sectors. Consequently, “chip” as
a term representing a concept is not self-explanatory. In addition, what may be considered as self-explanatory in one language
may well not be in another, (e.g., what is “chip” in other languages?)
10
   For an insight into the rationale for the development of the definition for “principle” and “rule”, see JTC1/SC32/WG1 document
N211R “What is a "Principle"? What is a "Rule"?: Need for Definitions”.
11
  It is noted that at times, ISO/IEC JTC1 and ITU work together to develop international standards which are assigned both
ISO/IEC international standard document numbers as well as international standard ITU numbers, i.e., as ITU
recommendations.
                                                                                                                                   20
the text of a definition of a concept into its equivalent text into one or more other HIEs that ambiguities in the source
text are “ferreted” out., i.e., identified.

Rule nnn:
As stated in Clause 5.1 above, a concept can consist of, i.e. inherit, one or more other concepts.
Consequently, where this occurs, the definition for a concept of this nature shall explicitly support this
requirement.


Rule nnn:
When a concept incorporates one or more other concepts, the terms representing these concepts shall be
                12
included in bold in the definition for that concept.
                                                                          13
For example, the concept of “business” incorporates, i.e., inherits , three other concepts (and thus their definitions)
namely: (1) process; (2) Person; and, (3) recorded information.

The definition of “business” (in English and French), in order to support this approach, thus appears as:

business                                                affaire
series of processes, each having a clearly              série de processus, ayant chacun une
understood purpose, involving more than one             finalité clairement définie, impliquant plus
Person, realised through the exchange of                d'une Personne, réalisés par échange
recorded information and directed towards               d'information enregistrée et tendant à
some mutually agreed upon goal, extending
                                                        l'accomplissement d'un objectif accepté
over a period of time
                                                        par accord mutuel pour une certaine
                                                        période de temps
[ISO/IEC 14662 :2004 (3.2)]


There is no bold text in NOTES or EXAMPLES.




12
  Where in the writing system of a language the use of bold does not “visually” serve the intended purpose, i.e., indicate that
use of a term, one may use a different font for the same purpose, (e.g., see Annex E in ISO/IEC 15944-7 here for the Chinese
where a different font is used instead of bold).
13
     Project Editors requested to provide a short paragraph explaining “inheritance”
                                                                                                                            21
Attachment C
The eBusiness Vocabulary is of the nature of a “controlled vocabulary” which is defined as:

           controlled vocabulary (CV): vocabulary for which the entries, i.e., definition/term pairs, are controlled
           by a Source Authority based on a rulebase and process for addition/deletion of entries

           NOTE 1 In a controlled vocabulary, there is a one-to-one relationship of definition and term.

           EXAMPLE The contents of "Clause 3 Definitions" in ISO/IEC standards are examples of controlled
           vocabularies with the entities being identified and referenced through their ID code, i.e., via their clause
           numbers.

           NOTE 2 In a multilingual controlled vocabulary, the definition/term pairs in the languages utilized are
           deemed to be equivalent, i.e., with respect to their semantics.

           NOTE 3 The rule base governing a controlled vocabulary may include a predefined concept system.

           [ISO/IEC 15944-5:2006 (3.34)]

The key characteristics of a controlled vocabulary are:

       1) It is a vocabulary, i.e., it is not a dictionary, glossary, etc.

       2) Its entries consist of definitions/term pairs for each concept forming part of the controlled vocabulary.

       3) The aspects controlled as to the inclusion of entries rests with a Source Authority and is managed through
          a rulebase process for the addition/deletion of entries.

With respect to this eBusiness Vocabulary, the Source Authority is ISO/IEC JTC1/SC32 “Data Management and
Interchange”. The actual sources for the definition/term pairs are the normative references stated in Clause 2 of an
ISO standard which in this Part 7 are consolidated in Annex A (normative).

The rulebase and process governing the eBusiness Vocabulary are a combination of those:
                                                                       14
       1) stated in Part 1 and Part 2 of the ISO/IEC Directives             (which are general in nature);

       2) those of a specific and direct nature applicable to the eBusiness Vocabulary as stated in Clauses 5, 6, 7,
                                15
          and 8 of this standard .; and,

     3) the inclusion of all the terms and definitions as stated in Clause 3 of ISO/IEC 14662 and the parts of the
           multipart ISO/IEC 15944 eBusiness standard (in the form of normative Annexes in Part 7).
----------------

Attachment D
Notes:

       1) This is draft text only and is to be reviewed, discussed and amended at the SC32/WG1 Hangzhou meeting
          when the FCD ballot comments are decided upon.

       2) The rules and text provided in the draft below for Clause 8.3 are based on or harmonized with:

               those of ISO/IEC 15944-1 re: “identifier”;

               those of ISO/IEC 15944-2 re: Registration of business objects and their identifiers;


14
     Need to add a footnote citing the full titles and reference and URL.
15
   The rules in Clauses 5, 6, 7, and 8, in this Part 7 are harmonized with and support those found in the ISO/IEC JTC1
Directives.


                                                                                                                          22
               those of ISO/IEC 6523, 7501, and 7812 for maintenance of registries and identification schemas.

       3) SC32/WGG1 needs to decide on the first part of the composite identifier here. It could be “ISO/IEC 15944-
          7”, etc., “eBVID”, some other unique acronym, etc.

       4) Any added entries to the FCD version of Annex D will be assigned 259+ ID numbers, i.e., those new in
          Part 6 or Part 7. There are two reasons here. The first is to highlight the fact that the “numbers” are
          assigned in sequential order. The second is that the number itself has no specific meaning.

       5) The eBusiness Vocabulary in Annex D can be viewed as a coded domain, in which case the “front” part of
          the composite identifier would be ISO/IEC 15944-7:01 followed by the 3(or 4) digit number in Annex D.

       6) Consideration should also be given to the creation of a unique (shorter) designator for use in XML
          namespace, (e.g., eBVID for the first part of the composite identifier followed by the 3(or 4) digit number as
          per Annex D).

Clause 8.3 – Rules governing the assignment of a unique identifier for each entry in the eBusiness
             Vocabulary

This Clause contains the basic rules governing the assignment of a unique identifier to each entry in the eBusiness
                                                                         16
Vocabulary. As such, this Clause serves as the Registration Schema (RS) for Part 7. Further, ISO/IEC
                 17                                                            18
JTC1/SC32/WG1 through this Part 7 serves as the Registration Authority (RA) for the eBusiness Vocabulary.

It is noted that in Annex A in this Part 7, thirty-seven (37) other international standards serve as Normative
References. In addition, over 25% of the entries in the eBusiness Vocabulary are based on international standards
other than either ISO/IEC 14662 or the multipart ISO/IEC 15944 standards.
                                        st
It is also recognized that in this 1 edition of Part 7:

       1) all the entries in the Annex D eBusiness Vocabulary will remain stable and fixed; and,

       2) any future entries to Annex D eBusiness Vocabulary will each be assigned a unique identifier.

Rule nnn:
The entries in the eBusiness Vocabulary shall consist of those terms and definitions which are Clause 3
sub-clauses in ISO/IEC 14662 and all parts of the ISO/IEC 15944 multipart standard, i.e., those which have
                      19 20
passed the FDIS stage .

Rule nnn:
Each definition/term entry entered in the eBusiness Vocabulary shall be assigned a unique and
                                                                                                    21
unambiguous identifier as a composite identifier, i.e., an eBusiness Vocabulary identifier (eBVID).

Rule nnn:
The eBusiness Vocabulary identifier as a composite identifier is composed of: (1) the ID for this standard,
i.e., ISO/IEC 15944-7; (2) code for the coded domain (the acronym “eBVID”); and, (3) the 3- (or 4) digit entry
number as stated in normative Annex D.5 of ISO/IEC 15944-7.

The proposed draft definition of eBusiness Vocabulary identifier (eBVID) is:

16
     See Annex D for the definition of “Registration Schema (RS)”.
17
  Should ISO/IEC JTC1 decide to reorganize its Sub-committees (SCs) and their Working Groups (WGs), then whichever SC
or WG is responsible for ISO/IEC 14662 and the multipart ISO/IEC 15944 standards assumes the responsibility (or role) of
Registration Authority.
18
     See Annex D for the definition of “Registration Authority (RA)”.
19
   At times, there is a delay (of several months) between the standard successfully passing its FDIS ballot stage and the
issuance of the resulting “IS” document by the ITTF.
20                                                         nd
     This rule is to be reviewed in preparation of the 2        edition for this standard.
21
  Temporary Footnote:
The acronym “eBVID” is currently not in current use (as per Google search). It therefore is available as part of the composite
identifier. To be discussed further in Hangzhou.


                                                                                                                           23
         eBusiness Vocabulary identifier (eBVID):            a composite identifier permanently assigned to a single
         definition/term pair in compliance with the rules of the Registration Schema (RS) of ISO/IEC 15944-
         7:2008.

Notes:

   1) If the eBusiness Vocabulary identifier is considered to be of the nature of a coded domain, the composite
      identifiers will be of the nature:

            ISO/IEC 15499-4:01:020; or,
            ISO/IEC 15944-7:01:179,

         with the 3- (or 4) digit number at the end being taken from Annex D.5

   2) If one finds “eBVID” to be a more recognizable ID for the Annex D coded domain, then the composite
      identifier would be of the nature:

            ISO/IEC 15944-7:eBVID020; or
            ISO/IEC 15944-7:eBVID179.

   3) There may be other approaches as well.

   4) To be discussed and decided upon by SC32/WG1 at its Hangzhou meeting with draft Clause 8.3 being
      amended accordingly.

   5) As part of this discussion, SC32/WG1 also needs to decide on how the eBVID is to be represented as a
      unique “XML namespace”.

Guideline nnnG1:
A short form of the composite identifier that could be used is “eBVID020”, or “eBVID179”, i.e. the
combination of components (2) and (3) only. Component (1) is understood as the default.

Rule nnn:
An eBusiness Vocabulary identifier once assigned shall not be reassigned or re-used.

Rule nnn:
A change in the label, i.e., term, assigned to the definition of a concept is deemed significant and where
this occurs the revised entry shall be assigned a new eBVID.

Rule nnn:
A change in the definition of a concept which changes or adds a characteristic is considered to be a new
concept therefore shall be assigned a new term to reflect the new concept. Where this new concept and its
definition/term pair replaces an existing concept (and its definition/term pair), the current entry in the
eBusiness Vocabulary shall be marked “cancelled and replaced by”.




                                                                                                                  24
 1            2               (3)              4                                  5                                                              (6)                                   (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                 Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                              on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)




CN01                                      ge       China supports this standards project and looks forward                                                               So noted
                                                   to its successful completion.
CN02   Annex F                            ed       China has prepared a draft for the Annex F, as the                Insert Annex F. Contents of draft Annex F to be     Accepted; also to be applied
                                                   Chinese version of the eBusiness Vocabulary. This                 discussed and reviewed at the SC32/WG1              to Annex E
                                                   Annex F is attached our ballot comments.                          Hangzhou meeting.
                                                                                                                                                                         PCEN: implemented in FDIS
                                                   Should there be changes or additions to the entries in                                                                document. {See also CA98
                                                   Annex D, on which Annex F is based, China will amend                                                                  above}
                                                   Annex F accordingly. Here China will work with the Part
                                                   7 Project Editors on this and other related matters in
                                                   finalizing the contents of Annex F
CN03       Annex D                        ge       China observes that there are no identifier and English           Add a chapter in Annex D “list of eBusiness terms   Resolved as follows by:
                                                   ordering of list of terms in Annex D and rest of the FCD          in English Alphabetical order".
                                                   document. This makes the search for a specific term               Add a chapter in Annex D ”List of eBusiness terms   1. Making clear in the
                                                   difficult, for the users in English jurisdictional domain.        in the order of identifier”                         relevant Annexes that the list
                                                                                                                                                                         of eBusiness terms in the
                                                                                                                                                                         order of identifier is already
                                                                                                                                                                         provided in Clause 3.
                                                                                                                                                                         2. Explain that Annex D.5 is
                                                                                                                                                                         in English alphabetical order.
                                                                                                                                                                         Place Annex D.4, French
                                                                                                                                                                         alphabetical order after D.5,
                                                                                                                                                                         and take the same approach
                                                                                                                                                                         for Annexes E and F.
                                                                                                                                                                         3. Project Editors are
                                                                                                                                                                         instructed to work with China
                                                                                                                                                                         and Russia to encourage the
                                                                                                                                                                         inclusion of a sub-clause in
                                                                                                                                                                         Annexes E and F of a list of
                                                                                                                                                                         terms in the alphabetical
                                                                                                                                                                         order in their language.
                                                                                                                                                                         (see also above, resolution of
                                                                                                                                                                         Canada comment CA98
                                                                                                                                                                         PCEN: implemented in FDIS

1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                     25
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1            2               (3)              4                                  5                                                              (6)                               (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB              Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                           on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                                                                                                                                      as per resolution of CA98.
                                                                                                                                                                      document. Note that the sub-
                                                                                                                                                                      clauses of Annex D have
                                                                                                                                                                      been re-organized so that D.4
                                                                                                                                                                      and D.5 are now D.3 and D.4.
CN04         All parts                    ed       The tables in the current 15944 part 7 FCD are with no            Add number and title for each table in the FCD   Accepted. All “tables” now
                                                   title and number                                                  document.                                        have their own ID and are
                                                                                                                                                                      also referenced on the ToC.




1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                 26
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1            2               (3)              4                                  5                                                              (6)                                    (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                  Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                               on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)




GB01     General                          ge       This draft standard consists of three distinct parts; firstly,    This standard should be reduced to the rules for     Not accepted. An effort is
                                                   a set of rules governing the development of definitions;          deriving definitions in the eBusiness sphere. The    being made to complete the
                                                   secondly some consolidated lists of references from other         other elements should be published as databases,     first edition of this standard
                                                   related standards; and thirdly, tables of equivalences of         maintained on-line. There are precedents for such    without undertaking the
                                                   concepts and definitions in a number (two, initially) of          publication in a number of other ISO committees,     extensive procedure of
                                                   natural languages. It would be reasonable to split it into        mostly outside JTC1. Refer to the ISO Technical      gaining JTC 1 approval of a
                                                   three, or possibly just two, separate standards. Rather           Management Board work on “Standards as               Registration Authority (RA)
                                                   than adding sets of definitions to the standard itself, it        Databases”.                                          that that would be needed to
                                                   may be better to establish a register managed by a                                                                     maintain the proposed
                                                   Registration Authority.                                                                                                databases. The feasibility of
                                                                                                                                                                          RA support will be
                                                                                                                                                                          considered for the second
                                                                                                                                                                          edition of this standard.
GB02     General                          ge       The document contains a large number of “Project                  The document that results from the changes           Not accepted. Extensive
                                                   Editor’s Notes” that identify in general terms changes that       identified in the current document and other         information was provided via
                                                   will be introduced into the next version of the document.         changes made in response to ballot comments          attachments to the FCD and
                                                   The intention is expressed that this next version will be         should be published and balloted again as an         Project Editors’ notes,
                                                   published as an FDIS, implying that the changes will not          FCD.                                                 allowing for sufficient
                                                   be subject to review. This is unacceptable, as it is not                                                               understanding of what was
                                                   possible to correct errors at that stage without returning                                                             being proposed for this
                                                   the document to a much earlier stage of the development                                                                standard. The delay of an
                                                   process.                                                                                                               additional FCD ballot is not
                                                                                                                                                                          warranted.
GB03     General                          ge       The first paragraph of Clause 6.5.2, “Footnotes to the            Review the footnotes and remove those that are of    Accepted. Project Editors
                                                   text”, in part 2 of the ISO/IEC Directives states “Footnotes      less than major significance. Consideration should   will review footnotes and
                                                   to the text give additional information; their use shall be       be given to converting those that remain into        revise the text as proposed.
                                                   kept to a minimum. A footnote shall not contain                   Notes integrated into the text of the document.
                                                                                                                     See ISO/IEC Directives, part 2, clause 6.5.1.        PCEN: implemented in FDIS
                                                   requirements or any information considered
                                                   indispensable for the use of the document.” The                                                                        document and kept in mind
                                                   extensive use of footnotes in this document does not                                                                   through the preparation of the
                                                                                                                                                                          FDIS document.
                                                   seem consistent with at least the second part of the first
                                                   sentence.
GB04     Foreword                         ed       The Foreword states that there are several Annexes, but           Although not required by the Directives, it is       Accepted
                                                   does not enumerate them or state whether they are                 common practice to identify the Annexes in the

1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                       27
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1             2              (3)              4                                  5                                                              (6)                                        (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                       Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                                    on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                   Normative or Informative. Is it really necessary to state         Introduction. The reference to the importance of
                                                   that Annex D is the most important? On what scale is its          Annex D should be deleted.
                                                   value judged relative to the value of other Annexes?
GB05     Foreword                         ed       The fifth paragraph refers to part 5 in a context where the                                                                 Accepted
                                                   reference should be to part 7.
GB06     Foreword                         ed       The final sentence of the Foreword has two terminal full          If the sentence is retained (see earlier comment),        Accepted
                                                   stops.                                                            delete one of the full stops.
GB07     Introduction                     ed       Much of the material in the Introduction is of a general          The generalities should be reduced to a minimum           Not accepted. The
                                                   tutorial nature and relevant to ISO/IEC 15944 as a whole,         and be identifiable as such. Tutorial material and        Introduction conforms to the
                                                   rather than just to this Part. It is not always clear which       specific references to the history of development         pattern established for other
                                                   elements are specific to this part and which are general          of the standard as a whole and this part in               parts of ISO/IEC 15944.
                                                   commentary and tutorial.                                          particular should be minimised. Some of the
                                                                                                                     material might be better located in the normative
                                                                                                                     text of the Part or in an Informative Annex.
                                                                                                                     All that is really necessary is a brief introduction to
                                                                                                                     the overall standard, followed by a brief statement
                                                                                                                     of the purpose of the current part. The first
                                                                                                                     sentence probably says enough about the general
                                                                                                                     background. A second sentence stating that this
                                                                                                                     part establishes a common vocabulary for use in
                                                                                                                     the domain would be enough to complete the
                                                                                                                     introduction for almost everyone.
GB08     0.1                              ed       It is not necessary to specify the year of publication.           Delete “:200n” from the first sentence.                   Accepted
                                                   Presumably the relationship between part 7 and other
                                                   parts of 15944 is reasonably stable.
GB09     0.1                              ed       The instance of “BOV” in the first sentence is the first          Change “BOV” to “Business Operational View                Accepted
                                                   occurrence of the abbreviation in the standard. The full          (BOV)”.
                                                   term should be used here.
GB10     0.2                              te       At least some of clause 0.2 seems to be making                    Delete those elements of the clause that are pure         Not accepted. Subclause 0.2
                                                   normative statements, statements that need to be                  commentary and move the rest to an appropriate            is the same as in other parts
                                                   understood in order to interpret other elements of the            point in the Normative text of the standard.              of ISO/IEC 15944.
                                                   standard.


1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                           28
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1             2              (3)              4                                  5                                                              (6)                                     (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                    Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                                 on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB11     0.2             Footnote 2       ed       Numbered elements in standards are clauses and                    If the footnote is retained, change “section” to       Accepted
                                                   subclauses, not sections.                                         “subclause”, or simply delete it. (See 6.6.7.3.1 in
                                                                                                                     part 2 of the ISO/IEC Directives.)
GB12     0.3                              ed       This clause contains material that should be obvious to           Delete the subclause (and when the occasion            Not accepted. Subclause 0.3
                                                   anyone using a standard, and is thus unnecessary.                 arises delete the corresponding text from other        is the same as in other parts
                                                                                                                     parts of 15944.)                                       of ISO/IEC 15944. Although
                                                                                                                                                                            this material may be obvious
                                                                                                                                                                            to anyone using a standard,
                                                                                                                                                                            this subclause has been
                                                                                                                                                                            included as rationale for
                                                                                                                                                                            overriding numerous
                                                                                                                                                                            objections to the precision
                                                                                                                                                                            taken on defining terms in
                                                                                                                                                                            this multi-part standard.
GB13     1.1             Paragraph 1      ed       It is not necessary to refer to the standard as being the         Replace the paragraph with, for example:               Accepted with the addition of
                                                   first edition. The phrasing of the first sentence gives the                                                              Part 6, work on which will
                                                   initial impression that we are reading some later edition         This Part of ISO/IEC 15944 provides a                  have been completed and
                                                                                                                     consolidated eBusiness vocabulary, defining
                                                   and contrasting its scope with what went before. Similarly                                                               ready for publication during
                                                   it is not necessary to specify the edition number of              concepts used in ISO/IEC 14662:2007 and the            the time period required to
                                                                                                                     other parts of ISO/IEC 15944.                          prepare the FDIS version.
                                                   ISO/IEC 14662, the year of publication is sufficient, or
                                                   explicitly identify the other published parts of 15944.                       Note: At the time of publication of this   PCEN: implemented in FDIS
                                                   Rather than use a footnote to refer to the parts still under                  Part of ISO/IEC 15944, parts 1, 2 4 and    document
                                                   development, a Note in the body of the text should be                         5 had been published and parts 3, 6
                                                   used.                                                                         and 8 were under development.
GB14     1.1                              ed       Rather than begin each paragraph after the first with “Part                                                              Not accepted. Proper nouns
                                                   7”, it is simpler, and makes easier reading, to begin “It ...”.                                                          should be used for a subject
                                                                                                                                                                            in each new paragraph.
GB15     1.1                              ed       The second paragraph of the clause seems more                     The second paragraph should be moved to                Not accepted. The logical
                                                   significant with respect to the main body of the document         become the first and references to the document        progression of the subclause
                                                   than does the first.                                              itself amended accordingly.                            requires that the paragraphs
                                                                                                                                                                            remain in their current
                                                                                                                                                                            sequence.



1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                       29
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1             2              (3)              4                                  5                                                              (6)                                     (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                   Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                                on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB16     1.2                              ed       Rather than beginning “This Part 7”, it would be clearer                                                                Accepted with modifications.
                                                   and more precise if the paragraph began “This                                                                           It would be OK to say “This
                                                   International Standard” or “ISO/IEC 15944”. A similar                                                                   Part of ISO/IEC 15944 is built
                                                   comment applies to the reference at the end of the                                                                      on ISO/IEC 14662 and
                                                   sentence. A consistent approach should be followed                                                                      existing Parts 1, 2, 4 and 5 of
                                                   throughout the document; for example a different (and                                                                   ISO/IEC 15944. The
                                                   better) style is used in 1.3.                                                                                           exclusions which apply to
                                                                                                                                                                           one or more of these
                                                                                                                                                                           standards apply to this Part.”

                                                                                                                                                                           PCEN: implemented in FDIS
                                                                                                                                                                           document
GB17     1.2                              te       The references to other standards in this clause make                                                                   Accepted
                                                   their content indispensible for full understanding the
                                                   current document. They should therefore be included in
                                                   the Normative References in clause 2.
GB18     1.3                              te       The limitation to members of the United Nations in item 4         Rather than scatter references to the UN              Not accepted. Item 4 says
                                                   seems unduly restrictive. Not all countries are members           throughout the document, it may be better to say      nothing about restricting the
                                                   of the UN, and some of the non-members are significant            something in the Scope to the effect that the UN      availability of this standard.
                                                   participants in international electronic trade.                   has the authority to recognise countries and          Change “subtypes” to
                                                                                                                     languages, but that the definitions provided by the   “administrative subdivisions.”
                                                                                                                     standard are available for use in interchange         Note that further discussion
                                                                                                                     between all bodies and jurisdictions, recognised or   of this item is provided in
                                                                                                                     not.                                                  Clause 6.


GB19     1.4                              te       The material that constitutes this clause does not seem           Delete subclause 1.4                                  Not accepted. Subclause 1.4
                                                   necessary. It describes what is essentially the default                                                                 is needed to emphasize that
                                                   situation, and so adds no value to the standard.                                                                        this standard focuses on the
                                                                                                                                                                           “what” not the “how.” Similar
                                                                                                                                                                           statements are made in
                                                                                                                                                                           ISO/IEC 15944-5 and
                                                                                                                                                                           ISO/IEC 11179.




1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                       30
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1            2               (3)              4                                  5                                                              (6)                                        (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                      Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                                   on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB20     2               Footnote 13      te       Footnote 13 seems to be based on a misunderstanding of            Delete footnote 13. If, for any reason, the footnote     Accommodated by making
                                                   the concept of “Normative reference”. Clause 2 should             is retained, delete the send full stop at the end of     the footnote part of the text.
                                                   provide references for all the standards on which this            the first sentence.
                                                   document depends. Whether or not they are referenced
                                                   in other Parts of this standard, or any related standard, is
                                                   irrelevant. The footnote should be deleted.
GB21     2                                Te       Although ISO 12620 is identified as the source of a               Delete the reference to ISO 12620.                       Accommodated by including
                                                   definition and is referenced in several Editor’s Notes, it is                                                              ISO 12620 in Annex A.
                                                   not necessary to follow any of these references for the
                                                   purposes of this standard. The references are therefore
                                                   informative rather than normative, and the standard
                                                   should not be included in this clause.
GB22     3                                te       Clause D.1.3 in part 2 of the ISO/IEC Directives states           Delete all definitions of terms that are not used        Not accepted. See rationale
                                                   regarding the contents of Definitions clauses:                    with a meaning that is specific to the context of this   in Subclause 0.3.
                                                               Any term which is not self-explanatory or             standard.
                                                               commonly known and which can be differently
                                                               interpreted in different contexts shall be
                                                               clarified by defining the relevant concept.

                                                               Common dictionary or current technical terms
                                                               shall be included only if they are used with a
                                                               specific meaning in the relevant context.
                                                   Most of the terms defined in clause 3 fail to satisfy these
                                                   criteria. For example concept, dictionary and glossary, as
                                                   well as others, appear to be defined to have their
                                                   commonly understood meanings.
GB23     3                                ed       The definitions are mainly grouped by first letter, but are       Arrange all definitions in this clause in alphabetical   Accepted
                                                   not fully in alphabetical order.                                  order.
                                                                                                                                                                              PCEN: implemented in FDIS
                                                                                                                                                                              document




1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                           31
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1              2             (3)              4                                  5                                                              (6)                                      (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                    Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                                 on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB24     3.05                             te       Is it really necessary to restrict eBusiness to interactions      Simplify the definition to something like “business    Accepted. To be worked on
                                                   based on Open-edi standards? The definition may also              conducted using information technology for             together with the disposition
                                                   be unnecessary elaborate in other respects. The Notes             communication of information”.                         of CA25.
                                                   following the definition do not reflect the restriction to
                                                   Open-edi.                                                                                                                PCEN: implemented in FDIS
                                                                                                                                                                            document. Definition of
                                                                                                                                                                            eBusiness revised as Clause
                                                                                                                                                                            3.06. The definition itself
                                                                                                                                                                            remains situated in an Open-
                                                                                                                                                                            edi context which is basically
                                                                                                                                                                            that of ISO/IEC 14662 and the
                                                                                                                                                                            multipart eBusiness standards
                                                                                                                                                                            since the definition integrates
                                                                                                                                                                            is based on six other concepts
                                                                                                                                                                            which are defined in these
                                                                                                                                                                            standards . The Notes reflect
                                                                                                                                                                            the key aspects of eBusiness
                                                                                                                                                                            and do indicate that
                                                                                                                                                                            application of Open-edi
                                                                                                                                                                            concepts is not “restrictive”.
GB25     5.1                              ed       A standard should, in general, make positive statements           Change the lead-in of the first paragraph to:          Accepted
                                                   using the present tense. Both paragraphs read as rather
                                                   tentative.                                                                    Clause 5 states, in an eBusiness           PCEN: implemented in FDIS
                                                                                                                                 context, the principles and rules for:”    document
                                                                                                                     Change the final paragraph to:
                                                                                                                                 This Part, in common with the other
                                                                                                                                 Parts of this International Standard, is
                                                                                                                                 focussed on the high level, i.e. common
                                                                                                                                 primitive, requirements.
GB26     5.2             1                ed       There seems to be an unnecessary instance of “based” in                                                                  Accepted
                                                   the first sentence.
GB27     5.2             2                te       The second sentence of the second paragraph is in the                                                                    Accepted with review of and
                                                   form of a requirement, but it is not clear on whom the                                                                   edit of Subclause 5.2 as per
                                                   burden of conformance is placed or how it is to be                                                                       CA comments.
                                                   monitored.
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                         32
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1               2            (3)              4                                  5                                                              (6)                                      (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                    Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                                 on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB28     5.2                              ed       Rather than leaving all draft rules as “Rule nnn”, in all                                                                Accepted. Rules to be
                                                   future drafts the rules should be numbered for ease of                                                                   numbered.
                                                   reference by reviewers. Renumbering rules from draft to
                                                   draft is not a problem.                                                                                                  PCEN: implemented in FDIS
                                                                                                                                                                            document.
GB29     5.2                              te       The penultimate paragraph seems to be informative                 Convert the paragraph from normative text to a         Accommodated by making
                                                   commentary rather than main text.                                 Note.                                                  the paragraph a footnote
GB30     5.3                              ed       The text immediately following the 5.3 heading is a               Introduce a level 3 heading between the 5.3            Accepted
                                                   hanging paragraph, contrary to the requirements of                heading and the immediately following text.
                                                   clause 5.2.4 of part2 of the ISO/IEC Directives.                                                                         PCEN: implemented in FDIS
                                                                                                                                                                            document
GB31     5.3.2                            ed       In the second paragraph (line 711) “re-sue” should be “re-        Change “re-sue” to “re-use”.                           Accepted
                                                   use”.
GB32     5.3.2                            ed       In the second instance of “Rule nnn”, the text of the rule is     Change the first few words of the rule to “Since the   Accepted – to be corrected
                                                   not a well-formed sentence.                                       primary use of the ...”
                                                                                                                                                                            PCEN: implemented in FDIS
                                                                                                                     Alternatively, dispense with the motivation and        document
                                                                                                                     simplify the rule to: “The term chosen to designate
                                                                                                                     a concept and its definition shall be unambiguous
                                                                                                                     and not easily confused with other concepts.”.
GB33     5.3.4           Table 1          te       The only ISO official languages are English, French and                                                                  Accepted but to be
                                                   Russian. Is “ISO Spanish” then a defined term?                                                                           harmonized with existing
                                                                                                                                                                            approach similar that found
                                                                                                                                                                            in other JTC1/SC32 standard
                                                                                                                                                                            (e.g. ISO/IEC 5218)
                                                                                                                                                                            PCEN: implemented in FDIS
                                                                                                                                                                            document. Note use of ISO
                                                                                                                                                                            English, ISO French, ISO,
                                                                                                                                                                            Russian, ISO Chinese, etc.,
                                                                                                                                                                            refers to use of that language
                                                                                                                                                                            in ISO standards.




1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                         33
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1               2            (3)              4                                  5                                                              (6)                                      (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB                    Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                                 on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB34     5.3.5                            ed       In the first instance of Rule nnn, “ISOIEC” should be                                                                    Accepted – just say JTC 1
                                                   “ISO/IEC”. However, it may be better to remove the
                                                   reference to SC32 altogether. There is also a
                                                   disagreement as to number between the two instances of                                                                   PCEN: Implemented where
                                                   “standard”. Further, this rule is implied by the ISO/IEC                                                                 applicable. However, as
                                                   Directives, so it is not really necessary.                                                                               stated in the Foreword for
                                                                                                                                                                            any JTC1 standard, it notes
                                                                                                                                                                            which specific SC is
                                                                                                                                                                            responsible for the standard
                                                                                                                                                                            and which for this standard is
                                                                                                                                                                            ISO/IEC JTC1/SC32.
GB35     5.3.5           Footnote 25      ed       The spelling “dictioinary” is incorrect. Also, consideration      Change “dictioinary” to “dictionary”.                  Accepted
                                                   should be given to moving this footnote to be a Note
                                                   integrated with the text.
GB36     5.3.5                            te       The rationale for the references to ISO 9000 and ISO              Delete the references to the two families of           Accommodated by making
                                                   14000 (line 846, page 30) is not immediately obvious.             standards, leaving the sentence to read in part “...   ISO 9000 and ISO 14000
                                                   The relevance of environmental standards (ISO 14000)              considered to be a quality control check.”.            references a footnote
                                                   seems particularly obscure.
                                                                                                                                                                            PCEN: implemented in FDIS
                                                                                                                                                                            document.{See ftnt 33}
GB37     6.2                              te       Rule nnn is not grammatically well-formed and contains            If we are to have anything in this area, it should     Accepted – to be taken into
                                                   conceptual errors. Even if corrected, the Rule is probably        probably be less formal than a Rule, and say           consideration by the Project
                                                   unworkable. Each P-member of any ISO or IEC TC or                 something to the effect that translation of concepts   Editors
                                                   SC in a national Standards Body. The Rule appears to              and definitions into other languages may be
                                                   be placing an obligation on every P-member. Standards             submitted for inclusion in Amendments to or future     PCEN: implemented in FDIS
                                                   may be used in countries that were not involved in their          editions of this standard. In practice there will      document. Note that the
                                                                                                                                                                            standard does not speak of
                                                   development. Are we to expect competing French                    probably be few, if any submissions from outside
                                                   versions of definitions from France, Canada, Belgium and          the JTC1 membership.                                   “translations” but of Human
                                                   a range of African countries.                                                                                            Interface Equivalents (HIEs).
                                                                                                                                                                                                  st
                                                                                                                                                                            Further, this Part 7 1 edition
                                                                                                                                                                            is based on the 14662 and
                                                                                                                                                                            15944 series of eBusiness
                                                                                                                                                                            standards only. Resolved
                                                                                                                                                                            through completion og Annex
                                                                                                                                                                            G..


1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                                         34
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1             2              (3)              4                                  5                                                              (6)                            (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB          Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                       on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB38     6.3                              te       Not all countries are members of the UN, and not all,             The clause should be merged into a relaxed   Not accepted. “Country” is
                                                   even if UN members, have national standards bodies.               version of 6.2                               not in question. Project
                                                   Such countries should not be excluded in principle from                                                        Editors to add a footnote
                                                   having their languages associated with this standard.                                                          explaining why “jurisdictional
                                                                                                                                                                  domain” is used, not
                                                                                                                                                                  “country.”
                                                                                                                                                                  PCEN: implemented in FDIS
                                                                                                                                                                  document {See ftnt 47}
GB39     6.3                              ed       In the first paragraph, “in this official” should probably be     Change “this” to “its”.                      Accepted
                                                   “in its official”.
GB40     6.4                              ed       Items 3) and 4) in the list of actions should be sub-items                                                     Accepted
                                                   of item 2). Item 5) should either be deleted or expanded
                                                   into a complete sentence.
GB41                     Page 41          ed       Rather than appearing here, the list of Annexes should be                                                      Accepted
                                                   included in the Introduction, along with an outline of the
                                                   major clauses of the standard.
GB42     Annex A                          te       The nature of this Annex seems to be Informative rather           Identify the Annex as Informative.           Not accepted. Annex A is the
                                                   than Normative, since it is not necessary to consult any of                                                    official list of normative
                                                   the referenced standards in order to apply ISO/IEC15944-                                                       references that are the
                                                   7                                                                                                              collective source of the
                                                                                                                                                                  consolidated eBusiness
                                                                                                                                                                  Vocabulary
GB43     Annex A                          te       A list of standards on its own is of little value. The value                                                   Not accepted. This is a
                                                   of the list would be greatly increased if for each standard                                                    specialized treatment of
                                                   the standards in which it is referenced were identified.                                                       Normative References
                                                                                                                                                                  applicable to this standard.
                                                                                                                                                                  Project Editors to add text in
                                                                                                                                                                  the introduction to Annex A
                                                                                                                                                                  as to why Normative
                                                                                                                                                                  References are being
                                                                                                                                                                  handled in this manner.



1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                               35
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1             2              (3)              4                                  5                                                              (6)                       (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB      Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                   on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)



GB44     A.2                              ed       In the first line of the clause, “Basil” should be changed to     Change “Basil” to “Basel”.               Accepted
                                                   the name of the Swiss city in which the convention was
                                                   agreed.
GB45     Annex B                          te       For the same reasons as given for Annex A, Annex B                                                         Not accepted. Annex B is the
                                                   should be identified as Informative.                                                                       official list of symbols and
                                                                                                                                                              abbreviations used in the
                                                                                                                                                              consolidated eBusiness
                                                                                                                                                              Vocabulary. This is a
                                                                                                                                                              specialized treatment of
                                                                                                                                                              Symbols and Abbreviations
                                                                                                                                                              applicable to this standard.
                                                                                                                                                              Project Editors to add text in
                                                                                                                                                              the introduction to Annex B
                                                                                                                                                              as to why Symbols and
                                                                                                                                                              Abbreviations are being
                                                                                                                                                              handled in this manner.
GB46     Annex C                          te       Since Annex C also consists largely of references to other                                                 Not accepted. Annex C
                                                   standards, it should also be Informative rather than                                                       serves as a control document
                                                   Normative.                                                                                                 for the management of the
                                                                                                                                                              eBusiness Vocabulary as
                                                                                                                                                              well as an easy-ot-use
                                                                                                                                                              reference.




1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                          36
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
 1            2               (3)            4                                    5                                                              (6)                      (7)

MB1      Clause No./      Paragraph/      Type             Comment (justification for change) by the MB                           Proposed change by the MB     Secretariat observations
         Subclause       Figure/Table/     of                                                                                                                  on each comment submitted
             No./             Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)




US01   Clause 1         lines     300,     ed      Align the 1.1, 1.2, 1.3 and 1.4 headings                                                                   Accepted
                        327, 333, 363
US02   Clause 5         lines 571-908      ed      Align the subclause headings appropriately.                                                                Accepted
US03   Clause 6.1       line 912           ed      Left justify all of the subclause titles of Clause 6                                                       Accepted
US04   Clause 8         lines   1164       ed      Align the subclause headings appropriately                                                                 Accepted
                        and 1181




1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)                                        37
2 Type of comment: ge = general            te = technical   ed = editorial
NOTE        Columns 1, 2, 4, 5 are compulsory.
ISO electronic balloting commenting template/version 2001-10
Japan
No. The scope of this part is exceeding the responsibility of SC32/WG1. Many definitions in this
part are seriously conflict with de-facto terminologies which are widely accepted among the
relevant business communities.

WG 1 Resolution of comment
This comment was not accepted, because the Scope of ISO/IEC 15944-7 is strictly limited to standards developed
                                                                   st
by SC 32/WG 1. The first paragraph of Clause 1 Scope states: The 1 edition of this Part of ISO/IEC 15944
                                                                                             rd
provides a consolidated vocabulary of eBusiness concepts as found in ISO/IEC 14662:2007 (3 edition) and the
                                                              22
existing parts of ISO/IEC 15944, namely, Parts 1, 2, 4 and 5.

The disposition of GB13 is to replace this paragraph with:
This Part of ISO/IEC 15944 provides a consolidated eBusiness vocabulary, defining concepts used in ISO/IEC
14662:2007 and the other parts of ISO/IEC 15944.
          Note: At the time of publication of this Part of ISO/IEC 15944, Parts 1, 2 4, 5 and 6 had been published
          and Parts 3 and 8 were under development.

It should be noted that this replacement results in no change to the scope of WG 1.

PCEN: implemented in FDIS document {See further Clause 1.1as well as in ftnt 14}




22
     The following parts of the ISO/IEC 15944 multipart standard are currently under development; namely:
           Part 3, Open-edi description techniques (OeDT);
           Part 6:    Technical Introduction of eBusiness modelling; and,
           Part 8: Identification of privacy requirements as external constraints on business  transactions

     The added definitions and terms resulting from this work will be incorporated in Part 7 when they are finalized (in
                 st   nd
     either its 1 or 2 edition).

                                                                                                                     38
   Draft text for Annex F provided by Russia


   RUSSIAN LANGUAGE EQUIVALENTS FOR INCLUSION IN THE ISO/IEC 15944-7:2007 “E-
   BUSINESS VOCABULARY” STANDARD


                   ISO English                     Gender                       ISO Russian
                        (1)                         (2)                              (3)
3.1                                                         3.1
address                                                     адрес
set of data elements that specifies a location
to which a recorded information item(s), a                  набор    элементов    данных,   определяющий
business object(s), a material object(s) and/or             местоположение, куда могут быть посланы
a person(s) can be sent or from which it can be             элемент(ы) записанной информации, бизнес
received                                                    объект(ы),    материальные    объекты    и/или
                                                            юридические или физические лица или откуда они
NOTE 1 An address can be specified as either a              могут быть получены
physical address and/or electronic address.
                                                            ПРИМЕЧАНИЕ 1 Адрес может быть определен как
NOTE 2 In the identification, referencing and               физический и/или как электронный адрес.
retrieving of registered business objects, it is
necessary to state whether the pertinent                    ПРИМЕЧАНИЕ 2 При идентификации, ссылке или
recorded information is available in both                   поиске зарегистрированных бизнес объектов
physical and virtual forms.                                 необходимо указать, доступна ли соответствующая
                                                            записанная информация как в физической, так и в
NOTE 3 In the context of Open-edi, a “recorded              виртуальной форме.
information item” is modelled and registered as
an Open-edi scenario (OeS), Information Bundle              ПРИМЕЧАНИЕ 3 В контексте Открытых систем
(IB) or Semantic Component (SC).                            электронного    обмена    данными    «элемент
                                                            записанной    информации»    моделируется   и
[ISO/IEC 15944-2:2006 (3.1)]                                регистрируется как сценарий Открытой системы
                                                            электронного обмена данными (OeS), пакет
                                                            информации (IB) или семантический компонент
                                                            (SC).

                                                            [ISO/IEC 15944-2:2006 (3.1)]
3.2                                                         3.2
administrative note                                         административное примечание
general note about the OeRI
                                                            Примечание относительно OeRI общего характера
[ISO/IEC 15944-2:2006 (3.2)]
                                                            [ISO/IEC 15944-2:2006 (3.2)]
3.3                                                         3.3
agent                                                       aАгент
Person acting for another Person in a clearly
specified capacity in the context of a business             Лицо, действующее в интересах другого Лица и
transaction                                                 обладающее четко очерченными полномочиями в
                                                            рамках некоторой бизнес транзакции
NOTE Excluded here are agents as
"automatons" (or robots, bobots, etc.). In                  ПРИМЕЧАНИЕ         Автоматические         устройства
ISO/IEC 14662, "automatons" are recognized                  (роботы, боботы и т.п.) не входят в эту категорию.
and provided for but as part of the Functional              В стандарте ISO/IEC 14662 "автоматические
Service View (FSV) where they are defined as                устройства" распознаются и предусмотрены, но
an "Information Processing Domain (IPD)".                   только как часть Представления Функционального
                                                            Сервиса (FSV), где они определяются как «Домен
                                                            Обработки Информации» (IPD)
[ISO/IEC 15944-1:2002 (3.1)]
                                                                                                        39
                  ISO English                       Gender                       ISO Russian
                       (1)                           (2)                              (3)


                                                             [ISO/IEC 15944-1:2002 (3.1)]
3.4                                                          3.4
applicant (for an OeRI)                                      cСоискатель (для OeRI)
Person who requests the assignment of an
OeRI and an associated entry label                           Лицо, которое запрашивает назначение OeRI и
                                                             связанного имени точки входа
NOTE An applicant can be an individual,
organization, or public administration.                      ПРИМЕЧАНИЕ        Соискателем   может         быть
                                                             физическое      лицо, организация или        орган
                                                             государственного управления
[ISO/IEC 15944-2:2006 (3.3)]
                                                             [ISO/IEC 15944-2:2006 (3.3)]

3.5                                                          3.5
Application Program Interface (API)                          Интерфейс Прикладных Программ (API)
a boundary across which application software
uses facilities of programming languages to                  Граница, через которую прикладная программа
invoke services                                              использует средства языков программирования для
                                                             вызова обслуживания
[ISO/IEC 14662:2004 (3.1)]
                                                             [ISO/IEC 14662:2004 (3.1)]

3.6                                                          3.6
artificial language                                          искусственный язык
language whose rules are explicitly established
prior to its use                                             Язык, правила которого устанавливаются прежде,
                                                             чем он будет применяться
[ISO 5127-1:2001 (1.1.2.03)]
                                                             [ISO 5127-1:2001 (1.1.2.03)]
3.7                                                          3.7
attribute                                                    атрибут
characteristic of an object or entity
                                                             Характеристика объекта или сущности
[ISO/IEC 11179-3:2003 (3.1.3)]
                                                             [ISO/IEC 11179-3:2003 (3.1.3)]
3.8                                                          3.8
authentication                                               Аутентификация
provision of assurance of the claimed identity of
an entity
                                                             Обеспечение гарантии заявленной идентичности
[ISO/IEC 10181-2:1996]                                       сущности

                                                             [ISO/IEC 10181-2:1996]

3.9                                                          3.9
authenticity                                                 подлинность
property that ensures that the identity of a
subject or resource is the one claimed                       Свойство обеспечивающее, что объект или ресурс
                                                             подлинны в том смысле, как это было заявлено.
NOTE Authenticity applies to entities such as
                                                             ПРИМЕЧАНИЕ Подлинность применяется к таким

                                                                                                     40
                   ISO English                       Gender                       ISO Russian
                        (1)                           (2)                              (3)
users, processes, systems and information.                    сущностям как пользователи, процессы, системы и
[ISO/IEC TR 13335-1:1996 (3.3)]                               информация.

                                                              [ISO/IEC TR 13335-1:1996 (3.3)]
3.10                                                          3.10
bilateral transaction                                         двусторонняя транзакция
subtype of a business transaction where the
Persons include only the buyer and the seller,                Разновидность (подтип) бизнес транзакции, где в
or alternatively other Persons acting as agents               качестве лица может быть только покупатель или
for the buyer or seller                                       продавец, или альтернативно другие лица,
                                                              действующие как агенты для покупателя или
[ISO/IEC 15944-4:2006 (3.4)]                                  продавца

                                                              [ISO/IEC 15944-4:2006 (3.4)]

3.11                                                          3.11
bilateral treaty                                              двусторонний договор
treaty made between two jurisdictional
domains
                                                              Договор, заключенный между двумя территориями
NOTE An important point here is that there is no              разных юрисдикций.
intention to bind both parties under international            ПРИМЕЧАНИЕ Важным моментом является то, что
law.                                                          здесь нет намерения связывать, ограничивать
                                                              стороны международным законодательством
[ISO/IEC 15944-5:2006]

3.12                                                          3.12
business                                                      Бизнес
series of processes, each having a clearly
understood purpose, involving more than one                   Ряд процессов, каждый из которых имеет ясно
Person, realised through the exchange of                      понимаемую цель, охватывающий более чем одно
recorded information and directed towards                     лицо,      реализуемый    посредством    обмена
some mutually agreed upon goal, extending                     зарегистрированной информацией, направленный
over a period of time                                         на достижение некоторой, взаимно согласованной
                                                              цели и протекающий в течение некоторого периода
                                                              времени.
[ISO/IEC 14662:2004 (3.2)]
                                                              [ISO/IEC 14662:2004 (3.2)]

3.13                                                          3.13
business event                                                бизнес событие
occurrence in time that partners to a business
transaction wish to monitor or control                        Своевременное наступление события, которое
                                                              партнеры по бизнес транзакции намерены
NOTE 1 Business events are the workflow tasks                 отслеживать или контролировать.
that business partners need to accomplish to
complete a business transaction among                         ПРИМЕЧАНИЕ 1: Бизнес события – это поток
themselves. As business events occur, they                    работ, которые партнеры по бизнесу должны
cause a business transaction to move through                  выполнить, чтобы совместно завершить бизнес
its various phases of planning , identification,              транзакцию. Когда наступают бизнес события, они
negotiation, actualization, and post-                         обуславливают прохождение бизнес транзакции
actualization.                                                через     различные     фазы:     планирование,
                                                              идентификация, переговоры, актуализация и пост-
NOTE 2 Occurrences in time can either be                      актуализация.

                                                                                                     41
                  ISO English                       Gender                       ISO Russian
                       (1)                           (2)                              (3)

(1) internal as mutually agreed to among the
parties to a business transaction; and/or,                   ПРИМЕЧАНИЕ 2: Своевременное наступление
                                                             события может удостоверяться либо
(2) reference some common publicly available                 (1) внутренним соглашением между партнерами по
and recognized date/time referencing schema,                 бизнесу и/или
(e.g., one based on using the ISO 8601 and/or                (2) ссылкой на некоторую публично доступную
ISO 19135 standards).                                        схему,    по  которой    признается  дата/время
                                                             (например, схему, основанную на применении
[ISO/IEC 15944-4:2006 (3.5)]                                 стандартов ISO 8601 и/или ISO 19135)

                                                             [ISO/IEC 15944-4:2006 (3.5)]

3.14                                                         3.14
business location                                            местоположение бизнеса
geographic site where an economic event is
deemed to occur with its attendant transfer of an            Географическое    место,   где   предполагается
economic resource from one Person to                         наступление    экономического      события    с
another                                                      сопутствующей      передачей     экономических
                                                             ресурсов от одного Лица другому.
[ISO/IEC 15944-4:2006 (3.6)]

3.15                                                         3.15
business object                                              бизнес объект
unambiguously identified, specified,
referenceable, registered and re-useable Open-               Однозначно идентифицируемый, определенный,
edi scenario or scenario component of a                      доступный для ссылки, зарегистрированный и
business transaction                                         пригодный для повторного использования Open-edi
                                                             сценарий или компонент сценария бизнес
NOTE As an “object”, a “business object” exists              транзакции.
only in the context of a business transaction.               ПРИМЕЧАНИЕ       Как «объект», «бизнес-объект»
                                                             существует только в контексте бизнес транзакции.
[ISO/IEC 15944-2:2006 (3.6)]
                                                             [ISO/IEC 15944-2:2006 (3.6)]

3.16                                                         3.16
business object identifier                                   идентификатор бизнес объекта
unique identifier of a business object in an
OeRI within an Open-edi Registration                         Уникальный идентификатор бизнес-объекта в
Organization(OeRO)                                           сообщении о регистрации Open-edi в рамках
                                                             организации по регистрации Open-edi (OeRO)
[ISO/IEC 15944-2:2006 (3.7)]
                                                             [ISO/IEC 15944-2:2006 (3.7)]

3.17                                                         3.17
business object status                                       статус бизнес объекта
designation of the status in the administrative
process of a Open-edi Registration                           Назначение       статуса      в       процессе
Organization for handling OeRI                               администрирования организации по регистрации
                                                             Open-edi для обработки сообщения по регистрации
[ISO/IEC 15944-2:2006 (3.8)]                                 Open-edi

                                                             [ISO/IEC 15944-2:2006 (3.8)]



                                                                                                     42
                  ISO English                       Gender                       ISO Russian
                       (1)                           (2)                              (3)
3.18                                                         3.18
business object type                                         тип бизнес объекта
coded domain for the type of business object
being registered, i.e., Open-edi scenario, IB or             домен кодов для типа бизнес объекта,
SC                                                           подлежащего регистрации, например, сценарий
                                                             Open-edi, IB или SC
[ISO/IEC 15944-2:2006 (3.9)]
                                                             [ISO/IEC 15944-2:2006 (3.9)]
3.19                                                         3.19
Business Operational View (BOV)                              операциональный взгляд на бизнес
perspective of business transactions limited to
those aspects regarding the making of
business decisions and commitments among                     Аспекты бизнес транзакции, рассматривающие
Persons, which are needed for the description                вопросы принятия бизнес решений и обязательств
of a business transaction                                    лиц, которые необходимы для описания бизнес
                                                             транзакции.
[ISO/IEC 14662:2004 (3.3)]

                                                             [ISO/IEC 14662:2004 (3.3)]

3.20                                                         3.20
business transaction                                         бизнес транзакция
predefined set of activities and/or processes of
Persons which is initiated by a Person to                    Заранее определенный набор работ, и/или
accomplish an explicitly shared business goal                процессов лиц, которые инициируются лицом для
and terminated upon recognition of one of the                достижения явно разделяемой бизнес цели.
agreed conclusions by all the involved Persons               Достижение цели подтверждается одним из
although some of the recognition may be implicit             согласованных заключений, сделанных всеми
                                                             вовлеченными     лицами,    хотя    некоторые
[ISO/IEC 14662:2004 (3.4)]                                   подтверждения достижения цели могут быть
                                                             неявными.

                                                             [ISO/IEC 14662:2004 (3.4)]
3.21                                                         3.21
business transaction entity                                  сущность бизнес транзакции
computable representation of any real world
entity that participates, occurs, or is                      Вычислимое представление любой сущности
materialized during a business transaction                   реального мира, которое участвует, происходит
                                                             или материализуется во время бизнес транзакции
[ISO/IEC 15944-4:2006 (3.9)]

                                                             [ISO/IEC 15944-4:2006 (3.9)]

3.22                                                         3.22
business transaction entity type                             тип сущности бизнес транзакции
abstract specification of a business
transaction entity, detailing its recommended                абстрактная спецификация сущности, связанной с
characteristics, its recommended methods,                    бизнес    транзакцией,     детализирующая     ее
and its recommended life-cycle states                        рекомендованные         характеристики,       ее
                                                             рекомендованные методы и ее рекомендованные
NOTE A business transaction entity type will                 состояния жизненного цикла.
usually specify the types of business events that            ПРИМЕЧАНИЕ: Тип сущности, связанной с бизнес
cause a business transaction entity of this type             транзакцией, обычно определяет виды бизнес
to proceed through its different states as the               событий,   которые    обусловливают     сущность,
                                                                                                      43
                  ISO English                        Gender                      ISO Russian
                       (1)                            (2)                             (3)
business transaction itself progresses through                связанную с бизнес транзакцией, этого типа
its phases of planning, identification                        проходить через ее различные состояния, в то
                                                              время как собственно бизнес транзакция проходит
[ISO/IEC 15944-4:2006 (3.10)]                                 через свои фазы планирования, идентификации,
                                                              переговоров, актуализации и пост-актуализации.

                                                              [ISO/IEC 15944-4:2006 (3.10)]
3.23                                                          3.23
business transaction identifier (BTI)                         идентификатор бизнес транзакции
identifier assigned by a seller or a regulator to
an instantiated business transaction among                    идентификатор присваивается продавцом или
the Persons involved                                          представителем       регулирующего      органа
                                                              обрабатываемой     бизнес    транзакции    для
                                                              использования всеми вовлеченными лицами

NOTE 1 The identifier assigned by the seller or               ПРИМЕЧАНИЕ 1 Идентификатор, назначенный
regulator shall have the properties and                       продавцом или представителем регулирующего
behaviours of an “identifier (in a business                   органа будет иметь свойства и поведение как
transaction)”.                                                «идентификатор (в бизнес транзакции)»

NOTE 2 As an identifier (in a business                        ПРИМЕЧАНИЕ В качестве идентификатора (в
transaction), a BTI serves as the unique                      бизнес транзакции) BTI служит как уникальный
common identifier for all Persons involved for                общий идентификатор для всех лиц, привлекаемых
the identification, referencing, retrieval of                 для   идентификации,     ссылки   (сравнения   с
recorded information, etc., pertaining to the                 образцом),    извлечения      зарегистрированной
commitments made and the resulting                            информации и т.д. в соответствии со сделанными
actualization (and post-actualization) of the                 обязательствами,   приводя     в   результате  к
business transaction agreed to.                               актуализации или пост-актуализации.

                                                              ПРИМЕЧАНИЕ       3      Идентификатор    бизнес
NOTE 3 A business transaction identifier can be               транзакции может быть назначен в любой момент
assigned at any time during the planning,                     во время этапов планирования, идентификации или
identification or negotiation phases but shall be             переговоров, но назначение должно состояться по
assigned at least prior to the start or during the            крайней мере до начала или во время этапа
actualization phase.                                          актуализации.

NOTE 4 As and where required by the                           ПРИМЕЧАНИЕ 4 Вполне вероятно, что по
applicable jurisdictional domain(s), the recorded             требованиям    соответствующего  юридического
information associated with the business                      домена (доменов) продавец будет вынужден
transaction identifier (BTI) may well require the             добавить к зарегистрированной информации,
seller to include other identifiers, (e.g., from a            связанной с идентификатором бизнес транзакции,
value-added good or service tax, etc.,                        другие идентификаторы (например, связанные с
perspective) as assigned by the applicable                    НДС), как это предписано соответствующим
jurisdictional domain(s).                                     юридическим доменом (доменами).
[ISO/IEC 15944-5:2006 (3.12)]
                                                              [ISO/IEC 15944-5:2006 (3.12)]




3.24                                                          3.24
buyer                                                         Покупатель
Person who aims to get possession of a good,

                                                                                                      44
                  ISO English                      Gender                       ISO Russian
                        (1)                         (2)                              (3)
service and/or right through providing an                   Лицо, намеревающееся стать обладателем товара,
acceptable equivalent value, usually in money,              услуги и/или некоторых прав путем обмена на
to the Person providing such a good, service                приемлемый стоимостной эквивалент, обычно в
and/or right                                                виде денег, с лицом, предоставляющим такой
[ISO/IEC 15944-1:2002 (3.8)]                                товар, услугу и/или права

                                                            [ISO/IEC 15944-1:2002 (3.8)]

3.25                                                        3.25
change description                                          описание изменения
description of why and how the OeRI has been
modified since the prior version of the OeRI                Описание того, зачем и каким образом предыдущая
                                                            версия OeRI была модифицирована
NOTE It is advised that such a change
description be accompanied by the “original “               ПРИМЕЧАНИЕ      Рекомендуется,     чтобы   такое
template values utilized and a “change                      описание изменения сопровождалось шаблонами
template” indicating which “Decision Code(s)”               «исходный» и «изменение», указывающими, какая
has been changed as well as the date the                    юридическая норма (нормы) принятия решений
change will take effect.                                    была изменена, а также, какова дата вступление в
                                                            действие изменения.
[ISO/IEC 15944-2:2006 (3.12)]
                                                            [ISO/IEC 15944-2:2006 (3.12)]


3.26                                                        3.26
character                                                   символ
member of a set of elements that is used for the
representation, organization or control of data.            элемент     некоторого  набора    элементов,
                                                            используемого для представления, организации
NOTE Characters may be categorized as                       или управления данными.
follows:
                                                            ПРИМЕЧАНИЕ             Символы                  могут
TYPES AND EXAMPLES                                          классифицироваться следующим образом:

   •   graphic character: (e.g., digit, letter,             ТИПЫ И ПРИМЕРЫ
       ideogram, special character)
                                                               •   графические символы: (например, цифра,
   •   control character: (e.g., transmission
                                                                   буква, идеограмма, специальный символ)
       control, character, format effector, code
                                                               •   управляющий символ: (например, символ
       extension character, device control
                                                                   управления передачей сообщения, символ
       character).
                                                                   спецификации        формата,      символ
                                                                   расширения кода, символ управления
[ISO/IEC 2382-4:1999 (04.01.01)]
                                                                   устройством)

                                                            [ISO/IEC 2382-4:1999 (04.01.01)]


3.27                                                        3.27
characteristic                                              характеристика
abstraction of a property of an object or of a
set of objects                                              абстракция    свойства     объекта   или   набора
                                                            объектов
NOTE Characteristics are used for describing
                                                            ПРИМЕЧАНИЕ Характеристики используются для

                                                                                                       45
                   ISO English                        Gender                       ISO Russian
                         (1)                           (2)                                 (3)
concepts.                                                      описания понятий
[ISO 1087-1:2000 (3.2.4)]
                                                               [ISO 1087-1:2000 (3.2.4)]

3.28                                                           3.28
character set                                                  набор символов
finite set of different characters that is complete
for a given purpose
                                                               конечное  множество    различных   символов,
EXAMPLE The international reference version                    являющееся полным для определенной цели
of the character set of ISO 646-1.
                                                               ПРИМЕР Международная эталонная версия набора
                                                               символов ISO 646-1.
[ISO/IEC 2382-4:1999 (04.01.02)]
                                                               [ISO/IEC 2382-4:1999 (04.01.02)]
3.29                                                           3.29
classification system                                          система классификации
systematic identification and arrangement of
business activities and/or scenario                            систематические идентификация и расположение
components into categories according to                        в определенном порядке бизнес работ и/или
logically structured conventions, methods and                  компонентов сценария в классификационные
procedural rules as specified in a classification              группировки   в   соответствии  с   логически
schema                                                         структурными     условиями,    методами     и
                                                               процедурными правилами, как определено в
NOTE 1 The classification code or number often                 схеме классификации
serves as a semantic identifier (SI) for which
one or more human interface equivalents exist.                 ПРИМЕЧАНИЕ 1 Код или номер классификации
                                                               часто служит как семантический идентификатор
NOTE 2 The rules of a classification schema                    (SI), для которого существует один или несколько
governing the operation of a classification                    эквивалентов человеко-машинного интерфейса.
system at times lead to the use of ID codes
which have an intelligence built into them, (e.g.,             ПРИМЕЧАНИЕ 2 Правила схемы классификации,
in the structure of the ID, the manner in which it             регламентирующие работу системы классификации
can be parsed, etc. Here the use of block-                     иногда приводят к использованию кодов ID,
numeric numbering schemas is an often used                     которые имеют встроенный интеллект (например,
convention.                                                    структура ID, способ, с помощью которого она
[ISO/IEC 15944-5:2006 (3.17)]                                  может быть проанализирована синтаксически)
                                                               [ISO/IEC 15944-5:2006 (3.17)]

3.30                                                           3.30
code                                                           код
data representation in different forms according
to a pre-established set of rules                              представление данных в различных формах в
                                                               соответствие с заранее установленным набором
NOTE In this standard the "pre-established set                 правил
of rules" are determined and enacted by a
Source Authority and must be explicitly stated.                ПРИМЕЧАНИЕ В этом стандарте «заранее
                                                               установленный набор правил» определяется и
[ISO 639-2:1998 (3.1)]                                         вводится в действие вышестоящим органом власти
                                                               и должен быть явно изложен.

                                                               [ISO 639-2:1998 (3.1)]
3.31                                                           3.31
coded domain                                                   домен кодов
domain for which
                                                                                                       46
                   ISO English                       Gender                      ISO Russian
                        (1)                           (2)                            (3)
                                                              домен, для которого:
(1) the boundaries are defined and explicitly
stated as a rulebase of a coded domain                           (1) границы      определяются      и    явно
Source Authority; and,                                               устанавливаются    как    база   правил
(2) each entity which qualifies as a member of                       Вышестоящего         органа      власти
that domain is identified through the assignment                     закодированного домена; и
of a unique ID code in accordance with the                       (2) каждая сущность, которая квалифицируется
applicable Registration Schema of that Source                        как член этого домена, идентифицируется
Authority                                                            путем назначения уникального кода ID в
                                                                     соответствии   с   применяемой    схемой
NOTE 1 The rules governing the assignment of                         регистрации этого Вышестоящего органа
an ID code to members of a coded domain                              власти
reside with its Source Authority and form part of
the Coded Domain Registration Schema of the                   ПРИМЕЧАНИЕ 1 Правила, регламентирующие
Source Authority.                                             присвоение кода ID элементам домена кодов,
                                                              соответствуют требованиям Вышестоящего органа
NOTE 2 Source Authorities which are                           власти и формируют часть Схемы регистрации
jurisdictional domains are the primary source of              доменов кодов этого органа.
coded domains.

NOTE 3 A coded domain is a data set for which                 ПРИМЕЧАНИЕ 2 Вышестоящие органы власти,
the contents of the data element values are                   являющиеся    юридическими    доменами, есть
predetermined and defined according to the                    первичные источники доменов кодов.
rulebase of its Source Authority and as such
have predefined semantics.                                    ПРИМЕЧАНИЕ 3 Домен кодов есть набор данных,
                                                              для   которого    значения   элементов  данных
NOTE 4 Associated with a code in a coded                      предопределены заранее и определяются в
domain can be:                                                соответствии с базой правил Вышестоящего органа
                                                              власти и как таковые имеют предопределенную
- one and/or more equivalent codes;                           семантику.

- one and/or more equivalent representations                  ПРИМЕЧАНИЕ 4 Связанными с кодом             домена
especially those in the form of Human Interface               кодов могут быть:
Equivalent (HIE) (linguistic) expressions.
                                                              - один или несколько эквивалентных кодов;
NOTE 5 In a coded domain the rules for
assignment and structuring of the ID codes must
                                                              -    одно     или   несколько   эквивалентных
be specified.
                                                              представлений, главным образом в форме
NOTE 6 Where an entity as member of a coded                   (лингвистических) выражений       Эквивалента
domain is allowed to have, i.e., assigned, more               Человеко-машинного Интерфейса (HIE).
than one ID code, i.e., as equivalent ID codes
(possibly including names), one of these must                 ПРИМЕЧАНИЕ 5 В домене кодов должны быть
be specified as the pivot ID code.                            определены правила присвоения и структуризации
                                                              кодов идентификатора (ID code).
NOTE 7 A coded domain in turn can consist of                  ПРИМЕЧАНИЕ 6 Если сущность как элемент
two or more coded domains, i.e., through the                  домена кодов присваивается более чем одному
application of the inheritance principle of object            коду ID, т.е. эквивалентным кодам ID (возможно,
classes.                                                      включающим имена), один из этих кодов ID
                                                              должен быть определен как ведущий.
NOTE 8 A coded domain may contain ID code
which pertain to predefined conditions other                  ПРИМЕЧАНИЕ 7 Домен кодов, в свою очередь,
than qualification of membership of entities in               может состоять из одного или более доменов
the coded domain. Further, the rules governing                кодов, когда применяется принцип наследования
a coded domain may or may not provide for                     классов в объектной методологии.
user extensions.
                                                              ПРИМЕЧАНИЕ 8 Домен кодов может содержать

                                                                                                          47
                   ISO English                        Gender                       ISO Russian
                        (1)                            (2)                              (3)

EXAMPLE Common examples include: (1) the                       код ID скорее в соответствии с
use of ID Code "0" (or "00", etc.) for “Others, (2)            предопределенными условиями, чем по
the use of ID Code "9" (or "99", etc.) for “Not                принадлежности множеству сущностей домена
Applicable”; (3) the use of “8” (or “98”) for “Not             кодов. Более того, правила регулирования домена
Known”; and/or, if required, (4) the pre-                      кодов могут обеспечивать или не позволять
reservation of a series of ID codes for use of                 пользовательское расширение.
“user extensions”.                                             ПРИМЕР Примеры общего характера включают:
NOTE 9 In object methodology, entities which                   (1) использование кода ID “0” (или “00” и т.д.) для
are members of a coded domain are referred to                  «другие», (2) использование кода ID “9” (или “99”)
as instances of a class.                                       для «Не применимо», (3) использование “8” (или
                                                               “98”) для «Не известно», и/или, если необходимо,
EXAMPLE In UML modelling notation, an ID                       (4) предварительное резервирование ряда кодов
code is viewed as an instance of an object                     ID для применения «пользовательских
class.                                                         расширений».
[ISO/IEC 15944-2:2006 (3.13)]                                  ПРИМЕЧАНИЕ 9 В объектной методологии к
                                                               сущностям, которые являются элементами
                                                               закодированного домена, обращаются как к
                                                               экземплярам класса.

                                                               ПРИМЕР В нотации моделирования языка UML
                                                               код ID рассматривается как экземпляр класса.
                                                               [ISO/IEC 15944-2:2006 (3.13)]

3.32                                                           3.32
coded Domain Registration Schema (cdRS)                        Схема Регистрации домена кодов (cdRS)
formal definition of both
(1) the data fields contained in the                           Формальное определение
identification and specification of an entity                     (1) полей     данных,    содержащихся    в
forming part of the members a coded domain                            идентификаторе      и     спецификации
including the allowable contents of those fields;                     сущности, формирующей часть элементов
and,                                                                  домена кодов, включающую допустимое
(2) the rules for the assignment of identifiers                       содержание этих полей и
                                                                  (2) правила присвоения идентификаторов
[ISO/IEC 15944-5:2006 (3.21)]
                                                               [ISO/IEC 15944-5:2006 (3.21)]

3.33                                                           3.33
coded domain Source Authority (cdSA)                           Вышестоящий орган власти             домена кодов
Person, usually an organization, as a Source                   (cdSA)
Authority which sets the rules governing a
coded domain                                                   Лицо, обычно организация, которое в качестве
                                                               Вышестоящего органа власти устанавливает
NOTE 1 Source Authority is a role of a Person                  правила регламентирования домена кодов
and for widely used coded domains the coded
domain Source Authority is often a jurisdictional              ПРИМЕЧАНИЕ 1 Вышестоящий орган власти есть
domain.                                                        роль лица и для широко используемых доменов
                                                               кодов Вышестоящий орган власти закодированного
NOTE 2 Specific sectors, (e.g., banking,                       домена есть юридический домен.
transport, geomatics, agriculture, etc.), may
have particular coded domain Source                            ПРИМЕЧАНИЕ        2    Специфические     сектора
Authority(ies) whose coded domains are used in                 (например,    банковский    бизнес,   транспорт,
many other sectors.                                            геоматика, сельское хозяйство и др.) могут иметь
                                                               отдельные Вышестоящие органы власти доменов
                                                                                                            48
                  ISO English                      Gender                      ISO Russian
                        (1)                         (2)                             (3)

NOTE 3 A coded domain Source Authority                      кодов, чьи домены кодов используются во многих
usually also functions as a Registration                    других областях
Authority but can use an agent, i.e., another
Person, to execute the registration function on             ПРИМЕЧАНИЕ 3 Вышестоящий орган власти
its behalf.                                                 домена кодов может также выполнять функции
                                                            Органа по регистрации, но может иметь Агента, т.е.
                                                            другое Лицо для выполнения функции регистрации
[ISO/IEC 15944-2:2006 (3.14)]                               от его имени.

                                                            [ISO/IEC 15944-2:2006 (3.14)]


3.34                                                        3.34
code (in coded domain)                                      код (в домене кодов)
identifier, i.e., an ID code, assigned to an
entity as member of a coded domain                          идентификатор,    т.е.  код   идентификатора,
according to the pre-established set of rules               присвоенный сущности как элементу домена
governing that coded domain                                 кодов в соответствии с заранее установленным
                                                            набором правил регламентирования домена
[ISO/IEC 15944-5:2006 (3:19)]                               кодов.

                                                            [ISO/IEC 15944-5:2006 (3:19)]
3.35                                                        3.35
collaboration space                                         пространство сотрудничества
business activity space where an economic
exchange of valued resources is viewed
independently and not from the perspective of
any business partner                                        пространство    бизнес    деятельности,    где
                                                            экономический обмен оцененными ресурсами
NOTE In collaboration space, an individual                  рассматривается независимо и не с точки зрения
partner’s view of economic phenomena is de-                 одного бизнес партнера
emphasized. Thus, the common use business
and accounting terms like purchase, sale, cash              ПРИМЕЧАНИЕ В пространстве сотрудничества
receipt, cash disbursement, raw materials, and              индивидуальным точкам зрения на экономические
finished goods is not allowed because they view             явления придается меньшее значение. Таким
resource flows from a participant’s perspective.            образом,      термины      общего    характера,
                                                            используемые в бизнесе и учете, такие, как
                                                            покупка,    продажа,     поступление   выручки,
[ISO/IEC 15944-4:2006 (3.12)]
                                                            выплаченная сумма, сырье и готовый продукт – не
                                                            разрешены, т.к. они описывают потоки ресурсов с
                                                            точки зрения участников бизнеса.

                                                            [ISO/IEC 15944-4:2006 (3.12)]
3.36                                                        3.36
commitment                                                  обязательство
making or accepting of a right, obligation,
liability or responsibility by a Person that is             передача или признание права, обязанности, долга
capable of enforcement in the jurisdictional                или ответственности Лицом, правоспособным к
domain in which the commitment is made                      принудительному взысканию в юридическом
                                                            домене, в котором выпущено это обязательство
[ISO/IEC 14662:2004 (3.5)]
                                                            [ISO/IEC 14662:2004 (3.5)]

3.37                                                        3.37
                                                                                                      49
                  ISO English                        Gender                      ISO Russian
                        (1)                           (2)                             (3)
composite identifier                                          составной идентификатор
identifier (in a business transaction)
functioning as a single unique identifier                     идентификатор      (в  бизнес    транзакции)
consisting of one or more other identifiers,                  действующий      как   единый     уникальный
and/or one or more other data elements, whose                 идентификатор, состоящий из одного или более
interworkings are rule-based                                  других идентификаторов и/или из одного или
                                                              более элементов данных, чье взаимодействие
NOTE 1 Identifiers (in business transactions)                 основано на правилах
are for the most part composite identifiers.
                                                              ПРИМЕЧАНИЕ 1 Идентификаторы (в бизнес
NOTE 2 The rules governing the structure and                  транзакциях)     большей    частью являются
working of a composite identifier should be                   составными идентификаторами.
specified.
                                                              ПРИМЕЧАНИЕ 2        Должны быть определены
NOTE 3 Most widely used composite identifiers                 правила,   регламентирующие      структуру  и
consist of the combinations of:                               функционирование составных идентификаторов.
(1) the ID of the overall identification/numbering
                                                              ПРИМЕЧАНИЕ 3 Наиболее широко используемые
schema, (e.g., ISO/IEC 6532, ISO/IEC 7812,
                                                              составные идентификаторы состоят из комбинаций:
ISO/IEC 7506, UPC/EAN, ITU-T E.164, etc.),
which is often assumed;
                                                                 (1) ID           общепринятых              схем
(2) the ID of the issuing organization (often                        идентификации/нумерации,        (например,
based on a block numeric numbering schema);                          ISO/IEC 6532, ISO/IEC 7812, ISO/IEC 7506,
and,                                                                 UPC/EAN, ITU-T E.164 и т.д.);
                                                                 (2) ID    выпускающих    организаций     (часто
(3) the ID of the entities forming part of                           основанных на схемах блок-нумерации); и
members of the coded domain of each issuing                      (3) ID    сущностей,    формирующих       часть
organization.                                                        элементов     домена      кодов     каждой
                                                                     выпускающей организации.
[ISO/IEC 15944-2:2006 (3.16)]
                                                              [ISO/IEC 15944-2:2006 (3.16)]

3.38                                                          3.38
composite type                                                составной тип
a data type that has a data structure composed
of the data structures of one or more data types              тип данных, имеющий структуру данных,
and that has its own set of permissible                       составленную из структур данных одного или
operations                                                    более или более типа и имеющий свой
                                                              собственный набор разрешенных операций
EXAMPLE A data type "complex number" may
be composed of two "real number" data types.                  ПРИМЕР Тип данных «комплексное число» может
                                                              быть   составлен   из двух   типов   данных
NOTE The operations of a composite type may                   «вещественное число».
manipulate its occurrences as a unit or may
manipulate portions of these occurrences.                     ПРИМЕЧАНИЕ Операции составного типа могут
[ISO/IEC 2382-17:1999 (17.05.10)]                             манипулировать    своими   экземплярами    как
                                                              единицами и могут манипулировать порциями этих
                                                              экземпляров.

                                                              [ISO/IEC 2382-17:1999 (17.05.10)]
3.39                                                          3.39
computational integrity                                       вычислительная целостность
expression of a standard in a form that ensures
precise description of behaviour and semantics                представление    стандарта      в   форме,   которая

                                                                                                           50
                  ISO English                        Gender                        ISO Russian
                       (1)                            (2)                              (3)
in a manner that allows for automated                         обеспечивает точное описание поведения и
processing to occur, and the managed evolution                семантики способом, позволяющим выполнять
of such standards in a way that enables                       автоматическую    обработку   данных,   и
dynamic introduction by the next generation of                обеспечивающим управляемую эволюцию таких
information systems                                           стандартов способом, который способствует
                                                              появлению новых поколений информационных
NOTE Open-edi standards have been designed                    систем
to be able to support computational integrity
requirements especially from a registration and               ПРИМЕЧАНИЕ      Стандарты     открытых    систем
re-use of business objects perspectives.                      электронного     обмена      данными        были
[ISO/IEC 15944-2:2006 (3.18)]                                 спроектированы так, чтобы быть в состоянии
                                                              поддерживать     требования      вычислительной
                                                              целостности,  особенно    при    регистрации   и
                                                              повторном использовании бизнес-объектов.

                                                              [ISO/IEC 15944-2:2006 (3.18)]
3.40                                                          3.40
computer program                                              компьютерная программа
means data representing instructions or
statements that, when executed in a computer                  означает команды представления данных или
system, causes the computer to perform a                      операторы,   которые   будучи   выполненными
function                                                      компьютерной      системой,     обусловливают
                                                              выполнение компьютером некоторой функции
[ISO/IEC 15944-5:2006 (3.28)]
                                                              [ISO/IEC 15944-5:2006 (3.28)]

3.41                                                          3.41
computer service                                              компьютерный сервис
service which includes data processing and the
storage or retrieval of data                                  сервис, который включает обработку данных и
                                                              хранение или поиск данных
[ISO/IEC 15944-5:2006 (3.29)]
                                                              [ISO/IEC 15944-5:2006 (3.29)]

3.42                                                          3.42
computer system
                                                              компьютерная система
device that, or a group of interconnected or
related devices one or more of which:
                                                              устройство  или   группа объединенных  или
(a) contains computer programs or other data;                 связанных устройств, одно или несколько из
and,                                                          которых:

(b)    pursuant   to       computer    programs,                 (a) содержит компьютерную программу или
                                                                     другие данные; и
 (i)   performs    logic     and   control,    and
                                                                 (b) согласно компьютерной программе
 (ii) may perform any other function
                                                                     (i)    выполняет последовательность команд
                                                                            и

[ISO/IEC 15944-5:2006 (3.30)]                                        (ii)   может   выполнять    любую   другую
                                                                            функцию



                                                                                                         51
                   ISO English                      Gender                         ISO Russian
                        (1)                          (2)                               (3)


                                                             [ISO/IEC 15944-5:2006 (3.30)]



3.43                                                         3.43
consensus (standardization perspective)                      консенсус (перспектива стандартизации)
general agreement, characterized by the                      общее соглашение, характеризующееся
absence of sustained opposition to substantial               отсутствием устойчивой оппозиции по
issues by any important part of the concerned                существенным вопросам, достигаемое благодаря
interests and by a process that involves                     не противоречию основных заинтересованных
seeking to take into account the views of all                сторон и посредством процесса, включающего
parties concerned and to reconcile any                       попытку рассмотрения точек зрения всех
conflicting arguments                                        заинтересованных сторон и примирения любых
                                                             конфликтующих аргументов
NOTE Consensus need not imply unanimity.
[ISO/IEC 15944-1:2002 (3.10)]                                ПРИМЕЧАНИЕ Консенсус не предполагает
                                                             единогласие.
                                                             [ISO/IEC 15944-1:2002 (3.10)]

3.44                                                         3.44
constraint                                                   ограничение
rule, explicitly stated, that prescribes, limits,
governs or specifies any aspect of a business                правило,    явно  сформулированное,    которое
transaction                                                  предписывает, ограничивает, регламентирует или
                                                             определяет любой аспект бизнес транзакции
NOTE 1 Constraints are specified as rules
forming part of components of Open-edi                       ПРИМЕЧАНИЕ 1 Ограничения определяются как
scenarios, i.e., as scenario attributes, roles,              правила,    формирующие      часть   компонентов
and/or information bundles.                                  сценария Open-edi, т.е. атрибутов сценария, ролей
                                                             и/или пакетов информации.
NOTE 2 For constraints to be registered for
implementation in Open-edi, they must have                   ПРИМЕЧАНИЕ 2 Чтобы быть зарегистрированными
unique and unambiguous identifiers.                          для реализации в Open-edi, ограничения должны
                                                             иметь уникальные однозначные идентификаторы.
NOTE 3 A constraint may be agreed to among
parties (condition of contract) and is therefore             ПРИМЕЧАНИЕ 3         Ограничение может быть
considered an "internal constraint". Or a                    согласовано между сторонами (условие контракта)
constraint may be imposed on parties, (e.g.,                 и рассматриваться таким образом как «внутреннее
laws, regulations, etc.), and is therefore                   ограничение».
considered an "external constraint".
                                                             [ISO/IEC 15944-1:2002 (3.11)]
[ISO/IEC 15944-1:2002 (3.11)]
3.45                                                         3.45
consumer                                                     потребитель
a buyer who is an individual to whom
consumer protection requirements are applied                 Покупатель, являющийся физическим лицом, к
as a set of external constraints on a business               которому применимы требования защиты прав
transaction                                                  потребителя как набор внешних ограничений для
                                                             бизнес транзакции
NOTE 1 Consumer protection is a set of
explicitly defined rights and obligations                    ПРИМЕЧАНИЕ        1     Требования   защиты    прав

                                                                                                       52
                  ISO English                        Gender                      ISO Russian
                       (1)                            (2)                             (3)
applicable as external constraints on a business              потребителя это набор явно изложенных прав и
transaction.                                                  обязательств,    применимых      как внешние
                                                              ограничения для бизнес транзакции.
NOTE 2 The assumption is that a consumer
protection applies only where a buyer in a                    ПРИМЕЧАНИЕ 2 Предполагается, что защита прав
business transaction is an individual. If this is             потребителя применима только если покупатель в
not the case in a particular jurisdiction, such               бизнес транзакции является физическим лицом.
external constraints should be specified as part              Если в конкретной юрисдикции предполагается
of scenario components as applicable.                         иное, это в качестве внешних ограничений должно
                                                              быть определено как часть компонентов сценария.
NOTE 3 It is recognized that external
constraints on a buyer of the nature of                       ПРИЧАНИЕ      3   Признается, что  внешние
consumer protection may be peculiar to a                      ограничения для покупателя, вытекающие из
specified jurisdiction.                                       природы законодательства по защите прав
[ISO/IEC 15944-1:2002 (3.12)]                                 потребителя могут быть специфическими для
                                                              конкретной юрисдикции.

                                                              [ISO/IEC 15944-1:2002 (3.12)]
3.46                                                          3.46
consumer protection                                           защита прав потребителя
set of external constraints of a jurisdictional
domain as rights of a consumer and thus as                    набор внешних ограничений юридического
obligations (and possible liabilities) of a vendor            домена как права потребителя и таким образом
in a business transaction which apply to the                  как обязательства (и, возможно, ответственность)
good, service and/or right forming the object of              поставщика в бизнес транзакции, применимых к
the business transaction (including associated                товарам, услугам и/или правам, формирующим
information management and interchange                        объект бизнес транзакции (включая связанные
requirements including applicable (sets of)                   требования к управлению и обмену информацией;
recorded information)                                         в свою очередь, требования могут включать
                                                              записанную информацию)
NOTE 1 Jurisdictional domains may restrict the
application of their consumer protection                      ПРИМЕЧАНИЕ 1 Юридические домены могут
requirements as applicable only to individuals                ограничивать применение их требований по защите
engaged in a business transaction of a                        прав     потребителей,     считая,   что    они
commercial activity undertaken for personal,                  распространяются только на физических лиц,
family or household purposes, i.e., they do not               вовлеченных в бизнес транзакцию коммерческой
apply to natural persons in their role as                     деятельности, выполняемую в личных, семейных
"organization" or "organization Person".                      целях или в целях, преследуемых домашним
                                                              хозяйством, т.е. что они неприменимы для «лиц»,
NOTE 2 Jurisdictional domains may have                        являющихся фактически «организациями»
particular consumer protection requirements
which apply specifically to individuals who are               ПРИМЕЧАНИЕ 2 Юридические домены могут иметь
considered to be a "child" or a “minor”, (e.g.,               конкретные    требования   по   защите    прав
those individuals who have not reached their                  потребителя, которые применяются в особенности
thirteenth (13) birthday).                                    к лицам, причисляемым к категории «дети» или
                                                              «малолетние» (например, лица, не достигшие
                                                              возраста 13 лет)
NOTE 3 Some jurisdictional domains may have
                                                              ПРИМЕЧАНИЕ 3 Некоторые юридические домены
consumer protection requirements which are
                                                              могут иметь      требования по защите прав
particular to the nature of the good, service
                                                              потребителя, которые соответствуют природе
and/or right being part of the goal of a business
                                                              товаров, услуг и/или прав, составляющих часть
transaction.
                                                              цели бизнес транзакции
[ISO/IEC 15944-5:2006 (3.33)]
                                                              [ISO/IEC 15944-5:2006 (3.33)]
                                                                                                      53
                  ISO English                       Gender                       ISO Russian
                         (1)                         (2)                              (3)


3.47                                                         3.47
Contact                                                      Контакт
instance of a role of a Person to whom a
recorded information item(s), a material                     экземпляр   роли    лица, которому  позиции
object(s), a business object(s), can be sent to              записанной      информации,    материальные
or received from in a specified context                      объекты, бизнес объекты могут быть посланы
                                                             или от которого могут быть получены в
NOTE 1 A Person here as a Contact can be an                  специальном контексте
individual, an organization (or organization part
or organization Person).                                     ПРИМЕЧАНИЕ 1 Здесь Лицо в качестве Контакта
                                                             может быть физическим лицом, организацией или
NOTE 2 Contact is capitalized to distinguish it              частью организации
from the many ordinary uses of the term.
                                                             ПРИМЕЧАНИЕ 2 Контакт здесь начинается с
[ISO/IEC 11179-3:2003 (3.3.26)]                              прописной буквы, чтобы отличить многие обычные
                                                             использования термина

                                                             [ISO/IEC 11179-3:2003 (3.3.26)]
3.48                                                         3.48
Contact Information                                          Информация для Контакта
information to enable a Contact to be located
or communicated with                                         Информация      чтобы      побудить    Контакт   к
                                                             коммуникации с ним
[ISO/IEC 11179-3:2003 (3.3.27)]
                                                             [ISO/IEC 11179-3:2003 (3.3.27)]

3.49                                                         3.49
Contact name                                                 имя Контакта
persona by which a Person wishes to be
designated as a Contact                                      персонаж, пользуясь которым Лицо желает быть
                                                             установленным в качестве Контакта
NOTE Where an organization is the applicant, it
may designate an organization Person, an                     ПРИМЕЧАНИЕ       Если     соискателем    является
agent, a third party as its Contact name in                  организация,    она    может     назначить    имя
applying to register a scenario or scenario                  организации, агента, третьей стороны как свое имя
component as a business object.                              Контакта   при    регистрации     сценария    или
                                                             компонента сценария как бизнес объекта.
[ISO/IEC 15944-2:2006 (3.21)]
                                                             [ISO/IEC 15944-2:2006 (3.21)]

3.50                                                         3.50
Contact position title                                       название должности Контакта
name of title of the position held by an
organization Person as a Contact                             название должности, используемой организацией
                                                             для Контакта
[ISO/IEC 15944-2:2006 (3.22)]
                                                             [ISO/IEC 15944-2:2006 (3.22)]

3.51                                                         3.51
control body                                                 орган управления
group of technical experts that makes decisions
regarding the content of a register                          группа    технических   экспертов,    принимающих

                                                                                                       54
                  ISO English                         Gender                       ISO Russian
                        (1)                            (2)                                (3)
[ISO 19135:2005 (4.1.2)]                                       решение относительно содержания реестра

                                                               [ISO 19135:2005 (4.1.2)]

3.52                                                           3.52
controlled vocabulary (CV)                                     управляемый словарь (CV)
vocabulary for which the entries, i.e.,
definition/term pairs, are controlled by a                     словарь, в котором элементы, т.е. пары
Source Authority based on a rulebase and                       определение/термин управляются Вышестоящей
process for addition/deletion of entries                       организацией на основе базы правил и процесса
                                                               добавления/исключения элементов
NOTE 1 In a controlled vocabulary, there is a
one-to-one relationship of definition and term.                ПРИМЕЧАНИЕ     1    В   управляемом словаре
                                                               существует взаимно-однозначное соответствие
EXAMPLE The contents "Clause 3 Definitions"                    между терминами и определениями.
in ISO/IEC standards are examples of controlled
vocabularies with the entities being identified                ПРИМЕР Содержание «Статьи 3 Определения»
and referenced through their ID code, i.e., via                стандартов ИСО/ МЭК есть пример управляемого
their clause numbers.                                          словаря, когда коды ID элементов используются
                                                               для идентификации элементов и ссылки на них
NOTE 2 In a multilingual controlled vocabulary,                посредством номеров их статей.
the definition/term pairs in the languages utilized
are deemed to be equivalent, i.e., with respect                ПРИМЕЧАНИЕ 2 В мультиязычных управляемых
to their semantics.                                            словарях    пары     определение/термин      в
                                                               используемых языках считаются эквивалентными с
NOTE 3 The rule base governing a controlled
                                                               учетом их семантики.
vocabulary may include a predefined concept
system.
                                                               ПРИМЕЧАНИЕ 3 База правил, регламентирующая
[ISO/IEC 15944-5:2006 (3.34)]                                  управляемый словарь, может включать систему
                                                               заранее определенных понятий.

                                                               [ISO/IEC 15944-5:2006 (3.34)]

3.53                                                           3.53
creation date                                                  дата создания
date the OeRI for a business object was
created                                                        дата создания OeRI для бизнес объекта

[ISO/IEC 15944-2:2006 (3.24)]                                  [ISO/IEC 15944-2:2006 (3.24)]

3.54                                                           3.54
custody                                                        опека
association between a Person and an
economic resource where the Person has                         связь между Лицом и экономическим ресурсом,
physical control only over the resource or                     когда Лицо только имеет физический контроль над
controls access                                                ресурсом или контролирует доступ к нему

NOTE Having custody of a good, service and/or                  ПРИМЕЧАНИЕ Наличие опеки товара, услуги и/или
right does not imply and is differentiated from                прав не подразумевает и отличается от
having economic control of the same, (e.g., a                  экономического   контроля   того   же   самого
Person may have economic control of a good                     (например, Лицо может иметь экономический
even though it is not under its custody).                      контроль над товаром, хотя он не находится под
                                                               его опекой).
[ISO/IEC 15944-4:2006 (3.15)]

                                                                                                       55
                   ISO English                     Gender                       ISO Russian
                        (1)                         (2)                              (3)
                                                            [ISO/IEC 15944-4:2006 (3.15)]
3.55                                                        3.55
data                                                        данные
reinterpretable representation of information in
a formalized manner suitable for                            представление информации в формализованном
communication, interpretation, or processing                виде, удобном для связи, интерпретации и
                                                            обработки; причем, это представление может быть
NOTE Data can be processed by humans or by                  повторно интерпретировано
automatic means.
                                                            ПРИМЕЧАНИЕ Данные могут обрабатываться
[ISO/IEC 2382-1:1998 (01.01.02)]                            человеком или автоматическими устройствами.

                                                            [ISO/IEC 2382-1:1998 (01.01.02)]

3.56                                                        3.56
data (in a business transaction)                            данные (в бизнес транзакции)
representations of recorded information that
are being prepared or have been prepared in a               представление записанной информации, которое
form suitable for use in a computer system                  готовится или подготовлено в форме, удобной для
                                                            использования в компьютерной системе
[ISO/IEC 15944-1:2002 (3.14)]
                                                            [ISO/IEC 15944-1:2002 (3.14)]

3.57                                                        3.57
data element                                                элемент данных
unit of data for which the definition,
identification, representation and permissible              единица данных, для которой определение,
values are specified by means of a set of                   идентификация, представление и разрешенные
attributes                                                  значения определяются посредством набора
                                                            атрибутов
[ISO/IEC 11179-1:2004 (3.3.8)]
                                                            [ISO/IEC 11179-1:2004 (3.3.8)]

3.58                                                        3.58
data element (in organization of data)                      элемент данных (при организации данных)
unit of data that is considered in context to be
indivisible                                                 единица данных, рассматриваемая в контексте как
                                                            не делимая
EXAMPLE The data element "age of a person"
with values consisting of all combinations of 3             ПРИМЕР Элемент данных «возраст лица» со
decimal digits.                                             значениями, состоящими из всех комбинаций 3
                                                            десятичных цифр.
NOTE Differs from the entry 17.06.02 in
ISO/IEC 2382-17.
                                                            ПРИМЕЧАНИЕ Отличается от элемента 17.06.02 в
                                                            ISO/IEC 2382-17.
[ISO/IEC 2382-4:1999 (3.16)]                                [ISO/IEC 2382-4:1999 (3.16)]
3.59                                                        3.59
dataset                                                     набор данных
identifiable collection of data

NOTE A dataset may be a smaller grouping of                 идентифицируемая совокупность данных
data which, though limited by some constraint
                                                            ПРИМЕЧАНИЕ Набором данных может быть более
                                                                                                   56
                  ISO English                        Gender                       ISO Russian
                       (1)                            (2)                              (3)
such as spatial extent or feature type, is located            мелкая группа данных, которая хотя и ограничена
physically within a larger dataset. Theoretically,            некоторыми       условиями,      такими      как
a dataset may be as small as a single feature or              пространственные размеры или типы признаков,
feature attribute contained within a larger                   содержится внутри более крупного набора данных.
dataset. A hardcopy map or chart may be                       Теоретически набор данных может быть настолько
considered a dataset.                                         мал, что будет соответствовать только одному
                                                              признаку или атрибуту признака в пределах более
[ISO 19115:2003 (4.2)]                                        крупного набора данных. Твердая копия карты или
                                                              схемы может рассматриваться как набор данных.


                                                              [ISO 19115:2003 (4.2)]
3.60                                                          3.60
dataset series                                                ряд наборов данных
collection of datasets sharing the same product
specification                                                 совокупность наборов данных, разделяющих одну
                                                              и ту же спецификацию продукта
[ISO 19115:2003 (4.3)]
                                                              [ISO 19115:2003 (4.3)]

3.61                                                          3.61
date                                                          дата
ISO 8601 compliant representation of a date in
a YYYY-MM-DD format using the Gregorian                       удовлетворяющее ISO 8601 представление даты в
calendar                                                      формате     ГГГГ-ММ-ДД    с    использованием
                                                              Грегорианского календаря
[ISO/IEC 15944-2:2006 (3.26)]
                                                              [ISO/IEC 15944-2:2006 (3.26)]

3.62                                                          3.62
Decision Making Application (DMA)                             Приложение Принятия Решений (DMA)
model of that part of an Open-edi system that
makes decisions corresponding to the role(s)                  модель той части системы Open-edi, которая
that the Open-edi Party plays as well as the                  принимает решения в соответствии с ролью
originating, receiving and managing data values               (ролями), которую играет сторона Open-edi, также
contained in the instantiated information                     как формирование, получение и управление
bundles which is not required to be visible to                значениями      данных,      содержащихся      в
the other Open-edi Party(ies)                                 сопровождаемых         примерами        пакетах
                                                              информации, которые не должны быть видимыми
[ISO/IEC 14662:2004 (3.6)]                                    для других сторон Open-edi

                                                              [ISO/IEC 14662:2004 (3.6)]

3.63                                                          3.63
Decision Making Application Interface (DMA                    Интерфейс Приложения            Принятия   Решений
Interface)                                                    (Интерфейс DMA)

set of requirements that permit a Decision                    набор    требований,    который    разрешает
Making Application to interact with the Open-                 Приложению      Принятия    Решений    чтобы
edi Support Infrastructure                                    взаимодействовать     с     Инфраструктурой,
                                                              поддерживающей Open-edi
[ISO/IEC 14662:2004 (3.7)]
                                                              [ISO/IEC 14662:2004 (3.7)]


                                                                                                          57
                  ISO English                        Gender                       ISO Russian
                       (1)                            (2)                                 (3)
3.64                                                          3.64
de facto language                                             язык де-факто
natural language used in a jurisdictional
domain which has the properties and                           естественный        язык,     используемый в
behaviours of an official language in that                    юридическом домене, который имеет свойства и
jurisdictional domain without having formally                 поведение официального языка в этом домене
been declared as such by that jurisdictional                  без признания как такового этим доменом
domain
                                                              ПРИМЕЧАНИЕ 1 Язык де-факто юридического
NOTE 1 A de facto language of a jurisdictional                домена часто устанавливается в результате
domain is often established through long term                 обычая его длительного использования
use and custom.
                                                              ПРИМЕЧАНИЕ 2 Если только явно не установлено
NOTE 2 Unless explicitly stated otherwise and                 иное и для целей моделирования бизнес
for the purposes of modelling a business                      транзакций    с     использованием     сценария
transaction through scenario(s), scenario                     (сценариев),    атрибутов     сценария    и/или
attributes and/or scenario components, a de                   компонентов сценария предполагается, что язык
facto language of a jurisdictional domain is                  де-факто юридического домена обладает теми же
assumed to have the same properties and                       самыми свойствами и поведением, как и
behaviours of an official language.                           официальный язык

[ISO/IEC 15944-5:2006 (3.42)]                                 [ISO/IEC 15944-5:2006 (3.42)]

3.65                                                          3.65
defined market model                                          определенная рыночная модель
trade model where the buyer and seller accept
the entry terms of a specified market in                      модель торговли, где покупатель и продавец
advance and where that market has an                          принимают условия вхождения в конкретный
accepted and recognized source for business                   рынок заранее и где этот рынок принимает и
rules and conventions                                         признает источник бизнес правил и условий

NOTE In a defined market, the phases of a                     ПРИМЕЧАНИЕ В определенном рынке фазы
business transaction –planning, identification,               бизнес      транзакции     –      планирование,
negotiation, actualization, and post-actualization            идентификация, переговоры, актуализация и пост-
– are governed by the rules and conventions of                актуализация – определяются правилами и
the particular defined market.                                условиями конкретного определенного рынка.


[ISO/IEC 15944-4:2006 (3.17)]                                 [ISO/IEC 15944-4:2006 (3.17)]
3.66                                                          3.66
definition                                                    определение
representation of a concept by a descriptive
statement which serves to differentiate it from               представление понятия путем описательного
related concepts                                              утверждения, которое служит для того чтобы
                                                              отличать его от связанных понятий
[ISO 1087-1:2000 (3.3.1)]
                                                              [ISO 1087-1:2000 (3.3.1)]


3.67                                                          3.67
designation                                                   назначение
representation of a concept by a sign which
denotes it                                                    представление понятия в виде знака, который его
                                                              обозначает

                                                                                                     58
                 ISO English                      Gender                       ISO Russian
                      (1)                          (2)                                 (3)

NOTE In terminology work three types of                    ПРИМЕЧАНИЕ В терминологической деятельности
designations are distinguished: symbols,                   различаются три типа назначений: символы,
appellations, (a.k.a. names), and terms.                   наименования (или имена) и термины.

[ISO 1087-1:2000 (3.4.1)]                                  [ISO 1087-1:2000 (3.4.1)]
3.68                                                       3.68
distinguishing identifier                                  различающий идентификатор

data that unambiguously distinguishes an entity            данные, которые однозначно различают сущность в
in the authentication process                              процессе удостоверения подлинности

[ISO/IEC 10181-2:1996]                                     [ISO/IEC 10181-2:1996]

3.69                                                       3.69
documentation language code                                код языка документации
language code of the language used for
documentation by the Open-edi Registration                 языковой    код  языка,  используемого  для
Organization                                               документации Организацией Регистрации Open-
                                                           edi
NOTE Use the three character alphabetic
language codes and names from ISO 639-2/T                  ПРИМЕЧАНИЕ Используйте 3-х символьные
(Terminology).                                             алфавитно-цифровые языковые коды и имена из
                                                           ISO 639-2/T (Терминология)
[ISO/IEC 15944-2:2006 (3.30)]
                                                           [ISO/IEC 15944-2:2006 (3.30)]

3.70                                                       3.70
duality                                                    двойственность
association between economic events where
one is the legal or economic consideration for             связь между экономическими событиями, когда
the other in an exchange                                   одно есть юридическое или экономическое
                                                           возмещение для другого при обмене
NOTE Duality is the conceptual analog of
double entry in traditional bookkeeping. For               ПРИМЕЧАНИЕ            Двойственность         есть
example, a shipment from a partner requires a              концептуальный    аналог   двойного    ввода    в
matching flow in like a payment to balance                 традиционном бухгалтерском учете. Например,
accounts between the parties.                              отгрузка партнером требует соответствующего
                                                           входящего    потока    типа     платежа    чтобы
[ISO/IEC 15944-4:2006 (3.18)]                              сбалансировать счета партнеров.

                                                           [ISO/IEC 15944-4:2006 (3.18)]




3.71                                                       3.71
economic agreement                                         экономическое соглашение
arrangement of reciprocated economic
commitments between two partners where the                 установление     взаимных   экономических
abstract specification of terms of trade is                обязательств между двумя партнерами, когда
incomplete and not subject to legal enforcement            абстрактная спецификация условий торговли
                                                           является не завершенной и не подчиняется
[ISO/IEC 15944-4:2006 (3.19)]                              юридическому принуждению



                                                                                                    59
                  ISO English                      Gender                      ISO Russian
                      (1)                           (2)                             (3)
                                                            [ISO/IEC 15944-4:2006 (3.19)]

3.72                                                        3.72
economic bundle                                             экономический пакет
association between economic commitments
and the economic contract that bundles those                соответствие       между      экономическими
promises and binds them to the two partners                 обязательствами и экономическим контрактом,
who negotiated them                                         которое увязывает эти обещания и связывает их с
                                                            двумя партнерами, которые рассматривают их на
[ISO/IEC 15944-4:2006 (3.20)]                               переговорах

                                                            [ISO/IEC 15944-4:2006 (3.20)]

3.73                                                        3.73
economic claim                                              экономическое требование
expectation of one Person to receive a future
inflow of economic resources from another                   ожидание одного Лица получить входящий поток
Person because of an economic exchange                      экономических ресурсов от другого Лица, т.к.
which is presently incomplete                               экономический обмен к настоящему моменту не
                                                            завершен
[ISO/IEC 15944-4:2006 (3.21)]
                                                            [ISO/IEC 15944-4:2006 (3.21)]

3.74                                                        3.74
economic commitment                                         экономическое обязательство
type of commitment by one Person to transfer
economic resources to another Person at                     тип обязательства, взятого одним Лицом по
some specified point in the future                          передаче экономических ресурсов другому Лицу
                                                            в некоторый определенный момент в будущем
[ISO/IEC 15944-4:2006 (3.22)]
                                                            [ISO/IEC 15944-4:2006 (3.22)]

3.75                                                        3.75
economic contract                                           экономический контракт
bundling of reciprocated economic
commitments between two partners where the                  увязывание     взаимных     экономических
abstract specification of the proposed                      обязательств между двумя партнерами, когда
economic exсhange is deemed to be complete                  абстрактная  спецификация  предполагаемого
                                                            экономического обмена предполагается быть
[ISO/IEC 15944-4:2006 (3.23)]                               завершенной

                                                            [ISO/IEC 15944-4:2006 (3.23)]


3.76                                                        3.76
economic control                                            экономическое управление
association between a Person and an
economic resource where the Person either                   связь между Лицом и экономическим ресурсом,
owns the resource or is otherwise able to derive            когда Лицо или владеет ресурсом или может
economic benefit (utility) from it                          получить экономическую выгоду (пользу) от него

[ISO/IEC 15944-4:2006 (3.24)]                               [ISO/IEC 15944-4:2006 (3.24)]


                                                                                                   60
                  ISO English                      Gender                      ISO Russian
                      (1)                           (2)                             (3)
3.77                                                        3.77
economic event                                              экономическое событие
occurrence in time wherein ownership of an
economic resource is transferred from one                   наступление события в срок, когда владение
Person to another Person                                    экономическим ресурсом переходит от одного
                                                            Лица к другому Лицу
NOTE Occurrences in time can either be
                                                            ПРИМЕЧАНИЕ Наступление события в срок может
(1) internal as mutually agreed to among the                быть:
parties to a business transaction; and/or,
                                                                      (1) внутренним, взаимно согласованным
(2) reference some common publicly available                              между    сторонами     в    бизнес
and recognized date/time referencing schema,                              транзакции; и/или
(e.g., one based on using the ISO 8601 and/or                         (2) со ссылкой на некоторую общую,
ISO 19135 standards).                                                     публично доступную референтную
[ISO/IEC 15944-4:2006 (3.25)]                                             схему (например, на ту, которая
                                                                          основана      на    использовании
                                                                          стандартов ISO 8601 и/или ISO
                                                                          19135


                                                             [ISO/IEC 15944-4:2006 (3.25)]
3.78                                                        3.78
economic event type                                         тип экономического события
abstract specification of an economic event
where its grouped properties can be designated              абстрактная    спецификация    экономического
without attachment to an actual, specific                   события,      когда     его     сгруппированная
occurrence in time                                          собственность может быть предназначена для
                                                            сделки без привязки к фактическому, конкретному
NOTE Example of attributes at the type level for            наступлению события в срок
events might be expected-duration or standard-
pricing-percentage.                                         ПРИМЕЧАНИЕ Примером атрибутов на уровне
                                                            типа для событий может быть ожидаемая
[ISO/IEC 15944-4:2006 (3.26)]                               продолжительность или снандартное- назначение-
                                                            цены-процента

                                                            [ISO/IEC 15944-4:2006 (3.26)]
3.79                                                        3.79
economic exchange                                           экономический обмен
type of a business transaction where the goal
is an exchange of economic resources                        тип бизнес транзакции, когда целью является
between two Persons where both parties derive               обмен экономическими ресурсами между двумя
higher utility after the completed business                 Лицами, когда обе стороны получают более
transaction                                                 высокую выгоду после завершения бизнес
                                                            транзакции
NOTE An economic exchange usually involves
two economic events with different types of                 ПРИМЕЧАНИЕ Экономический обмен обычно
economic resources flowing in opposite                      включает   два    экономических    события     с
directions. For example, an exchange of cash                различными типами экономических ресурсов,
for a good involves a shipment with a requited              перемещающихся в противоположные стороны.
payment following.                                          Например, обмен денег на товар включает отгрузку
                                                            с последующей оплатой вознаграждения.
[ISO/IEC 15944-4:2006 (3.27)]
                                                            [ISO/IEC 15944-4:2006 (3.27)]

                                                                                                    61
                  ISO English                         Gender                      ISO Russian
                        (1)                            (2)                             (3)
3.80                                                           3.80
economic resource                                              экономический ресурс
good, right, or service of value, under the control
of a Person                                                    товар, право, услуга определенной стоимости под
                                                               управлением Лица
[ISO/IEC 15944-4:2006 (3.28)]
                                                               [ISO/IEC 15944-4:2006 (3.28)]

3.81                                                           3.81
economic resource type                                         тип экономического ресурса
abstract specification of an economic resource                 абстрактная спецификация экономического
where its grouped properties can be designated                 ресурса, когда его сгруппированная собственность
without attachment to an actual, specific                      может быть предназначена без привязки к
economic resource                                              фактическому, конкретному экономическому
                                                               ресурсу
NOTE Example of attributes at the type level for
an economic resource like an automobile might                  ПРИМЕЧАНИЕ Пример атрибутов на уровне типа
include its designated fuel capacity or its                    для экономического ресурса вида автомобиль
maximum expected range.                                        может быть определенная вместимость топливного
[ISO/IEC 15944-4:2006 (3.29)]                                  бака или его максимальный пробег без дозаправки.
                                                               [ISO/IEC 15944-4:2006 (3.29)]

3.82                                                           3.82
economic role                                                  экономическая роль
abstract specification of a Person for economic
purposes where its grouped properties can be                   абстрактная     спецификации       Лица    для
designated without attachment to an actual                     экономических целей, когда его сгруппированная
Person                                                         собственность может быть предназначена для
                                                               сделки без привязки к фактическому Лицу
NOTE An example economic role might be
qualified buyer or approved shipper.                           ПРИМЕЧАНИЕ Примером экономической роли
                                                               может быть квалифицированный покупатель или
                                                               одобренный поставщик.
[ISO/IEC 15944-4:2006 (3.30)]

                                                               [ISO/IEC 15944-4:2006 (3.30)]


3.83                                                           3.83
economic specification                                         экономическая спецификация
association between an economic
commitment and the abstract properties of an                   связь между экономическим обязательством и
economic event, an economic resource, a                        абстрактной  собственностью  экономического
partner, or a business location                                события, экономического ресурса, партнера или
                                                               месторасположения бизнеса
[ISO/IEC 15944-4:2006 (3.31)]

                                                               [ISO/IEC 15944-4:2006 (3.31)]

3.84                                                           3.84
effective date                                                 дата вступления в силу
date an OeRI became/becomes available to
                                                               дата,   когда   OeRI   стал/становится   доступным

                                                                                                          62
                  ISO English                     Gender                       ISO Russian
                          (1)                      (2)                              (3)
registry users                                             пользователям реестра
[ISO/IEC 15944-2:2006 (3.31)]
                                                           [ISO/IEC 15944-2:2006 (3.31)]

3.85                                                       3.85
electronic address                                         электронный адрес
address utilized in a recognized electronic
addressing scheme, (e.g., telephone, telex, IP,            адрес, используемый в схеме распознавания
etc.), to which recorded information item(s)               электронной адресации (например, телефон,
and/or business object(s) can be sent to or                телекс, IP и т.д.), по которому элемент записанной
received from a Contact                                    информации и/или бизнес объект (объекты)
                                                           могут быть посланы или получены от Контакта
[ISO/IEC 15944-2:2006 (3.32)]
                                                           [ISO/IEC 15944-2:2006 (3.32)]

3.86                                                       3.86
Electronic Data Interchange (EDI)                          Электронный Обмен Данными (EDI)
the automated exchange of any predefined and
structured data for business purposes among                Автоматизированный обмен любыми заранее
information systems of two or more Persons.                определенными и структурированными данными
                                                           для целей бизнеса между информационными
NOTE This definition includes all categories of            системами двух или более Лиц
electronic business transactions.
                                                           ПРИМЕЧАНИЕ Это определение включает все
[ISO/IEC 14662:2004 (3.8)]                                 категории электронных бизнес транзакций

                                                           [ISO/IEC 14662:2004 (3.8)]
3.87                                                       3.87
entity                                                     сущность
any concrete or abstract thing that exists, did
exist, or might exist, including associations              любая конкретная или абстрактная вещь, которая
among these things                                         существует, существовала в прошлом или может
                                                           существовать, включая связи между этими вещами
EXAMPLE A person, object, event, idea,
process, etc.                                              ПРИМЕР Лицо, объект, событие, идея, процесс и
                                                           т.д.
NOTE An entity exists whether data about it are
available or not.                                          ПРИМЕЧАНИЕ Сущность существует независимо
[ISO/IEC 2382-17:1999 (17.02.05)]                          от того, доступны ли данные о ней или нет.

                                                           [ISO/IEC 2382-17:1999 (17.02.05)]

3.88                                                       3.88
entity authentication                                      аутентификация сущности

the corroboration that the entity is the one               удостоверение того, что сущность та, которая
claimed                                                    кому- то требуется

[ISO/IEC 9788-1:1997 (3.3.1)]                              [ISO/IEC 9788-1:1997 (3.3.1)]

3.89                                                       3.89
(entity) identification                                    идентификация (сущности)
a method of using one or more attributes

                                                                                                     63
                  ISO English                        Gender                      ISO Russian
                        (1)                           (2)                             (3)
whose attribute values uniquely identify each                 метод использования одного или более атрибутов,
occurrence of a specified entity                              чьи значения уникально идентифицируют каждое
[ISO/IEC 2382-17:1999 (17.02.14)]                             появление определенной сущности

                                                              [ISO/IEC 2382-17:1999 (17.02.14)]
3.90                                                          3.90
entry label                                                   метка входа
name information uniquely associated with the
identification and resulting International                    информация об имени, уникально связанная с
Registration Business Object Identifier                       идентификацией      бизнес      объекта    и
(IRBOI) of a business object as a registered                  обусловленным               Идентификатором
Open-edi scenario or scenario component                       Международной Регистрации Бизнес Объекта
                                                              (IRBOI), в виде зарегистрированного сценария
NOTE More than one entry label may be                         Open-edi или компонента сценария
associated with an IRBOI depending on the
applicable language(s) utilized as Human                      ПРИМЕЧАНИЕ Более чем одна метка входа может
Interface Equivalents (HIEs).                                 связана с IRBOI в зависимости от применяемого
                                                              языка   (языков), используемого   в  качестве
                                                              Эквивалентов Человеко-машинного Интерфейса
[ISO/IEC 15944-2:2006 (3.33)]                                 (HIE)

                                                              [ISO/IEC 15944-2:2006 (3.33)]




3.91                                                          3.91
exchange code set                                             набор кодов обмена
a set of ID codes identified in a coded domain
as being suitable for information exchange as                 набор кодов ID, идентифицируемых в домене
shareable data                                                кодов, как удобных для обмена информацией в
                                                              качестве разделяемых данных
EXAMPLE The 3 numeric, 2-alpha and 3-alpha
code sets in ISO 3166-1.                                      ПРИМЕР 3 числовой, 2 и 3 алфавитные наборы
                                                              кодов в ISO 3166-1
[ISO/IEC 15944-5:2006 (3.49)]
                                                               [ISO/IEC 15944-5:2006 (3.49)]
3.92                                                          3.92
external constraint                                           внешнее ограничение
constraint which takes precedence over
internal constraints in a business                            ограничение, которое имеет превосходство над
transaction, i.e., is external to those agreed                внутренними       ограничениями    в     бизнес
upon by the parties to a business transaction                 транзакции, т.е. является внешним по отношению
                                                              к тем, которые согласованы сторонами бизнес
NOTE 1 Normally external constraints are                      транзакции
created by law, regulation, orders, treaties,
conventions or similar instruments.                           ПРИМЕЧАНИЕ 1 Обычно внешние ограничения
                                                              создаются законами, регламентами, договорами,
NOTE 2 Other sources of external constraints                  соглашениями или подобными инструментами
are those of a sectorial nature, those which
pertain to a particular jurisdiction or a mutually            ПРИМЕЧАНИЕ 2 Другими источниками внешних
agreed to common business conventions, (e.g.,                 ограничений являются те, которые имеют природу,
INCOTERMS, exchanges, etc.).                                  связанную сконкретными секторами бизнеса, те,
                                                              которые соответствуют конкретной юрисдикции или
NOTE 3 External constraints can apply to the                  взаимно   согласованным     бизнес  конвенциям

                                                                                                     64
                   ISO English                         Gender                      ISO Russian
                        (1)                             (2)                             (3)
nature of the good, service and/or right provided               (например, INCOTERMS, обмены и т.д.).
in a business transaction.
                                                                ПРИМЕЧАНИЕ 3 Внешние ограничения могут
NOTE 4 External constraints can demand that a                   применяться к природе товаров, услуг или прав,
party to a business transaction meet specific                   составляющих предметы обмена в бизнес
requirements of a particular role.                              транзакции.
EXAMPLE 1 Only a qualified medical doctor                       ПРИМЕЧАНИЕ 4 Внешние ограничения могут
may issue a prescription for a controlled drug.                 требовать, чтобы сторона бизнес транзакции
EXAMPLE 2 Only an accredited share dealer                       удовлетворяла    специфические  требования
may place transactions on the New York Stock                    конкретной роли.
Exchange.
                                                                ПРИМЕР 1 Только квалифицированный доктор
EXAMPLE 3 Hazardous wastes may only be                          может выписывать рецепты на контролируемые
conveyed by a licensed enterprise.                              лекарства.

NOTE 5 Where the information bundles (IBs),                     ПРИМЕР2 Только аккредитованный дилер может
including their Semantic Components (SCs) of a                  размещать транзакции на Нью-йоркской фондовой
business transaction are also to form the whole                 бирже.
of a business transaction, (e.g., for legal or audit
purposes), all constraints must be recorded.                    ПРИМЕР 3 Потери от риска могут передаваться
                                                                только лицензированными предприятиями
EXAMPLE There may be a legal or audit
requirement to maintain the complete set of                     ПРИМЕЧАНИЕ 5 Когда пакеты информации (IB),
recorded information pertaining to a business                   включая их Семантичесие Компоненты (SC) бизнес
transaction, i.e., as the information bundles                   транзакции, должны также формировать бизнес
exchanged, as a "record".                                       транзакцию в целом (например для юридических
                                                                или аудиторских целей), все ограничения должны
NOTE 6 A minimum external constraint
                                                                быть записаны.
applicable to a business transaction often
requires one to differentiate whether the Person,
                                                                ПРИМЕР      Может     быть    юридическое  или
i.e., that is a party to a business transaction, is
                                                                аудиторское требование поддерживать полный
an "individual", "organization", or "public
                                                                набор записанной информации, связанной с
administration". For example, privacy rights
                                                                транзакцией,     т.е.    пакеты     информации,
apply only to a Person as an "individual".
                                                                участвовавшие в обмене, записи.
[ISO/IEC 15944-1:2002 (3.23)]
                                                                ПРИМЕЧАНИЕ 6         Минимальным      внешним
                                                                ограничением, применяемым к бизнес транзакции,
                                                                часто необходимым, является то, которое служит
                                                                для различения Лица, т.е. стороны бизнес
                                                                транзакции. А именно, является ли Лицо
                                                                физическим лицом, организацией или органом
                                                                государственного управления. Например, защита
                                                                прав личности применима только если Лицо
                                                                является физическим.

                                                                [ISO/IEC 15944-1:2002 (3.23)]




3.93                                                            3.93
Formal Description Technique (FDT)                              Метод Формального Описания (FDT)
specification method based on a description
language using rigorous and unambiguous                         метод спецификации основан на дескриптивном
                                                                языке с использованием строгих и однозначных
                                                                                                        65
                 ISO English                      Gender                      ISO Russian
                      (1)                          (2)                             (3)
rules both with respect to developing                      правил как в отношении выражений вывода в
expressions in the language (formal syntax)                языке (формальный синтаксис) и интерпретации
and interpreting the meaning of these                      этих выражений (формальная семантика)
expressions (formal semantics)
[ISO/IEC 14662:2004 (3.9)]                                 [ISO/IEC 14662:2004 (3.9)]

3.94                                                       3.94
fulfillment                                                выполнение
association between an economic
commitment and an economic event where                     связь между экономическим обязательством и
the event executes the promised resource flow              экономическим    событием,   когда   событие
from one Person to another                                 реализует поток обещанного ресурса от одного
                                                           Лица другому
NOTE For example, a delivery to a customer
would fulfill that customer’s sale order.                  ПРИМЕЧАНИЕ Например, поставка         заказчику
                                                           выполняет заказ на продажу клиента
[ISO/IEC 15944-4:2006 (3.34)]
                                                           [ISO/IEC 15944-4:2006 (3.34)]




3.95                                                       3.95
Functional       Service     View        (FSV)             Вид Функционального Сервиса (FSV)
perspective of business transactions limited to
those information technology interoperability              Вид бизнес транзакции, ограниченный теми
aspects of information technology systems                  аспектами взаимодействия в IT Системах, которые
(IT Systems) needed to support the execution               необходимы     для    поддержки     выполнения
of Open-edi transactions                                   транзакций Open-edi

[ISO/IEC 14662:2004 (3.10)]                                [ISO/IEC 14662:2004 (3.10)]


3.96                                                       3.96
glyph                                                      глиф
recognizable abstract graphic symbol which is
independent of any specific design                         распознаваемый абстрактный графический символ,
                                                           который независим от любого конкретного проекта
[ISO/IEC TR 15285:1998 (3.5)]
                                                           [ISO/IEC TR 15285:1998 (3.5)]

3.97                                                       3.97
governed                                                   управляемая
association between an economic agreement
and the business transaction whose conduct                 связь между экономическим соглашением и
and phases are subject to that economic                    бизнес транзакцией, управление которой и фазы
agreement of the business transaction                      выполнения   зависят   от     экономического
                                                           соглашения о бизнес транзакции
[ISO/IEC 15944-4:2006 (3.35)]
                                                           [ISO/IEC 15944-4:2006 (3.35)]

3.98                                                       3.98

                                                                                                  66
                   ISO English                         Gender                      ISO Russian
                         (1)                            (2)                             (3)
Human Interface Equivalent (HIE)                                Эквивалент Человеко-машинного Интерфейса
representation of the unambiguous and IT-                       (HIE)
enabled semantics of an IT interface
equivalent (in a business transaction), often                   представление однозначной и приспособленной
the ID code of a coded domain (or a                             для эффективного применения IT семантики
composite identifier), in a formalized manner                   эквивалента     IT   интерфейса   (в   бизнес
suitable for communication to and                               транзакции), часто являющееся кодом ID домена
understanding by humans                                         кодов (или составным идентификатором), в
                                                                формализованном виде удобном для связи и
NOTE 1 Human interface equivalents can be                       понимания людьми
linguistic or non-linguistic in nature but their
semantics remains the same although their                       ПРИМЕЧАНИЕ 1 Эквиваленты человеко-машинного
representations may vary.                                       интерфейса     могут    быть     по    природе
                                                                лингвистическими или не лингвистическими, но их
NOTE 2 In most cases there will be multiple                     семантика остается той же самой, хотя их
Human Interface Equivalent representations as                   представление может варьироваться.
required to meet localization requirements, i.e.
those of a linguistic nature, jurisdictional nature,            ПРИМЕЧАНИЕ 2 В большинстве случаев будут
and/or sectoral nature.                                         множественные     представления    Эквивалента
                                                                Человеко-машинного Интерфейса, что требуется
NOTE 3 Human Interface Equivalents include                      для удовлетворения требований локализации. Эти
representations in various forms or formats,                    требования      имеют      разную     природу:
(e.g., in addition to written text those of an                  лингвистическую, юридическую или определяемую
audio, symbol (and icon) nature, glyphs, image,                 сектором бизнеса.
etc.).
                                                                ПРИМЕЧАНИЕ       3   Эквиваленты        Человеко-
[ISO/IEC 15944-2:2006 (3.35)]                                   машинного Интерфейса включают представления в
                                                                различных формах и форматах (например, к
                                                                письменному тексту может быть добавлена аудио-
                                                                информация, информация символической (и
                                                                знаковой) природы, глифы, образы и т.д.

                                                                [ISO/IEC 15944-2:2006 (3.35)]
3.99                                                            3.99
IB Identifier                                                   Идентификатор IB
unique, linguistically neutral, unambiguous
referenceable identifier for an Information                     Уникальный,    лингвистически   нейтральный,
Bundle                                                          допускающий однозначную ссылку идентификатор
                                                                для Пакета Информации
                                                                 (IB)
[ISO/IEC 15944-2:2006 (3.36)]

                                                                [ISO/IEC 15944-2:2006 (3.36)]
3.100                                                           3.100
ID Code                                                         код идентификатора
identifier assigned by the coded domain
Source Authority (cdSA) to a member of a                        идентификатор   назначается Вышестоящим
coded domain ID                                                 органом   домена кодов (cdSA) элементу ID
                                                                домена кодов
NOTE 1 ID codes must be unique within the
Registration Schema of that coded domain.                       ПРИМЕЧАНИЕ     1  Коды    ID  должны    быть
                                                                уникальными в Схеме Регистрации этого домена
NOTE 2 Associated with an ID code in a coded                    кодов.
domain can be:

                                                                                                         67
                   ISO English                        Gender                       ISO Russian
                        (1)                            (2)                              (3)

- one or more equivalent codes;                                ПРИМЕЧАНИЕ 2 Связанными с кодом ID в домене
                                                               кодов могут быть:
- one or more equivalent representations,
especially those in the form of human equivalent               - один или более эквивалентных кода;
(linguistic) expressions.
                                                               - одно или более эквивалентных представлений,
NOTE 3 Where an entity as a member of a                        особенно     тех,   которые   имеют    форму
coded domain is allowed to have more than one                  лингвистических выражений.
ID code, i.e., as equivalent codes (possibly
including names), one of these must be
                                                               ПРИМЕЧАНИЕ 3 Если сущность как элемент
specified as the pivot ID code.                                домена кодов присваивается более чем одному
NOTE 4 A coded domain may contain ID codes                     коду ID, т.е. эквивалентным кодам ID (возможно,
pertaining to entities which are not members as                включающим имена), один из этих кодов ID
peer entities, i.e., have the same properties and              должен быть определен как ведущий.
behaviours, such as ID codes which pertain to                  ПРИМЕЧАНИЕ 4 Домен кодов может содержать
predefined conditions other than member                        коды ID, принадлежащие к множеству сущностей,
entities. If this is the case, the rules governing             которые не являются элементами домена кодов.
such exceptions must be predefined and                         Правила, регламентирующие такие исключения,
explicitly stated.                                             должны заранее и явно сформулированы.
EXAMPLE Common examples include: (1) the                       ПРИМЕР Примеры общего характера включают:
use of an ID code "0" (or "00", etc.), for “Other”;
(2) the use of an ID code "9" (or "99") for “Not               (1) использование кода ID “O” (или “OO”) для
Applicable”; (3) the use of “8” (or “98”) for “Not             “Другие”;
Known”; if required, (4) the pre-reservation of a
series or set of ID codes for use for "user                    (2) использование кода ID “9” (или “99”) для “Не
extensions".                                                   применяется”;

NOTE 5 In UML modeling notation, an ID codes                   (3) использование “8” (или “98”) для “Не известно”;
is viewed as an instance of an object class.
                                                               (4) если необходимо, предварительное
                                                               резервирование ряда или набора кодов ID для
[ISO/IEC 15944-2:2006 (3.37)]                                  пользовательских расширений.

                                                               ПРИМЕЧАНИЕ 5 В нотации моделирования языка
                                                               UML коды ID рассматриваются как экземпляры
                                                               классов объектов.

                                                               [ISO/IEC 15944-2:2006 (3.37)]
3.101                                                          3.101
identification                                                 идентификация
rule-based process, explicitly stated, involving
the use of one or more attributes, i.e., data                  процесс      на      основе   правил,     явно
elements, whose value (or combination of                       сформулированный, включающий использование
values) are used to identify uniquely the                      одного или более атрибутов, т.е. элементов
occurrence or existence of a specified entity                  данных, чьи значения (или комбинации значений)
                                                               используются для уникальной идентификации
                                                               появления или существования определенной
[ISO/IEC 15944-1:2002 (3.26)]                                  сущности
                                                               [ISO/IEC 15944-1:2002 (3.26)]

3.102                                                          3.102
identifier (in business transaction)                           идентификатор (в бизнес транзакции)
unambiguous, unique and a linguistically
                                                                                                           68
                   ISO English                         Gender                       ISO Russian
                        (1)                             (2)                             (3)
neutral value, resulting from the application of a              однозначное,   уникальное  и   лингвистически
rule-based identification process                               нейтральное    значение,   получаемое     при
                                                                применении основанного на правилах процесса
NOTE 1 Identifiers must be unique within the                    идентификации
identification scheme of the issuing authority.
                                                                ПРИМЕЧАНИЕ 1 Идентификаторы могут быть
NOTE 2 An identifier is a linguistically                        уникальными в пределах схемы идентификации
independent sequence of characters capable of                   выпускающего органа.
uniquely and permanently identifying that with
which it is associated. {See ISO 19135:2005                     ПРИМЕЧАНИЕ          2   Идентификатор    есть
(4.1.5)}                                                        лингвистически независимая последовательность
                                                                символов, способная уникально и постоянно
[ISO/IEC 15944-1:2002 (3.27)]                                   идентифицировать все, с чем она связана. {См.
                                                                ISO 19135:2005 (4.1.5)}

                                                                [ISO/IEC 15944-1:2002 (3.27)]
3.103                                                           3.103
indexing language                                               язык индексирования
artificial language established to characterize
the content or form of a document                               искусственный язык, введенный для того чтобы
                                                                охарактеризовать содержание    формы     или
                                                                документа
[ISO/IEC 2382-1:1998 (01.05.10)]
                                                                [ISO/IEC 2382-1:1998 (01.05.10)]
3.104                                                           3.104
individual                                                      личность
Person who is a human being, i.e., a natural
person, who acts as a distinct indivisible entity               Лицо    (человек),  т.е.   физическое     лицо,
or is considered as such                                        действующее     как   различимая     неделимая
                                                                сущность или рассматриваемая как таковая

[ISO/IEC 15944-1:2002 (3.28)]
                                                                [ISO/IEC 15944-1:2002 (3.28)]
3.105                                                           3.105
individual accessibility                                        индивидуальная доступность
set of external constraints of a jurisdictional
domain as rights of an individual with                          набор внешних ограничений юридического
disabilities to be able to utilize IT systems at the            домена    в    качестве  прав   личности   с
human, i.e., user, interface and the concomitant                ограниченными физическими возможностями для
obligation of a seller to provide such adaptive                 использования IT систем с соответствующим
technologies                                                    пользовательским интерфейсом и сопутствующие
                                                                обязательства продавца по обеспечению таких
NOTE Although “accessibility” typically                         адаптивных технологий
addresses users who have a disability, the
concept is not limited to disability issues.                    ПРИМЕЧАНИЕ       Хотя   «доступность»   обычно
                                                                адресуется пользователям с ограниченными
EXAMPLE Examples of disabilities in the form                    физическими     возможностями,    понятие   не
of functional and cognitive limitations include:                ограничивается проблемами инвалидности.

- people who are blind;                                         ПРИМЕР    Примеры        инвалидности  в   виде
- people with low vision;                                       функциональных и        когнитивных ограничений
- people with colour blindness;                                 включают:
- people who are hard of hearing or deaf, i.e.,
are hearing impaired;                                           - незрячих людей;

                                                                                                        69
                  ISO English                       Gender                      ISO Russian
                        (1)                          (2)                             (3)
- people with physical disabilities;                         - людей с плохим зрением;
- people with language or cognitive disabilities.            - дальтоников;
[ISO/IEC 15944-5:2006 (3.60)]                                - плохо слышащих или глухих людей;
                                                             - людей с физическими недостатками;
                                                             - людей с недостатками речи или когнитивными
                                                             недостатками.
                                                             [ISO/IEC 15944-5:2006 (3.60)]
3.106                                                        3.106
information (in information processing)                      нформация        (в      процессе       обработки
knowledge concerning objects, such as facts,                 информации)
events, things, processes, or ideas, including
concepts,that within a certain context has a                 объекты, касающиеся знаний, такие как факты,
particular meaning                                           события, предметы, процессы или идеи, включая
                                                             понятия, которые в определенном контексте имеют
                                                             конкретный смысл
[ISO/IEC 2382-1:1998 (01.01.01)]
                                                             [ISO/IEC 2382-1:1998 (01.01.01)]

3.107                                                        3.107
Information Bundle (IB)                                      Пакет Информации (IB)
formal description of the semantics of the
recorded information to be exchanged by                      формальное описание семантики записанной
Open-edi Parties playing roles in an Open-edi                информации для обмена в процессе Open-edi
scenario                                                     сторонами, играющими роли по сценарию Open-
                                                             edi
[ISO/IEC 14662:2004 (3.11)]
                                                             [ISO/IEC 14662:2004 (3.11)]

3.108                                                        3.108
Information Processing Domain (IPD)                          Домен Обработки Информации
Information Technology System which
includes at least either a Decision Making                   Система Информационных Технологий, которая
Application (DMA) and/or one of the                          включает по крайней мере Приложение Принятия
components of an Open-edi Support                            Решений       (DMA)      и/или     компоненты
Infrastructure, and acts/executes on behalf of               Инфраструктуры      Поддержки     Open-edi  и
an Open-edi Party (either directly or under a                функционирует/выполняет от имени одной из
delegated authority)                                         Сторон Open-edi (или непосредственно или в
                                                             рамках делегированных полномочий)
[ISO/IEC 14662:2004 (3.12)]
                                                             [ISO/IEC 14662:2004 (3.12)]
3.109                                                        3.109
Information Technology System (IT System)                    Система    Информационных          Технологий   (IT
set of one or more computers, associated                     Система)
software, peripherals, terminals, human
operations, physical processes, information                  Набор из одного или более компьютеров,
transfer means, that form an autonomous                      системного       программного      обеспечения,
whole, capable of performing information                     периферийных устройств, операций, выполняемых
processing and/or information transfer                       людьми, физических процессов, средств передачи
                                                             информации,    который   образует   автономный
[ISO/IEC 14662:2004 (3.13)]                                  комплекс,   способный    выполнять    обработку
                                                             информации и/или передачу информации

                                                             [ISO/IEC 14662:2004 (3.13)]


                                                                                                        70
                  ISO English                       Gender                       ISO Russian
                        (1)                          (2)                                (3)
3.110                                                        3.110
internal constraint                                          внутреннее ограничение
constraint which forms part of the
commitment(s) mutually agreed to among the                   ограничение,     которое    формирует     часть
parties to a business transaction                            обязательств,      совместно     согласованных
                                                             сторонами в бизнес транзакции
NOTE Internal constraints are self-imposed.
They provide a simplified view for modelling and             ПРИМЕЧАНИЕ Внутренние ограничения являются
re-use of scenario components of a business                  обязательствами,    добровольно возложенными
transaction for which there are no external                  сторонами на самих себя. Они обеспечивают
constraints or restrictions to the nature of the             упрощенную ситуацию для моделирования и
conduct of a business transaction other than                 повторного использования компонентов сценария
those mutually agreed to by the buyer and                    бизнес транзакции, для которой не существует
seller.                                                      внешних     ограничений    или     ограничений,
                                                             наложенных    природой   выполняемой     бизнес
[ISO/IEC 15944-1:2002 (3.33)]                                транзакции.   Имеются    только    ограничения,
                                                             согласованные между покупателем и продавцом.

                                                             [ISO/IEC 15944-1:2002 (3.33)]

3.111                                                        3.111
International Registration Business Object                   Идентификатор    Бизнес      Объекта         для
Identifier (IRBOI)                                           Международной Регистрации (IRBOI)
internationally unique identifier for an OeRI
                                                             Международно уникальный идентификатор для
NOTE IRBOIs are of the nature of a composite                 OeRI
identifier.
                                                             ПРИМЕЧАНИЕ Идентификаторы IRBOI по своей
[ISO/IEC 15944-2:2006 (3.42)]                                природе являются составными.

                                                             [ISO/IEC 15944-2:2006 (3.42)]

3.112                                                        3.112
International Standard Identifier                            Идентификатор Международного Стадарта
identifier of the version of this part of ISO/IEC
15944 upon which attributes are based                        Идентификатор версии этой части ISO/IEC 15944,
                                                             на которой базируются атрибуты
[ISO/IEC 15944-2:2006 (3.43)]
                                                             [ISO/IEC 15944-2:2006 (3.43)]

3.113                                                        3.113
item class                                                   класс предметов
set of items with common properties
                                                             набор предметов с общим свойствами
NOTE Class is used in this context to refer to a
set of instances, not the concept abstracted                 ПРИМЕЧАНИЕ Класс используется в таком
from that set of instances.                                  контексте, чтобы сослаться на набор экземпляров,
                                                             а не как понятие , абстрактное для этого набора
[ISO 19135:2005 (4.1.6)]                                     экземпляров

                                                             [ISO 19135:2005 (4.1.6)]

3.114                                                        3.114
IT-enablement                                                использование возможностей IT
                                                                                                     71
                   ISO English                        Gender                      ISO Russian
                        (1)                            (2)                              (3)

transformation of a current standard utilized in
business transactions, (e.g., coded                            преобразование        текущего      стандарта,
domains), from a manual to computational                       используемого в бизнес транзакциях ( например,
perspective so as to be able to support                        закодированные домены) из ручной формы в
commitment exchange and computational                          компьютерную     так,   чтобы    можно    было
integrity                                                      поддерживать    обмен     обязательствами    и
                                                               вычислительную целостность
[ISO/IEC 15944-5:2006]
                                                               [ISO/IEC 15944-5:2006]

3.115                                                          3.115
IT interface equivalent                                        эквивалент IT интерфейса
computer processable identification of the
unambiguous semantics of a scenario,                           выполняемая     компьютером    идентификация
scenario attribute and/or scenario                             однозначной семантики сценария, атрибута
component(s) pertaining to a commitment                        сценария    и/или    компонентов    сценария,
exchange in a business transaction which                       относящихся к обмену обязательствами в бизнес
supports computational integrity                               транзакции,        которая       поддерживает
                                                               вычислительную целостность
NOTE 1 IT interface equivalents have the
properties of identifiers (in business transaction)            ПРИМЕЧАНИЕ 1 Эквиваленты IT интерфейса
and are utilized to support semantic                           обладают свойствами идентификаторов (в бизнес
interoperability in commitment exchange.                       транзакции) и используются для поддержки
                                                               семантического взаимодействия при обмене
NOTE 2 The value of an IT interface equivalent                 обязательствами.
at times is a composite identifier.
                                                               ПРИМЕЧАНИЕ 2 Иногда эквивалент IT интерфейса
NOTE 3 An IT interface equivalent as a                         представляет собой составной идентификатор
composite identifier can consist of the identifier
of a coded domain plus an ID code of that                      ПРИМЕЧАНИЕ 3 Эквивалент IT интерфейса как
coded domain.                                                  оставной идентификатор может состоять из
                                                               идентификатора домена кодов плюс код ID этого
NOTE 4 An IT interface equivalent is at times
                                                               домена кодов.
utilized as a semantic identifier.

NOTE 5 An IT interface equivalent may have                     ПРИМЕЧАНИЕ 4        Эквивалент IT интерфейса
associated with it one or more Human Interface                 иногда    используется    как   семантический
Equivalents (HIEs).                                            идентификатор.

NOTE 6 The value of an IT Interface is                         ПРИМЕЧАНИЕ 5 Эквивалент IT интерфейса может
independent of its encoding in programming                     быть связан с одним или более эквивалентом
languages or APIs.                                             человеко-машинного интерфейса (HIE).
[ISO/IEC 15944-2:2006 (3.48)]
                                                               ПРИМЕЧАНИЕ 6 Значение эквивалента IT
                                                               интерфейса не зависит от способа его кодирования
                                                               в языках программирования или API.


                                                               [ISO/IEC 15944-2:2006 (3.48)]




3.116                                                          3.116
jurisdictional domain                                          юридический домен
jurisdiction, recognized in law as a distinct legal

                                                                                                       72
                   ISO English                       Gender                     ISO Russian
                        (1)                           (2)                            (3)
and/or regulatory framework, which is a source                Юрисдикция,    признаваемая      законом  как
of external constraints on Persons, their                     определенная правовая или нормативная основа,
behaviour and the making of commitments                       являющаяся источником внешних ограничений,
among Persons including any aspect of a                       накладываемых на лиц, их поведение          и
business transaction                                          выполнение обязательств перед другими лицами,
                                                              включая любые аспекты бизнес транзакций.
NOTE 1 The pivot jurisdictional domain is a
United Nations (UN) recognized member state.                  ПРИМЕЧАНИЕ 1 Главным видом юридического
From a legal and sovereignty perspective they                 домена    является     территория,     являющаяся
are considered "peer" entities. Each UN                       признанным членом       ООН. С правовой точки
member state, (a.k.a. country) may have sub-                  зрения, с точки зрения суверенитета такие
administrative divisions as recognized                        территории рассматриваются как равноправные
jurisdictional domains, (e.g., provinces,                     сущности. Каждое государство,          являющееся
territories, cantons, länder, etc.), as decided by            членом ООН        (известное также под названием
that UN member state.                                         страна)    может      иметь     административно-
                                                              территориальное деление, включая в себя
NOTE 2 Jurisdictional domains can combine to                  различные юридические домены (провинции,
form new jurisdictional domains, (e.g., through               территории, кантоны, земли и т.д.), как определено
bilateral, multilateral and/or international                  этим государством-членом ООН.
treaties).

EXAMPLE Included here, for example, are the                   ПРИМЕЧАНИЕ 2 Юридические домены могут
European Union (EU), NAFTA, WTO, WCO,                         объединяться, формируя новые юридические
ICAO, WHO, Red Cross, the ISO, the IEC, the                   домены (например, посредством двусторонних,
ITU, etc.                                                     многосторонних и/или международных договоров.

NOTE 3 Several levels and categories of                       ПРИМЕРЫ: Европейский Союз (ЕС),        NAFTA (
jurisdictional domains may exist within a                     Североамериканское Соглашение о Свободной
jurisdictional domain.                                        торговле), ВТО (Всемирная Торговая Организация),
                                                              ВТС (Всемирный Таможенный Союз), ICAO
NOTE 4 A jurisdictional domain may impact                     (Международная     Организация    по   Вопросам
aspects of the commitment(s) made as part of a                Гражданской      Авиации),   ВОЗ     (Всемирная
business transaction including those pertaining               Организация Здравоохранения), Красный Крест,
to the making, selling, transfer of goods,                    ISO     (Международная       Организация     по
services and/or rights (and resulting liabilities)            Стандартизации),       МЭК      (Международная
and associated information. This is independent               Электротехническая       Комиссия),         ITU
of whether such interchange of commitments                    (Международный Союз Электросвязи) и т.д.
are conducted on a for-profit or not-for-profit
basis and/or include monetary values.                         ПРИМЕЧАНИЕ 3 В пределах любого юридического
                                                              домена может существовать несколько уровней и
NOTE 5 Laws, regulations, directives, etc.,                   категорий других юридических доменов.
issued by a jurisdictional domain are considered
as parts of that jurisdictional domain and are the            ПРИМЕЧАНИЕ 4 Юридический домен может влиять
primary sources of external constraints on                    на обязательство(а), взятые как часть выполнения
business transactions.                                        бизнес транзакции, включая те, которые связаны с
[ISO/IEC 15944-5:2006 (3.67)]                                 производством, продажей, передачей товаров,
                                                              услуг и/или прав (и вытекающих из них
                                                              обязательств) и сопровождающей информации.
                                                              Это не зависит от того, выполняется ли такой
                                                              обмен обязательствами на коммерческой или
                                                              некоммерческой основе и включает ли он
                                                              денежные ресурсы.

                                                              ПРИМЕЧАНИЕ 5 Законы, регламенты, директивы и
                                                              т.д.,  выпускаемые    юридическим    доменом,
                                                              рассматриваются как составные компоненты этого

                                                                                                        73
                 ISO English                      Gender                       ISO Russian
                         (1)                       (2)                              (3)
                                                           домена и являются первичными источниками для
                                                           формирования внешних ограничений на бизнес
                                                           транзакции.

                                                           . [ISO/IEC 15944-5:2006 (3.67)]


3.117                                                      3.117
jurisdictional domain identifier                           идентификатор юридического домена
ID code of a jurisdictional domain as
recognized for use by peer jurisdictional                  код ID юридического домена, признанный для
domains within a system of mutual recognition              использования равноправными юридическими
                                                           доменами в пределах системы взаимного
[ISO/IEC 15944-2:2006 (3.47)]                              признания


                                                           [ISO/IEC 15944-2:2006 (3.47)]

3.118                                                      3.118
language                                                   язык
system of signs for communication, usually
consisting of a vocabulary and rules                       система знаков, обычно состоящая из словаря и
                                                           правил
NOTE In this standard, language refers to
natural languages or special languages, but not            ПРИМЕЧАНИЕ В этом стандарте термин «язык»
"programming languages" or "artificial                     применяется   к    естественным    языкам     и
languages".                                                специальным   языкам,    но   не   к   «языкам
                                                           программирования» или «искусственным языкам».
[ISO 5127-1:2001 (1.1.2.01)]
                                                           [ISO 5127-1:2001 (1.1.2.01)]

3.119                                                      3.119
language code                                              код языка
combination of characters used to represent a
language or languages                                      комбинация    символов,    используемая     для
                                                           представления языка или языков
NOTE In this multipart ISO/IEC 15944 standard,
the ISO 639-2/T (terminology) three alpha-code,            ПРИМЕЧАНИЕ В этом стандарте ISO/IEC 15944,
shall be used.                                             состоящем     из   нескольких    частей, будут
                                                           использованы три алфавитно-цифровых кода
[ISO 639-2:1998 (3.2)]                                     стандарта ISO 639-2/T (терминология)

                                                           [ISO 639-2:1998 (3.2)]

3.120                                                      3.120
legally recognized language (LRL)                          юридически признанный язык (LRL)
natural language which has status (other than
an official language (or de facto language) in             естественный язык, который имеет статус
a jurisdictional domain as stated in an act,               (отличающийся от официального языка или
regulation, or other legal instrument, which               языка де-факто)      в домене определенной
grants a community of people (or its                       юрисдикции как заявлено в акте, регламенте или
individuals) the right to use that natural                 другом   юридическом    инструменте,    который
language in the context stipulated by the legal            предоставляет сообществу людей (или конкретным
                                                           физическим     лицам)    право     использовать
                                                                                                  74
                  ISO English                        Gender                      ISO Russian
                       (1)                            (2)                             (3)
instrument(s)                                                 естественный язык в контексте, предусмотренном
                                                              юридическим инструментом (инструментами)
NOTE The LRL can be specified through either:
- the identification of a language by the name                ПРИМЕЧАНИЕ LRL может быть определен также
utilized; or,                                                 путем::
- the identification of a people and thus their               - идентификации языка по используемому
language(s).                                                  названию; или,
                                                              - идентификации людей и таким образом их
EXAMPLE In addition to acts and regulations,                  языка(ов)
legal instruments include self-government
agreements, land claim settlements, court                     ПРИМЕР В дополнение к законам и регламентам,
decisions, jurisprudence, etc.                                юридические инструменты включают соглашения
                                                              самоуправления,    урегулирования    претензий
[ISO/IEC 15944-5:2006 (3.71)]                                 государств, решения судов, судебную практику, и
                                                              т.д.

                                                              [ISO/IEC 15944-5:2006 (3.71)]

3.121                                                         3.121
legally recognized name (LRN)                                 юридически признанное название (LRN)
persona associated with a role of a Person
recognized as having legal status and so                      персона, выступающая в роли Лица, обладающего
recognized in a jurisdictional domain as                      правовым    статусом    как   признанного   в
accepted or assigned in compliance with the                   юридическом домене, либо назначенного в
rules applicable of that jurisdictional domain,               согласии с правилами, применимыми в этом
i.e. as governing the coded domain of which                   юридическом домене, то есть      управляющего
the LRN is a member                                           доменом кодов, элементом которого является
                                                              LRN
NOTE 1 A LRN may be of a general nature and
thus be available for general use in commitment
exchange or may arise from the application of a               ПРИМЕЧАНИЕ 1: LRN может иметь общее
particular law, regulation, program or service of             происхождение и таким образом быть доступным
a jurisdictional domain and thus will have a                  для    общего     использования    в    обмене
specified use in commitment exchange.                         обязательствами, или может явиться результатом
                                                              применения специфического закона, регламента,
NOTE 2 The process of establishment of a LRN                  программы или обслуживания в юридическом
is usually accompanied by the assignment of a                 домене и, таким образом, будет иметь указанное
unique identifier.                                            использование при обмене обязательствами.

NOTE 3 A LRN is usually a registry entry in a                 ПРИМЕЧАНИЕ 2 Процесс учреждения LRN обычно
register established by the jurisdictional domain             сопровождается  назначением     уникального
(usually by a specified public administration                 идентификатора
within that jurisdictional domain) for the purpose
of applying the applicable rules and registering              ПРИМЕЧАНИЕ 3 LRN – как правило, запись в
and recording LRNs (and possible                              реестре, установленном юридическим доменом
accompanying unique identifiers accordingly).                 (обычно специальной государственной службой в
                                                              пределах того юридического домена) с целью
NOTE 4 A Person may have more than one
                                                              применения правил и регистрации LRNs (и
LRN (and associated LRN identifier).
                                                              возможных      сопровождающих      уникальных
                                                              идентификаторов соответственно).
[ISO/IEC 15944-5:2006 (3.72)]
                                                              ПРИМЕЧАНИЕ 4 Лицо может иметь больше одного
                                                              LRN (и связанный идентификатор LRN).

                                                              [ISO/IEC 15944-5:2006 (3.72)]
                                                                                                     75
                   ISO English                        Gender                        ISO Russian
                        (1)                            (2)                               (3)
3.122                                                          3.122
list                                                           список

ordered set of data elements                                   упорядоченный набор элементов данных

[ISO/IEC 2382-4:1999 (04.08.01)]                               [ISO/IEC 2382-4:1999 (04.08.01)]

3.123                                                          3.123
localization                                                   локализация
pertaining to or concerned with anything that is
not global and is bound through specified sets                 имеющее отношение или свойственное чему-либо,
of constraints of:                                             что не глобально и связанное с указанными
                                                               наборами ограничений:
(a) a linguistic nature including natural and
special languages and associated multilingual                     (a) лингвистической     природы,      включая
requirements;                                                         естественные и специальные языки и
(b) jurisdictional nature, i.e., legal, regulatory,                   связанные многоязычные требования;
geopolitical, etc.;                                               (b) юридической природы, т.е. юридической,
(c) a sectorial nature, i.e., industry sector,                        регламентирующей, геополитической и т.д.
scientific, professional, etc.;                                   (c) отраслевой природы, т.е. связанные с
(d) a human rights nature, i.e., privacy,                             секторами промышленности, отраслями
disabled/handicapped persons, etc.;                                   науки, профессиями, и т.д.;
(e) consumer behaviour requirements; and/or                       (d) связанных с защитой прав человека, то
(f) safety or health requirements.                                    есть, неприкосновенность частной жизни,
                                                                      защита прав людей с ограниченными
Within and among "locales", interoperability and                      физическими возможностями и т.д.;
harmonization objectives also apply                               (e) требования к защите прав потребителя;
                                                                  (f) требования    безопасности   и     охраны
[ISO/IEC 15944-5:2006 (3.75)]                                         здоровья
                                                               В пределах и среди "мест действия", также
                                                               применяются способность к взаимодействию и
                                                               гармонизации

                                                               [ISO/IEC 15944-5:2006 (3.75)]
3.124                                                          3.124
location                                                       местоположение
place, either physical or electronic, that can be
defined as an address                                          Место, физическое или электронное,      которое
                                                               может быть определено как адрес

[ISO/IEC 15944-2:2006 (3.50)]
                                                               [ISO/IEC 15944-2:2006 (3.50)]
3.125                                                          3.125
location type                                                  тип местоположения
abstract specification of a business location                  абстрактная   спецификация   местоположения
where its grouped properties can be designated                 бизнеса таким образом что его сгруппированные
without attachment to an actual location                       свойства могут быть определены без привязки к
                                                               фактическому местоположению
NOTE An example location type might be an
accepted shipping facility or approved hospital                ПРИМЕЧАНИЕ Пример типа местоположения может
location                                                       представлять собой принятое средство доставки
[ISO/IEC 15944-4:2006 (3.39)]                                  или одобренное местоположение больницы

                                                               [ISO/IEC, 15944-4:2006 (3.39)]
                                                                                                       76
                  ISO English                         Gender                        ISO Russian
                        (1)                            (2)                               (3)


3.126                                                          3.126
materialized                                                   материализация
association between an economic event and
                                                               ассоциации между экономическим событием и
an economic claim where the occurrence of
                                                               экономическим требованием, где наличие
the economic event causes the economic                         экономического события вызывает появление
claim to come into existence                                   экономического требования
[ISO/IEC 15944-4:2006 (3.40)]
                                                               [ISO/IEC, 15944-4:2006 (3.40)]

3.127                                                          3.127
mediated transaction                                           опосредованная транзакция
sub-type of a business transaction where a
third party mediates between the partners as
                                                               подтип бизнес транзакции, когда третья сторона
mutually agreed to by the partners                             есть взаимно согласованный между партнерами
[ISO/IEC 15944-4:2006 (3.41)]                                  посредник


                                                               [ISO/IEC 15944-4:2006 (3.41)]

3.128                                                          3.128
medium                                                         Среда
physical material which serves as a functional
                                                               физические         материалы,         служащие
unit, in or on which information or data is
                                                               функциональным модулем, неразрушающимся в
normally recorded, in which information or data                природе, при помощи которого информация или
can be retained and carried, from which                        данные обычно регистрируются, могут быть
information or data can be retrieved, and                      сохранены и перенесены, или могут быть найдены.
which is non-volatile in nature
                                                               ПРИМЕЧАНИЕ 1 Это определение не зависит от
NOTE 1 This definition is independent of the                   характера материала, при помощи которого
material nature on which the information is                    информация       записана,     и/или     технологии,
recorded and/or technology utilized to record the              использующейся        для    записи     информации
information, (e.g., paper, photographic,                       (например,    на     бумаге,   пленке,(химической),
(chemical), magnetic, optical, ICs (integrated                 магнитной ленте, оптический, ICs (интегральные
circuits), as well as other categories no longer in            схемы), так же как другие категории,              не
common use such as vellum, parchment (and                      используемые в широком профиле, такие как
other animal skins), plastics, (e.g., bakelite or              пергамент,        (и   другие    кожи    животных),
vinyl), textiles, (e.g., linen, canvas), metals,               пластмассы, (например, бакелитовая мастика или
etc.).                                                         винил), текстиль, (например, полотно, холст),
                                                               металлы, и т.д.), .
NOTE 2 The inclusion of the "non-volatile in
nature" attribute is to cover latency and records              ПРИМЕЧАНИЕ      2    Назначение   атрибута
retention requirements.                                        "неразрушающийся в природе" – покрыть срок
                                                               службы, к которому актуальность информации
NOTE 3 This definition of "medium" is                          будет утеряна.
independent of: i)form or format of recorded
information; ii)physical dimension and/or size;                ПРИМЕЧАНИЕ 3        Это   определение   “среды”
and, iii)any container or housing that is                      независимо от: i) формы или формата записанной
physically separate from material being housed                 информации; ii) физической размерности и/или
and without which the medium can remain a                      размера; и, iii) любого контейнера или блока,
functional unit.                                               который является физически отделенным от
                                                               размещаемого     материала,   и  без   которого
NOTE 4 This definition of "medium" also                        поддержка может остаться функциональным
                                                               модулем.
                                                                                                           77
                   ISO English                        Gender                        ISO Russian
                         (1)                           (2)                               (3)
captures and integrates the following key
properties: i) the property of medium as a                     ПРИМЕЧАНИЕ 4 Это определение “среды” также
material in or on which information or data can                фиксирует и интегрирует следующие ключевые
be recorded and retrieved; ii) the property of                 свойства: i) свойство среды как материала, в
storage; iii) the property of physical carrier; iv)            котором информация или данные могут быть
the property of physical manifestation, i.e.,                  записаны и найдены; ii) свойство памяти; iii)
material; v) the property of a functional unit;                свойство физического носителя; iv) свойство
and, vi) the property of (some degree of)                      физического проявления, т.е., материальные
                                                               свойства ; v) свойство функционального модуля;
stability of the material in or on which the
                                                               и,   vi)  с войство  (в    некоторой   степени)
information or data is recorded.
                                                               стабильности материала, при использовании
                                                               которого информация или данные были записаны.
[ISO/IEC 15944-1:2002 (3.34)]

                                                               [ISO/IEC, 15944-1:2002 (3.34)]

3.129                                                          3.129
metadata                                                       метаданные

data about data elements, including their data                 данные об элементах данных, которые включают в
descriptions, and data about data ownership,                   себя описания данных, информацию о владельце,
access paths, access rights and data volatility                пути доступа, правах доступа и изменчивости
                                                               данных
[ISO/IEC 2382-17:1999 (17.06.05)]
                                                               [ISO/IEC 2382-17:1999 (17.06.05)]

3.130                                                          3.130
metadata entity                                                сущность метаданных
set of metadata elements describing the same
aspect of data                                                 набор элементов метаданных, описывающих один
                                                               и тот же аспект данных
NOTE 1 May contain one or more metadata
entities.                                                      ПРИМЕЧАНИЕ 1 Может заключать в себе одну или
                                                               несколько сущностей метаданных.
NOTE 2 Equivalent to a class in UML
terminology.                                                   ПРИМЕЧАНИЕ 2 Является эквивалентом классу в
[ISO 19115:2003 (4.7)]                                         терминологии UML.

                                                               [ISO 19115:2003 (4.7)]
3.131                                                          3.131
metadata section                                               раздел метаданных
subset of metadata which consists of a
collection of related metadata entities and                    подмножество метаданных, состоящее из набора
metadata elements                                              связанных сущностей метаданных и элементов
                                                               метаданных
[ISO 19115:2003 (4.8)]
                                                               [ISO 19115:2003 (4.8)]




3.132                                                          3.132
model                                                          модель
abstraction of some aspect of reality
                                                               абстракция некоторого аспекта действительности
[ISO 19115:2003 (4.9)]
                                                                                                       78
                   ISO English                       Gender                       ISO Russian
                        (1)                           (2)                              (3)


                                                              [ISO 19115:2003 (4.9)]
3.133                                                         3.133
multilateral treaty                                           многосторонний международный договор
treaty (or convention) that has the ambition to
become universal (or near universal) and thus                 международный договор (или конвенция) это
bind most of the international community by                   договор, который претендует на то, чтобы стать
declaring general rules of law                                общепринятым (или почти общепринятым) и таким
                                                              образом связать большинство международного
EXAMPLE Law of the Sea, Law on Genocide.                      сообщества путем декларирования общих правил
                                                              законодательства
NOTE 1 A multilateral treaty may have the goal
of creating a regulatory regime of law for a                  ПРИМЕР Морское право, Закон о геноциде
particular area or major multilateral institution,
i.e., Agreement Establishing the WTO, Kyoto                   ПРИМЕЧАНИЕ 1 Многосторонний международный
Protocol, Safety of Life at Sea Convention.                   договор может иметь целью создание режима
                                                              регулирования права для специальных областей
NOTE 2 A multilateral treaty may allow for                    или большинства многосторонних институтов,
reservations or the treaty may be subject to                  например, Соглашение об учреждении ВТО,
many amendments which do not bind all parties                 Киотский протокол, Безопасность жизни в Морской
or require all parties to undertake the same legal            Конвенции.
obligations, (e.g., the Berne and Paris
conventions).                                                 ПРИМЕЧАНИЕ 2 Многосторонний международный
                                                              договор может предусматривать оговорки или
[ISO/IEC 15944-5:2006 (3.81)]                                 подвергаться многим поправкам, которые не
                                                              связывают все стороны или не требуют, чтобы все
                                                              стороны выполняли те же самые правовые
                                                              обязательства (например, Бернская и Парижская
                                                              конвенции).


                                                              [ISO/IEC 15944-5:2006 (3.81)]

3.134                                                         3.134
multilingualism                                               многоязычие
ability to support not only character sets
specific to a (natural) language (or family of                способность поддерживать не только набор
languages) and associated rules but also                      символов, характерный для (натурального) языка
localization requirements, i.e., use of a                     (или семейства языков), и необходимые правила,
language from jurisdictional domain, sectoral                 но и требования локализации, т.е. использование
and/or consumer marketplace perspectives                      языка из юридического домена, учет перспектив
                                                              конкретных секторов бизнеса и потребительского
                                                              рынка
[ISO/IEC 15944-5:2006 (3.82)]
                                                              [ISO/IEC 15944-5:2006 (3.82)]

3.135                                                         3.135
name                                                          имя
designation of an object by a linguistic
expression                                                    присвоение объекту лингвистического выражения

[ISO 5217:2000 (1.1.2.02)]                                    [ISO 5217:2000 (1.1.2.02)]


                                                                                                       79
                  ISO English                       Gender                       ISO Russian
                       (1)                           (2)                                 (3)
3.136                                                        3.136
natural language                                             естественный язык
language which is or was in active use in a
community of people, and the rules of which are              язык, который находится (находился) в активном
mainly deduced from the usage                                использовании в некотором сообществе людей, и
                                                             правила этого языка в основном сформированы на
[ISO 5217:2000 (1.1.2.02)]                                   основе его практического использования

                                                             [ISO 5217:2000 (1.1.2.02)]


3.137                                                        3.137
object                                                       объект
anything perceivable or conceivable
                                                             нечто воспринимаемое или понимаемое
NOTE Objects may be material, (e.g., engine, a
sheet of paper, a diamond), or immaterial, (e.g.,            ПРИМЕЧАНИЕ        Объекты       могут    быть
conversion ratio, a project play) or imagined,               материальными   (Например,    двигатель, лист
(e.g., a unicorn).                                           бумаги, алмаз), интеллектуальными (например,
                                                             коэффициент перевода, проектируемая операция)
[ISO 1087-1:2000 (3.1.1)]                                    или воображаемыми (например, единорог)

                                                             [ISO 1087-1:2000 (3.1.1)]




3.138                                                        3.138
object class                                                 класс объекта
set of ideas, abstractions, or things in the real
world that can be identified with explicit                   набор идей, абстракций или предметов из
boundaries and meaning and whose properties                  реального мира, которые имеют явные границы и
and behavior follow the same rules                           значение, и чьи        свойства и поведения
                                                             подчиняются одним правилам

[ISO/IEC 11179-1:2004 (3.3.22)]                              [ISO/IEC 11179-1:2004 (3.3.22)]

3.139                                                        3.139
OeRI addition                                                дополнение OeRI
insertion into a register of an OeRI that
describes a concept not described by an OeRI                 Вставка в реестр OeRI, описывающая понятие, не
already in the register                                      раскрытое еще OeRI в этом реестре

[ISO/IEC 15944-2:2006 (3.54)]                                [ISO/IEC 15944-2:2006 (3.54)]


3.140                                                        3.140
OeRI clarification                                           уточнение OeRI
non-substantive change to an OeRI
                                                             Несущественное изменение в OeRI
NOTE 1 A non-substantive change does not
change the semantics or technical meaning of                 ПРИМЕЧАНИЕ 1        Несущественное не меняет
the OeRI.                                                    семантики или технического значения OeRI.


                                                                                                    80
                    ISO English                        Gender                      ISO Russian
                         (1)                            (2)                             (3)

NOTE 2 A clarification does not result in a                     ПРИМЕЧАНИЕ 2        Разъяснение не влияет на
change to the registration status of the OeRI.                  изменение статуса регистрации OeRI.

[ISO/IEC 15944-2:2006 (3.55)]                                   [ISO/IEC 15944-2:2006 (3.55)]
3.141                                                           3.141
OeRI harmonization                                              гармонизация OeRI
the resolution of any potential duplicate or
overlapping of OeRIs, accounting for justifiable                Разрешение        ситуации      потенциального
differences that may exist among the                            дублирования или частичного совпадения OeRI,
harmonized OeRIs                                                учет допустимых различий, которые         могут
                                                                существовать среди гармонизированных OeRI
[ISO/IEC 15944-2:2006 (3.56)]
                                                                ISO/IEC 15944-2:2006 (3.56)]
3.142                                                           3.142
OeRI language code                                              языковой код OeRI
language code of the language used for the
OeRI by the submitting organization                             Языковой код или язык, используемый для OeRI
                                                                организацией, представляющей информацию
[ISO/IEC 15944-2:2006 (3.57)]
                                                                [ISO/IEC 15944-2:2006 (3.57)]




3.143                                                           3.143
OeRI retirement                                                 объявление недействительным OeRI
declaration that an OeRI is no longer suitable for
use in the production of new data                               Сообщение о том, что OeRI более не годится для
                                                                использования в производстве новых данных.
NOTE The status of the retired OeRI changes                     ПРИМЕЧАНИЕ. Статус OeRI изменяется с
from ‘valid’ to ‘retired’. A retired OeRI is kept in            «действительный» на         «недействительный».
the register to support the interpretation of data              Недействительный OeRI содержится в реестре,
produced before its retirement.                                 чтобы поддерживать интерпретацию данных,
                                                                произведенных       до      объявления      его
[ISO/IEC 15944-2:2006 (3.58)]                                   недействительным.

                                                                [ISO/IEC 15944-2:2006 (3.58)]

3.144                                                           3.144
OeRI supersession                                               замена OeRI
replacement of an OeRI by one or more new
OeRIs                                                           Замена OeRI одним или несколькими новыми OeRI

NOTE The status of the replaced item changes                    ПРИМЕЧАНИЕ Статус замененного сообщения
from "valid" to "superseded".                                   меняется с «действительный» на «замененный».
[ISO/IEC 15944-2:2006 (3.59)]                                   [ISO/IEC 15944-2:2006 (3.59)]

3.145                                                           3.145
official language                                               официальный язык
external constraint in the form of a natural
language specified by a jurisdictional domain                   внешнее ограничение в форме естественного
for official use by Persons forming part of                     языка, определенного юридическим доменом
and/or subject to that jurisdictional domain for                для   официального  использования Лицами,

                                                                                                       81
                  ISO English                         Gender                     ISO Russian
                        (1)                            (2)                            (3)
use in communication(s) either                                 формирующими часть субъекта или субъект этого
(1) within that jurisdictional domain; and/or,                 юридического домена для использования в
(2) among such Persons, where such                             коммуникации (коммуникациях):
communications are recorded information
involving commitment(s)                                           (1) в пределах этого юридического домена;
                                                                      и/или
NOTE 1 Unless official language requirements                      (2) среди    таких   Лиц,   которые   при
state otherwise, Persons are free to choose                           коммуникациях используют записанную
their mutually acceptable natural language                            информацию, включающую обязательства
and/or special language for communications as
well as exchange of commitments.                               ПРИМЕЧАНИЕ 1 До тех пор , пока в требованиях к
                                                               официальному языку не будет заявлено иное, Лица
NOTE 2 A jurisdictional domain decides whether                 свободны в выборе их взаимно приемлемых
or not it has an official language. If not, it will            естественных языков и/или специальных языков
have a de facto language.                                      для связи, также как для обмена обязательствами.
NOTE 3 An official language(s) can be
mandated for formal communications as well as                  ПРИМЕЧАНИЕ 2 Юридический домен решает,
provision of goods and services to Persons                     будет ли он иметь официальный язык. Если нет, то
subject to that jurisdictional domain and for use              он будет иметь язык де-факто.
in the legal and other conflict resolution
system(s) of that jurisdictional domain, etc.                  ПРИМЕЧАНИЕ 3 Официальный язык (языки)
                                                               может быть санкционирован для формальной
NOTE 4 Where applicable, use of an official                    связи, также как для обеспечения товарами и
language may be required in the exercise of                    услугами Лиц, действующих в рамках юридического
rights and obligations of individuals in that                  домена и для использования в системах
jurisdictional domain.                                         разрешения правовых и других конфликтов этого
                                                               домена и т.д.
NOTE 5 Where an official language of a
jurisdictional domain has a controlled                         ПРИМЕЧАНИЕ 4 Использование официального
vocabulary of the nature of a terminology, it may              языка, если он применим, может потребоваться
well have the characteristics of a special                     при реализации прав и обязанностей физических
language. In such cases, the terminology to be                 лиц в этом юридическом домене.
used must be specified.
                                                               ПРИМЕЧАНИЕ 5        Когда официальный язык
NOTE 6 For an official language, the writing                   юридического домена имеет управляемый словарь
system(s) to be used shall be specified, where                 происхождения терминологии, он, вероятно, может
the spoken use of a natural language has more                  иметь свойства специального языка. В таких
than one writing system.                                       случаях используемая терминология должна быть
                                                               определена.
EXAMPLE 1 The spoken language of use of an
official language may at times have more than
                                                               ПРИМЕЧАНИЕ 6 Для официального языка должны
one writing system. For example, three writing
                                                               быть определены правила письменного языка, если
systems exist for the Inuktitut language. Canada
                                                               устному использованию естественного языка
uses two of these writing systems, namely, a
                                                               соответствует более чем одна система написания.
Latin-1 based (Roman), the other is syllabic-
based. The third is used in Russia and is Cyrillic
                                                               ПРИМЕР      1   Устная     речь,   использующая
based.
                                                               официальный язык, может иногда иметь более чем
EXAMPLE 2 Another example is that of Norway                    одну систему написания. Например, три системы
which has two official writing systems, both                   написания существуют для языка Инуктикут.
Latin-1 based, namely, Bokmål (Dano-                           Канада использует две из этих систем написания, а
Norwegian) and Nynorsk (New Norwegian).                        именно: одна – романская, основанная на т.н.
                                                               Латинице-1, другая – на силлабической основе.
NOTE 7 A jurisdictional domain may have more                   Третья система используется в России и основана
than one official language but these may or may                на кириллице.
not have equal status.

                                                                                                        82
                  ISO English                      Gender                      ISO Russian
                       (1)                          (2)                             (3)

EXAMPLE Canada has two official languages,                  ПРИМЕР 2 Другой пример – норвежский язык,
Switzerland has three, while the Union of South             использующий 2 системы написания, обе основаны
Africa has eleven official languages.                       на Латинице-1.

NOTE 8 The BOV requirement of the use of a                  ПРИМЕЧАНИЕ 7 Юридический домен может иметь
specified language will place that requirement              более одного официального языка, которые могут
on any FSV supporting service.                              иметь, а могут не иметь одинаковый статус.

EXAMPLE A BOV requirement of Arabic,                        ПРИМЕР Канада имеет два официальных языка,
Chinese, Russian, Japanese, Korean, etc., as                Швейцария – 3, а Южно-Африканский Союз имеет
an official language requires the FSV support               11 официальных языков.
service to be able to handle the associated
character sets.                                             ПРИМЕЧАНИЕ 8 Требования BOV в арабском,
                                                            китайском, русском, японском, корейском и др.
[ISO/IEC 15944-5:2006 (3.87)]                               языках вызывают необходимость поддержки FSV
                                                            сервиса для управления связанными наборами
                                                            символов.

                                                            [ISO/IEC 15944-5:2006 (3.87)]

3.146                                                       3.146
Open-edi                                                    Открытая   система        электронного   обмена
                                                            данными (Open-edi)
electronic data interchange among multiple
autonomous Persons to accomplish an explicit                электронный обмен данными между многими
shared business goal according to Open-edi                  Лицами     с   целью   достижения   взаимно
standards                                                   согласованной бизнес цели в соответствии со
                                                            стандартами Open-edi
[ISO/IEC 14662:2004 (3.14)]
                                                            [ISO/IEC 14662:2004 (3.14)]
3.147                                                       3.147
Open-edi Business Transaction Ontology                      Онтология Бизнес Транзакции Open-edi (OeBTO)
(OeBTO)
formal, rule-based, specification and definition            Формальные,     основанные   на     правилах,
of the concepts pertaining to business                      спецификация и определение понятий, имеющих
transactions and scenarios and the                          отношение к бизнес транзакции и к сценариям и
relationships that hold among these concepts                связи между этими понятиями

[ISO/IEC 15944-4:2006 (3.44)]                               [ISO/IEC 15944-4:2006 (3.44)]

3.148                                                       3.148
Open-edi configuration                                      конфигурация Open-edi
formal specification of an operational
configuration of Open-edi Parties and their                 формальная    спецификация   эксплуатационной
associated IPDs, which can execute Open-edi                 конфигурации Сторон Open-edi и связанных с
transactions corresponding to a given Open-                 ними IPD, которые могут выполнять транзакции,
edi scenario                                                соответствующие данному сценарию Open-edi

[ISO/IEC 14662:2004 (3.15)]                                 [ISO/IEC 14662:2004 (3.15)]
3.149                                                       3.149
Open-edi Description Technique (OeDT)                       Метод Описания Open-edi (OeDT)
specification method such as a Formal
Description Technique, another methodology                  Метод  спецификации,  такой  как   Метод
                                                            Формального Описания, другая методология,
                                                                                                     83
                  ISO English                        Gender                      ISO Russian
                       (1)                            (2)                             (3)
having the characteristics of a Formal                        имеющая    свойства    Метода   Формального
Description Technique, or a combination of                    Описания, или комбинация таких методов, как
such techniques as needed to formally specify                 необходимо для формального описания понятий
BOV concepts, in a computer processable form                  BOV,    в    форме,    приспособленной  для
[ISO/IEC 14662:2004 (3.16)]                                   компьютерной обработки

                                                              [ISO/IEC 14662:2004 (3.16)]


3.150                                                         3.150
Open-edi disposition                                          распоряжение Open-edi
process governing the implementation of                       Процесс, управляющий реализацией формально
formally approved records retention, destruction              одобренных указаний о сохранении, уничтожении
(or expungement) or transfer of recorded                      или передаче записанной информации под
information under the control of a Person                     управлением Лица, которое документально
which are documented in disposition authorities               оформлено распорядительной властью или
or similar instruments                                        другими органами

[adapted from ISO 15489-1:2001 (3.9)]                         [адаптировано из ISO 15489-1:2001 (3.9)]
[ISO/IEC 15944-5:2006 (3.90)]                                 [ISO/IEC 15944-5:2006 (3.90)]

3.151                                                         3.151
Open-edi Party (OeP)                                          Сторона Open-edi (OeP)
Person that participates in Open-edi
                                                              Лицо, которое участвует в Open-edi
NOTE Often referred to generically in this, and
other e-business standards, (e.g., parts of the               ПРИМЕЧАНИЕ Типичный вариант ссылки на
ISO/IEC 15944 multipart “e-business” standard)                термины «Сторона» или «Стороны» в этом и других
as “party” or “parties” for any entity modelled as            е-бизнес стандартах (например, стандарт ISO/IEC
a Person as playing a role in Open-edi                        15944) для любой сущности, моделируемой как
scenarios.                                                    Лицо, играющее роль в сценариях Open-edi
[ISO/IEC 14662:2004 (3.17)]
                                                              [ISO/IEC 14662:2004 (3.17)]

3.152                                                         3.152
Open-edi Record Retention (OeRR)                              Сохранение записи Open-edi (OeRR)
specification of a period of time that a set of
recorded information must be kept by a                        Спецификация периода времени, в течение
Person in order to meet operational, legal,                   которого набор записанной информации должен
regulatory, fiscal or other requirements as                   сохраняться Лицом, для того чтобы выполнить
specified in the external constraints (or                     операционные,      правовые,    регламентные,
internal constraints) applicable to a Person                  налоговые       и      другие      требования,
who is a party to a business transaction                      специфицированные во внешних ограничениях
                                                              (или внутренних ограничениях), применимых к
[ISO/IEC 15944-5:2006 (3.92)]                                 Лицу, являющемуся стороной бизнес транзакции

                                                              [ISO/IEC 15944-5:2006 (3.92)]
3.153                                                         3.153
Open-edi register                                             регистр Open-edi
information store or database maintained by an
Open-edi Registry                                             накопитель информации или база             данных,
                                                              поддерживаемые Реестром Open-edi

                                                                                                         84
                  ISO English                     Gender                      ISO Russian
                       (1)                         (2)                             (3)
[ISO/IEC 15944-2:2006 (3.62)]
                                                           [ISO/IEC 15944-2:2006 (3.62)]

3.154                                                      3.154
Open-edi       registration      administration            административный атрибут регистрации Open-
attribute                                                  edi
member of a set of attributes to uniquely
identify an Open-edi scenario, Information                 элемент набора атрибутов для уникальной
Bundle, or Semantic Component and the                      идентификации   сценария  Open-edi, Пакета
relevant Person responsible for its maintenance            Информации или Семантического Компонента и
                                                           соответствующее Лицо, ответственное за его
[ISO/IEC 15944-2:2006 (3.63)]                              поддержку

                                                           [ISO/IEC 15944-2:2006 (3.63)]
3.155                                                      3.155
Open-edi Registration Authority (OeRA)                     Уполномоченный Орган Регистрации Open-edi
Person responsible for maintaining the register            (OeRA)
of OeROs and for the issuance of OeRO
identifiers                                                Лицо, ответственное за поддержку регистра OeRO
                                                           и за выпуск идентификаторов OeRO
[ISO/IEC 15944-2:2006 (3.64)]
                                                           [ISO/IEC 15944-2:2006 (3.64)]


3.156                                                      3.156
Open-edi Registration Organization (OeRO)                  Организация Регистрации Open-edi (OeRO)
Person qualified by the OeRA to assume the
responsibility for the registration of scenario            Лицо, квалифицированное OeRA для возложения
and scenario components                                    на   него   ответственности за  регистрацию
                                                           сценария и компонентов сценария
[ISO/IEC 15944-2:2006 (3.65)]
                                                           [ISO/IEC 15944-2:2006 (3.65)]
3.157                                                      3.157
Open-edi Registration Organization address                 Адрес Организации Регистрации Open-edi
physical and/or electronic address of the
Open-edi Registration Organization                         Физический    и/или    электронный        адрес
                                                           Организации Регистрации Open-edi
NOTE A physical address includes a “pick-up”
address such as a mailbox or such other                    ПРИМЕЧАНИЕ Физический адрес включает адрес
location one can deliver to.                               доставки, такой как почтовый ящик или другие
                                                           места доставки
[ISO/IEC 15944-2:2006 (3.66)]                              [ISO/IEC 15944-2:2006 (3.66)]
3.158                                                      3.158
Open-edi Registration Organization Identifier              Идентификатор Организации Регистрации Open-
(OeORI)                                                    edi (OeORI)
identifier assigned to an Open-edi
Registration Organization                                  идентификатор, присвоенный       Организации
                                                           Регистрации Open-edi
[ISO/IEC 15944-2:2006 (3.67)]
                                                           [ISO/IEC 15944-2:2006 (3.67)]
3.159                                                      3.159
Open-edi Registration Organization name                    название Организации Регистрации Open-edi

                                                                                                  85
                 ISO English                      Gender                         ISO Russian
                      (1)                          (2)                               (3)

designation for the Open-edi Registration
Organization                                               обозначение     для     Организации       Регистрации
                                                           Open-edi
[ISO/IEC 15944-2:2006 (3.68)]
                                                           [ISO/IEC 15944-2:2006 (3.68)]

3.160                                                      3.160
Open-edi Registry (OeR)                                    Реестр Open-edi (OeR)
information system for the registration of
scenarios and scenario components                          Информационная система              для   регистрации
                                                           сценария и компонентов
[ISO/IEC 15944-2:2006 (3.69)]
                                                           [ISO/IEC 15944-2:2006 (3.69)]

3.161                                                      3.161
Open-edi Registry Item (OeRI)                              Позиция Реестра Open-edi (OeRI)
recorded information within a registry relating
to a specific Open-edi scenario or scenario                нформация, записанная в реестре и связанная с
components of a scenario including linkage                 конкретным     Open-edi  сценарием   или    с
information to a scenario content                          компонентами сценария включая информацию о
                                                           связи с контентом сценария
[ISO/IEC 15944-2:2006 (3.70)]
                                                           [ISO/IEC 15944-2:2006 (3.70)]
3.162                                                      3.162
Open-edi registry record                                   Запись реестра Open-edi
collection of recorded information for an OeRI
                                                           совокупность записанной информации для OeRI
[ISO/IEC 15944-2:2006 (3.71)]
                                                           [ISO/IEC 15944-2:2006 (3.71)]

3.163                                                      3.163
Open-edi scenario (OeS)                                    Сценарий Open-edi (OeS)
formal specification of a class of business
transactions having the same business goal                 Формальная    спецификация    класса   бизнес
                                                           транзакций, имеющих одну и ту же самую бизнес
                                                           цель
[ISO/IEC 14662:2004 (3.18)]
                                                           [ISO/IEC 14662:2004 (3.18)]
3.164                                                      3.164
Open-edi sponsoring authority                              поручительские полномочия Open-edi
Person recognized in accordance with the
requirements of this part of ISO/IEC 15944, to             Лицо,    признанное     в    соответствии    с
receive Open-edi Registration Organization                 требованиями этой части стандарта ISO/IEC
applications for submission to an Open-edi                 15944    получать   ходатайство    Организации
Registration Authority                                     Регистрации Open-edi для представления в Орган
                                                           по Регистрации Open-edi
[ISO/IEC 15944-2:2006 (3.73)]
                                                           [ISO/IEC 15944-2:2006 (3.73)]

3.165                                                      3.165
Open-edi standard                                          стандарт Open-edi

standard that complies with the Open-edi                   стандарт, который соответствует Референтной

                                                                                                         86
                  ISO English                       Gender                      ISO Russian
                       (1)                           (2)                             (3)
Reference Model                                              Модели Open-edi

[ISO/IEC 14662:2004 (3.19)]                                  [ISO/IEC 14662:2004 (3.19)]

3.166                                                        3.166
Open-edi Support Infrastructure (OeSI)                       Инфраструктура Поддержки Open-edi (OeSI)
model of the set of functional capabilities for
Open-edi systems which, when taken together
with the Decision Making Applications, allows                модель набора функциональных возможностей
Open-edi Parties to participate in Open-edi                  для    систем     Open-edi,   которые,   будучи
transactions                                                 использованы вместе с Приложенями Принятия
                                                             Решений,     позволяют     Сторонам    Open-edi
[ISO/IEC 14662:2004 (3.20)]                                  участвовать в транзакциях Open-edi

                                                             [ISO/IEC 14662:2004 (3.20)]

3.167                                                        3.167
Open-edi support organization                                организация поддержки Open-edi

organization, acting on behalf of an Open-edi                оранизация, действующая от имени Стороны
Party(ies) to provide necessary support                      (Сторон) Open-edi чтобы обеспечить необходимую
enabling execution of Open-edi transactions,                 поддержку создания условий для выполнения
but which is not modelled as a role(s)                       транзакций Open-edi, но которая не моделируется
                                                             как роль (роли)
[ISO/IEC 14662:2004 (3.21)]
                                                             [ISO/IEC 14662:2004 (3.21)]
3.168                                                        3.168
Open-edi system                                              система Open-edi
information technology system (IT system)
which enables an Open-edi Party to participate               система,    использующая      информационные
in Open-edi transactions                                     технологии (IT система), которая создает условия
                                                             для участия стороне Open-edi в транзакции Open-
[ISO/IEC 14662:2004 (3.22)]                                  edi

                                                             [ISO/IEC 14662:2004 (3.22)]
3.169                                                        3.169
Open-edi transaction                                         транзакция Open-edi
business transaction that is in compliance with
an Open-edi scenario                                         бизнес    транзакция,   которая  находится    в
                                                             соответствии со сценарием Open-edi
[ISO/IEC 14662:2004 (3.23)]
                                                             [ISO/IEC 14662:2004 (3.23)]

3.170                                                        3.170
organization                                                 организация
unique framework of authority within which a
person or persons act, or are designated to act,             уникальная структура власти, которая вместе с
towards some purpose                                         лицом или лицами действует иле предназначена
                                                             действовать для достижения некоторой цели
NOTE The kinds of organizations covered by
this International Standard include the following            ПРИМЕЧАНИЕ Виды организаций, охватываемые
examples:                                                    этим Международным Стандартом, включают
                                                             следующие примеры:

                                                                                                     87
                   ISO English                    Gender                       ISO Russian
                       (1)                         (2)                              (3)

EXAMPLE 1 An organization incorporated under
law.                                                       ПРИМЕР     1    Организация,       объединенная   в
                                                           соответствии с законом.

                                                           ПРИМЕР 2 Не корпоративная организация или вид
EXAMPLE 2 An unincorporated organization or                деятельности, обеспечивающий товары и/или
activity providing goods and/or services                   услуги, включая:
including:
                                                              1) партнерство;
1) partnerships;                                              2) социальные или другие не коммерческие
                                                                 организации или подобные органы, в
2) social or other non-profit organizations or
                                                                 которых    владение      или управление
similar bodies in which ownership or control is
                                                                 возлагается на группу лиц;
vested in a group of individuals;
                                                              3) единоличное владение;
3) sole proprietorships                                       4) правительственные органы.

4) governmental bodies.                                    ПРИМЕР 3 Группирование указанных выше типов
                                                           организаций, когда необходимо идентифицировать
EXAMPLE 3 Groupings of the above types of                  их в информационном обмене
organizations where there is a need to identify            [ISO/IEC 6523-1:1998 (3.1)]
these in information interchange.
[ISO/IEC 6523-1:1998 (3.1)]




3.171                                                      3.171
organization address                                       адрес организации
physical and/or electronic address of an
organization                                               физический       и/или     электронный       адрес
                                                           организации
NOTE A physical address includes a "pick-up"
address such as a mailbox or such other                    ПРИМЕЧАНИЕ Физический адрес включает адрес
location one can deliver to.                               доставки, какй, как почтовый ящик или другое
                                                           место, куда может быть проведена доставка
[ISO/IEC 15944-2:2006 (3.75)]
                                                           [ISO/IEC 15944-2:2006 (3.75)]
3.172                                                      3.172
organization name                                          имя организации
designation for the organization
                                                           обозначение организации
NOTE The name by which the organization is
known to the registration authority.                       ПРИМЕЧАНИЕ Имя, под которым организация
                                                           известна регистрационным органам
[ISO/IEC 11179-3:2003 (3.3.94)]
                                                           [ISO/IEC 11179-3:2003 (3.3.94)]




3.173                                                      3.173
organization part                                          часть организации
any department, service or other entity within
an organization, which needs to be identified              любое подразделение,            служба или другая
                                                           сущность в пределах            организации, которую

                                                                                                       88
                  ISO English                      Gender                       ISO Russian
                       (1)                          (2)                              (3)
for information interchange                                 требуется  идентифицировать         для   обмена
[ISO/IEC 6523-1:1998 (3.2)]                                 информации

                                                            [ISO/IEC 6523-1:1998 (3.2)]
3.174                                                       3.174
organization Person                                         Лицо организации
organization part which has the properties of a
Person and thus is able to make commitments                 часть организации, которая имеет свойства Лица
on behalf of that organization                              и   таким   образом    в    состоянии   делать
                                                            обязательства от имени организации
NOTE 1 An organization can have one or more
organization Persons.                                       ПРИМЕЧАНИЕ 1 Организация может иметь одно
                                                            или более Лиц организации
NOTE 2 An organization Person is deemed to
represent and act on behalf of the organization             ПРИМЕЧАНИЕ 2 Полагают, что Лицо организации
and to do so in a specified capacity.                       может представлять и действовать от имени
                                                            организации   и    действовать  так,   имея
NOTE 3 An organization Person can be a                      специфицированные полномочия
"natural person" such as an employee or officer
of the organization.                                        ПРИМЕЧАНИЕ 3 Лицом организации может быть
                                                            физическое лицо, такое как служащий или
NOTE 4 An organization Person can be a legal
                                                            должностное лицо организации.
person, i.e., another organization.
[ISO/IEC 15944-1:2002 (3.46)]                               ПРИМЕЧАНИЕ 4 Лицом организации может быть
                                                            юридическое лицо, т.е. другая организация.

                                                            [ISO/IEC 15944-1:2002 (3.46)]
3.175                                                       3.175
origin                                                      источник
source (document, project, discipline or model)
for the OeRI                                                источник (документ,     проект,   дисциплина   или
                                                            модель) для OeRI

[ISO/IEC 15944-2:2006 (3.77)]                               [ISO/IEC 15944-2:2006 (3.77)]

3.176                                                       3.176
participate                                                 участвовать
association between an economic event and
each of the two Persons participating in the                связь между экономическим действием и каждым
economic event                                              из двух Лиц, участвующих в экономическом
                                                            действии
NOTE Usually there is a “from” association and
a “to” association, depending upon the direction            ПРИМЕЧАНИЕ Обычно это связь «от кого» «кому»,
of the flow of the economic resource.                       в    зависимости    от  направления    потока
                                                            экономических ресурсов.
[ISO/IEC 15944-4:2006 (3.50)]

                                                            [ISO/IEC 15944-4:2006 (3.50)]

3.177                                                       3.177
partner                                                     партнер
sub-type of Person that includes buyer and
seller                                                      подтип Лица, который включает покупателя и
                                                            продавца
                                                                                                      89
                   ISO English                        Gender                      ISO Russian
                        (1)                            (2)                             (3)
[ISO/IEC 15944-4:2006 (3.51)]
                                                               [ISO/IEC 15944-4:2006 (3.51)]

3.178                                                          3.178
Person                                                         Лицо
entity, i.e., a natural or legal person, recognized
by law as having legal rights and duties, able to
make commitment(s), assume and fulfil                          сущность, т.е. физическое или юридическое лицо,
resulting obligation(s), and able of being held                признаваемое законом как имеющее права и
accountable for its action(s)                                  обязанности, способное делать обязательство (а),
                                                               брать на себя и выполнять результирующие
NOTE 1 Synonyms for "legal person" include                     обязательства и быть в состоянии отвечать за свои
"artificial person", "body corporate", etc.,                   действия
depending on the terminology used in
competent jurisdictions.                                       ПРИМЕЧАНИЕ 1 Синонимы для «юридического
                                                               лица»    включают     «искусственное    лицо»,
NOTE 2 "Person" is capitalized to indicate that it             «корпоративный орган» и т.д. в зависимости от
is being utilized as formally defined in the                   терминологии,   используемой    компетентными
standards and to differentiate it from its day-to-             юрисдикциями.
day use.
                                                               ПРИМЕЧАНИЕ 2 «Лицо» пишется с прописной
NOTE 3 Minimum and common external                             буквы. Это указывает на то, что термин определен
constraints applicable to a business transaction               в стандарте и отличает от каждодневного
often require one to differentiate among three                 использования слова.
common subtypes of Person, namely
"individual", "organization", and "public                      ПРИМЕЧАНИЕ 3 Минимальные и общие внешние
administration".                                               ограничения, применимые к бизнес транзакции
[ISO/IEC 14662:2004 (3.24)]                                    часто требуют различать среди трех общих
                                                               подтипов Лица, а именно «физическое лицо»,
                                                               «юридическое лицо» и «орган государственной
                                                               власти».

                                                               [ISO/IEC 14662:2004 (3.24)]

3.179                                                          3.179
persona                                                        персона
set of data elements and their values by which
a Person wishes to be known and thus                           набор элементов данных и их значений, по
identified in a business transaction                           которым Лицо желает быть узнаваемым и таким
                                                               образом идентифицируемым в бизнес транзакции
[ISO/IEC 15944-1:2002 (3.51)]

                                                               [ISO/IEC 15944-1:2002 (3.51)]
3.180                                                          3.180
personal information                                           персональная информация
any information about an identifiable individual
that is recorded in any form, including                        любая    информации     о    идентифицируемом
electronically or on paper                                     физическом лице, записанная в любой форме,
                                                               включая электронную или бумажную
NOTE Some examples would be information
about a person's religion, age, financial                      ПРИМЕЧАНИЕ В качестве некоторых примеров
transactions, medical history, address, or blood               может быть информация о религии, возрасте,
type.                                                          финансовых транзакциях, история болезни, адрес
                                                               или тип крови личности.

                                                                                                        90
                  ISO English                       Gender                      ISO Russian
                       (1)                           (2)                             (3)

[ISO/IEC 15944-5:2006 (3.103)]                               [ISO/IEC 15944-5:2006 (3.103)]
3.181                                                        3.181
persona Registration Schema (pRS)                            Схема Регистрации персоны (pRS)

formal definition of the data fields contained in            Формальное    определение    полей  данных,
the specification of a persona of a Person and               содержащих спецификацию персоны или Лица и
the allowable contents of those fields, including            допустимое содержание этих полей, включая
the rules for the assignment of identifiers.                 правила для присвоения идентификаторов. (Это
(This may also be referred to as a persona                   может также называться профилем персоны или
profile of a Person)                                         Лица)

[ISO/IEC 15944-1:2002 (3.52)]                                [ISO/IEC 15944-1:2002 (3.52)]
3.182                                                        3.182
Person authentication                                        аутентификация Лица
provision of the assurance of a recognized
Person identity (rPi) (sufficient for the purpose            обеспечение   уверенности     в   подлинности
of the business transaction) by corroboration                признанного Лица (rPi) (достаточной для целей
                                                             бизнес транзакции) путем подтверждения
[ISO/IEC 15944-1:2002 (3.48)]
                                                             [ISO/IEC 15944-1:2002 (3.48)]

3.183                                                        3.183
Person identity                                              подлинность Лица
combination of persona information and
identifier used by a Person in a business                    сочетание    информации   о     персоне  и
transaction                                                  идентификатора, использованного    Лицом в
                                                             бизнес транзакции
[ISO/IEC 15944-1:2002 (3.49)]
                                                             [ISO/IEC 15944-1:2002 (3.49)]

3.184                                                        3.184
Person signature                                             подпись Лица
signature, i.e., a name representation,
distinguishing mark or usual mark, which is                  подпись, т.е. представление имени, отличительный
created by and pertains to a Person                          знак или обычный знак, который создается и
                                                             принадлежит Лицу
[ISO/IEC 15944-1:2002 (3.50)]
                                                             [ISO/IEC 15944-1:2002 (3.50)]

3.185                                                        3.185
physical address                                             физический адрес
address that is used/recognized by a postal
authority and/or courier service to deliver                  адрес, который используется/признается почтовой
information item(s), material object(s), or                  службой или курьерской службой для доставки
business object(s) to a Contact at either an                 информационных         объектов,  материальных
actual address or a pick-up point address,                   объектов или бизнес объектов Контакту или по
(e.g., P.O. Box, rural route, etc.)                          действительному адресу или по адресу доставки
                                                             (например, P.O. Box, зона доставки почты в
[ISO/IEC 15944-2:2006 (3.80)]                                сельской местности и т.д.)

                                                             [ISO/IEC 15944-2:2006 (3.80)]
3.186                                                        3.186

                                                                                                     91
                  ISO English                      Gender                      ISO Russian
                       (1)                          (2)                             (3)
pivot code set                                              набор основных кодов
set of ID codes in a coded domain which is
made publicly known and available, the most                 Набор кодов идентификаторов в домене кодов,
stable, representing the defined semantics.                 который      является      общедоступным    и
Most often it is the same as the ID code                    общеизвестным,      стабильным,    отражающим
                                                            определенную семантику. Обычно данный набор
NOTE 1 The use of the pivot code set as                     совпадает с набором кодов ID
distinguished from the ID code supports the
requirement of a Source Authority to maintain               ПРИМЕЧАНИЕ 1 Использование основного набора
internally and on a confidential basis the ID               кодов как самостоятельной единицы (отдельно от
code of its members.                                        кода     ID)     удовлетворяет    требованиям
                                                            Вышестоящего Органа Власти, в отношении
NOTE 2 At times a coded domain has more                     сохранения      конфиденциальности       кодов
than one valid code set, (e.g., ISO 639, ISO                идентификации ее членов.
3166, etc.).
                                                            ПРИМЕЧАНИЕ 2 Иногда в домене кодов
EXAMPLE In ISO 3166-1 the 3-digit numeric                   содержится       более  одного    правильного
code is the pivot. The 2-alpha and 3-alpha code             (действующего) кодового набора (например, ISO
sets can change when the name of the entity                 639, ISO 3166 и т.д.).
referenced is changed by that entity.
[ISO/IEC 15944-5:2006 (3.104)]                              ПРИМЕР: В ISO 3166-1 основным является
                                                            трехсимовльный    численный   код.    Двух-   и
                                                            трехбуквенные кодовые наборы могут изменяться в
                                                            случае, если имя сущности было изменено самой
                                                            сущностью.

                                                            [ISO/IEC 15944-5:2006 (3.104)]
3.187                                                       3.187
pivot ID code                                               основной код ID
most stable ID code assigned to identify a
member of a coded domain where more than                    самый стабильный код ID, предназначенный для
one ID code may be assigned and/or                          идентификации элемента домена кодов, когда
associated with a member of that coded                      более чем один код ID может быть присвоен или
domain                                                      связан с элементом этого домена кодов

EXAMPLE ISO 3166-1:1997 (E/F) "Codes for                    ПРИМЕР ISO 3166-1:1997 (E/F) «Коды для
the representation of names of countries and                представления названий стран и их составных
their subdivisions - Part 1: Country codes/Codes            частей – Часть 1 Коды стран содержат три набора
pour la représentations des noms de pays et de              кодов:
leur subdivisions - Partie 1: Codes pays"
contains three code sets:                                   - численный трех цифровой код;
                                                            - двух буквенный код;
- a three digit numeric code;                               - трех буквенный код.
- a two alpha code
- a three alpha code.                                       Здесь численный трех цифровой код служит как
                                                            основной код. Он наиболее стабильный, остается
Here, the three digit numeric code serves as the            неизменным, даже если двух буквенный и/или трех
pivot code. It is the most stable, remains the              буквенный коды могут изменяться и фактически
same even though the two alpha and/or three                 меняются.
alpha codes may and do change.
[ISO/IEC 15944-5:2006 (3.105)]                              [ISO/IEC 15944-5:2006 (3.105)]


3.188                                                       3.188

                                                                                                   92
                  ISO English                        Gender                        ISO Russian
                       (1)                            (2)                                 (3)
plurilateral treaty                                           многосторонний международный договор
treaty among a defined set of jurisdictional
domains                                                       договор    среди    определенного         набора
                                                              юридических доменов
NOTE A plurilateral treaty restricts the
jurisdictional domains which may become                       ПРИМЕЧАНИЕ Многосторонний международный
signatories generally on either:                              договор ограничивает множество юридических
                                                              доменов, которые могут подписать этот договор на
• a geo-political basis, (e.g., NAFTA, Mecrosur,              основе:
European Union, etc.); or
                                                                 •   геополитической   (   например,    NAFTA,
• some other set of criteria which candidate                         Mecrosur, Европейский Союз и т.д.
members must meet and then their membership                      •   некоторого набора критериев, которым
approved by the existing membership, (e.g.,                          должны удовлетворять кандидаты в члены и
WTO).                                                                тогда      их    членство       одобряется
                                                                     существующими членами (например, ВТО).
[ISO/IEC 15944-5:2006 (3.106)]

                                                              [ISO/IEC 15944-5:2006 (3.106)]
3.189                                                         3.189
preferred term                                                предпочтительный термин

term recommended by an authoritative body                     термин, рекомендуемый авторитетным органом

[ISO 1087-1:2000 (5.6.1)]                                     [ISO 1087-1:2000 (5.6.1)]

3.190                                                         3.190
principle                                                     принцип
fundamental, primary assumption and quality
which constitutes a source of action determining              Фундаментальное первичное предположение,
                                                              которое составляет источник действия,
particular objectives or results
                                                              определяющего специфические цели или
NOTE 1 A principle is usually enforced by rules               результаты
that affect its boundaries.
                                                              ПРИМЕЧАНИЕ 1Принцип ,как правило, воплощается
NOTE 2 A principle is usually supported through               в жизнь по правилам, которые влияют на границы
one or more rules.                                            его действия.

NOTE 3 A principle is usually part of a set of                ПРИМЕЧАНИЕ 2 Принцип обычно поддерживается
principles which together form a unified whole.               одним или более правилом.

EXAMPLE Within a jurisdictional domain,                       ПРИМЕЧАНИЕ 3 Принцип обычно - часть ряда
examples of a set of principles include a charter,            принципов, которые вместе формируют
a constitution, etc.                                          объединенное целое.
[ISO/IEC 15944-2:2006 (3.81)]                                 ПРИМЕР В пределах юридического домена примеры
                                                              ряда принципов включают устав, конституцию, и
                                                              т.д.

                                                              [ISO/IEC, 15944-2:2006 (3.81)]

3.191                                                         3.191
privacy protection                                            защита прав личности
set of external constraints of a jurisdictional
                                                              набор внешних ограничений юридического
domain pertaining to recorded information on
                                                                                                       93
                   ISO English                        Gender                        ISO Russian
                        (1)                            (2)                               (3)
or about an identifiable individual, i.e.,                     домена, относящихся к записанной информации
personal information, with respect to the                      или об опознаваемом человеке, то есть, личной
creation, collection, management, retention,                   информации, относительно создания, сбора,
access and use and/or distribution of such                     управления, сохранения, доступа и использования
recorded information about that individual                     и/или распределения записанной информации о
including its accuracy, timeliness, and relevancy              человеке, включая ее точность,
                                                               своевременность, и уместность
NOTE 1 Recorded information collected or
created for a specific purpose on an identifiable              ПРИМЕЧАНИЕ 1 Записанная информация,
individual, i.e., the explicitly shared goal of the            собранная или созданная об опознаваемом
business transaction involving an individual shall             человеке с определенной целью, соответству ющей
not be utilized for another purpose without the                цели бизнес транзакции, в которой участвует
                                                               человек, не должна использоваться в другой цели
explicit and informed consent of the individual to
                                                               без получения согласия на основе полной
whom the recorded information pertains.
                                                               информации человека, которому принадлежит
NOTE 2 Privacy requirements include the right                  зарегистрированная информация.
of an individual to be able to view the recorded
                                                               ПРИМЕЧАНИЕ 2 Приватные требования включают
information about him/her and to request
                                                               право человека ознакомиться с информацией о
corrections to the same in order to ensure that                себе и вносить изменения, чтобы гарантировать
such recorded information is accurate and up-                  точность и современность информации.
to-date.
                                                               ПРИМЕЧАНИЕ 3 Когда юридические домены имеют
NOTE 3 Where jurisdictional domains have                       юридические права нарушать требования защиты
legal requirements which override privacy                      прав личности, то такие права должны быть
protection requirements these must be                          специфицированы (например, интересы
specified, (e.g., national security, investigations            национальной безопасности, интересы следствия,
by law enforcement agencies, etc.).                            проводимого государственными службами, и т.д.).
[ISO/IEC 15944-5:2006 (3.109)]
                                                               [ISO/IEC, 15944-5:2006 (3.109)]

3.192                                                          3.192
process                                                        процесс
series of actions or events taking place in a                  комплекс действий или событий, следующих
defined manner leading to the accomplishment                   определенным способом, приводящих к
of an expected result                                          достижению ожидаемого результата
[ISO/IEC 15944-1:2002 (3.53)]
                                                               [ISO/IEC, 15944-1:2002 (3.53)]

3.193                                                          3.193
property                                                       свойство
peculiarity common to all members of an object
class                                                          особенность обычная для всех членов класса
                                                               объектов.
[ISO/IEC 11179-1:2004 (3.3.29)]
                                                               [ISO/IEC 11179-1:2004 (3.3.29)]

3.194                                                          3.194
public administration                                          государственное управление
entity, i.e., a Person, which is an organization
and has the added attribute of being authorized                сущность, например, персона, которая является
to act on behalf of a regulator                                организацией, наделенной атрибутом, который
                                                               позволяет действовать от имени регулятора
[ISO/IEC 15944-1:2002 (3.54)]
                                                               [ISO/IEC 15944-1:2002 (3.54)]

                                                                                                       94
                  ISO English                        Gender                       ISO Russian
                       (1)                            (2)                               (3)


3.195                                                         3.195
public policy                                                 государственная политика
category of external constraints of a
                                                              категория внешних ограничений юридического
jurisdictional domain specified in the form of a
                                                              домена, определенных в форме прав человека
right of an individual or a requirement of an                 или требований организации и/или органа
organization and/or public administration                     государственного руководства относительно
with respect to an individual pertaining to any               человека, имеющего отношение к любому обмену
exchange of commitments among the parties                     обязательствами среди заинтересованных сторон
concerned involving a good, service and/or right              вовлеченных в процессы обмена товарами,
including information management and                          услугами и/или правами, включая информационное
interchange requirements                                      управление, и обмен требованиями

NOTE 1 Public policy requirements may apply                   ПРИМЕЧАНИЕ 1 Государственная политика может
to any one, all or combinations of the                        относиться к любому, всем или комбинациям
fundamental activities comprising a business                  фундаментальных видов деятельности, включая
transaction, i.e., planning, identification,                  бизнес транзакции, то есть, планирование,
negotiation, actualization and post-actualization.            идентификация, переговоры, актуализация и пост-
{See further Clause 6.3 "Rules governing the                  актуализация.
process component" in ISO/IEC 15944-1:2002}
                                                              ПРИМЕЧАНИЕ 2 В праве каждого юридического
NOTE 2 It is up to each jurisdictional domain to              домена определить, соответствует ли возраст
determine whether or not the age of an                        человека требованиям государственной политики
individual qualifies a public policy requirement,             (т.е., те, которые относятся к людям моложе
(e.g., those which specifically apply to an                   тринадцати (13) – как "ребенок", или те, которые
individual under the age of thirteen (13) as a                требуют, чтобы человек достиг совершеннолетия,
"child", those which require an individual to have            (например, 18 лет или 21 года) чтобы быть в
attained the age of adulthood, (e.g., 18 years or             состоянии взять на себя определенного рода
21 years of age) of an individual to be able to               обязательства
make commitments of a certain nature.                         .
                                                              ПРИМЕЧАНИЕ 3 Юридические домены могут иметь
NOTE 3 Jurisdictional domains may have                        защиту прав потребителя или личности, которой
consumer protection or privacy requirements                   могут обладать люди, которые, как полагают,
which apply specifically to individuals who are               являются "детьми", (например те, кто не достиг 18
                                                              лет или 21 года согласно правилам юридического
considered to be "children", "minorsÈ, etc.(e.g.
                                                              домена).
those who have not reached their 18th or 21st
birthday according to the rules of the applicable             [ISO/IEC, 15944-5:2006 (3.113)]
jurisdictional domain).

[ISO/IEC 15944-5:2006 (3.113)]
3.196                                                         3.196
reciprocal                                                    взаимно обязывающий
association between economic commitments
where the promise by one partner to execute                   связь между экономическими обязательствами,
an economic resource transfer in the future is                когда обещание одного партнера выполнить
reciprocated by the other partner promising a                 передачу     экономических ресурсов ведет к
requited transfer in the opposite direction                   взаимному    обязательству  другого  партнера
                                                              выполнить    свою    передачу   экономических
[ISO/IEC 15944-4:2006 (3.55)]                                 ресурсов в будущем.

                                                              [ISO/IEC 15944-4:2006 (3.55)]

3.197                                                         3.197
recognized individual name (RIN)                              распознаваемое имя личности (LRN)

                                                                                                       95
                   ISO English                         Gender                      ISO Russian
                         (1)                            (2)                             (3)

persona of an individual having the properties
of a legally recognized name (LRN)                              «лицо»   индивида,   обладающее    свойством
                                                                легально распознаваемого имени (LRN)
NOTE 1 On the whole, a persona presented by
an individual should have a basis in law (or                    ПРИМЕЧАНИЕ 1 В общем «лицо», представляемое
recognized jurisdictional domain) in order to be                личностью должно иметь юридическую базу (или
considered as the basis for a recognized                        признаваемый юридический домен) для того чтобы
individual name (RIN).                                          его   можно    было    считать  основой    для
                                                                признаваемого имени личности.
NOTE 2 An individual may have more than one
RIN and more than one RIN at the same time.                     ПРИМЕЧАНИЕ 2 Личность может иметь больше
                                                                одного признаваемого имени в общем и
NOTE 3 The establishment of a RIN is usually                    единовременно.
accompanied by the assignment of a unique
identifier, i.e. by the jurisdictional domain (or               ПРИМЕЧАНИЕ 3 Учреждение признаваемого имени
public administration) which recognizes the                     обычно       сопровождается      присваиванием
persona as a RIN.                                               уникального      идентификатора,      например
[ISO/IEC 15944-5:2006 (3.114)]                                  юридическом доменом, который распознает «лицо»
                                                                как признаваемое имя личности.

                                                                [ISO/IEC 15944-5:2006 (3.114)]

3.198                                                           3.198
recognized Person identity (rPi)                                признанная подлинность Лица (rPi)
identity of a Person, i.e., Person identity,
established to the extent necessary for a                       подлинность     лица   устанавливается для
specific purpose in a business transaction                      специфической цели бизнес транзакции со
                                                                степенью необходимости
[ISO/IEC 15944-1:2002 (3.56)]

                                                                [ISO/IEC 15944-1:2002 (3.56)]

3.199                                                           3.199
recorded information                                            записанная информация
any information that is recorded on or in a
medium irrespective of form, recording medium                   любая информация, записанная на носителе
or technology utilized, and in a manner allowing                независимо от формы, системы записи или
for storage and retrieval                                       используемой технологии и метода хранения и
                                                                поиска
NOTE 1 This is a generic definition and is
independent of any ontology, (e.g., those of                    ПРИМЕЧАНИЕ 1 Это типовое определение ,
"facts" versus "data" versus "information" versus               независящее от любой онтологии (например,
"intelligence" versus "knowledge", etc.).                       противопоставление понятий «факты», «данные»,
                                                                «информация», «интеллект», «знания» и т.д.)

                                                                ПРИМЕЧАНИЕ 2 При использовании        термина
NOTE 2 Through the use of the term                              «информация» все атрибуты этого       термина
"information," all attributes of this term are                  унаследованы в этом определении.
inherited in this definition.
                                                                ПРИМЕЧАНИЕ 3 Это определение охватывает:
NOTE 3 This definition covers:
                                                                  (i)  любую форму записанной информации,
(i) any form of recorded information, means of
                                                                       средства записи и любой носитель, на
recording, and any medium on which
                                                                       котором   информация    может    быть
information can be recorded; and,
                                                                       записана;
(ii) all types of recorded information including all

                                                                                                       96
                  ISO English                      Gender                       ISO Russian
                       (1)                          (2)                             (3)
data types, instructions or software, databases,               (ii)   все виды записанной информации,
etc.                                                                  включая все типы данных, команды
                                                                      программного обеспечения, базы данных
[ISO/IEC 15944-1:2002 (3.56)]                                         и т.д.


                                                            [ISO/IEC 15944-1:2002 (3.56)]

3.200                                                       3.200
reference document                                          референтная документация
external document(s) containing relevant
recorded information about the scenario or                  внешний документ (документы), содержащий
scenario component                                          соответствующую записанную информацию о
                                                            сценарии или компоненте сценария
[ISO/IEC 11179-3:2003 (3.3.112)]
                                                            [ISO/IEC 11179-3:2003 (3.3.112)]

3.201                                                       3.201
reference document identifier                               идентификатор референтного документа
identifier assigned to a reference document
by the OeRO
                                                            идентификатор, присвоенный OeRO
[ISO/IEC 11179-3:2003 (3.3.112)]                            референтному документу
                                                            [ISO/IEC 11179-3:2003 (3.3.112)]
3.202                                                       3.202
reference document language code                            код языка референтного документа
ISO 639-2/T based language code(s)
identifying the language(s) used in the                     коды    языка   на   основе    ISO   639-2/T,
reference document                                          идентифицирующие   языки,   используемые    в
                                                            референтном документе
[ISO/IEC 15944-2:2006 (3.86)]
                                                            [ISO/IEC 15944-2:2006 (3.86)]

3.203                                                       3.203
reference document title                                    наименование референтного документа
title(s) of the reference document
                                                            наименование(я) референтного документа
NOTE A reference document may have more
than one title depending on the languages in                ПРИМЕЧАНИЕ Референтный документ может
which it is produced                                        иметь   более    чем    одно    наименование в
                                                            зависимости от языка, на котором он написан
[ISO/IEC 11179-3:2003 (3.3.114)]
                                                            [ISO/IEC 11179-3:2003 (3.3.114)]




3.204                                                       3.204
reference document type description                         описание типа референтного документа
description of the document type of the
reference document
                                                            описание     типа     документа    референтного
                                                            документа
[ISO/IEC 11179-3:2003 (3.3.115)]
                                                                                                    97
                  ISO English                     Gender                       ISO Russian
                       (1)                         (2)                                 (3)

                                                           [ISO/IEC 11179-3:2003 (3.3.115)]
3.205                                                      3.205
reference organization                                     референтная организация
relationship between a reference document
and an organization                                        связь между      референтным        документом    и
                                                           организацией
[ISO/IEC 11179-3:2003 (3.3.116)]
                                                           [ISO/IEC 11179-3:2003 (3.3.116)]




3.206                                                      3.206
register                                                   регистр
set of files containing identifiers assigned to
items with descriptions of the associated items            набор файлов, содержащий идентификаторы,
                                                           присвоенные позициям с описаниями связанных
                                                           позиций
[ISO 19135:2005 (4.1.9)]
                                                           [ISO 19135:2005 (4.1.9)]
3.207                                                      3.207
register manager                                           менеджер регистра
organization to which management of a
register has been delegated by the register                организация,   которой    владелец         регистра
owner                                                      делегировал управление регистром.

NOTE In the case of an ISO register, the                   ПРИМЕЧАНИЕ В случае регистра ISO менеджер
register manager performs the functions of the             регистра выполняет функции органа регистрации,
registration authority specified in the ISO/IEC            описанные в Директивах
Directives.                                                ISO/IEC.
[ISO 19135:2005 (4.1.10)]                                  [ISO 19135:2005 (4.1.10)]


3.208                                                      3.208
register owner                                             владелец регистра
organization that establishes a register
                                                           организация, которая учредила регистр
[ISO 19135:2005 (4.1.11)]
                                                           [ISO 19135:2005 (4.1.11)]
3.209                                                      3.209
registrar                                                  регистратор
representative of an Open-edi Registration
Organization                                               представитель    Организации       по   Регистрации
                                                           Open-edi
[ISO/IEC 15944-2:2006 (3.93)]
                                                           [ISO/IEC 15944-2:2006 (3.93)]

3.210                                                      3.210
registrar Contact                                          Контакт с регистратором
Contact information associated with a
registrar of an Open-edi registration                      Контактная   информация,             связанная  с
                                                           регистратором организации          по регистрации

                                                                                                       98
                  ISO English                       Gender                       ISO Russian
                       (1)                           (2)                              (3)
organization                                                 Open-edi
[ISO/IEC 15944-2:2006 (3.94)]
                                                             [ISO/IEC 15944-2:2006 (3.94)]

3.211                                                        3.211
registration                                                 регистрация
rule-based process, explicitly stated, involving
the use of one or more data elements, whose                  процесс,   основанный  на   правилах,   явно
value (or combination of values) are used to                 сформулированный, включающий использование
identify uniquely the results of assigning an                одного или более элементов данных, чьи
OeRI                                                         значения (или комбинации значений) уникально
                                                             используются для идентификации результатов
[ISO/IEC 15944-2:2006 (3.95)]                                назначения OeRI

                                                             [ISO/IEC 15944-2:2006 (3.95)]
3.212                                                        3.212
Registration Authority (RA)                                  Орган Регистрации (RA)
Person responsible for the maintenance of one
or more Registration Schemas (RS) including                  Лицо, ответственное за за поддержку одной или
the assignment of a unique identifier for each               более   Схем     Регистрации   (RS),   включая
recognized entity in a Registration Schema                   назначение уникального идентификатора для
(RS)                                                         каждой   распознанной    сущности    в   Схеме
                                                             Регистрации (RS)
[ISO/IEC 15944-1:2002 (3.57)]
                                                             [ISO/IEC 15944-1:2002 (3.57)]

3.213                                                        3.213
Registration Authority Identifier (RAI)                      Идентификатор Органа Регистрации (RAI)
identifier assigned to a Registration Authority
(RA)                                                         идентификатор,          присвоенный      Органу
                                                             Регистрации (RA)
[ISO/IEC 11179-1:2004 (3.3.32)]
                                                             [ISO/IEC 11179-1:2004 (3.3.32)]

3.214                                                        3.214
Registration Schema (RS)                                     Схема Регистрации
formal definition of a set of rules governing the
data fields for the description of an entity and             формальное    определение     набора  правил,
the allowable contents of those fields, including            управляющих полями данных для описания
the rules for the assignment of identifiers                  сущности и допустимого содержания этих полей,
                                                             включая правила назначения идентификаторов
[ISO/IEC 15944-1:2002 (3.58)]
                                                             [ISO/IEC 15944-1:2002 (3.58)]

3.215                                                        3.215
registration status                                          статус регистрации
designation of the status in the registration
administration of an OeRI                                    назначение статуса в администрации регистрации
                                                             OeRI
[ISO/IEC 15944-2:2006 (3.98)]

                                                             [ISO/IEC 15944-2:2006 (3.98)]


                                                                                                    99
                  ISO English                      Gender                      ISO Russian
                       (1)                          (2)                             (3)
3.216                                                       3.216
registry                                                    системный реестр
information system on which a register is
maintained                                                  информационная система поддержки реестра

[ISO/IEC 15944-2:2006 (3.99)]                               [ISO/IEC 15944-2:2006 (3.99)]

3.217                                                       3.217
regulator                                                   Регулятор (тот, кто регулирует)
Person who has authority to prescribe external
constraints which serve as principles, policies             Лицо,    имеющее      полномочия   устанавливать
or rules governing or prescribing the behaviour             внешние ограничения, которые служат в качестве
of Persons involved in a business transaction               принципов, политики или правил, управляющих
as well as the provisioning of goods, services,             или предписывающих поведение Лиц, вовлеченных
and/or rights interchanged                                  в бизнес транзакцию, равно как обеспечивающих
                                                            товары, услуги и/или правы, подлежащие обмену
[ISO/IEC 15944-1:2002 (3.59)]
                                                            [ISO/IEC 15944-1:2002 (3.59)]

3.218                                                       3.218
regulatory business transaction (RBT)                       регламентирующая бизнес транзакция (RBT)
class of business transactions for which the
explicitly shared goal has been established and             класс бизнес транзакций, для которых явно
specified by a jurisdictional domain, as a                  разделяемая цель установлена и описана
Person in the role of a regulator                           юридическим доменом как Лицо в роли
                                                            регулятора
NOTE 1 A regulatory business transaction                    ПРИМЕЧАНИЕ       1 Регламентирующая бизнес
(RBT) can itself be modelled as a stand-alone               транзакция (RBT) сама может быть смоделирована
business transaction and associated                         как автономная транзакция и связанный сценарий
scenario(s). For example, the filing of a tax               (сценарии). Например, регистрация возвращения
return, the making of a customs declaration, the            налога, подготовка таможенной декларации, запрос
request for and issuance of a license, the                  и       выпуск        лицензии,     обеспечение
provision of a specified service of a public                специфицированного сервиса государственной
administration, a mandatory filing of any kind              администрации, обязательная регистрация любого
with a regulator, etc.                                      типа регулятором и т.д.

NOTE 2 A regulatory business transaction                    ПРИМЕЧАНИЕ 2         Регламентирующая бизнес
(modelled as a scenario) can form part of                   транзакция (моделируемая как сценарий) может
another business transaction.                               формировать часть или другую бизнес транзакцию.

                                                            ПРИМЕЧАНИЕ 3 RBT может применяться только к
                                                            продавцу, только к покупателю или к обоим, также
NOTE 3 A RBT may apply to a seller only, a
                                                            как любая комбинация сторон бизнес транзакции.
buyer only or both, as well as any combination
of parties to a business transaction.
                                                            ПРИМЕЧАНИЕ 4 RBT может требовать или
NOTE 4 A RBT may require or prohibit the use                запрещать использование агента или третьей
of an agent or third party.                                 стороны.

                                                            ПРИМЕЧАНИЕ       5 Регламентирующая бизнес
                                                            транзакция (RBT) может быть специфической в
NOTE 5 A regulatory business transaction                    зависимости от природы товара, услуги и/или прав,
(RBT) may be specific to the nature of the good,            формируя часть бизнес транзакции.
services and/or right forming part of a business
transaction.

                                                                                                    100
                   ISO English                      Gender                      ISO Russian
                       (1)                           (2)                             (3)
                                                             [ISO/IEC 15944-5:2006 (3.124)]
[ISO/IEC 15944-5:2006 (3.124)]
3.219                                                        3.219
repertoire                                                   репертуар
a specified set of characters that are
represented in a coded character set                         специфицированный набор символов, которые
                                                             представлены   в   закодированном  наборе
[ISO/IEC TR 15285:1998 (3.16)]                               символов

                                                             [ISO/IEC TR 15285:1998 (3.16)]

3.220                                                        3.220
resource-flow                                                поток ресурсов
association between an economic event and
an economic resource                                         связь между экономическим           событием   и
                                                             экономическим ресурсом
NOTE A common example would be a
resource-flow between some inventory and the                 ПРИМЕЧАНИЕ Примером общего характера мог бы
shipment that caused control of that inventory to            быть поток ресурсов между некоторым запасом и
flow from one Person to another.                             отгрузкой, который вызван управления этим
                                                             запасом, чтобы обеспечить поток от одного Лица к
[ISO/IEC 15944-4:2006 (3.58)]                                другому.

                                                             [ISO/IEC 15944-4:2006 (3.58)]

3.221                                                        3.221
responsibility                                               ответственность
association between Persons where one is
responsible to the other or between a Person                 связь между Лицами, когда они ответственны
and an organization Person where that                        перед другими или между Лицом и юридическим
Person is assigned                                           Лицом, когда Лицо назначено

NOTE Subtypes of Persons include individuals,                ПРИМЕЧАНИЕ         Подтипы      лица включают
organizations, and public administrations. An                физических     лиц, юридических лиц и органы
“individual” is non-divisible but organizations              государственной администрации. Физическое лицо
and public administrations are and as such will              – неделимо, в отличие от юридических лиц и
assign specific responsibilities to organization             органов государственной администрации, которые
Persons. {See further Clause 6.2.7 and Figure                могут определять специфические ответственности
17 in ISO/IEC 15944-1:2002}                                  юридическим Лицам. {См. далее Статью 6.2.7 и
                                                             рис. 17 в ISO/IEC 15944-1:2002}
[ISO/IEC 15944-4:2006 (3.59)]
                                                             [ISO/IEC 15944-4:2006 (3.59)]
3.222                                                        3.222
retention period                                             период удержания
length of time for which data on a data medium
is to be preserved                                           длина промежутка времени, в течение которого
                                                             данные на носителе данных должны быть
[ISO/IEC 2382-12:1988 (12.04.01)]                            зарезервированы

                                                             [ISO/IEC 2382-12:1988 (12.04.01)]
3.223                                                        3.223
role                                                         роль
specification which models an external intended

                                                                                                     101
                  ISO English                      Gender                      ISO Russian
                       (1)                          (2)                             (3)
behaviour (as allowed within a scenario) of an              спецификация, которая моделирует внешнее
Open-edi Party                                              заданное поведение (как разрешено сценарием)
[ISO/IEC 14662:2004 (3.25)]                                 Стороны Open-edi

                                                            [ISO/IEC 14662:2004 (3.25)]


3.224                                                       3.224
rule                                                        правило
statement governing conduct, procedure,
conditions and relations                                    утверждение,    регламентирующее         поведение,
                                                            процедуру, условия и отношения
NOTE 1 Rules specify conditions that must be
complied with. These may include relations                  ПРИМЕЧАНИЕ 1 Правила определяют условия,
among objects and their attributes.                         которые надо выполнять. Они могут включать связи
                                                            между объектами и их атрибутами.
NOTE 2 Rules are of a mandatory or conditional
nature.                                                     ПРИМЕЧАНИЕ 2 Правила по природе бывают
                                                            обязательными или условными.
NOTE 3 In Open-edi, rules formally specify the
commitment(s) and role(s) of the parties                    ПРИМЕЧАНИЕ 3 В системах Open-edi правила
involved, and the expected behaviour(s) of the              формально определяют обязательства и роли
parties involved as seen by other parties                   вовлеченных сторон и ожидаемое поведение
involved in (electronic) business transactions.             вовлеченных сторон, как оно видится другими
Such rules are applied to: -content of the                  сторонами, вовлеченными в (электронную) бизнес
information flows in the form of precise and                транзакцию. Такие правила применяются к:
computer-processable meaning, i.e. the                      - содержанию информационных потоков в виде
semantics of data; and, -the order and                      точных и допускающих компьютерную обработку
behaviour of the information flows themselves.              значений, т.е. семантики данных;
                                                            - порядку и поведению самих информационных
NOTE 4 Rules must be clear and explicit
                                                            потоков.
enough to be understood by all parties to a
business transaction. Rules also must be
                                                            ПРИМЕЧАНИЕ 4 Правила должны быть точными и
capable of being able to be specified using a
                                                            ясными, чтобы быть понятыми всеми сторонами
using a Formal Description Technique(s)
                                                            бизнес транзакции. Правила также должны
(FDTs).
                                                            обладать   свойствами,  обеспечивающими   их
EXAMPLE A current and widely used FDT is                    определение    с    использованием   Методов
"Unified Modelling Language (UML)".                         Формального Описания (FDT).

NOTE 5 Specification of rules in an Open-edi                ПРИМЕР Актуальным и широко используемым FDT
business transaction should be compliant with               является «Унифицированный Язык Моделирования
the requirements of ISO/IEC 15944-3 "Open-edi               (UML)».
Description Techniques (OeDT)".
                                                            ПРИМЕЧАНИЕ 5 Спецификация бизнес транзакций
[ISO/IEC 15944-2:2006 (3.101)]
                                                            Open-edi должна соответствовать требованиям
                                                            ISO/IEC 15944-3 «Методы Описания Open-edi
                                                            (OeDT)»

                                                            [ISO/IEC 15944-2:2006 (3.101)]

3.225                                                       3.225
rulebase                                                    база правил
pre-established set of rules which interwork and
which together form an autonomous whole                     заранее     установленный        набор     правил,

                                                                                                      102
                  ISO English                      Gender                      ISO Russian
                       (1)                          (2)                             (3)

NOTE One considers a rulebase to be to rules                взаимодействующих между собой и формирующих
as database is to data.                                     автономное целое

[ISO/IEC 15944-2:2006 (3.102)]                              ПРИМЕЧАНИЕ

                                                            [ISO/IEC 15944-2:2006 (3.102)]
3.226                                                       3.226
scenario attribute                                          атрибут сценария
formal specification of information, relevant to
an Open-edi scenario as a whole, which is                   формальная описание информации, имеющей
neither specific to roles nor to Information                отношение к сценарию Open-edi, не являющей
Bundles                                                     специфической ни по отношению к ролям, ни по
                                                            отношению к Пакетам Информации
[ISO/IEC 14662:2004 (3.26)]
                                                            [ISO/IEC 14662:2004 (3.26)]

3.227                                                       3.227
scenario component                                          компонент сценария
one of the three fundamental elements of a
scenario, namely role, information bundle,                  один из трех фундаментальных элементов
and semantic component                                      сценария, а именно роль, информационный
                                                            пакет и семантический компонент
[ISO/IEC 15944-2:2006 (3.104)]
                                                            [ISO/IEC 15944-2:2006 (3.104)]

3.228                                                       3.228
scenario content                                            содержание сценария
set of recorded information containing
registry entry identifiers, labels and their                набор записанной информации, содержащий
associated definitions and related recorded                 идентификаторы входа регистров, метки и их
information posted (or reposted) in any                     ассоциированные определения       и связанную
registry for business objects                               записанную информацию, направленную (или
                                                            вновь направленную) в любой регистр для бизнес
[ISO/IEC 15944-2:2006 (3.105)]                              объектов

                                                            [ISO/IEC 15944-2:2006 (3.105)]

3.229                                                       3.229
scenario specification attribute                            атрибут спецификации сценария
any attribute of a scenario, role, information
bundle, and/or semantic component                           любые  атрибут    сценария,   роль,   пакет
                                                            информации и/или семантический компонент
[ISO/IEC 15944-2:2006 (3.106)]
                                                            [ISO/IEC 15944-2:2006 (3.106)]

3.230                                                       3.230
SC identifier                                               идентификатор SC
unique, linguistically neutral, unambiguous,
referencable identifier of a Semantic                       уникальный,   лингвистически   нейтральный,
Component                                                   однозначный    доступный     для     ссылки
                                                            идентификатор Семантического Компонента
[ISO/IEC 15944-2:2006 (3.107)]
                                                            [ISO/IEC 15944-2:2006 (3.107)]

                                                                                                  103
                 ISO English                      Gender                      ISO Russian
                      (1)                          (2)                             (3)


3.231                                                      3.231
seller                                                     продавец
Person who aims to hand over voluntarily or in
response to a demand, a good, service and/or               Лицо,      которое      намеревается передать
right to another Person and in return receives             добровольно или в ответ на требование товар,
an acceptable equivalent value, usually in                 услугу и/или права другому Лицу и в ответ
money, for the good, service and/or right                  получить приемлемую эквивалентную стоимость,
provided                                                   обычно в денежном виде, за предоставленные
                                                           товар, услугу и/или права.

[ISO/IEC 15944-1:2002 (3.62)]
                                                           [ISO/IEC 15944-1:2002 (3.62)]
3.232                                                      3.232
Semantic Component (SC)                                    Семантический Компонент (SC)
unit of recorded information unambiguously
defined in the context of the business goal of             единица записанной информации, однозначно
the business transaction                                   определенной в контексте бизнес цели бизнес
                                                           транзакции
NOTE A SC may be atomic or composed of
other SCs.                                                 ПРИМЕЧАНИЕ SC может быть элементарным или
                                                           составленным из других SC
[ISO/IEC 14662:2004 (3.27)]                                [ISO/IEC 14662:2004 (3.27)]
3.233                                                      3.233
semantic identifier (SI)                                   cемантический идентификатор (SI)
IT-interface identifier for a semantic
component or other semantic for which (1) the              идентификатор        IT-интерфейса         для
associated context, applicable rules and/or                семантического    компонента     или    другой
possible uses as a semantic are predefined and             семантики, для которой (1) связанный контекст,
structured and the Source Authority for the                применимые     правила     и/или    возможные
applicable rulebase is identified; and (2) for             использования как семантики предопределены и
which one or more Human Interface                          структурированы и Вышестоящий Орган Власти
Equivalents (HIEs) exist                                   для применимой базы правил идентифицирован;
                                                           и (2) для которой существует один или более
NOTE 1 The identifier for a Semantic                       Эквивалентов              Человеко-машинного
Component (SC), an Information Bundle (IB)                 Интерфейса (HIEs)
and/or an ID Code for which one or more
Human Interface Equivalents (HIEs) exist are               ПРИМЕЧАНИЕ Считается, что Идентификатор
considered to have the properties or behaviours            Семантического   Компонента    (SC),    Пакет
of semantic identifiers.                                   Информации (IB)   и/или Код ID, для которых
                                                           существует один или более        Эквивалентов
[ISO/IEC 15944-5:2006 (3.136)]                             Человеко-машинного Интерфейса (HIEs), имеют
                                                           свойства    или   поведение     семантических
                                                           идентификаторов

                                                           [ISO/IEC 15944-5:2006 (3.136)]

3.234                                                      3.234
set of recorded information (SRI)                          набор записанной информации (SRI)
recorded information of an organization or
public administration, which is under the                  записанная информация об организации или
control of the same and which is treated as a              органе государственной власти, которая под
                                                           одним управлением и которая обрабатывается как
                                                                                                 104
                    ISO English                   Gender                      ISO Russian
                         (1)                       (2)                             (3)
unit in its information life cycle                         единица в своем информационном жизненном
                                                           цикле
NOTE 1 A SRI can be a physical or digital
document, a record, a file, etc., that can be              ПРИМЕЧАНИЕ 1 SRI может быть физическим       или
read, perceived or heard by a person or                    цифровым документом, записью, файлом и       т.д.,
computer system or similar device.                         который может быть почитан, воспринят        или
                                                           услышан лицом, или компьютерной системой     или
NOTE 2 A SRI is a unit of recorded information             подобным устройством.
that is unambiguously defined in the context of
the business goals of the organization, i.e., a            ПРИМЕЧАНИЕ 2 SRI есть единица записанной
semantic component.                                        информации,        которая      однозначно
NOTE 3 A SRI can be self-standing (atomic), or             идентифицируется в контексте бизнес цели
a SRI can consist of a bundling of two or more             организации,  т.е.  является семантическим
SRIs into another “new” SRI. Both types can                компонентом.
exist simultaneously within the information
management systems of an organization.                     ПРИМЕЧАНИЕ 3 SRI может быть самостоятельным
                                                           (элементарным) или состоять из связанных двух
                                                           или более SRI, образующих «новый» SRI. Оба типа
[ISO/IEC 15944-5:2006 (3.137)]                             могут существовать одновременно в составе
                                                           информационной        управляющей      системы
                                                           организации.

                                                           [ISO/IEC 15944-5:2006 (3.137)]
3.235                                                      2.235
settlement                                                 урегулирование
association between a requiting economic
event and an economic claim where the                      связь   между   оплаченным    экономическим
occurrence of the event causes the economic                событием и экономической претензией, когда
claim to expire                                            наступление события окончание срока действия
                                                           экономической претензии
[ISO/IEC 15944-4:2006 (3.63)]
                                                           [ISO/IEC 15944-4:2006 (3.63)]
3.236                                                      3.236
site                                                       участок
association between an economic event and
the business location where the transfer of                связь между экономическим событием и местом
economic resources involved in that event is               расположения бизнеса, где, предполагается,
deemed to have occurred                                    происходит передача экономических ресурсов в
                                                           этом событии
[ISO/IEC 15944-4:2006 (3.64)]
                                                           [ISO/IEC 15944-4:2006 (3.64)]
3.237                                                      3.237
Source Authority (SA)                                      Вышестоящий орган власти (SA)
Person recognized by other Persons as the
authoritative source for a set of constraints              Лицо      (юридическое      или     физическое),
                                                           признаваемое другими лицами как вышестоящий
NOTE 1 A Person as a Source Authority for                  орган власти для установления ограничений
internal constraints may be an individual,
organization, or public administration.                    ПРИМЕЧАНИЕ 1 Лицо как вышестоящий орган
                                                           власти для установления внутренних ограничений
NOTE 2 A Person as Source Authority for                    может быть физическое лицо, организация или
external constraints may be an organization or             орган государственной власти.
public administration.
                                                           ПРИМЕЧАНИЕ 2 Лицо как вышестоящий орган

                                                                                                  105
                   ISO English                         Gender                      ISO Russian
                        (1)                             (2)                                 (3)

EXAMPLE In the field of air travel and                          власти для установления внешних ограничений
transportation, IATA as a Source Authority, is an               может     быть     организация или    орган
"organization," while ICAO as a Source                          государственной власти.
Authority, is a "public administration".
                                                                ПРИМЕР В области воздушных перевозок и
NOTE 3 A Person as an individual shall not be a                 транспорта IATA как вышестоящий орган власти
Source Authority for external constraints.                      есть «организация», в то время как ICAO как
                                                                вышестоящий     орган   власти  есть   орган
NOTE 4 Source Authorities are often the issuing                 «государственной власти» (на самом деле –
authority for identifiers (or composite identifiers)            межгосударственной).
for use in business transactions.
                                                                ПРИМЕЧАНИЕ 3 Физическое лицо не может быть
NOTE 5 A Source Authority can undertake the                     вышестоящим органом власти для установления
role of Registration Authority or have this role                внешних ограничений.
undertaken on its behalf by another Person.
                                                                ПРИМЕЧАНИЕ 4 Вышестоящие органы власти
NOTE 6 Where the sets of constraints of a
                                                                часто являются органами, выдающими разрешение
Source Authority control a coded domain, the
                                                                на присвоение идентификаторов (или сложных
SA has the role of a coded domain Source
                                                                идентификаторов) для использования в бизнес
Authority.
                                                                транзакциях.

[ISO/IEC 15944-2:2006 (3.109)]                                  ПРИМЕЧАНИЕ 5        Вышестоящие органы власти
                                                                могут выполнять роль органа по регистрации и
                                                                имеют право доверять выполнение этой роли
                                                                другим лицам от их имени.

                                                                ПРИМЕЧАНИЕ 6 Когда наборы ограничений
                                                                Вышестоящего органа власти управляют доменом
                                                                кодов SA играет роль Вышестоящего органа власти
                                                                домена кодов.


                                                                [ISO/IEC 15944-2:2006 (3.109)]


3.238                                                           3.238
special language                                                специальный язык
language for special purposes (LSP), language
used in a subject field and characterized by the                язык для специальных целей (LSP), язык
use of specific linguistic means of expression                  используемый в предметной области и
                                                                характеризующийся применением специальных
NOTE The specific linguistic means of                           лингвистических выразительных средств
expression always include subject-specific
terminology and phraseology and also may                        ПРИМЕЧАНИЕ       Специальные     лингвистические
cover stylistic or syntactic features.                          выразительные средства включают предметно-
                                                                специфическую терминологию и фразеологию, а
[ISO 1087-1:2000 (3.1.3)]                                       также стилистические и синтаксические свойства

                                                                [ISO 1087-1:2000 (3.1.3)]

3.239                                                           3.239
standard                                                        стандарт
documented agreement containing technical
specifications or other precise criteria to be used

                                                                                                       106
                  ISO English                       Gender                       ISO Russian
                       (1)                           (2)                                 (3)
consistently as rules, guidelines, or definitions            документированное    соглашение,    содержащее
of characteristics, to ensure that materials,                технические спецификации или другие точные
products, processes and services are fit for                 критерии для согласованного использования в
their purpose                                                качестве правил, руководств или определений
                                                             характеристик, чтобы обеспечить, что материалы,
NOTE This is the generic definition of “standard”            продукты, процессы и услуги соответствовали их
of the ISO and IEC (and now found in the                     назначению
ISO/IEC JTC1 Directives, Part 1, Section
2.5:1998). {See also ISO/IEC Guide 2: 1996
(1.7)}                                                       ПРИМЕЧАНИЕ Это типовое определение понятия
                                                             «стандарт» ИСО и МЭК (в настоящее время
[ISO/IEC 15944-1:2002 (3.64)]                                находится в Директивах ISO/IEC JTC1, Часть1,
                                                             Раздел 2.5:1998). {См. также ISO/IEC Guide 2: 1996
                                                             (1.7)}
                                                             [ISO/IEC 15944-1:2002 (3.64)]

3.240                                                        3.240
stewardship (of an OeRI)                                     служба (OeRI)
relationship of an OeRI, a Contact, and an
organization involved in the stewardship of an               взаимодействие OeRI, Контакта и организации
OeRI                                                         включены в службу OeRI

                                                             [ISO/IEC 15944-2:2006 (3.111)]
[ISO/IEC 15944-2:2006 (3.111)]
3.241                                                        3.241
stewardship organization                                     организация службы
unique framework of authority within which a
Person or Persons act, or are designated to act              уникальная структура власти, в пределах которой
in the stewardship of an OeRI                                Лицо или Лица действуют или назначаются
                                                             действовать в службе OeRI

[ISO/IEC 15944-2:2006 (3.112)]
                                                             [ISO/IEC 15944-2:2006 (3.112)]
3.242                                                        3.242
submission (of an OeRI)                                      представление документов (OeRI)
relationship of an OeRI, a Contact, and an
organization involved in the submission of an                взаимоотношение OeRI, Контакта и организации в
OeRI                                                         представлении документов OeRI

[ISO/IEC 15944-2:2006 (3.112)]                               [ISO/IEC 15944-2:2006 (3.112)]

3.243                                                        3.243
submitting organization                                      организация, представляющая документы
organization authorised by a register owner to
propose changes to the content of a register                 организация,   авторизованная  владельцем
                                                             регистра предлагать изменения в содержание
[ISO 19135:2005 (4.1.16)]                                    регистра

                                                             [ISO 19135:2005 (4.1.16)]

3.244                                                        3.244
term                                                         термин
designation of a defined concept in a special
                                                             назначение       определенного       понятия         в
                                                                                                       107
                   ISO English                       Gender                      ISO Russian
                        (1)                           (2)                             (3)
language by a linguistic expression                           специальном языке лингвистическим выражением

NOTE A term may consist of one or more words                  ПРИМЕЧАНИЕ Термин может состоять из одного
i.e. simple term, or complex term or even                     или более слов, т.е. простой термин или составной
contain symbols.                                              термин, и даже содержать обозначения.
[ISO 1087:1990 (5.3.1.2)]                                     [ISO 1087:1990 (5.3.1.2)]


3.245                                                         3.245
text                                                          текст
data in the form of characters, symbols, words,
phrases, paragraphs, sentences, tables, or                    данные в форме символов, обозначений, слов,
other character arrangements, intended to                     фраз, абзацев, предложений, таблиц или других
convey a meaning and whose interpretation is                  конструкций символов, предназначенных для
essentially based upon the reader's knowledge                 переноса   смысла    и    чья   интерпретация
of some natural language or artificial                        существенно основана на знаниях читателя
language                                                      некоторого    естественного     языка     или
                                                              искусственного языка
EXAMPLE A business letter printed on paper or
displayed on a screen.                                        ПРИМЕР Бизнес письмо, отпечатанное на бумаге
                                                              или отраженное на экране.
[ISO/IEC 2381-23:1994 (23.01.01)]
                                                              [ISO/IEC 2381-23:1994 (23.01.01)]

3.246                                                         3.246
third party                                                   третья сторона
Person besides the two primarily concerned in
a business transaction who is agent of neither                Лицо кроме двух первично связанных (основных) с
and who fulfils a specified role or function as               бизнес транзакцией, которое не является ничьим
mutually agreed to by the two primary Persons                 агентом и которое выполняет специфическую
or as a result of external constraints                        роль или функцию, либо взаимно согласованную
                                                              двумя основными Лицами, либо в соответствии с
NOTE It is understood that more than two                      внешним ограничением.
Persons can at times be primary parties in a
business transaction.                                         ПРИМЕЧАНИЕ Понятно, что иногда более чем два
                                                              Лица могут быть первичными сторонами в бизнес
                                                              транзакции.
[ISO/IEC 15944-1:2002 (3.65)]
                                                              [ISO/IEC 15944-1:2002 (3.65)]
3.247                                                         247
treaty                                                        международный договор
international agreement concluded between
jurisdictional domains in written form and
governed by international law                                 международное соглашение, заключаемое между
                                                              юридическими доменами в письменной форме,
NOTE 1 On the whole a treaty is concluded                     регулируемое международным законодательством
among UN member states.
                                                              ПРИМЕЧАНИЕ 1 В общем международный договор
NOTE 2 Treaties among UN member states                        заключается между членами ООН
when coming into force are required to be
transmitted to the Secretariat of the United                  ПРМЕЧАНИЕ 2 Международные договора между
Nations for registration or filing or recording as            членами ООН, когда они вступают в силу, должны
the case may be and for publication. {See                     быть переданы в Секретариат ООН для
further Article 80 or the Charter of the UN}                  регистрации или подшивки или записи как примера

                                                                                                      108
                  ISO English                       Gender                      ISO Russian
                       (1)                           (2)                             (3)

NOTE 3 Treaties can also be entered into by                  для возможной публикации {Далее см. Статью 80
jurisdictional domains other than UN member                  Хартии ООН}
states, i.e., non-members such as international
organizations and the rare sub-national units of             ПРИМЕЧАНИЕ 3 В международные договора могут
federations which are constitutionally                       входить    также   юридические   домены     не
empowered to do so.                                          являющиеся гсударствами-членами ООН, такие как
                                                             международные     организации       и    реже
NOTE 4 A treaty can be embodied in a single                  субнациональные    подразделения   федераций,
instrument or in two or more related instruments             которые уполномочены это делать
and whatever it particular designations.
However, each treaty is a single entity.                     ПРИМЕЧАНИЕ 4 Международный договор может
                                                             быть воплощен в одном инструменте или в двух
NOTE 5 Jurisdictional domains can make                       или нескольких инструментах , каковы бы не были
agreements which they do not mean to be                      его конкретные предназначения. Вместе с тем
legally binding for reasons of administrative                каждый      международный договор является
convenience or expressions of political intent               единственной сущностью.
only, (e.g., as a Memorandum of Understanding
(MOU)).                                                      ПРИМЕЧАНИЕ 5 Юридические домены могут
                                                             заключать соглашения, которые они не считают
[adapted from the Vienna Convention on the                   связанными      юридически     по    причинам
Law of Treaties, 1(a)]                                       административных условий или выражений только
[ISO/IEC 15944-5:2006 (3.144)]                               политического намерения (например, Меморандум
                                                             Взаимопонимания (MOU))

                                                             [использована Венская Конвенция о Законах и
                                                             Международных договорах 1(a)]

                                                             [ISO/IEC 15944-5:2006 (3.144)]

3.248                                                        3.248
truncated name                                               сокращенное имя
short form of a name or persona of a Person
resulting from the application of a rule-based               короткое имя или персона Лица, образующееся
truncation process                                           при    применении     процесса  сокращения,
                                                             основанного на правилах
[ISO/IEC 15944-5:2006 (3.145)]
                                                             [ISO/IEC 15944-5:2006 (3.145)]

3.249                                                        3.249
truncated recognized name (TRN)                              сокращенное признаваемое имя (TRN)
truncated name, i.e., persona, of a Person
which has the properties of a legally                        сокращенное имя, т.е. персона Лица, которое
recognized name (LRN)                                        имеет свойства официально признаваемого
                                                             имени (LRN)
NOTE 1 Truncated recognized name(s) may be
required for use in machine-readable travel                  ПРИМЕЧАНИЕ 1 Сокращенное признаваемое имя
documents, (e.g., passports or visas), identity              (имена) может потребоваться для использование в
tokens, drivers’ licenses, medicare cards, etc.).            машиночитаемых документах в путешествиях
                                                             (например, паспорта или визы),         признаках
NOTE 2 The source of a truncated recognized                  опознания,    водительских     правах,    картах
name may be a legally recognized name.                       медицинского обслуживания и т.д.
[ISO/IEC 15944-5:2006 (3.146)]
                                                             ПРИМЕЧАНИЕ     2   Источником сокращенного
                                                             признаваемого имени может быть официально

                                                                                                    109
                   ISO English                        Gender                      ISO Russian
                        (1)                            (2)                             (3)
                                                               признаваемое имя

                                                               [ISO/IEC 15944-5:2006 (3.146)]


3.250                                                          3.250
truncation                                                     сокращение
rule-base process, explicitly stated, for
shortening an existing name of an entity to fit                основанный   на   правилах   процесс,  явно
within a predefined maximum length (of                         сформулированный,   для сокращения имени
characters)                                                    сущности, для того чтобы соответствовать
                                                               максимальной, заранее определенной длине (в
NOTE Truncation may be required for the use of                 символах)
names in IT systems, electronic data
interchange (EDI), the use of labels in                        ПРИМЕЧАНИЕ Сокращение может потребоваться
packaging, in the formation of a Person identity               для     использования  имен   в  IT   системах,
(Pi), etc.                                                     электронном     обмене   данными    (EDI),  при
                                                               использовании этикеток в пакетировании, при
                                                               обеспечении определения подлинности Личности
[ISO/IEC 15944-5:2006 (3.147)]                                 (Pi) и т.д.

                                                               [ISO/IEC 15944-5:2006 (3.147)]

3.251                                                          3.251
typification                                                   типификация
association between a concrete entity and the
abstract specification of its grouped properties               связь между конкретной сущностью и абстрактной
                                                               спецификацией ее сгруппированных свойств

[ISO/IEC 15944-4:2006 (3.66)]                                  [ISO/IEC 15944-4:2006 (3.66)]


3.252                                                          3.252
unambiguous                                                    однозначность
level of certainty and explicitness required in the
completeness of the semantics of the recorded                  уровень определенности и ясности, требуемый для
information interchanged appropriate to the                    завершенности     семантики        обмениваемой
goal of a business transaction                                 записанной информации в соответствии с целью
                                                               бизнес транзакции

[ISO/IEC 15944-1:2002 (3.66)]
                                                               [ISO/IEC 15944-1:2002 (3.66)]

3.253                                                          3.253
undefined market model                                         неопределенная рыночная модель
trade model where participants are not
registered in advance and where that market                    модель     торговли,    когда    участники    не
does not have accepted and recognized                          зарегистрированы заранее и когда рынок не принял
sources or business rules and conventions                      и не признал источники бизнес правил и условий

[ISO/IEC 15944-4:2006 (3.67)]                                  [ISO/IEC 15944-4:2006 (3.67)]

3.254                                                          3.254

                                                                                                      110
                  ISO English                       Gender                       ISO Russian
                       (1)                           (2)                              (3)
until date                                                   дата действия
date at which an OeRI is no longer effective in
the registry                                                 дата, когда OeRI перестает быть действительным в
                                                             реестре

[ISO/IEC 15944-2:2006 (3.116)]                               [ISO/IEC 15944-2:2006 (3.116)]
3.255                                                        3.255
vendor                                                       поставщик
seller on whom consumer protection
requirements are applied as a set of external                продавец, к которому применяются требования по
constraints on a business transaction                        защите прав потребителя как набор внешних
                                                             ограничений на бизнес транзакцию
NOTE 1 Consumer protection is a set of
explicitly defined rights and obligations                    ПРИМЕЧАНИЕ 1 Защита прав потребителя есть
applicable as external constraints on a business             набор явно определенных прав и обязательств,
transaction.                                                 применяемых как внешние ограничения бизнес
                                                             транзакции
NOTE 2 It is recognized that external
constraints on a seller of the nature of consumer            ПРИМЕЧАНИЕ 2           Принято, что внешние
protection may be peculiar to a specified                    ограничения, распространяющиеся на продавца и
jurisdiction.                                                связанные с защитой прав потребителя, могут быть
[ISO/IEC 15944-1:2002 (3.67)]                                специфическими для конкретной юрисдикции

                                                             [ISO/IEC 15944-1:2002 (3.67)]


3.256                                                        3.256
version identifier                                           идентификатор версии
unique number assigned to identify a version of
an OeRI                                                      уникальный   номер,    предназначенный       для
                                                             идентификации версии OeRI
NOTE The default value = 1.0.
                                                             ПРИМЕЧАНИЕ Значение по умолчанию = 1.0.
[ISO/IEC 15944-2:2006 (3.117)]
                                                             [ISO/IEC 15944-2:2006 (3.117)]

3.257                                                        3.257
vocabulary                                                   словарь
terminological dictionary which contains
designations and definitions for one or more                 терминологический словарь, который содержит
specific subject fields                                      назначения и определения для одного или более
                                                             специфических предметных полей
NOTE The vocabulary may be monolingual,
bilingual or multilingual.                                   ПРИМЕЧАНИЕ Словарь может быть одноязычным,
                                                             двуязычным или многоязычным
[ISO 1087-1:2000 (13.7.2)]
                                                             [ISO 1087-1:2000 (13.7.2)]




                                                                                                    111
112
Draft text for Annex F provided by China

X

              Annex F –             (Normative) Chinese HIE for the eBusiness Vocabulary
                                                           (DRAFT)
File Name: FCD15944-7-NormativeAnnex-EFdefintions-AcceptAll.doc




                                                                                 [AcceptAll Version, as of 2007-06-04]




Complete set of terms and definitions to be included in Annex ? (Normative) in the FCD
document for 15944-7.

Project Editors’ Note(s):

(1) 1. This is the corrected version based on (Draft) Piscataway, 7-11May, 2007, resulting from review by
Jake Knoppers and Wengfeng SUN + translation and added corrections by Francois Mouzard plus further
integrity check done by Janice Pereira. and then edited accordingly by Jake Knoppers and David Clemis,
25 May, 2007.


2. In addition the font for the text of fthe defintions has been changed to Arial 10 and that for the Notes
and Examples to Arial 9 (as per JTC1 Directives).This was completed 2007-06-04.

3. It is noted that the in the numbering below the “3” in “3.n” will be rplaced by the latter of the Normative
Annex. The final set of numbering will also be done at the same time

Introductory contents of Annex F are to be added by the project editors.
(2) The organization of Annex F and table structure for the Chinese HIE to be changed to a style like
Annex D.
(3) The current Chinese HIE is based on a outdated version of English terms and definetions, the
identifier, term and definition for each English HIE need to be changed and checked against Annex D.


3.1
address
set of data elements that specifies a location to which a
recorded information item(s), a business object(s), a
material object(s) and/or a person(s) can be sent or from which
it can be received
                                                                         (   )
NOTE 1 An address can be specified as either a physical address
and/or electronic address.
                                                                         1                              (   )
NOTE 2 In the identification, referencing and retrieving of registered
business objects, it is necessary to state whether the pertinent
recorded information is available in both physical and virtual forms.
                                                                         2
NOTE 3 In the context of Open-edi, a “recorded information item” is
modelled and registered as an Open-edi scenario (OeS), Information
Bundle (IB) or Semantic Component (SC).


[ISO/IEC 15944-2:2006 (3.1)]                                             3               edi                        “

                                                                                                                  113
                                                                                          ”                  edi
                                                                               IB                    SC
3.2
administrative note
general note about the OeRI
[ISO/IEC 15944-2:2006 (3.2)]                                                            edi         (OeRI)

3.3
agent
Person acting for another Person in a clearly specified
capacity in the context of a business transaction

NOTE Excluded here are agents as "automatons" (or robots, bobots,
etc.). In ISO/IEC 14662, "automatons" are recognized and provided for
but as part of the Functional Service View (FSV) where they are
defined as an "Information Processing Domain (IPD)".
                                                                                    “            ”
                                                                                              ISO/IEC
[ISO/IEC 15944-1:2002 (3.1)]
                                                                         14662      “           ”
                                                                         FSV                                 “     ”
3.4
applicant (for an OeRI)
Person who requests the assignment of an OeRI and an
associated entry label

NOTE An applicant can be an individual, organization, or public
administration.


[ISO/IEC 15944-2:2006 (3.3)]

3.5
Application Program Interface (API)
a boundary across which application software uses facilities of
programming languages to invoke services

NOTE 1 These facilities may include procedures or operations,
shared data objects and resolution of identifiers.
                                                                               1
NOTE 2 A wide range of services may be required to support
applications. Different methods may be appropriate for documenting
API specifications for different types of services.                            2
NOTE 3 The information flows across the API boundary are defined
by the syntax and the semantics of a particular programming               API
language, such that the user of that language may access the services
provided by the platform on the other side of the boundary. This               3        API
implies the specification of the mapping of the functions being made
available by the application platform into the syntax and semantics of
the programming language.

[ISO/IEC JTC1 Directives::2007(J.1.1)]


3.6
artificial language
language whose rules are explicitly established prior to its use
[ISO 5127-1:2001 (1.1.2.03)]

3.7
attribute

                                                                                                                   114
characteristic of an object or entity
[ISO/IEC 11179-3:2003 (3.1.3)]

3.8
authentication
provision of assurance of the claimed identity of an entity
[ISO/IEC 10181-2:1996] ???

3.9
authenticity
property that ensures that the identity of a subject or resource
is the one claimed

NOTE Authenticity applies to entities such as users, processes,
systems and information.
[ISO/IEC TR 13335-1:1996 (3.3)]

3.10
bilateral transaction
sub-type of a business transaction where the Persons
include only the buyer and the seller, or alternatively other
Persons acting as agents for the buyer or seller
[ISO/IEC 15944-4:2006 (3.3)]

3.11
bilateral treaty
treaty made between two jurisdictional domains

NOTE An important point here is that there is no intention to bind both
parties under international law.
[ISO/IEC 15944-5:2006 (3.7)]

3.12
business
series of processes, each having a clearly understood
purpose, involving more than one Person, realised through the
exchange of recorded information and directed towards some
mutually agreed upon goal, extending over a period of time


[ISO/IEC 14662:2004 (3.2)]

3.13                                                                      3.13
business event
occurrence in time that partners to a business transaction
wish to monitor or control

NOTE 1 Business events are the workflow tasks that business
partners need to accomplish to complete a business transaction
among themselves. As business events occur, they cause a business                1
transaction to move through its various phases of planning ,
identification, negotiation, actualization, and post-actualization.

NOTE 2 Occurrences in time can either be

(1) internal as mutually agreed to among the parties to a business
transaction; and/or,

(2) reference some common publicly available and recognized                      2
                                                                                     115
date/time referencing schema, (e.g., one based on using the ISO 8601
and/or ISO 19135 standards).                                               a)
[ISO/IEC 15944-4:2006 (3.5)]
                                                                                    /

                                                                           b)
                                                                                                                       (
                                                                                            ISO 8601
                                                                                (       )ISO19135          )


3.14
business location
geographic site where an economic event is deemed to occur
with its attendant transfer of an economic resource from one
Person to another
[ISO/IEC 15944-4:2006 (3.6)]

3.15
business object
unambiguously identified, specified, referenceable, registered
and re-useable Open-edi scenario or scenario component of
a business transaction

NOTE As an “object”, a “business object” exists only in the context of a                        “      ”       “   ”
business transaction.
[ISO/IEC 15944-2:2006 (3.6)]

3.16
business object identifier
unique identifier of a business object in an OeRI within an
Open-edi Registration Organization(OeRO)
[ISO/IEC 15944-2:2006 (3.7)]

3.17
business object status
designation of the status in the administrative process of a
Open-edi Registration Organization for handling OeRI
[ISO/IEC 15944-2:2006 (3.8)]

3.18
business object type
coded domain for the type of business object being
registered, i.e., Open-edi scenario, IB or SC
[ISO/IEC 15944-2:2006 (3.9)]

3.19
Business Operational View (BOV)
perspective of business transactions limited to those aspects
regarding the making of business decisions and
commitments among Persons, which are needed for the
description of a business transaction
[ISO/IEC 14662:2004 (3.3)]


                                                                                                                       116
3.20
business transaction
predefined set of activities and/or processes of Persons which
is initiated by a Person to accomplish an explicitly shared                            (
business goal and terminated upon recognition of one of the
agreed conclusions by all the involved Persons although some
of the recognition may be implicit
[ISO/IEC 14662:2004 (3.4)]


3.21
business transaction entity
computable representation of any real world entity that
participates, occurs, or is materialized during a business
transaction
[ISO/IEC 15944-4:2006 (3.9)]

3.22
business transaction entity type
abstract specification of a business transaction entity,
detailing its recommended characteristics, its recommended
methods, and its recommended life-cycle states

NOTE A business transaction entity type will usually specify the types
of business events that cause a business transaction entity of this type
to proceed through its different states as the business transaction itself
progresses through its phases of planning, identification, negotiation,
actualization, and post-actualization.
[ISO/IEC 15944-4:2006 (3.10)]




3.23
business transaction identifier (BTI)
identifier assigned by a seller or a regulator to an instantiated
business transaction among the Persons involved

NOTE 1 The identifier assigned by the seller or regulator shall have
the properties and behaviours of an “identifier (in a business
transaction)”.                                                                     1
NOTE 2 As an identifier (in a business transaction), a BTI serves as                           “
the unique common identifier for all Persons involved for the
                                                                             ”
identification, referencing, retrieval of recorded information, etc.,
pertaining to the commitments made and the resulting actualization
(and post-actualization) of the business transaction agreed to.                    2       (   )
                                                                             BTI

NOTE 3 A business transaction identifier can be assigned at any time
during the planning, identification or negotiation phases but shall be
assigned at least prior to the start or during the actualization phase.

NOTE 4 As and where required by the applicable jurisdictional
domain(s), the recorded information associated with the business
transaction identifier (BTI) may well require the seller to include other          3
identifiers, (e.g., from a value-added good or service tax, etc.,
perspective) as assigned by the applicable jurisdictional domain(s).
[ISO/IEC 15944-5:2006 (3.12)]
                                                                                   4
                                                                                       (BTI)
                                                                                                   117
                                                                                              (
                                                                                  )


3.24
buyer
Person who aims to get possession of a good, service and/or
right through providing an acceptable equivalent value, usually
in money, to the Person providing such a good, service and/or
right
[ISO/IEC 15944-1:2002 (3.8)]

3.25
change description
description of why and how the OeRI has been modified since
the prior version of the OeRI

NOTE It is advised that such a change description be accompanied by
the “original “ template values utilized and a “change template”                                  “   ”
indicating which “Decision Code(s)” has been changed as well as the
date the change will take effect.                                                     “   ”
[ISO/IEC 15944-2:2006 (3.12)]

3.26
character
member of a set of elements that is used for the representation,
organization or control of data

NOTE Characters may be categorized as follows:

TYPES AND EXAMPLES

    •   graphic character: (e.g., digit, letter, ideogram, special    
        character)

    •   control character: (e.g., transmission control, character,
        format effector, code extension character, device control     
        character).

[ISO/IEC 2382-4:1999 (04.01.01)]


3.27
characteristic
abstraction of a property of an object or of a set of objects

NOTE Characteristics are used for describing concepts.
[ISO 1087-1:2000 (3.2.4)]

3.28
character set
finite set of different characters that is complete for a given
purpose

EXAMPLE The international reference version of the character set of
ISO 646-1.                                                            ISO 646-1

[ISO/IEC 2382-4:1999 (04.01.02)]


                                                                                                          118
3.29
classification system
systematic identification and arrangement of business
activities and/or scenario components into categories                                    ( )
according to logically structured conventions, methods and
procedural rules as specified in a classification schema

NOTE 1 The classification code or number often serves as a semantic
identifier (SI) for which one or more human interface equivalents exist.
                                                                               1
NOTE 2 The rules of a classification schema governing the operation
of a classification system at times lead to the use of ID codes which
have an intelligence built into them, (e.g., in the structure of the ID, the
manner in which it can be parsed, etc. Here the use of block-numeric           2
numbering schemas is an often used convention.                                     ID                ID
[ISO/IEC 15944-5:2006 (3.17)]                                                            ID



3.30
code
data representation in different forms according to a pre-
established set of rules

NOTE In this standard the "pre-established set of rules" are
determined and enacted by a Source Authority and must be explicitly
stated.
[ISO 639-2:1998 (3.1)]

3.31
code (in coded domain

identifier, i.e., an ID code, assigned to an entity as member                           ID
of a coded domain according to the pre-established set of
rules governing that coded domain

[ISO/IEC 19544-5 (3.19)]

3.32
coded domain
domain for which
                                                                                               (1)
(1) the boundaries are defined and explicitly stated as a
rulebase of a coded domain Source Authority; and,                                                              (2)
(2) each entity which qualifies as a member of that domain is
identified through the assignment of a unique ID code in
accordance with the applicable Registration Schema of that
Source Authority
                                                                               1                          ID
NOTE 1 The rules governing the assignment of an ID code to
members of a coded domain reside with its Source Authority and form
part of the Coded Domain Registration Schema of the Source                                       Schema
Authority.

NOTE 2 Source Authorities which are jurisdictional domains are the
                                                                               2
primary source of coded domains.

NOTE 3 A coded domain is a data set for which the contents of the
data element values are predetermined and defined according to the             3
rulebase of its Source Authority and as such have predefined
semantics.

NOTE 4 Associated with a code in a coded domain can be:

                                                                                                                     119
- one and/or more equivalent codes;                                                   4
                                                                                    a)                               (   )
- one and/or more equivalent representations especially those in the
form of Human Interface Equivalent (HIE) (linguistic) expressions.
                                                                               b)                                                    HIE
NOTE 5 In a coded domain, the rules for assignment and structuring of
the ID codes must be specified.

NOTE 6 Where an entity as member of a coded domain is allowed to                      5                         ID
have, i.e., assigned, more than one ID code, i.e., as equivalent ID
codes (possibly including names), one of these must be specified as
the pivot ID code.
                                                                                      6
NOTE 7 A coded domain in turn can consist of two or more coded
domains, i.e., through the application of the inheritance principle of                           ID                      ID
object classes.                                                                                                                             I
NOTE 8 A coded domain may contain ID code which pertain to                     D
predefined conditions other than qualification of membership of entities
in the coded domain. Further, the rules governing a coded domain                      7
may or may not provide for user extensions.



EXAMPLE Common examples include: (1) the use of ID Code "0" (or
                                                                                      8
"00", etc.) for “Others, (2) the use of ID Code "9" (or "99", etc.) for “Not                     ID
Applicable”; (3) the use of “8” (or “98”) for “Not Known”; and/or, if
required, (4) the pre-reservation of a series of ID codes for use as
“user extensions”.
                                                                                                            1                “       ”ID     “
NOTE 9 In object methodology, entities which are members of a coded
domain are referred to as instances of a class.                                0”         “00”              2            “            ”ID
                                                                                    “9”      “99”               3                “          ”I
EXAMPLE In UML modelling notation, an ID code is viewed as an
instance of an object class.                                                   D     “8”         “98”                (   )
[ISO/IEC 15944-2:2006 (3.13)]                                                         4           “     ”                            ID



                                                                                      9



                                                                                            UML             ID


3.33
coded Domain Registration Schema (cdRS)
formal definition of both
(1) the data fields contained in the identification and
specification of an entity forming part of the members a coded
domain including the allowable contents of those fields; and,
(2) the rules for the assignment of identifiers
[ISO/IEC 15944-5:2006 (3.21)]

3.34
coded domain Source Authority (cdSA)
Person, usually an organization, as a Source Authority
which sets the rules governing a coded domain                                  “             ”
NOTE 1 Source Authority is a role of a Person, and for widely used
coded domains, the coded domain Source Authority is often a
jurisdictional domain.
                                                                                      1
NOTE 2 Specific sectors, (e.g., banking, transport, geomatics,
agriculture, etc.), may have particular coded domain Source

                                                                                                                                       120
Authority(ies) whose coded domains are used in many other sectors.            2
NOTE 3 A coded domain Source Authority usually also functions as a
Registration Authority but can use an agent, i.e., another Person, to
execute the registration function on its behalf.

                                                                              3
[ISO/IEC 15944-2:2006 (3.14)]
                                                                                                        “   ”



3.35
collaboration space
business activity space where an economic exchange of
valued resources is viewed independently and not from the
perspective of any business partner

NOTE In collaboration space, an individual partner’s view of economic
phenomena is de-emphasized. Thus, the common use business and
accounting terms like purchase, sale, cash receipt, cash disbursement,
raw materials, and finished goods is not allowed because they view
resource flows from a participant’s perspective.


[ISO/IEC 15944-4:2006 (3.12)]


3.36
commitment
making or accepting of a right, obligation, liability or
responsibility by a Person that is capable of enforcement in the
jurisdictional domain in which the commitment is made
[ISO/IEC 14662:2004 (3.5)]

3.37
composite identifier
identifier (in a business transaction) functioning as a single
unique identifier consisting of one or more other identifiers,
and/or one or more other data elements, whose interworkings
are rule-based                                                                            (   )

NOTE 1 Identifiers (in business transactions) are for the most part
composite identifiers.

NOTE 2 The rules governing the structure and working of a composite           1
identifier should be specified.

NOTE 3 Most widely used composite identifiers consist of the
combinations of:                                                              2
(1) the ID of the overall identification/numbering schema, (e.g.,
ISO/IEC 6532, ISO/IEC 7812, ISO/IEC 7501, UPC/EAN, ITU-T E.164,
etc.), which is often assumed;
                                                                              3
(2) the ID of the issuing organization (often based on a block numeric   ID
numbering schema); and,

(3) the ID of the entities forming part of members of the coded domain   a)      /          ISO/IEC
of each issuing organization.                                            6532 ISO/IEC          7812   ISO/IEC
[ISO/IEC 15944-2:2006 (3.16)]                                            7501 UPC/EAN ITU-T
                                                                         E.164     ID

                                                                         b)

                                                                                                            121
                                                                               ID

                                                                          c)
                                                                                                      I
                                                                          D

3.38
composite type
a data type that has a data structure composed of the data
structures of one or more data types and that has its own set of
permissible operations

EXAMPLE A data type "complex number" may be composed of two
"real number" data types.

NOTE The operations of a composite type may manipulate its                          “   ”     “   ”
occurrences as a unit or may manipulate portions of these
occurrences.
[ISO/IEC 2382-17:1999 (17.05.10)]

3.39
computational integrity
expression of a standard in a form that ensures precise
description of behaviour and semantics in a manner that allows
for automated processing to occur, and the managed evolution
of such standards in a way that enables dynamic introduction
by the next generation of information systems

NOTE Open-edi standards have been designed to be able to support
computational integrity requirements especially from a registration and
re-use of business objects perspectives.
[ISO/IEC 15944-2:2006 (3.18)]                                                           edi




3.40
computer program
means data representing instructions or statements that, when
executed in a computer system, causes the computer to
perform a function
[ISO/IEC 15944-5:2006 (3.28)]

3.41
computer service
service which includes data processing and the storage or
retrieval of data
[ISO/IEC 15944-5:2006 (3.29)]

3.42
computer system
device that, or a group of interconnected or related devices one
or more of which:
(a) contains computer programs or other data; and,
(b) pursuant to computer programs,
                                                                          a)
      (i) performs logic and control, and                                 b)


                                                                                                  122
      (ii) may perform any other function



[ISO/IEC 15944-5:2006 (3.30)]

3.nn
concept
unit of knowledge created by a unique combination of
characteristics.

NOTE Concepts are not necessarily bound to particular languages.
They are, however, influenced by the social or cultural background
which often leads to different categorizations.
[ISO 1087-1:2000 (3.2.1)

3.43
consensus (standardization perspective)
general agreement, characterized by the absence of sustained
opposition to substantial issues by any important part of the
concerned interests and by a process that involves seeking to
take into account the views of all parties concerned and to
reconcile any conflicting arguments

NOTE Consensus need not imply unanimity.
[ISO/IEC 15944-1:2002 (3.10)]

3.44
constraint
rule, explicitly stated, that prescribes, limits, governs or
specifies any aspect of a business transaction

NOTE 1 Constraints are specified as rules forming part of components
of Open-edi scenarios, i.e., as scenario attributes, roles, and/or
information bundles.                                                       1                 edi
NOTE 2 For constraints to be registered for implementation in Open-
edi, they must have unique and unambiguous identifiers.

NOTE 3 A constraint may be agreed to among parties (condition of
contract) and is therefore considered an "internal constraint". Or a       2           edi
constraint may be imposed on parties, (e.g., laws, regulations, etc.),
and is therefore considered an "external constraint".

                                                                           3
[ISO/IEC 15944-1:2002 (3.11)]
                                                                                   “               ”
                                                                                       (               )
                                                                               “             ”

3.45
consumer
a buyer who is an individual to whom consumer protection
requirements are applied as a set of external constraints on a
business transaction

NOTE 1 Consumer protection is a set of explicitly defined rights and
obligations applicable as external constraints on a business               1
transaction.

NOTE 2 The assumption is that a consumer protection applies only
where a buyer in a business transaction is an individual. If this is not
                                                                           2
                                                                                                       123
the case in a particular jurisdiction, such external constraints should be
specified as part of scenario components as applicable.



NOTE 3 It is recognized that external constraints on a buyer of the
nature of consumer protection may be peculiar to a specified                     3
jurisdiction.
[ISO/IEC 15944-1:2002 (3.12)]

3.46
consumer protection
set of external constraints of a jurisdictional domain as
rights of a consumer and thus as obligations (and possible
liabilities) of a vendor in a business transaction which apply
to the good, service and/or right forming the object of the
business transaction (including associated information                                                    (
management and interchange requirements including                                                 (   )               )
applicable (sets of) recorded information

NOTE 1 Jurisdictional domains may restrict the application of their
consumer protection requirements as applicable only to individuals               1
engaged in a business transaction of a commercial activity undertaken
for personal, family or household purposes, i.e., they do not apply to
natural persons in their role as "organization" or "organization Person".

NOTE 2 Jurisdictional domains may have particular consumer                   “       ”   “   ”
protection requirements which apply specifically to individuals who are
considered to be a "child" or a “minor”, (e.g., those individuals who
have not reached their thirteenth (13) birthday).
                                                                                 2
                                                                                                      “       ”   “       ”
NOTE 3 Some jurisdictional domains may have consumer protection
requirements which are particular to the nature of the good, service                             13
and/or right being part of the goal of a business transaction.
[ISO/IEC 15944-5:2006 (3.33)]                                                    3




3.47
Contact
instance of a role of a Person to whom a recorded
information item(s), a material object(s), a business
object(s), can be sent to or received from in a specified context

NOTE 1 A Person here as a Contact can be an individual, an
organization (or organization part or organization Person).

NOTE 2 Contact is capitalized to distinguish it from the many ordinary           1
uses of the term.


[adapted from ISO/IEC 11179-3:2003 (3.3.26)] 23                                  2


3.48
Contact Information
information to enable a Contact to be located or

23
  Harmonized with ISO/IEC 11179-3 and Cor.1:2004 but from an eBusiness perspective / Harminsé avec ISO/CEI
11179-3 et Cor.1:2004 mais dans une perspective d’eAffaires

                                                                                                                          124
communicated with
[ISO/IEC 11179-3:2003 (3.3.27)]

3.49                                                                      3.49
Contact name
persona by which a Person wishes to be designated as a
Contact

NOTE Where an organization is the OeRI applicant, it may designate
an organization Person, an agent, a third party as its Contact name in                         edi   (OeRI)
applying to register a scenario or scenario component as a business
object.
ISO/IEC 15944-2:2006 (3.21)] 24

3.50
Contact position title
name of title of the position held by an organization Person as
a Contact
[ISO/IEC 15944-2:2006 (3.22)]

3.51
control body
group of technical experts that makes decisions regarding the
content of a register
[ISO 19135:2005 (4.1.2)]

3.52
controlled vocabulary (CV)
vocabulary for which the entries, i.e., definition/term pairs,
are controlled by a Source Authority based on a rulebase and                         (         )
process for addition/deletion of entries

NOTE 1 In a controlled vocabulary, there is a one-to-one relationship
of definition and term.

EXAMPLE The contents of "Clause 3 Definitions" in ISO/IEC                        1
standards are examples of controlled vocabularies with the entities
being identified and referenced through their ID code, i.e., via their
clause numbers.

NOTE 2 In a multilingual controlled vocabulary, the definition/term              ISO/IEC   “
pairs in the languages utilized are deemed to be equivalent, i.e., with
respect to their semantics.                                                      ”
                                                                          ID
NOTE 3 The rule base governing a controlled vocabulary may include
a predefined concept system.
                                                                                 2
[ISO/IEC 15944-5:2006 (3.34)]


                                                                                 3


3.53
creation date


24
  Harmonized with ISO/IEC 11179-3 and Cor.1:2004 but from an eBusiness perspective / Harminsé avec ISO/CEI
11179-3 et Cor.1:2004 mais dans une perspective d’eAffaires

                                                                                                          125
date the OeRI for a business object was created
[ISO/IEC 15944-2:2006 (3.24)]

3.54
custody
association between a Person and an economic resource
where the Person has physical control only over the resource
or controls access

NOTE Having custody of a good, service and/or right does not imply
and is differentiated from having economic control of the same, (e.g., a
Person may have economic control of a good even though it is not
under its custody).                                                                            (   )
[ISO/IEC 15944-4:2006 (3.15)]                                                                          (


                                                                                       )

3.55
data
reinterpretable representation of information in a formalized
manner suitable for communication, interpretation, or
processing

NOTE Data can be processed by humans or by automatic means.
[ISO/IEC 2382-1:1993 (01.01.02)]


3.56
data (in a business transaction)
representations of recorded information that are being
prepared or have been prepared in a form suitable for use in a
computer system
[ISO/IEC 15944-1:2002 (3.14)]

3.57
data element
unit of data for which the definition, identification,
representation and permissible values are specified by means
of a set of attributes
[ISO/IEC 11179-1:2004 (3.3.8)]

3.58
data element (in organization of data)

unit of data that is considered in context to be indivisible

EXAMPLE The data element "age of a person" with values consisting
of all combinations of 3 decimal digits.                                           “       ”

NOTE Differs from the entry 17.06.02 in ISO/IEC 2382-17.

                                                                                 ISO/IEC 2382-
[ISO/IEC 2382-4:1999 (3.16)]                                               17   17.06.02

3.59
dataset
identifiable collection of data

                                                                                                           126
NOTE A dataset may be a smaller grouping of data which, though
limited by some constraint such as spatial extent or feature type, is
located physically within a larger dataset. Theoretically, a dataset may
be as small as a single feature or feature attribute contained within a
larger dataset. A hardcopy map or chart may be considered a dataset.
[ISO 19115:2003 (4.2)]


3.60
dataset series
collection of datasets sharing the same product specification
[ISO 19115:2003 (4.3)]

3.61
date
ISO 8601 compliant representation of a date in a YYYY-MM-DD
format using the Gregorian calendar                                                 YYYY-MM-
[ISO/IEC 15944-2:2006 (3.26)]                                              DD       ISO 8601

3.62
Decision Making Application (DMA)
model of that part of an Open-edi system that makes
decisions corresponding to the role(s) that the Open-edi Party
plays as well as the originating, receiving and managing data
values contained in the instantiated information bundles
which is not required to be visible to the other Open-edi
Party(ies)
[ISO/IEC 14662:2004 (3.6)]

3.63
Decision       Making        Application         Interface       (DMA
Interface)

set of requirements that permit a Decision Making
Application to interact with the Open-edi Support
Infrastructure

[ISO/IEC 14662:2004 (3.7)]

3.64
de facto language
natural language used in a jurisdictional domain which has
the properties and behaviours of an official language in that
jurisdictional domain without having formally been declared
as such by that jurisdictional domain

NOTE 1 A de facto language of a jurisdictional domain is often
established through long term use and custom.
                                                                                1
NOTE 2 Unless explicitly stated otherwise and for the purposes of
modelling a business transaction through scenario(s), scenario
attributes and/or scenario components, a de facto language of a
jurisdictional domain is assumed to have the same properties and                2
behaviours of an official language.
[ISO/IEC 15944-5:2006 (3.42)]




                                                                                               127
3.65
defined market model
trade model where the buyer and seller accept the entry terms
of a specified market in advance and where that market has an
accepted and recognized source for business rules and
conventions

NOTE In a defined market, the phases of a business transaction,
i.e.,planning, identification, negotiation, actualization, and post-
actualization, are governed by the rules and conventions of the
particular defined market.
[ISO/IEC 15944-4:2006 (3.17)]

3.66
definition
representation of a concept by a descriptive statement which
serves to differentiate it from related concepts
[ISO 1087-1:2000 (3.3.1)]

3.67
designation
representation of a concept by a sign which denotes it

NOTE In terminology work three types of designations are
distinguished: symbols, appellations, (a.k.a. names), and terms.
[ISO 1087-1:2000 (3.4.1)]



3.68
distinguishing identifier

data that unambiguously distinguishes an entity in the
authentication process

[ISO/IEC 10181-2:1996] ???

3.69
documentation language code
language code of the language used for documentation by the
Open-edi Registration Organization

NOTE Use the three character alphabetic language codes and names
from ISO 639-2/T (Terminology).
[ISO/IEC 15944-2:2006 (3.30)]                                               ISO   639-
                                                                       2/

3.70
duality
association between economic events where one is the legal
or economic consideration for the other in an exchange

NOTE Duality is the conceptual analog of double entry in traditional
bookkeeping. For example, a shipment from a partner requires a
matching flow in like a payment to balance accounts between the
parties.
[ISO/IEC 15944-4:2006 (3.18)]

                                                                                  128
3.71
economic agreement
arrangement of reciprocated economic commitments
between two partners where the abstract specification of terms
of trade is incomplete and not subject to legal enforcement
[ISO/IEC 15944-4:2006 (3.19)]

3.72
economic bundle
association between economic commitments and the
economic contract that bundles those promises and binds
them to the two partners who negotiated them
[ISO/IEC 15944-4:2006 (3.20)]

3.73
economic claim
expectation of one Person to receive a future inflow of
economic resources from another Person because of an
economic exchange which is presently incomplete
[ISO/IEC 15944-4:2006 (3.21)]

3.74
economic commitment
type of commitment by one Person to transfer economic
resources to another Person at some specified point in the
future
[ISO/IEC 15944-4:2006 (3.22)]

3.75
economic contract
bundling of reciprocated economic commitments between
two partners where the abstract specification of the proposed
economic exchange is deemed to be complete
[ISO/IEC 15944-4:2006 (3.23)]

3.76
economic control
association between a Person and an economic resource
where the Person either owns the resource or is otherwise able
to derive economic benefit (utility) from it
                                                                          (   )
[ISO/IEC 15944-4:2006 (3.24)]

3.77
economic event
occurrence in time wherein ownership of an economic
resource is transferred from one Person to another Person

NOTE Occurrences in time can either be

(1) internal as mutually agreed to among the parties to a business
transaction; and/or,

(2) reference some common publicly available and recognized          a)
                                                                                  129
date/time referencing schema, (e.g., one based on using the ISO 8601
and/or ISO 19135 standards).
                                                                             /
[ISO/IEC 15944-4:2006 (3.25)]
                                                                        b)
                                                                                                         /       (
                                                                                 ISO 8601   (   ) ISO 19135)
3.78
economic event type
abstract specification of an economic event where its grouped
properties can be designated without attachment to an actual,
specific occurrence in time

NOTE Example of attributes at the type level for events might be
expected-duration or standard-pricing-percentage.
[ISO/IEC 15944-4:2006 (3.26)]


3.79
economic exchange
type of a business transaction where the goal is an exchange
of economic resources between two Persons where both
parties derive higher utility after the completed business
transaction

NOTE An economic exchange usually involves two economic events
with different types of economic resources flowing in opposite
directions. For example, an exchange of cash for a good involves a
shipment with a requited payment following.
[ISO/IEC 15944-4:2006 (3.27)]
3.80
economic resource
good, right, or service of value, under the control of a Person
[ISO/IEC 15944-4:2006 (3.28)]


3.81
economic resource type
abstract specification of an economic resource where its
grouped properties can be designated without attachment to an
actual, specific economic resource

NOTE Example of attributes at the type level for an economic resource
like an automobile might include its designated fuel capacity or its
maximum expected range.
[ISO/IEC 15944-4:2006 (3.29)]


3.82
economic role
abstract specification of a Person for economic purposes
where its grouped properties can be designated without
attachment to an actual Person

NOTE An example economic role might be qualified buyer or approved
shipper.


[ISO/IEC 15944-4:2006 (3.30)]

                                                                                                               130
3.83
economic specification
association between an economic commitment and the
abstract properties of an economic event, an economic
resource, a partner, or a business location
[ISO/IEC 15944-4:2006 (3.31)]

3.84
effective date
date an OeRI became/becomes available to registry users
[ISO/IEC 15944-2:2006 (3.31)]

3.85
electronic address
address utilized in a recognized electronic addressing scheme,
(e.g., telephone, telex, IP, etc.), to which recorded information
item(s) and/or business object(s) can be sent to or received
from a Contact                                                            IP
                                                                      (   )
[ISO/IEC 15944-2:2006 (3.32)]


3.86
Electronic Data Interchange (EDI)
the automated exchange of any predefined and structured data
for business purposes among information systems of two or
more Persons

NOTE This definition includes all categories of electronic business
transactions.
[ISO/IEC 14662:2004 (3.8)]

3.87
entity
any concrete or abstract thing that exists, did exist, or might
exist, including associations among these things

EXAMPLE A person, object, event, idea, process, etc.

NOTE An entity exists whether data about it are available or not.
[ISO/IEC 2382-17:1999 (17.02.05)]

3.88
entity authentication

the corroboration that the entity is the one claimed

[ISO/IEC 9788-1:1997 (3.3.1)]

3.89
(entity) identification
a method of using one or more attributes whose attribute
values uniquely identify each occurrence of a specified entity
[ISO/IEC 2382-17:1999 (17.02.14)]

                                                                               131
3.90
entry label
name information uniquely associated with the identification
and resulting International Registration Business Object
Identifier (IRBOI) of a business object as a registered Open-
edi scenario or scenario component

NOTE More than one entry label may be associated with an IRBOI
depending on the applicable language(s) utilized as Human Interface
Equivalents (HIEs).                                                                                     HIE
                                                                                                   IRBOI
[ISO/IEC 15944-2:2006 (3.33)]


3.91
exchange code set
a set of ID codes identified in a coded domain as being
suitable for information exchange as shareable data

EXAMPLE The 3 numeric, 2-alpha and 3-alpha code sets in ISO 3166-
1.                                                                                   ISO 3166-
[ISO/IEC 15944-5:2006 (3.49)]                                               1             3         2         3

3.92
external constraint
constraint which takes precedence over internal constraints
in a business transaction, i.e., is external to those agreed
upon by the parties to a business transaction

NOTE 1 Normally external constraints are created by law, regulation,
orders, treaties, conventions or similar instruments.

NOTE 2 Other sources of external constraints are those of a sectorial                1
nature, those which pertain to a particular jurisdiction or a mutually
agreed to common business conventions, (e.g., INCOTERMS,
exchanges, etc.).
                                                                                     2
NOTE 3 External constraints can apply to the nature of the good,
service and/or right provided in a business transaction.
                                                                                             (   . INCOTERMS,     )
NOTE 4 External constraints can demand that a party to a business
transaction meet specific requirements of a particular role.
                                                                                     3
EXAMPLE 1 Only a qualified medical doctor may issue a prescription                       (   )
for a controlled drug.

EXAMPLE 2 Only an accredited share dealer may place transactions                     4
on the New York Stock Exchange.

EXAMPLE 3 Hazardous wastes may only be conveyed by a licensed
enterprise.                                                                     1:
NOTE 5 Where the information bundles (IBs), including their Semantic
Components (SCs) of a business transaction are also to form the
whole of a business transaction, (e.g., for legal or audit purposes), all
constraints must be recorded.
                                                                                2
EXAMPLE There may be a legal or audit requirement to maintain the
complete set of recorded information pertaining to a business
transaction, i.e., as the information bundles exchanged, as a "record".
                                                                                3
NOTE 6 A minimum external constraint applicable to a business
transaction often requires one to differentiate whether the Person, i.e.,
that is a party to a business transaction, is an "individual",
"organization", or "public administration". For example, privacy rights              5
                                                                                                                  132
apply only to a Person as an "individual".                              (               )
[ISO/IEC 15944-1:2002 (3.23)]




                                                                        “   ”

                                                                6




3.93
Formal Description Technique (FDT)
specification method based on a description language using
rigorous and unambiguous rules both with respect to
developing expressions in the language (formal syntax) and
interpreting the meaning of these expressions (formal
semantics)                                                          (           )
[ISO/IEC 14662:2004 (3.9)]                                              (           )

3.94
fulfillment
association between an economic commitment and an
economic event where the event executes the promised
resource flow from one Person to another

NOTE For example, a delivery to a customer would fulfill that
customer’s sale order.
[ISO/IEC 15944-4:2006 (3.34)]

3.95
Functional Service View (FSV)
perspective of business transactions limited to those
information technology interoperability aspects of
information technology systems (IT Systems) needed
to support the execution of Open-edi transactions

[ISO/IEC 14662:2004 (3.10)]

3.96
glyph
recognizable abstract graphic symbol which is independent of
any specific design

[ISO/IEC TR 15285:1998 (3.5)]


3.97
governed
association between an economic agreement and the
business transaction whose conduct and phases are subject
to that economic agreement of the business transaction

                                                                                            133
[ISO/IEC 15944-4:2006 (3.35)]

3.98
Human Interface Equivalent (HIE)
representation of the unambiguous and IT-enabled semantics
of an IT interface equivalent (in a business transaction),
often the ID code of a coded domain (or a composite
identifier), in a formalized manner suitable for communication
to and understanding by humans

NOTE 1 Human interface equivalents can be linguistic or non-linguistic
in nature but their semantics remains the same although their
representations may vary.                                                          1
NOTE 2 In most cases there will be multiple Human Interface
Equivalent representations as required to meet localization
requirements, i.e. those of a linguistic nature, jurisdictional nature,
and/or sectoral nature.
                                                                                   2
NOTE 3 Human Interface Equivalents include representations in                                     (   )
various forms or formats, (e.g., in addition to written text those of an
audio, symbol (and icon) nature, glyphs, image, etc.).


[ISO/IEC 15944-2:2006 (3.35)]                                                      3




3.99                                                                        3.99
IB Identifier
unique, linguistically neutral, unambiguous referenceable
identifier for an Information Bundle


[ISO/IEC 15944-2:2006 (3.36)]

3.100
ID Code
identifier assigned by the coded domain Source Authority
(cdSA) to a member of a coded domain ID                                                                   ID
NOTE 1 ID codes must be unique within the Registration Schema of
that coded domain.
                                                                                   1    ID
NOTE 2 Associated with an ID code in a coded domain can be:

- one or more equivalent codes;

- one or more equivalent representations, especially those in the form             2         ID
of human equivalent (linguistic) expressions.                                    a)
NOTE 3 Where an entity as a member of a coded domain is allowed to
have more than one ID code, i.e., as equivalent codes (possibly             b)
including names), one of these must be specified as the pivot ID code.

NOTE 4 A coded domain may contain ID codes pertaining to entities
which are not members as peer entities, i.e., have the same properties             3
and behaviours, such as ID codes which pertain to predefined
conditions other than member entities. If this is the case, the rules              ID
governing such exceptions must be predefined and explicitly stated.                                            I
EXAMPLE Common examples include: (1) the use of an ID code "0"
                                                                            D
(or "00", etc.), for “Other”; (2) the use of an ID code "9" (or "99") for
“Not Applicable”; (3) the use of “8” (or “98”) for “Not Known”; if                 4                  ID
required, (4) the pre-reservation of a series or set of ID codes for use

                                                                                                           134
for "user extensions".

NOTE 5 In UML modeling notation, an ID code is viewed as an
instance of an object class.
                                                                                          ID
[ISO/IEC 15944-2:2006 (3.37)]

                                                                                                     1                “       ”   ID     “
                                                                        0”         “00”                  2                “       ”ID
                                                                             “9”      “99”                   3                “         ”I
                                                                        D     “8”         “98”                    (       )
                                                                               4           “     ”                                ID



                                                                               5      UML                    ID


3.101
identification
rule-based process, explicitly stated, involving the use of one
or more attributes, i.e., data elements, whose value (or
combination of values) are used to identify uniquely the
occurrence or existence of a specified entity


[ISO/IEC 15944-1:2002 (3.26)]

3.102
identifier (in business transaction)
unambiguous, unique and a linguistically neutral value,
resulting from the application of a rule-based identification
process

NOTE 1 Identifiers must be unique within the identification scheme of
the issuing authority.                                                         1
NOTE 2 An identifier is a linguistically independent sequence of
characters capable of uniquely and permanently identifying that with
which it is associated. {See ISO 19135:2005 (4.1.5)}
                                                                               2
[ISO/IEC 15944-1:2002 (3.27)]

3.103
indexing language
artificial language established to characterize the content or
form of a document
[ISO/IEC 2382-1:1998 (01.05.10)]

3.104
individual
Person who is a human being, i.e., a natural person, who acts
as a distinct indivisible entity or is considered as such
[ISO/IEC 15944-1:2002 (3.28)]

3.105
individual accessibility
set of external constraints of a jurisdictional domain as
rights of an individual with disabilities to be able to utilize IT                               (            )                   IT
                                                                                                                                   135
systems at the human, i.e., user, interface and the concomitant
obligation of a seller to provide such adaptive technologies

NOTE Although “accessibility” typically addresses users who have a
disability, the concept is not limited to disability issues.

EXAMPLE Examples of disabilities in the form of functional and                    “               ”
cognitive limitations include:

- people who are blind;
- people with low vision;
- people with colour blindness;
- people who are hard of hearing or deaf, i.e.,     are hearing
impaired;                                                            a)
- people with physical disabilities;                                 b)
- people with language or cognitive disabilities.
                                                                     c)
                                                                     d)
[ISO/IEC 15944-5:2006 (3.60)]                                        e)
                                                                     f)

3.106
information (in information processing)
knowledge concerning objects, such as facts, events, things,
processes, or ideas, including concepts, that within a certain                (
context has a particular meaning
                                                                              )

[ISO/IEC 2382-1:1998 (01.01.01)]

3.107
Information Bundle (IB)
formal description of the semantics of the recorded
information to be exchanged by Open-edi Parties playing
roles in an Open-edi scenario
[ISO/IEC 14662:2004 (3.11)]

3.108
Information Processing Domain (IPD)
Information Technology System which includes at least
either a Decision Making Application (DMA) or one of the
components of an Open-edi Support Infrastructure or both),
and acts/executes on behalf of an Open-edi Party (either
                                                                                          (           )
directly or under a delegated authority)                                              (
[ISO/IEC 14662:2004 (3.12)]                                               )                   /

3.109
Information Technology System (IT System)
set of one or more computers, associated software, peripherals,
terminals, human operations, physical processes, information
transfer means, that form an autonomous whole, capable of
performing information processing and/or information transfer
[ISO/IEC 14662:2004 (3.13)]


3.110
internal constraint
constraint which forms part of the commitment(s) mutually
agreed to among the parties to a business transaction

                                                                                                          136
NOTE Internal constraints are self-imposed. They provide a simplified
view for modelling and re-use of scenario components of a business
transaction for which there are no external constraints or restrictions to
the nature of the conduct of a business transaction other than those
mutually agreed to by the buyer and seller.
[ISO/IEC 15944-1:2002 (3.33)]




3.111
International Registration Business Object Identifier
(IRBOI)
internationally unique identifier for an OeRI

NOTE IRBOIs are of the nature of a composite identifier.
                                                                                    IRBOI
[ISO/IEC 15944-2:2006 (3.42)]

3.112
International Standard Identifier
identifier of the version of this part of ISO/IEC 15944 upon
which attributes are based                                                   ISO/IEC
[ISO/IEC 15944-2:2006 (3.43)]                                                15944


3.113
item class
set of items with common properties

NOTE Class is used in this context to refer to a set of instances, not
the concept abstracted from that set of instances.
[ISO 19135:2005 (4.1.6)]


3.114
IT-enablement
transformation of a current standard utilized in business
transactions, (e.g., coded domains), from a manual to
computational perspective so as to be able to support
commitment exchange and computational integrity
[ISO/IEC 15944-5:2006]


3.115
IT interface equivalent
computer processable identification of the unambiguous
semantics of a scenario, scenario attribute and/or scenario
component(s) pertaining to a commitment exchange in a
business transaction which supports computational
integrity

NOTE 1 IT interface equivalents have the properties of identifiers (in
business transaction) and are utilized to support semantic                      1    IT
interoperability in commitment exchange.

NOTE 2 The value of an IT interface equivalent at times is a composite
identifier.                                                                     2    IT

NOTE 3 An IT interface equivalent as a composite identifier can
consist of the identifier of a coded domain plus an ID code of that

                                                                                            137
coded domain.                                                                     3                      IT
NOTE 4 An IT interface equivalent is at times utilized as a semantic                                     ID
identifier.

NOTE 5 An IT interface equivalent may have associated with it one or              4   IT
more Human Interface Equivalents (HIEs).

NOTE 6 The value of an IT Interface is independent of its encoding in
programming languages or APIs.                                                    5   IT
[ISO/IEC 15944-2:2006 (3.48)]

                                                                                  6   IT
                                                                            API

3.116
jurisdictional domain
jurisdiction, recognized in law as a distinct legal and/or
regulatory framework, which is a source of external
constraints on Persons, their behaviour and the making of
commitments among Persons including any aspect of a
business transaction

NOTE 1 The pivot jurisdictional domain is a United Nations (UN)
recognized member state. From a legal and sovereignty perspective
they are considered "peer" entities. Each UN member state, (a.k.a.                1                           (UN)
country) may have sub-administrative divisions as recognized
jurisdictional domains, (e.g., provinces, territories, cantons, länder,                                                    “
etc.), as decided by that UN member state.                                   ”             UN

                                                                                                UN
NOTE 2 Jurisdictional domains can combine to form new jurisdictional
domains, (e.g., through bilateral, multilateral and/or international
treaties).                                                                        2
                                                                                                     /
EXAMPLE Included here, for example, are the European Union (EU),
NAFTA, WTO, WCO, ICAO, WHO, Red Cross, the ISO, the IEC, the
ITU, etc.                                                                                                EU    NAFTA           W
NOTE 3 Several levels and categories of jurisdictional domains may          TO    WCO      ICAO   WHO                ISO       IE
exist within a jurisdictional domain.                                       C ITU
NOTE 4 A jurisdictional domain may impact aspects of the
commitment(s) made as part of a business transaction including those              3
pertaining to the making, selling, transfer of goods, services and/or
rights (and resulting liabilities) and associated information. This is
independent of whether such interchange of commitments are
conducted on a for-profit or not-for-profit basis and/or include monetary         4
values.
                                                                                                                     /


NOTE 5 Laws, regulations, directives, etc., issued by a jurisdictional
domain are considered as parts of that jurisdictional domain and are
the primary sources of external constraints on business transactions.
[ISO/IEC 15944-5:2006 (3.67)]                                                     5




3.117
jurisdictional domain identifier
ID code of a jurisdictional domain as recognized for use by
peer jurisdictional domains within a system of mutual
recognition

                                                                                                                           138
[ISO/IEC 15944-2:2006 (3.47)]

3.118
language
system of signs for communication, usually consisting of a
vocabulary and rules

NOTE In this standard, language refers to natural languages or special
languages, but not "programming languages" or "artificial languages".
[ISO 5127-1:2001 (1.1.2.01)]


3.119
language code
combination of characters used to represent a language or
languages

NOTE In this multipart ISO/IEC 15944 standard, the ISO 639-2/T
(terminology) three alpha-code, shall be used.                                      ISO/IEC
[ISO 639-2:1998 (3.2)]                                                    15944                         ISO 639-2/T



3.120
legally recognized language (LRL)
natural language which has status (other than an official
language or de facto language) in a jurisdictional domain as
stated in an act, regulation, or other legal instrument, which
                                                                                                (
grants a community of people (or its individuals) the right to
use that natural language in the context stipulated by the legal           )                        (                 )
instrument(s)

NOTE The LRL can be specified through either:

- the identification of a language by the name utilized; or,
- the identification of a people and thus their language(s).
                                                                                   LRL

EXAMPLE In addition to acts and regulations, legal instruments            ——
include self-government agreements, land claim settlements, court
decisions, jurisprudence, etc.                                            ——

                                                                           :
[ISO/IEC 15944-5:2006 (3.71)]


3.121
legally recognized name (LRN)
persona associated with a role of a Person recognized as
having legal status and so recognized in a jurisdictional
domain as accepted or assigned in compliance with the rules
applicable of that jurisdictional domain, i.e. as governing the
coded domain of which the LRN is a member

NOTE 1 A LRN may be of a general nature and thus be available for
general use in commitment exchange or may arise from the
                                                                               1    LRN
application of a particular law, regulation, program or service of a
jurisdictional domain and thus will have a specified use in commitment
exchange.

NOTE 2 The process of establishment of a LRN is usually
accompanied by the assignment of a unique identifier.
                                                                               2          LRN
NOTE 3 A LRN is usually a registry entry in a register established by
the jurisdictional domain (usually by a specified public administration
                                                                                                                  139
within that jurisdictional domain) for the purpose of applying the
applicable rules and registering and recording LRNs (and possible
                                                                                   3   LRN
accompanying unique identifiers accordingly).
                                                                                                 (
NOTE 4 A Person may have more than one LRN (and associated LRN
identifier).                                                                   )                            LR
                                                                          N(                           )
[ISO/IEC 15944-5:2006 (3.72)]
                                                                                   4                 LRN(
                                                                               LRN           )

3.122
list

ordered set of data elements

[ISO/IEC 2382-4:1999 (04.08.01)]

3.123
localization
pertaining to or concerned with anything that is not global and is
bound through specified sets of constraints of:

(a) a linguistic nature including natural and special languages
and associated multilingual requirements;
(b) jurisdictional nature, i.e., legal, regulatory, geopolitical, etc.;   a)
(c) a sectorial nature, i.e., industry sector, scientific,
professional, etc.;
(d) a human rights nature, i.e., privacy, disabled/handicapped
                                                                          b)
persons, etc.;
(e) consumer behaviour requirements; and/or
(f) safety or health requirements
                                                                          c)
Within and among "locales", interoperability and
harmonization objectives also apply                                       d)
                                                                          e)
[ISO/IEC 15944-5:2006 (3.75)]
                                                                          f)

                                                                               “       ”



3.124
location
place, either physical or electronic, that can be defined as an
address


[ISO/IEC 15944-2:2006 (3.50)]

3.125
location type
abstract specification of a business location where its grouped
properties can be designated without attachment to an actual
location

NOTE An example location type might be an accepted shipping facility
or approved hospital location
[ISO/IEC 15944-4:2006 (3.39)]


                                                                                                            140
3.126
materialized
association between an economic event and an economic
claim where the occurrence of the economic event causes the
economic claim to come into existence
[ISO/IEC 15944-4:2006 (3.40)]

3.127
mediated transaction
sub-type of a business transaction where a third party
mediates between the partners as mutually agreed to by the
partners
[ISO/IEC 15944-4:2006 (3.41)]

3.128
medium
physical material which serves as a functional unit, in or on
which information or data is normally recorded, in which
information or data can be retained and carried, from which
information or data can be retrieved, and which is non-volatile
in nature

NOTE 1 This definition is independent of the material nature on which
the information is recorded and/or technology utilized to record the
information, (e.g., paper, photographic, (chemical), magnetic, optical,                  1
ICs (integrated circuits), as well as other categories no longer in
common use such as vellum, parchment (and other animal skins),                       (   )                                               (
plastics, (e.g., bakelite or vinyl), textiles, (e.g., linen, canvas), metals,                                    (           )                       IC       (
etc.).
                                                                                                     )
                                                                                                                 (                   )           (
NOTE 2 The inclusion of the "non-volatile in nature" attribute is to                                     )               (                       )
cover latency and records retention requirements.                                            )
NOTE 3 This definition of "medium" is independent of:
                                                                                         2                   “                   ”
i) form or format of recorded information;

ii) physical dimension and/or size; and,
                                                                                         3       “           ”
iii) any container or housing that is physically separate from material
being housed and without which the medium can remain a functional               a)
unit.                                                                           b)                               (   )
                                                                                c)
NOTE 4 This definition of "medium" also captures and integrates the
following key properties:

i) the property of medium as a material in or on which information or
data can be recorded and retrieved;
                                                                                         4       “               ”
ii) the property of storage;

iii) the property of physical carrier;                                          a)

iv) the property of physical manifestation, i.e., material;

v) the property of a functional unit; and,                                      b)
vi) the property of (some degree of) stability of the material in or on         c)
which the information or data is recorded.                                      d)
[ISO/IEC 15944-1:2002 (3.34)]                                                   e)
                                                                                f)
                                                                                                                                             (            )

                                                                                                                                                          141
3.129
metadata

data about data elements, including their data
descriptions, and data about data ownership, access
paths, access rights and data volatility

[ISO/IEC 2382-17:1999 (17.06.05)]
3.130
metadata entity
set of metadata elements describing the same aspect of data

NOTE 1 May contain one or more metadata entities.

NOTE 2 Equivalent to a class in UML terminology.                            1
[ISO 19115:2003 (4.7)]

                                                                            2   UML

3.131
metadata section
subset of metadata which consists of a collection of related
metadata entities and metadata elements
[ISO 19115:2003 (4.8)]

3.132
model
abstraction of some aspect of reality
[ISO 19115:2003 (4.9)]

3.133
multilateral treaty
treaty (or convention) that has the ambition to become
universal (or near universal) and thus bind most of the
international community by declaring general rules of law



EXAMPLE Law of the Sea, Law on Genocide.

NOTE 1 A multilateral treaty may have the goal of creating a
regulatory regime of law for a particular area or major multilateral        1
institution, i.e., Agreement Establishing the WTO, Kyoto Protocol,
Safety of Life at Sea Convention.
                                                                          WTO
NOTE 2 A multilateral treaty may allow for reservations or the treaty
may be subject to many amendments which do not bind all parties or
require all parties to undertake the same legal obligations, (e.g., the     2
Berne and Paris conventions).


[ISO/IEC 15944-5:2006 (3.81)]


3.134
multilingualism
ability to support not only character sets specific to a (natural)
language (or family of languages) and associated rules but
                                                                                      142
also localization requirements, i.e., use of a language from
jurisdictional domain, sectoral and/or consumer marketplace
perspectives
                                                                             ( )
[ISO/IEC 15944-5:2006 (3.82)]

3.135
name
designation of an object by a linguistic expression
[ISO 5217:2000 (1.1.2.02)]

3.136
natural language
language which is or was in active use in a community of
people, and the rules of which are mainly deduced from the
usage
[ISO 5217:2000 (1.1.2.02)]

3.137
object
anything perceivable or conceivable

NOTE Objects may be material, (e.g., engine, a sheet of paper, a
diamond), or immaterial, (e.g., conversion ratio, a project play) or
imagined, (e.g., a unicorn).
[ISO 1087-1:2000 (3.1.1)]


3.138
object class
set of ideas, abstractions, or things in the real world that can be
identified with explicit boundaries and meaning and whose
properties and behavior follow the same rules


[ISO/IEC 11179-1:2004 (3.3.22)]

3.139
OeRI addition
insertion into a register of an OeRI that describes a concept
not described by an OeRI already in the register
[ISO/IEC 15944-2:2006 (3.54)]

3.140
OeRI clarification
non-substantive change to an OeRI

NOTE 1 A non-substantive change does not change the semantics or
technical meaning of the OeRI.
                                                                         1          OeRI
NOTE 2 A clarification does not result in a change to the registration
status of the OeRI.
                                                                         2   OeRI
[ISO/IEC 15944-2:2006 (3.55)]
3.141
OeRI harmonization
the resolution of any potential duplicate or overlapping of
OeRIs, accounting for justifiable differences that may exist
                                                                                           143
among the harmonized OeRIs
[ISO/IEC 15944-2:2006 (3.56)]


3.142
OeRI language code
language code of the language used for the OeRI by the
submitting organization
[ISO/IEC 15944-2:2006 (3.57)]

3.143
OeRI retirement
declaration that an OeRI is no longer suitable for use in the
production of new data

NOTE The status of the retired OeRI changes from ‘valid’ to ‘retired’. A
retired OeRI is kept in the register to support the interpretation of data                  OeRI       “       ”       “    ”
produced before its retirement.                                                      OeRI
[ISO/IEC 15944-2:2006 (3.58)]

3.144
OeRI supersession
replacement of an OeRI by one or more new OeRIs

NOTE The status of the replaced item changes from "valid" to
"superseded".
                                                                                                   “       ”       “            ”
[ISO/IEC 15944-2:2006 (3.59)]

3.145
official language
external constraint in the form of a natural language
specified by a jurisdictional domain for official use by
Persons forming part of and/or subject to that jurisdictional
domain for use in communication(s) either
(1) within that jurisdictional domain; and/or,                                                                             ( )
(2) among such Persons, where such communications are
recorded information involving commitment(s)
                                                                             a               ;
NOTE 1 Unless official language requirements state otherwise,                b
Persons are free to choose their mutually acceptable natural language
and/or special language for communications as well as exchange of
commitments.
                                                                                 1
NOTE 2 A jurisdictional domain decides whether or not it has an
official language. If not, it will have a de facto language.

NOTE 3 An official language(s) can be mandated for formal
                                                                                     ( )
communications as well as provision of goods and services to Persons
subject to that jurisdictional domain and for use in the legal and other         2
conflict resolution system(s) of that jurisdictional domain, etc.

NOTE 4 Where applicable, use of an official language may be required
in the exercise of rights and obligations of individuals in that                 3
jurisdictional domain.

NOTE 5 Where an official language of a jurisdictional domain has a
controlled vocabulary of the nature of a terminology, it may well have
the characteristics of a special language. In such cases, the
terminology to be used must be specified.
                                                                                 4
NOTE 6 For an official language, the writing system(s) to be used shall

                                                                                                                                144
be specified, where the spoken use of a natural language has more
than one writing system.

EXAMPLE 1 The spoken language of use of an official language may             5
at times have more than one writing system. For example, three
writing systems exist for the Inuktitut language. Canada uses two of
these writing systems, namely, a Latin-1 based (Roman), the other is
syllabic-based. The third is used in Russia and is Cyrillic based.

EXAMPLE 2 Another example is that of Norway which has two official           6
writing systems, both Latin-1 based, namely, Bokmål (Dano-
Norwegian) and Nynorsk (New Norwegian).

NOTE 7 A jurisdictional domain may have more than one official
language but these may or may not have equal status.                     1
EXAMPLE Canada has two official languages, Switzerland has three,                                 “Lnuktitut”         3
while the Union of South Africa has eleven official languages.

NOTE 8 The BOV requirement of the use of a specified language will                Latin       1       Roman
place that requirement on any FSV supporting service.

EXAMPLE A BOV requirement of Arabic, Chinese, Russian,
Japanese, Korean, etc., as an official language requires the FSV
support service to be able to handle the associated character sets.
                                                                         2                                2
                                                                                      Latin       1
[ISO/IEC 15944-5:2006 (3.87)]


                                                                             7




                                                                                 11

                                                                             8                          BOV
                                                                        FSV



                                                                                          BOV                   FSV


3.146                                                                  3.146
Open-edi

electronic   data    interchange     among    multiple
autonomous Persons to accomplish an explicit shared
business goal according to Open-edi standards

[ISO/IEC 14662:2004 (3.14)]

3.147
Open-edi Business Transaction Ontology (OeBTO)
formal, rule-based, specification and definition of the concepts
pertaining to business transactions and scenarios and the
relationships that hold among these concepts
[ISO/IEC 15944-4:2006 (3.44)]

3.148
Open-edi configuration
formal specification of an operational configuration of Open-edi
                                                                                                                          145
Parties and their associated IPDs, which can execute Open-
edi transactions corresponding to a given Open-edi scenario
[ISO/IEC 14662:2004 (3.15)]
3.149
Open-edi Description Technique (OeDT)
specification method such as a Formal Description
Technique, another methodology having the characteristics
of a Formal Description Technique, or a combination of such
techniques as needed to formally specify BOV concepts, in a
computer processable form
[ISO/IEC 14662:2004 (3.16)]

3.150
Open-edi disposition
process governing the implementation of formally approved
records retention, destruction (or expungement) or transfer of
recorded information under the control of a Person which are
documented in disposition authorities or similar instruments

[adapted from ISO 15489-1:2001 (3.9)]
[ISO/IEC 15944-5:2006 (3.90)]

3.151
Open-edi Party (OeP)
Person that participates in Open-edi

NOTE Often referred to generically in this, and other e-business
standards, (e.g., parts of the ISO/IEC 15944 multipart “e-business”
 standard) as “party” or “parties” for any entity modelled as a Person                     ISO/IEC 15944-
as playing a role in Open-edi scenarios.
                                                                         1
[ISO/IEC 14662:2004 (3.17)]                                                  edi
                                                                                       “       ”       “    ”

3.152
Open-edi Record Retention (OeRR)
specification of a period of time that a set of recorded
information must be kept by a Person in order to meet
operational, legal, regulatory, fiscal or other requirements as
specified in the external constraints (or internal constraints)
applicable to a Person who is a party to a business                                (               )
transaction
[ISO/IEC 15944-5:2006 (3.92)]
3.153
Open-edi register
information store or database maintained by an Open-edi
Registry
[ISO/IEC 15944-2:2006 (3.62)]


3.154
Open-edi registration administration attribute
member of a set of attributes to uniquely identify an Open-edi
scenario, Information Bundle, or Semantic Component and
the relevant Person responsible for its maintenance
[ISO/IEC 15944-2:2006 (3.63)]

                                                                                                                146
3.155
Open-edi Registration Authority (OeRA)
Person responsible for maintaining the register of OeROs and
for the issuance of OeRO identifiers
[ISO/IEC 15944-2:2006 (3.64)]

3.156
Open-edi Registration Organization (OeRO)
Person qualified by the OeRA to assume the responsibility for
the registration of scenario and scenario components
[ISO/IEC 15944-2:2006 (3.65)]




3.157
Open-edi Registration Organization address
physical and/or electronic address of the Open-edi
Registration Organization                                               (   )
NOTE A physical address includes a “pick-up” address such as
a mailbox or such other location one can deliver to.            “   ”


[ISO/IEC 15944-2:2006 (3.66)]
3.158
Open-edi Registration Organization Identifier (OeORI)
identifier assigned to an Open-edi Registration Organization
[ISO/IEC 15944-2:2006 (3.67)]


3.159
Open-edi Registration Organization name
designation for the Open-edi Registration Organization
[ISO/IEC 15944-2:2006 (3.68)]


3.160
Open-edi Registry (OeR)
information system for the registration of scenarios and
scenario components
[ISO/IEC 15944-2:2006 (3.69)]
3.161
Open-edi Registry Item (OeRI)
recorded information within a registry relating to a specific
Open-edi scenario or scenario components of a scenario
including linkage information to a scenario content
[ISO/IEC 15944-2:2006 (3.70)]

3.162
Open-edi registry record
collection of recorded information for an OeRI

                                                                                147
[ISO/IEC 15944-2:2006 (3.71)]

3.163
Open-edi scenario (OeS)
formal specification of a class of business transactions having
the same business goal


[ISO/IEC 14662:2004 (3.18)]

3.164
Open-edi sponsoring authority
Person recognized in accordance with the requirements of this
part of ISO/IEC 15944, to receive Open-edi Registration
Organization applications for submission to an Open-edi
Registration Authority
[ISO/IEC 15944-2:2006 (3.73)] 25

3.165
Open-edi standard

standard that complies with the Open-edi Reference
Model

[ISO/IEC 14662:2004 (3.19)]

3.166
Open-edi Support Infrastructure (OeSI)
model of the set of functional capabilities for Open-edi
systems which, when taken together with the Decision
Making Applications, allows Open-edi Parties to participate
in Open-edi transactions
[ISO/IEC 14662:2004 (3.20)]

3.167
Open-edi support organization

organization, acting on behalf of an Open-edi Party(ies)
to provide necessary support enabling execution of
Open-edi transactions, but which is not modelled as a
role(s)

[ISO/IEC 14662:2004 (3.21)]

3.168
Open-edi system
information technology system (IT system) which enables
an Open-edi Party to participate in Open-edi transactions
[ISO/IEC 14662:2004 (3.22)]

3.169
Open-edi transaction
business transaction that is in compliance with an Open-edi


25
  Adapted from ISO/IEC 7812-2:2007.. JISO/IEC TC1/ serves as the Open-edi Sponsoring Authority for ISO/IEC
15944? SC32 ? ?????
                                                                                                       148
scenario
[ISO/IEC 14662:2004 (3.23)]

3.170
organization
unique framework of authority within which a person or persons
act, or are designated to act, towards some purpose

NOTE The kinds of organizations covered by this International
Standard include the following examples:

EXAMPLE 1 An organization incorporated under law.

EXAMPLE 2 An unincorporated organization or activity providing
goods and/or services including:
                                                                              1
1) partnerships;
                                                                              2           (   )
2) social or other non-profit organizations or similar bodies in which
ownership or control is vested in a group of individuals;
                                                                         a)
3) sole proprietorships
                                                                         b)
4) governmental bodies.

EXAMPLE 3 Groupings of the above types of organizations where
there is a need to identify these in information interchange.            c)
[ISO/IEC 6523-1:1998 (3.1)]                                              d)

                                                                              3



3.171
organization address
physical and/or electronic address of an organization

NOTE A physical address includes a "pick-up" address such as a
mailbox or such other location one can deliver to.
                                                                                  “   ”
[ISO/IEC 15944-2:2006 (3.75)]

3.172
organization name
designation for the organization

NOTE The name by which the organization is known to the registration
authority.
[ISO/IEC 11179-3:2003 (3.3.94)]



3.173
organization part
any department, service or other entity within an organization,
which needs to be identified for information interchange
[ISO/IEC 6523-1:1998 (3.2)]

3.174
organization Person
organization part which has the properties of a Person and
thus is able to make commitments on behalf of that
                                                                                                  149
organization

NOTE 1 An organization can have one or more organization Persons.
                                                                                 1
NOTE 2 An organization Person is deemed to represent and act on
behalf of the organization and to do so in a specified capacity.

NOTE 3 An organization Person can be a "natural person" such as an               2
employee or officer of the organization.

NOTE 4 An organization Person can be a legal person, i.e., another
organization.                                                                    3:
[ISO/IEC 15944-1:2002 (3.46)]
                                                                                       “           ”

                                                                                 4:




3.175
origin
source (document, project, discipline or model) for the OeRI


[ISO/IEC 15944-2:2006 (3.77)]


3.176
participate
association between an economic event and each of the two
Persons participating in the economic event

NOTE Usually there is a “from” association and a “to” association,
depending upon the direction of the flow of the economic resource.
[ISO/IEC 15944-4:2006 (3.50)]                                                                              “   ”   “   ”

3.177
partner
sub-type of Person that includes buyer and seller
[ISO/IEC 15944-4:2006 (3.51)]

3.178
Person
entity, i.e., a natural or legal person, recognized by law as
having legal rights and duties, able to make commitment(s),
assume and fulfill resulting obligation(s), and able of being held
accountable for its action(s)



NOTE 1 Synonyms for "legal person" include "artificial person", "body            1                                         “   ”
corporate", etc., depending on the terminology used in competent             “             ”       “           ”
jurisdictions.
                                                                                 2                 “Person”
NOTE 2 "Person" is capitalized to indicate that it is being utilized as
formally defined in the standards and to differentiate it from its day-to-
day use.
                                                                                 3
NOTE 3 Minimum and common external constraints applicable to a
business transaction often require one to differentiate among three
common subtypes of Person, namely "individual", "organization", and          “        ”“       ”       “               ”
                                                                                                                                   150
"public administration".
[ISO/IEC 14662:2004 (3.24)]

3.179
persona
set of data elements and their values by which a Person
wishes to be known and thus identified in a business
transaction
[ISO/IEC 15944-1:2002 (3.51)]
3.180
personal information
any information about an identifiable individual that is recorded
in any form, including electronically or on paper

NOTE Some examples would be information about a person's religion,
age, financial transactions, medical history, address, or blood type.


[ISO/IEC 15944-5:2006 (3.103)]


3.181
persona Registration Schema (pRS)

formal definition of the data fields contained in the
specification of a persona of a Person and the allowable
contents of those fields, including the rules for the
assignment of identifiers. (This may also be referred to
as a persona profile of a Person)                                       )

[ISO/IEC 15944-1:2002 (3.52)]
3.182
Person authentication
provision of the assurance of a recognized Person identity
(rPi) (sufficient for the purpose of the business transaction)                  (
by corroboration
                                                                            )
[ISO/IEC 15944-1:2002 (3.48)]

3.183
Person identity
combination of persona information and identifier used by a
Person in a business transaction
[ISO/IEC 15944-1:2002 (3.49)]

3.184
Person signature
signature, i.e., a name representation, distinguishing mark or
usual mark, which is created by and pertains to a Person
[ISO/IEC 15944-1:2002 (3.50)]

3.185
physical address
address that is used/recognized by a postal authority and/or
courier service to deliver information item(s), material
object(s), or business object(s) to a Contact at either an
actual address or a pick-up point address, (e.g., P.O. Box,
                                                                                151
rural route, etc.)
[ISO/IEC 15944-2:2006 (3.80)]


3.186
pivot code set
set of ID codes in a coded domain which is made publicly
known and available, the most stable, representing the defined
semantics. Most often it is the same as the ID code

NOTE 1 The use of the pivot code set as distinguished from the ID code
supports the requirement of a Source Authority to maintain internally and on a
confidential basis the ID code of its members.
                                                                                          1
NOTE 2 At times a coded domain has more than one valid code set, (e.g., ISO
639, ISO 3166, etc.).



EXAMPLE In ISO 3166-1 the 3-digit numeric code is the pivot. The 2-alpha and              2
3-alpha code sets can change when the name of the entity referenced is
changed by that entity.                                                                   ISO 639,ISO 3166

[ISO/IEC 15944-5:2006 (3.104)]                                                                ISO 3166-
                                                                                 1        3
                                                                                                          2         3


3.187
pivot ID code
most stable ID code assigned to identify a member of a coded
domain where more than one ID code may be assigned and/or
associated with a member of that coded domain

EXAMPLE ISO 3166-1:1997 (E/F) "Codes for the representation of
names of countries and their subdivisions - Part 1: Country
codes/Codes pour la représentations des noms de pays et de leur
subdivisions - Partie 1: Codes pays" contains three code sets:                      ISO
                                                                                 3166 1:1997          E/F
- a three digit numeric code;
- a two alpha code
- a three alpha code.                                                                 1                             3
Here, the three digit numeric code serves as the pivot code. It is the           a) 3
most stable, remains the same even though the two alpha and/or three             b) 2
alpha codes may and do change.
                                                                                 c) 3
[ISO/IEC 15944-5:2006 (3.105)]
                                                                                              3
                                                                                              2                 3


3.188
plurilateral treaty
treaty among a defined set of jurisdictional domains

NOTE A plurilateral treaty restricts the jurisdictional domains which
may become signatories generally on either:

• a geo-political basis, (e.g., NAFTA, Mecrosur, European Union, etc.);
or

• some other set of criteria which candidate members must meet and               a)                           NAFTA     MECROSUR
then their membership approved by the existing membership, (e.g.,
                                                                                                                              152
WTO).


[ISO/IEC 15944-5:2006 (3.106)]                                               b)
                                                                                      WTO



3.189
preferred term

term recommended by an authoritative body

[ISO 1087-1:2000 (5.6.1)]

3.190
principle
fundamental, primary assumption and quality which constitutes
a source of action determining particular objectives or results

NOTE 1 A principle is usually enforced by rules that affect its
boundaries.
                                                                                  1
NOTE 2 A principle is usually supported through one or more rules.

NOTE 3 A principle is usually part of a set of principles which together
form a unified whole.
                                                                                  2
EXAMPLE Within a jurisdictional domain, examples of a set of
principles include a charter, a constitution, etc.                                3
[ISO/IEC 15944-2:2006 (3.81)]




3.191
privacy protection
set of external constraints of a jurisdictional domain
pertaining to recorded information on or about an identifiable
individual, i.e., personal information, with respect to the
creation, collection, management, retention, access and use
and/or distribution of such recorded information about that
individual including its accuracy, timeliness, and relevancy

NOTE 1 Recorded information collected or created for a specific
purpose on an identifiable individual, i.e., the explicitly shared goal of
the business transaction involving an individual shall not be utilized for        1
another purpose without the explicit and informed consent of the
individual to whom the recorded information pertains.

NOTE 2 Privacy requirements include the right of an individual to be
able to view the recorded information about him/her and to request
corrections to the same in order to ensure that such recorded
information is accurate and up-to-date.

NOTE 3 Where jurisdictional domains have legal requirements which                 2
override privacy protection requirements these must be specified,
(e.g., national security, investigations by law enforcement
agencies, etc.).
[ISO/IEC 15944-5:2006 (3.109)]
                                                                                  3




                                                                                       153
3.192
process
series of actions or events taking place in a defined manner
leading to the accomplishment of an expected result
[ISO/IEC 15944-1:2002 (3.53)]


3.193
property
peculiarity common to all members of an object class
[ISO/IEC 11179-1:2004 (3.3.29)]

3.194
public administration
entity, i.e., a Person, which is an organization and has the
added attribute of being authorized to act on behalf of a
regulator
[ISO/IEC 15944-1:2002 (3.54)]

3.195
public policy
category of external constraints of a jurisdictional domain
specified in the form of a right of an individual or a requirement
of an organization and/or public administration with respect
to an individual pertaining to any exchange of commitments
among the parties concerned involving a good, service and/or
right including information management and interchange
requirements

NOTE 1 Public policy requirements may apply to any one, all or
combinations of the fundamental activities comprising a business                    1
transaction, i.e., planning, identification, negotiation, actualization and
post-actualization. {See further Clause 6.3 "Rules governing the
process component" in ISO/IEC 15944-1:2002}

NOTE 2 It is up to each jurisdictional domain to determine whether or               ISO/IEC 15944-1:2002
not the age of an individual qualifies a public policy requirement, (e.g.,    6.3    “                ”
those which specifically apply to an individual under the age of thirteen
(13) as a "child", those which require an individual to have attained the
age of adulthood, (e.g., 18 years or 21 years of age) of an individual to           2
be able to make commitments of a certain nature.

NOTE 3 Jurisdictional domains may have consumer protection or                                                  13
privacy requirements which apply specifically to individuals who are                                                18
considered to be "children", "minorsÈ, etc.(e.g. those who have not
                                                                                    21
reached their 18th or 21st birthday according to the rules of the
applicable jurisdictional domain).
                                                                                    3
[ISO/IEC 15944-5:2006 (3.113)]                                                                        “    ”    “    ”

                                                                                18       21

3.196
reciprocal
association between economic commitments where the
promise by one partner to execute an economic resource
transfer in the future is reciprocated by the other partner
promising a requited transfer in the opposite direction

                                                                                                                    154
[ISO/IEC 15944-4:2006 (3.55)]

3.197
recognized individual name (RIN)
persona of an individual having the properties of a legally
recognized name (LRN)                                                                                     LRN
NOTE 1 On the whole, a persona presented by an individual should
have a basis in law (or recognized jurisdictional domain) in order to be
considered as the basis for a recognized individual name (RIN).                     1
NOTE 2 An individual may have more than one RIN and more than
one RIN at the same time.                                                                        RIN
NOTE 3 The establishment of a RIN is usually accompanied by the
assignment of a unique identifier, i.e. by the jurisdictional domain (or            2                              RIN       RIN
public administration) which recognizes the persona as a RIN.
[ISO/IEC 15944-5:2006 (3.114)]                                                      3    RIN
                                                                                                                  RIN


3.198
recognized Person identity (rPi)                                                                          (rPi)
identity of a Person, i.e., Person identity, established to the
extent necessary for a specific purpose in a business
transaction
[ISO/IEC 15944-1:2002 (3.56)]

3.199
recorded information
any information that is recorded on or in a medium
irrespective of form, recording medium or technology utilized,
and in a manner allowing for storage and retrieval

NOTE 1 This is a generic definition and is independent of any
ontology, (e.g., those of "facts" versus "data" versus "information"
versus "intelligence" versus "knowledge", etc.).
                                                                                    1:
                                                                                                                              (
NOTE 2 Through the use of the term "information," all attributes of this        “        ”            “   ”       “      ”    “
term are inherited in this definition.
                                                                           ”             “        ”           )
NOTE 3 This definition covers:
(i) any form of recorded information, means of recording, and any                   2:
medium on which information can be recorded; and,
(ii) all types of recorded information including all data types,                             “        ”
instructions or software, databases, etc.


[ISO/IEC 15944-1:2002 (3.56)]                                                       3
                                                                           a)



                                                                           b)




3.200
reference document
                                                                                                                                   155
external document(s) containing relevant recorded
information about the scenario or scenario component
[ISO/IEC 15944-2:2006 (3.84)]


3.201
reference document identifier
identifier assigned to a reference document by the OeRO
(adapted from ISO/IEC 11179-3:2003 (3.3.112)

[ISO/IEC 15944-2:2006 (3.85)]


3.202
reference document language code
ISO 639-2/T based language code(s) identifying the
language(s) used in the reference document                                            ISO   639-
[ISO/IEC 15944-2:2006 (3.86)]                                          2/T


3.203
reference document title
title(s) of the reference document

NOTE A reference document may have more than one title depending
on the languages in which it is produced
[ISO/IEC 11179-3:2003 (3.3.114)]



3.204
reference document type description
description of the document type of the reference document
[ISO/IEC 11179-3:2003 (3.3.115)]


3.205
reference organization
relationship between a reference document and an
organization
[ISO/IEC 11179-3:2003 (3.3.116)]

3.206
register
set of files containing identifiers assigned to items with
descriptions of the associated items
[ISO 19135:2005 (4.1.9)]

3.207
register manager
organization to which management of a register has been
delegated by the register owner

NOTE In the case of an ISO register, the register manager performs              ISO           I
the functions of the registration authority specified in the ISO/IEC   SO/IEC
                                                                                            156
Directives.
[ISO 19135:2005 (4.1.10)]

3.208
register owner
organization that establishes a register
[ISO 19135:2005 (4.1.11)]

3.209
registrar
representative of an Open-edi Registration Organization
[ISO/IEC 15944-2:2006 (3.93)]

3.210
registrar Contact
Contact information associated with a registrar of an Open-
edi registration organization
[ISO/IEC 15944-2:2006 (3.94)]

3.211
registration
rule-based process, explicitly stated, involving the use of one
or more data elements, whose value (or combination of
values) are used to identify uniquely the results of assigning an
OeRI
[ISO/IEC 15944-2:2006 (3.95)]


3.212
Registration Authority (RA)                                         (RA)
Person responsible for the maintenance of one or more
Registration Schemas (RS) including the assignment of a
unique identifier for each recognized entity in a Registration
Schema (RS)
[ISO/IEC 15944-1:2002 (3.57)]

3.213
Registration Authority Identifier (RAI)
identifier assigned to a Registration Authority (RA)
[ISO/IEC 11179-1:2004 (3.3.32)]

3.214
Registration Schema (RS)
formal definition of a set of rules governing the data fields for
the description of an entity and the allowable contents of those
fields, including the rules for the assignment of identifiers
[ISO/IEC 15944-1:2002 (3.58)]


3.215
registration status
designation of the status in the registration administration of
an OeRI
[ISO/IEC 15944-2:2006 (3.98)]
                                                                           157
3.216
registry
information system on which a register is maintained
[ISO/IEC 15944-2:2006 (3.99)]

3.217
regulator
Person who has authority to prescribe external constraints
which serve as principles, policies or rules governing or
prescribing the behaviour of Persons involved in a business
transaction as well as the provisioning of goods, services,
and/or rights interchanged
[ISO/IEC 15944-1:2002 (3.59)]

3.218
regulatory business transaction (RBT)
class of business transactions for which the explicitly shared
goal has been established and specified by a jurisdictional
domain, as a Person in the role of a regulator

NOTE 1 A regulatory business transaction (RBT) can itself be
modelled as a stand-alone business transaction and associated              1             RBT
scenario(s). For example, the filing of a tax return, the making of a
customs declaration, the request for and issuance of a license, the
provision of a specified service of a public administration, a mandatory
filing of any kind with a regulator, etc.

NOTE 2 A regulatory business transaction (modelled as a scenario)
can form part of another business transaction.
                                                                           2   RBT

NOTE 3 A RBT may apply to a seller only, a buyer only or both, as
well as any combination of parties to a business transaction.
                                                                           3   RBT
NOTE 4 A RBT may require or prohibit the use of an agent or third
party.

                                                                           4   RBT             3

NOTE 5 A regulatory business transaction (RBT) may be specific to
the nature of the good, services and/or right forming part of a business
transaction.                                                               5   RBT
[ISO/IEC 15944-5:2006 (3.124)]                                                       /

3.219
repertoire
a specified set of characters that are represented in a coded
character set
[ISO/IEC TR 15285:1998 (3.16)]

3.220
resource-flow
association between an economic event and an economic
resource

NOTE A common example would be a resource-flow between some
inventory and the shipment that caused control of that inventory to flow

                                                                                               158
from one Person to another.
[ISO/IEC 15944-4:2006 (3.58)]

3.221                                                                        3.221
responsibility
association between Persons where one is responsible to the
other or between a Person and an organization Person where
that Person is assigned

NOTE Subtypes of Persons include individuals, organizations, and
public administrations. An “individual” is non-divisible but organizations
and public administrations are and as such will assign specific
responsibilities to organization Persons. {See further Clause 6.2.7 and
Figure 17 in ISO/IEC 15944-1:2002}                                            “       ”
[ISO/IEC 15944-4:2006 (3.59)]                                                                             “    ”

3.222                                                                        3.222
retention period
length of time for which data on a data medium is to be
preserved
[ISO/IEC 2382-12:1988 (12.04.01)]
3.223                                                                        3.223
role
specification which models an external intended behaviour (as
allowed within a scenario) of an Open-edi Party                                                                        (
[ISO/IEC 14662:2004 (3.25)]                                                                          )

3.224                                                                        3.224
rule
statement governing conduct, procedure, conditions and
relations

NOTE 1 Rules specify conditions that must be complied with. These
may include relations among objects and their attributes.                         1

NOTE 2 Rules are of a mandatory or conditional nature.

NOTE 3 In Open-edi, rules formally specify the commitment(s) and                  2
role(s) of the parties involved, and the expected behaviour(s) of the
parties involved as seen by other parties involved in (electronic)
business transactions. Such rules are applied to: -content of the                 3                      edi
information flows in the form of precise and computer-processable
meaning, i.e. the semantics of data; and, -the order and behaviour of
the information flows themselves.

NOTE 4 Rules must be clear and explicit enough to be understood by
                                                                             a)
all parties to a business transaction. Rules also must be capable of
being able to be specified using a using a Formal Description
Technique(s) (FDTs).

EXAMPLE A current and widely used FDT is "Unified Modelling                  b)
Language (UML)".

NOTE 5 Specification of rules in an Open-edi business transaction                 4
should be compliant with the requirements of ISO/IEC 15944-3 "Open-
edi Description Techniques (OeDT)".
                                                                                          FDT
[ISO/IEC 15944-2:2006 (3.101)]
                                                                                                                   “
                                                                                      UML       ”

                                                                                  5                 edi                    ISO/I
                                                                                                                             159
                                                                       EC 15944-
                                                                       3“     edi      OeDT    ”

3.225                                                                  3.225
rulebase
pre-established set of rules which interwork and which together
form an autonomous whole

NOTE One considers a rulebase to be to rules as database is to data.
[ISO/IEC 15944-2:2006 (3.102)]



3.226                                                                  3.226
scenario attribute
formal specification of information, relevant to an Open-edi
scenario as a whole, which is neither specific to roles nor to
Information Bundles
[ISO/IEC 14662:2004 (3.26)]

3.227                                                                  3.227
scenario component
one of the three fundamental elements of a scenario, namely
role, information bundle, and semantic component
[ISO/IEC 15944-2:2006 (3.104)]

3.228                                                                  3.228
scenario content
set of recorded information containing registry entry
identifiers, labels and their associated definitions and related
recorded information posted (or reposted) in any registry for
business objects
[ISO/IEC 15944-2:2006 (3.105)]

3.229                                                                  3.229
scenario specification attribute
any attribute of a scenario, role, information bundle, and/or
semantic component                                                                     (   )
[ISO/IEC 15944-2:2006 (3.106)]

3.230                                                                  3.230
SC identifier
unique, linguistically neutral, unambiguous, referenceable
identifier of a Semantic Component
[ISO/IEC 15944-2:2006 (3.107)]

3.231                                                                  3.231
seller
Person who aims to hand over voluntarily or in response to a
demand, a good, service and/or right to another Person and in
return receives an acceptable equivalent value, usually in                     (   )
money, for the good, service and/or right provided
[ISO/IEC 15944-1:2002 (3.62)]



                                                                                                   160
3.232                                                                       3.232
Semantic Component (SC)
unit of recorded information unambiguously defined in the
context of the business goal of the business transaction

NOTE A SC may be atomic or composed of other SCs.


[ISO/IEC 14662:2004 (3.27)]

3.233                                                                       3.233
semantic identifier (SI)
IT-interface identifier for a semantic component or other
semantic for which (1) the associated context, applicable rules                                     IT
and/or possible uses as a semantic are predefined and                                   1
structured and the Source Authority for the applicable
rulebase is identified; and (2) for which one or more Human                                         ( )
Interface Equivalents(HIEs) exist                                                                                2
NOTE The identifier for a Semantic Component (SC), an Information
Bundle (IB) and/or an ID Code for which one or more Human Interface
Equivalents (HIEs) exist are considered to have the properties or                1                HIE
behaviours of semantic identifiers.
                                                                                        ( )ID
[ISO/IEC 15944-5:2006 (3.136)]


3.234                                                                       3.234
set of recorded information (SRI)
recorded information of an organization or public
administration, which is under the control of the same and
which is treated as a unit in its information life cycle

NOTE 1 A SRI can be a physical or digital document, a record, a file,
etc., that can be read, perceived or heard by a person or computer
system or similar device.
                                                                                 1   SRI
NOTE 2 A SRI is a unit of recorded information that is unambiguously
defined in the context of the business goals of the organization, i.e., a
semantic component.

NOTE 3 A SRI can be self-standing (atomic), or a SRI can consist of a            2   SRI
bundling of two or more SRIs into another “new” SRI. Both types can
exist simultaneously within the information management systems of an
organization.


[ISO/IEC 15944-5:2006 (3.137)]                                                   3   SRI                  SRI
                                                                                            SRI
                                                                             “       ”SRI



3.235                                                                       3.235
settlement
association between a requiting economic event and an
economic claim where the occurrence of the event causes the
economic claim to expire
[ISO/IEC 15944-4:2006 (3.63)]
3.236                                                                       3.236
site
association between an economic event and the business
location where the transfer of economic resources involved

                                                                                                                161
in that event is deemed to have occurred
[ISO/IEC 15944-4:2006 (3.64)]
3.237                                                                      3.237
Source Authority (SA)                                                              (SA)
Person recognized by other Persons as the authoritative
source for a set of constraints

NOTE 1 A Person as a Source Authority for internal constraints may
be an individual, organization, or public administration.
                                                                               1                             “ ”
NOTE 2 A Person as Source Authority for external constraints may be
an organization or public administration.

EXAMPLE In the field of air travel and transportation, IATA as a               2                             “ ”
Source Authority, is an "organization," while ICAO as a Source
Authority, is a "public administration".

NOTE 3 A Person as an individual shall not be a Source Authority for                                  IATA
external constraints.
                                                                                                  ICAO
NOTE 4 Source Authorities are often the issuing authority for
identifiers (or composite identifiers) for use in business transactions.

NOTE 5 A Source Authority can undertake the role of Registration               3                “ ”
Authority or have this role undertaken on its behalf by another Person.

NOTE 6 Where the sets of constraints of a Source Authority control a
coded domain, the SA has the role of a coded domain Source                     4
Authority.
[ISO/IEC 15944-2:2006 (3.109)]
                                                                               5
                                                                                          “ ”

                                                                               6




3.238                                                                      3.238
special language
language for special purposes (LSP), language used in a
subject field and characterized by the use of specific linguistic
means of expression

NOTE The specific linguistic means of expression always include
subject-specific terminology and phraseology and also may cover
stylistic or syntactic features.
[ISO 1087-1:2000 (3.1.3)]

3.239                                                                      3.239
standard
documented agreement containing technical specifications or
other precise criteria to be used consistently as rules,
guidelines, or definitions of characteristics, to ensure that
materials, products, processes and services are fit for their
purpose

NOTE This is the generic definition of “standard” of the ISO and IEC
(and now found in the ISO/IEC JTC1 Directives, Part 1, Section
2.5:1998). {See also ISO/IEC Guide 2: 1996 (1.7)}
[ISO/IEC 15944-1:2002 (3.64)]

                                                                                                                   162
3.240                                                               3.240
stewardship (of an OeRI)
relationship of an OeRI, a Contact, and an organization
involved in the stewardship of an OeRI


[ISO/IEC 15944-2:2006 (3.111)]

3.241                                                               3.241
stewardship organization
unique framework of authority within which a Person or
Persons act, or are designated to act in the stewardship of an
OeRI


[ISO/IEC 15944-2:2006 (3.112)]

3.242                                                               3.242
submission (of an OeRI)
relationship of an OeRI, a Contact, and an organization
involved in the submission of an OeRI
[ISO/IEC 15944-2:2006 (3.112)]

3.243                                                               3.243
submitting organization
organization authorised by a register owner to propose
changes to the content of a register
[ISO 19135:2005 (4.1.16)]

3.244                                                               3.244
term
designation of a defined concept in a special language by a
linguistic expression

NOTE A term may consist of one or more words i.e. simple term, or
complex term or even contain symbols.
[ISO 1087:1990 (5.3.1.2)]

3.245                                                               3.245
text
data in the form of characters, symbols, words, phrases,
paragraphs, sentences, tables, or other character
arrangements, intended to convey a meaning and whose
interpretation is essentially based upon the reader's knowledge
of some natural language or artificial language

EXAMPLE A business letter printed on paper or displayed on a
screen.
[ISO/IEC 2381-23:1994 (23.01.01)]
3.246                                                               3.246
third party
Person besides the two primarily concerned in a business
transaction who is agent of neither and who fulfils a specified
role or function as mutually agreed to by the two primary
Persons or as a result of external constraints

NOTE It is understood that more than two Persons can at times be
primary parties in a business transaction.

                                                                            163
[ISO/IEC 15944-1:2002 (3.65)]

3.247                                                                       3.247
treaty
international agreement concluded between jurisdictional
domains in written form and governed by international law

NOTE 1 On the whole a treaty is concluded among UN member
states.
                                                                                1                      UN
NOTE 2 Treaties among UN member states when coming into force
are required to be transmitted to the Secretariat of the United Nations
for registration or filing or recording as the case may be and for              2    UN                           ,
publication. {See further Article 80 or the Charter of the UN}

NOTE 3 Treaties can also be entered into by jurisdictional domains                                                (
other than UN member states, i.e., non-members such as international                80    )
organizations and the rare sub-national units of federations which are
constitutionally empowered to do so.                                            3

NOTE 4 A treaty can be embodied in a single instrument or in two or
more related instruments and whatever it particular designations.
However, each treaty is a single entity.
                                                                                4
NOTE 5 Jurisdictional domains can make agreements which they do
not mean to be legally binding for reasons of administrative
convenience or expressions of political intent only, (e.g., as a
Memorandum of Understanding (MOU)).                                             5
[adapted from the Vienna Convention on the Law of Treaties, 1(a)]                                                 (
                                                                                              )
[ISO/IEC 15944-5:2006 (3.144)]

                                                                            (                                 )
3.248                                                                       3.248
truncated name
short form of a name or persona of a Person resulting from
the application of a rule-based truncation process
[ISO/IEC 15944-5:2006 (3.145)]

3.249                                                                       3.249
truncated recognized name (TRN)
truncated name, i.e., persona, of a Person which has the
properties of a legally recognized name (LRN)                                                                LRN

NOTE 1 Truncated recognized name(s) may be required for use in
machine-readable travel documents, (e.g., passports or visas), identity
tokens, drivers’ licenses, medicare cards, etc.).                               1
NOTE 2 The source of a truncated recognized name may be a legally
recognized name.
[ISO/IEC 15944-5:2006 (3.146)]
                                                                                2                            LRN

3.250                                                                       3.250
truncation
rule-base process, explicitly stated, for shortening an existing
name of an entity to fit within a predefined maximum length (of
characters)

NOTE Truncation may be required for the use of names in IT systems,
electronic data interchange (EDI), the use of labels in packaging, in the                         IT        EDI
formation of a Person identity (Pi), etc.
                                                                                                                      Pi
                                                                                                                           164
[ISO/IEC 15944-5:2006 (3.147)]

3.251                                                              3.251
typification
association between a concrete entity and the abstract
specification of its grouped properties


[ISO/IEC 15944-4:2006 (3.66)]

3.252                                                              3.252
unambiguous
level of certainty and explicitness required in the completeness
of the semantics of the recorded information interchanged
appropriate to the goal of a business transaction


[ISO/IEC 15944-1:2002 (3.66)]

3.253                                                              3.253
undefined market model
trade model where participants are not registered in advance
and where that market does not have accepted and recognized
sources or business rules and conventions
[ISO/IEC 15944-4:2006 (3.67)]

3.254                                                              3.254
until date
date at which an OeRI is no longer effective in the registry


[ISO/IEC 15944-2:2006 (3.116)]

3.255                                                              3.255
vendor
seller on whom consumer protection requirements are
applied as a set of external constraints on a business
transaction

NOTE 1 Consumer protection is a set of explicitly defined rights
and obligations applicable as external constraints on a business       1
transaction.

NOTE 2 It is recognized that external constraints on a seller of
the nature of consumer protection may be peculiar to a                 2
specified jurisdiction.
[ISO/IEC 15944-1:2002 (3.67)]

3.256                                                              3.256
version identifier
unique number assigned to identify a version of an OeRI

NOTE The default value = 1.0.
[ISO/IEC 15944-2:2006 (3.117)]                                             1.0.

3.257                                                              3.257
vocabulary

                                                                                  165
terminological dictionary which contains designations and
definitions for one or more specific subject fields

NOTE The vocabulary may be monolingual, bilingual or multilingual.
[ISO 1087-1:2000 (13.7.2)]




                                                                     166

								
To top