ISONET Manual

Transcription

ISONET Manual

ISONET Manual
ISONET Manual
Second edition 1998
ISBN 00-00-00000-0
MAN98E.DOC
ISONET Manual
Contents
1
General
10
Data elements for projects
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Introduction .................................................... 4
Scope .............................................................. 4
References ..................................................... 4
Definitions ...................................................... 6
Formats for bibliographic information ............. 7
Exchange format ............................................ 7
Production and exchange formats .................. 7
2
Outline of record requirements
2.1
2.2
2.3
Bibliographic records and descriptions ........... 8
Data elements ................................................ 8
Mandatory data elements ............................... 9
3
ISONET Manual concept
3.1
3.2
3.3
3.3.1
3.3.2
Format of data elements ................................ 9
File label ........................................................ 10
Forms of representation ............................... 10
SGML representation ................................... 10
Conventional representation ......................... 10
4
List of data elements
00
Data elements for the file label
00.001
00.003
00.004
00.006
00.009
00.011
00.013
00.015
00.017
Character set ................................................ 13
Date of creation of file .................................. 13
Data element group ...................................... 14
File owner identifier ...................................... 14
Number of data elements ............................. 15
Number of records ....................................... 15
Size of uncompressed file ............................ 15
File name ...................................................... 16
Compression method ................................... 16
10.001
10.002
10.004
10.100
10.102
10.104
10.200
10.202
10.204
10.206
10.300
10.302
10.304
10.306
10.308
10.312
10.314
10.320
10.322
10.332
10.334
10.336
10.338
10.340
10.400
10.402
10.404
10.406
10.408
10.410
10.500
10.502
Record identifier (project) .............................. 17
Alteration date of record (project) ................. 17
Creation date of record (project) ................... 18
Item number (project) ................................... 18
Current document reference ........................ 19
Project reference .......................................... 19
Title (project) ................................................. 20
Project owner ................................................ 21
Technical committee (project) ...................... 21
Abstract (project) ........................................... 22
Current stage code (project) ......................... 22
Date of current stage (project) ...................... 22
Target date for draft ...................................... 23
Latest date for comment (project) ................ 23
Target date for formal vote ........................... 24
Latest date of implementation (project) ........ 24
Latest date for announcement (project) ........ 25
Target date for ratification (project) ............... 25
Target date for official publication ................. 25
Latest date for withdrawal (project) .............. 26
Date for existing products (project) ............... 26
Next stage (project) ....................................... 27
Target date for next stage (project) ............... 27
Date of project initiation ................................ 28
Development status ...................................... 28
Track ............................................................. 28
Financial authority ......................................... 29
Core reference document ............................. 29
Type of project .............................................. 30
Type of publication ........................................ 30
Sorting key (project) ...................................... 31
ICS (project) .................................................. 31
ISONET MANUAL 1998
1
10.504
10.506
10.508
10.606
10.610
10.612
10.617
10.619
10.900
TIT descriptors (project) .................................32
ROOT descriptors (project) ............................32
Free descriptors (project) ..............................33
Replaced by (project) .....................................33
Replaces (project) ..........................................34
Corresponding documents (project) ..............34
Development obligation ................................35
Obligation development reference ................36
General notes (project) ..................................36
20
Data elements for products
20.001
20.002
20.004
20.100
20.104
20.106
20.108
20.110
20.112
20.114
20.116
20.200
20.204
20.206
20.208
20.210
20.212
20.214
20.216
20.218
20.220
20.222
20.224
20.226
20.228
20.230
20.232
20.234
20.236
20.238
20.240
20.242
20.300
20.302
20.306
20.310
20.312
20.314
20.316
20.318
20.320
20.324
20.326
20.328
20.330
20.332
20.334
20.500
20.502
20.504
Record identifier (product) .............................37
Alteration date of record (product) ................37
Creation date of record (product) ..................38
Project reference (product) ............................38
Product reference ..........................................39
Stock number ................................................40
Amendment type ..........................................40
Amended by ..................................................41
Amends .........................................................41
ISBN ..............................................................42
ISSN ..............................................................42
Title (product) ................................................43
Technical committee (product) ......................44
Abstract (product) ..........................................44
Languages .....................................................45
Languages notes ...........................................45
Number of pages ...........................................45
Document status ...........................................46
Document type (product) ..............................46
Document series ...........................................47
Edition ...........................................................48
Edition notes .................................................48
Version ..........................................................49
Price and currency .........................................49
Price group ....................................................50
Price notes ....................................................50
Medium .........................................................51
Medium, notes ..............................................51
Collation .........................................................52
Electronic format ...........................................52
Electronic format notes .................................53
Electronic file size ..........................................53
Current stage code (product) .........................54
Date of current stage (product) .....................54
Latest date for comment (product) ...............55
Date of publication ........................................55
Latest date of implementation (product) .......55
Latest date for announcement (product) .......56
Date of announcement ..................................56
Effective date ................................................57
Target date for ratification (product) ..............57
Date of validation ...........................................58
Confirmation date ..........................................58
Date of expiration of validity ..........................58
Withdrawal date (product) .............................59
Latest date for withdrawal (product) .............59
Date for existing products .............................60
Sorting key (product) .....................................60
ICS (product) ..................................................61
TIT descriptors (product) ...............................61
2
20.506
20.508
20.510
20.600
20.602
20.604
20.606
20.608
20.610
20.612
20.614
20.616
20.618
20.620
20.622
20.700
20.702
20.704
20.706
20.708
20.712
20.714
20.716
20.718
20.800
20.900
20.902
20.910
ROOT descriptors (product) .......................... 62
Free descriptors (product) ............................ 62
Authors ......................................................... 63
Document source ......................................... 63
Republished in .............................................. 64
Translations .................................................. 64
Replaced by (product) ................................... 65
Included product ........................................... 65
Replaces (product) ........................................ 66
Corresponding documents (product) ............ 67
Cross-references .......................................... 68
References to implementations ................... 68
Regulations referred to ................................. 69
Documents referred to ................................. 70
Certification systems .................................... 70
Issuing body ................................................. 71
Supplier ......................................................... 71
Validating body ............................................. 72
Area of validity .............................................. 72
Area of validity, country notes ...................... 73
Implementation not required ........................ 73
Implementation delayed ............................... 74
Implementation notes .................................. 74
Mode of implementation .............................. 75
Linking .......................................................... 75
General notes (product) ................................ 76
Notes to date field ........................................ 76
Full text file names ....................................... 77
30
Data elements for harmonized
stage codes
30.002 Alteration date of record (harmonized
stage code) ................................................... 78
30.100 Stage codes identifiers ................................. 78
30.110 Stage codes, names ..................................... 79
40
Data elements for committee information
40.002 Alteration date of record (committee
information) .................................................. 80
40.104 Committee identifier ..................................... 80
40.110 Committee record number ........................... 81
40.130 Committee name .......................................... 81
40.140 Committee type ............................................ 82
40.150 Reporting committee .................................... 82
40.160 Date of creation of committee ...................... 83
40.168 Current status ............................................... 83
40.169 Status date ................................................... 84
40.170 Scope of the committee ............................... 84
40.180 Committee chairman .................................... 84
40.182 Country of the chairman ............................... 85
40.185 Committee secretary .................................... 85
40.190 Organization holding the secretariat ............. 86
40.192 Organization responsible for the secretariat . 86
40.200 Technical officer in charge of committee ..... 87
50
Data elements for ICS
50.001
50.002
50.110
50.120
50.122
ICS notation .................................................. 88
Alteration date of record (ICS) ...................... 88
ICS FGS name .............................................. 89
Note for scope of ICS notation ..................... 89
Reference notes ........................................... 90
ISONET MANUAL 1998
60
Data elements for TIT Thesaurus
60.001
60.002
60.005
60.105
60.110
60.120
60.140
60.150
60.155
Descriptor identifier, TIT ............................... 91
Alteration date of record (TIT thesaurus) ...... 91
TIT subject number ....................................... 92
Descriptor name, TIT .................................... 92
Synonym, TIT ................................................ 93
Scope note, TIT ............................................ 93
Narrower term, TIT ....................................... 93
Related term, TIT .......................................... 94
Broader term, TIT ......................................... 94
70
Data elements for ROOT Thesaurus
70.001
70.002
70.105
70.110
70.120
70.130
70.140
70.150
70.152
70.154
ROOT identifier ............................................. 96
Alteration date of record (ROOT thesaurus) . 96
Descriptor name, ROOT ............................... 97
Non-preferred term, ROOT ........................... 97
Scope note, ROOT ....................................... 98
Synthesis note, ROOT .................................. 98
Narrower term, ROOT .................................. 99
Related term, ROOT ..................................... 99
Broader term, ROOT ..................................... 99
Facet indicator, ROOT ................................ 100
80
Data elements for organizations
80.001
80.002
80.102
80.110
80.120
80.130
80.140
80.150
80.160
80.165
80.170
80.180
80.190
80.200
Organization identifier ................................. 101
Alteration date of record (organizations) ..... 101
Acronym ..................................................... 102
Name of organization .................................. 102
Scope .......................................................... 103
Postal address ............................................ 103
Visiting address .......................................... 104
Telephone number ..................................... 104
Fax number ................................................. 105
Telex number .............................................. 105
X.400 e-mail address .................................. 106
Internet e-mail address ............................... 106
Other electronic mail address ..................... 107
URL ............................................................. 107
ISONET MANUAL 1998
ANNEX A — Contact information for ISO
maintenance agencies and registration
authorities ............................................................. 108
ANNEX B — MIME specification ...................... 109
ANNEX C — Examples ....................................... 111
C.1
C.2
C.3
C.4
Example of project information ................... 111
Example of product information .................. 112
Example of committee information ............ 116
Example of organizations information ......... 117
Alphabetical index of data elements
..................................................................... 119
3
1
GENERAL
1.1
Introduction
The ISO Information Network (ISONET) is designed to promote the flow of information on standards,
technical regulations and related documents. ISONET is therefore concerned with a wide range of
activities, each of which may be regarded as a link in the information chain between the makers and
users of standards and technical regulations. ISONET is a decentralized information system. Each
national member of ISONET is responsible for information about all documents valid within its territory
which fall within the scope of ISONET. The ISO/IEC Information Centre in Geneva has a similar function
for international documents.
The more general functions of an information centre operating within ISONET and seeking to meet
these obligations are covered in a separate publication, the ISONET Guide. This Manual specifies
technical requirements for the exchange of bibliographic information on standards and technical
regulations. Some recommendations for storage of this type of information are given.
It is considered essential that ISONET practices should conform to international standard practices for
documents in general as defined in International Standards prepared by ISO.
1.2
Scope
This Manual specifies a way of describing standards documents, regulatory documents and their
subject content for the purposes of exchanging bibliographic information about these documents. The
Manual is designed to aid the compilation of records in such a form that information systems based on
these records may be mutually compatible.
The major objective of the ISONET Manual is to serve as a guide for ISONET members designing
information systems and services for their sets of standards and technical regulations and to make
interchange of information on these documents possible. The Manual describes the main data
elements needed to identify and describe such documents.
Implementation of the ISONET Manual by an ISONET member should make it possible for any other
member or organization to understand and exchange the recorded data without ambiguity.
1.3
References
ISO 9:1995, Information and documentation — Transliteration of Cyrillic characters into Latin
characters — Slavic and non-Slavic languages.
ISO 233-2:1993, Information and documentation — Transliteration of Arabic characters into Latin
characters — Part 2: Arabic language — Simplified transliteration.
ISO 259:1984, Documentation — Transliteration of Hebrew characters into Latin characters.
ISO 639:1988, Code for the representation of names of languages.
ISO/IEC 646:1991, Information technology — ISO 7-bit coded character set for information interchange.
ISO 843:1997, Information and documentation —- Conversion of Greek characters into Latin characters.
ISO/IEC 2022:1994, Information technology — Character code structure and extension techniques.
ISO 2108:1992, Information and documentation —- International standard book numbering (ISBN).
ISO 2382-4:1987, Information processing systems —- Vocabulary —- Part 04: Organization of data.
ISO 2709:1996, Information and documentation — Format for Information Exchange.
4
ISONET MANUAL 1998
ISO 3166-1:1997, Codes for the representation of names of countries and their subdivisions — Part 1:
Country codes.
ISO 3297:— 1) , Information and documentation —- International standard serial numbering (ISSN).
ISO 3602:1989, Documentation — Romanization of Japanese (kana script).
ISO 4217:1995, Codes for the representation of currencies and funds.
ISO 5127-6:1983, Documentation and information — Vocabulary — Part 6: Documentary languages.
ISO 5426:1983, Extension of the Latin alphabet coded character set for bibliographic information
interchange.
ISO 5426-2:1996, Information and documentation — Extension of the Latin alphabet coded character
set for bibliographic information interchange — Part 2: Latin characters used in minor European
languages and obsolete typography.
ISO 7098:1991, Information and documentation — Romanization of Chinese.
ISO 8601:1988, Data elements and interchange formats — Information interchange — Representation
of dates and times.
ISO 8859-1:1987, Information processing — 8-bit single-byte coded graphic character sets — Part 1:
Latin alphabet No. 1.
ISO 8859-2:1987, Information processing — 8-bit single byte coded graphic character sets — Part 2:
ISO/IEC 8859-5:1988, Information processing — 8-bit single-byte coded graphic character sets —
Part 5: Latin/Cyrillic alphabet.
ISO 8859-6:1987, Information processing — 8-Bit single-byte coded graphic character sets — Part 6:
Latin/Arabic alphabet.
Latin/Greek alphabet.
Latin/Hebrew alphabet.
ISO/IEC 8859-9:1989, Information processing — 8-bit single-byte coded graphic character sets —
Part 9: Latin alphabet No. 5.
ISO 8879:1986, Information processing — Text and office systems — Standard Generalized Markup
Language (SGML).
ISO/IEC 9070:1991, Information technology — SGML support facilities — Registration procedures for
public text owner identifiers.
ISO 9984:1996, Information and documentation — Transliteration of Georgian characters into Latin
characters.
ISO 9985:1996, Information and documentation — Transliteration of Armenian characters into Latin
characters.
ISO/IEC 10646-1:1993; Information technology — Universal Multiple-Octet Coded Character Set (UCS)
— Part 1: Architecture and Basic Multilingual Plane.
1) To be published. (Revision of ISO 3297:1986)
ISONET MANUAL 1998
5
ISO/IEC 11179-3:1994, Information technology — Specification and standardization of data elements —
Part 3: Basic attributes of data elements.
ISO/IEC 11179-6:1997, Information technology — Specification and standardization of data elements —
Part 6: Registration of data elements.
ISO 11940:— 2) , Information and documentation — Transliteration of Thai.
ISO/TR 11941:1996, Information and documentation — Transliteration of Korean script into Latin
characters.
International Classification for Standards, Third edition, 1996.
ISO/IEC Guide 2:1996, Standardization and related activities — General vocabulary.
ISO/IEC Guide 21:1981, Adoption of International Standards in national standards.
Addendum 1:1983 to ISO/IEC Guide 21:1981, Indication of the degree of equivalence between national
standards and international standards.
International harmonized stage code system for the development of standards, Annex 1 to circular
letter ISO/Council 94 of 1994-10-27.
1.4
Definitions
For the purposes of the ISONET Manual, the definitions given in ISO Guide 2:1996, ISO 2382-4:1987
and ISO 5127-6:1983 apply, with the following exceptions.
data element: item of data as specified in this manual.
Note — In the case of conventional file transfer, individual data elements are separated by separators in
accordance with subclause 3.3.2. In the case of file transfer using SGML, separation is provided by the
SGML tagging (see subclause 3.3.1).
project: a unique set of coordinated activities, with definite starting and finishing points, undertaken by
an individual organization to meet specific objectives within defined schedule, cost and performance
parameters.
Note — A project may produce more than one product. One project may combine with one or more
other projects to produce one or more products.
product: form of work produced as a result of a project.
Examples: standards, technical regulations and related documents in hard copy and/or electronic
format.
Note — A product may be an article (e.g. dealing with standards, in a technical journal), an unpublished
document, a chapter (in a book or voluminous regulation), a volume (e.g. a handbook of standards), a
monograph (e.g. individual standards), a serial or collection (e.g. handbook or compendium), a catalogue,
a chart, a collection of other products (e.g. a standard and an amendment).
record: set of related data elements treated as a unit.
Note — In the context of ISONET, a record contains the data elements agreed upon, between two or
more organisations, for the description of a project and the products developed within that project.
2) To be published.
6
ISONET MANUAL 1998
1.5
Formats for bibliographic information
A clear distinction is made between a local or internal format and a communication or exchange format.
They differ in the emphasis placed on each of these two constituent elements and particularly in the
specific form the format takes. These differences are the result of different objectives. An internal
format is mainly concerned with ensuring efficient, effective and economic storage and retrieval of
information; in other words the chief purpose is efficient and economic computer processing. This calls
for a suitable file and record structure which will normally be different from that used for an exchange
format. The main objective of an exchange format is to provide a record structure which is hospitable to
the requirements of a wide variety of systems and, hence, allows for the unambiguous identification of
discrete data elements, appearing in well-defined places in the record, necessary for automatic
conversion from the exchange to the local internal format and vice versa.
This Manual gives technical requirements only for the exchange format.
1.6
Exchange format
The exchange format is the arrangement of the data required for the transfer of a copy of the file or part
of the file to another operation centre, for example on magnetic disks. One purpose of the ISONET
Manual is to describe the writing rules and organization of data for exchanges between the members of
the network. When information is to be exchanged between organizations there should be agreement
between the organizations on the files and data elements to be sent and received.
The hardware, software and languages used by the ISONET members differ and will continue to do so.
The ISONET Manual provides two formats: a conventional format and the SGML format.
1.7
Production and exchange formats
Production and exchange is achieved by means of a conversion operation. An interface program has to
be written that may be complex or simple depending on the type of transcoding to be done and the
customization of an organization's internal format (e.g. some data being partially taken over to build up
special reverse files, etc.).
There have to be several program chains: one for changing over from the production format to the
exchange format (if the processing concerns one's own file), another for changing over from the
exchange format to the local production format (if the processing concerns a file supplied by a partner).
To facilitate conversion operations, it is desirable to limit the operations to the content of the elements,
i.e. to adopt the same writing rules for the different formats. For example, the number of the standard,
its title, etc., may be the same in each of the formats. Other items, on the other hand, may be in full
text form in the production and operation formats and in coded form in the exchange format.
The Manual does not aim to prescribe the structure of the production format and the operation format
since these are subject to local constraints, but provides a list of data elements with the descriptions
and offers exchange formats of ISONET databases. For any given database, a manual for users in
general will be required to explain the interpretation of search results from the operation format.
ISONET members should supplement their general user's manual with an explanation (for other
ISONET members) of the correlation between operational data elements and those defined in the
ISONET Manual.
ISONET MANUAL 1998
7
2
OUTLINE OF RECORD REQUIREMENTS
2.1
Bibliographic records and descriptions
For the purposes of the ISONET Manual, a bibliographic record is defined as a collection of information
which pertains to a single product, and which is stored in machine-readable form as a self-contained
and unique logical structure. Bibliographic records should include a description of the subject content of
the record, by including, for example, ICS codes, an abstract or summary, descriptors or other additional
information.
It must be borne in mind that the prime function of secondary information services is to inform their
users of the existence of relevant documents, and to provide this information in such a form as to
enable the user
a) to retrieve relevant references,
b) to assess the likely value of the products referred to, and
c) to obtain original products on the basis of the references given.
The most important function of the bibliographic description is to meet these objectives by means of
describing a given product.
2.2
Data elements
Each data element contains an item of information. For example, data elements for a product represent
characteristics of that product.
The data elements are classified into groups as follows:
00
10
20
30
40
50
60
70
80
Data elements for the file label
Data elements for projects
Data elements for products
Data elements for harmonized stage codes
Data elements for ICS
Data elements for TIT thesaurus
Data elements for ROOT thesaurus
NOTE - Groups 60 and 70 will be replaced by a new group of data elements for the new ISO thesaurus
on which work has started at the time of printing this manual.
Data elements are separately identified within a machine record so that each element can be
independently accessed and manipulated by computer program. This is achieved by dividing the
bibliographic record into a series of data elements.
8
ISONET MANUAL 1998
2.3
Mandatory data elements
The data elements that are likely to be useful to most ISONET members are described in section 4 of
this Manual. For each group, the elements that are mandatory are shown at the beginning of each
group. The other data elements are optional, and the sender and the recipient should agree which
elements are to be exchanged. Having reached agreement, the users of this manual should then
a) complete the agreed elements strictly in accordance with this Manual,
b) complete the agreed elements for every product to which they apply, and
c) transmit the agreed elements in the order given in this Manual.
3
ISONET MANUAL CONCEPT
3.1
Format of data elements
The format is presented in accordance with ISO/IEC 11179-3:1994. The specification of basic attributes
of data elements in accordance with ISO/IEC 11179-3:1994 is as follows:
Name:
Synonyms:
Identifier:
Definition:
Form of representation:
Maximum occurrence:
Max. size data element value:
Conventional representation:
SGML representation:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Unique single or multi-word designation assigned to a data
element
Single word or multi-word designation or acronym that differs
from the given name, but represents the same data element
concept
A language independent numeric identifier of a data element
Statement that expresses the essential nature of a data
element and permits its differentiation from all other data
elements.
Name or description of the form of representation, text, date,
integer, real or a code value
Number of different sub-elements allowed
The maximum number (integer) of storage units (of the
corresponding data type) to represent the data element value
Note: This is for each occurrence and not the maximum size
of the data element
Representation of data element values for conventional file
transfer
Representation of data element values using SGML
The permissible instances of this data element in accordance
with the form of representation, maximum size and the
conventional or SGML representation as specified in the
corresponding attributes. The instances may be defined by
reference to a source or another data element, by
enumeration of the representation of the instances or by rules
for generating the instances.
Reference to other data elements, which are semantically
related or are derived from the same data element concept
and have different representations
Remarks on the data element
Code letter, M, for mandatory, indicates that the data element
will be exchanged
9
3.2
File label
The file label should accompany every file exchanged: it is a separate uncompressed file that contains
information concerning the content and structure of the file as described in the data elements of
group 00. The ISO/IEC 646:1991 character set should be used for all information contained in the file
label.
3.3
Forms of representation
Two forms of representation are given in the tables: conventional representation and SGML
representation. Table 1 below summarizes the permitted forms of representation used in the tables of
data elements.
Acronyms should be used for the representation of names of organizations in all cases except those
where data elements refer to the ISO 9070 identifier.
Data elements should be transferred in the order given in this Manual.
3.3.1 SGML representation
All separation of elements and sub-elements is provided by the SGML tags. Data elements without
content (empty) should still be present i.e. the tags should still be present.
3.3.2 Conventional representation
For conventional file transfer, data elements should be separated by "<Exx.xxx>", where E and the data
element identifier, xx.xxx, are enclosed by angle-brackets. Sub-elements should be separated by an
asterisk (*) and sub sub-elements by a delimiter as indicated in the description of the data element. A
vertical bar (|) should indicate the end of file. A hyphen should be entered as the value of a data element
that has been agreed to be transferred but is without content (empty) i.e. the tag. "<Exx.xxx>" and a
hyphen should be transferred. If required, language codes, preceded by a hash sign (#), indicate the
different languages of sub-elements, for example:
<E10.100>#en=title of the document*fr=titre de document
There are no fixed length data elements or sub-elements.
With respect to character sets, ISONET practice will be based on the Latin alphabet as given in
ISO 5426 and ISO 5426-2. When transliteration or Romanization is required the latest edition of the
appropriate ISO standards should be used.
It is recommended to use the binary coded character set (International reference version) defined in
ISO 646 with, if necessary, standardized extensions as specified in ISO 2022, ISO 5426 and ISO 8859
for international information exchange.
10
ISONET MANUAL 1998
Table 1 - Permitted forms of representation
Permitted form of representation
Amendment code
Committee identifier
Committee status code
Compression method
1)
Country code
Currency code
Data element identifier code
2)
Date
Development status code
Document reference
Document status code
Equivalence code
F-code
File name
Harmonized stage code
I-code
ICS code
Implementation code
Integer
ISBN code
ISSN code
Language code
Medium code
MIME code
Organization acronym
Organization identifier
Paper size code
P-code
Price code
Project reference
Real number
Record ID (project)
Replace code
ROOT code
Sort code
Table code
Text
TIT code
Title
TIT subject code
Type code
Update code
A(x)
AA
I(x)
R
X
1)
2)
ISONET MANUAL 1998
Conventional
representation
A
A(50)
A(15)
A(30)
AA
A(3)
XX.XXX
CCYYMMDD
A
A
A
A(3)
A
A(30)
XX.XX
A
XX.XXX.XX
A
I(x)
X(2)-X(5)-X(5)-A
XXXX-XXXA
AA
A or A,A
A(50)
A(15)
A(15)
A
A
A(15)
A
R
A(15):XX:I(20)
A(2)
A(12)
A(100)
XX
A(n)
X(3)
A(600)
XXX
AA
A
SGML representation
<AMEND.CODE>
<COMM.ID.CODE>
<COMM.STATUS.CODE>
<COMP.METHOD>
<COUNTRY.CODE>
<CURR.CODE>
<ELEM.ID>
<DATE>
<DEV.STATUS.CODE>
<DOC.REF>
<DOC.STATUS.CODE>
<EQUIV.CODE>
<F.CODE>
<FILE.NAME>
<HSTAGE.CODE>
<I.CODE>
<ICS.CODE>
<IMP.CODE>
<INT>
<ISBN.CODE>
<ISSN.CODE>
<LANG.CODE>
<MEDIUM.CODE>
<MIME.CODE>
<ORG.ACR>
<ORG.ID>
<PAPER.CODE>
<P.CODE>
<PRICE.CODE>
<PRO.REF>
<REAL>
<REC.ID>
<REP.CODES>
<ROOT.CODE>
<SORT.CODE>
<TAB.CODE>
<TEXT LANG=XX>
<TIT.CODE>
<TITLE>
<SUB.CODE>
<TYPE.CODE>
<UPDATE.CODE>
is a number of alphanumeric characters (x is the maximum number
of characters)
is two alphanumeric characters
is an integer (x is the maximum number of integers)
is a real number (with decimal comma)
is a numeric value
Alpha-2 country code (see ISO 3166-1:1997)
Artificial dates should not be sent
11
Table 2 - Codes for character sets (see data element 00.001)
Identification
code
12
Organisation
Source document
Comment
us-ascii
ANSI
ANSI X3.4:1968
Close to ISO/IEC 646:1991
iso-8859-1
ISO
ISO 8859-1:1987
Western Europe Languages
iso-8859-2
ISO
ISO 8859-2:1987
Eastern Europe Languages
iso-8859-3
ISO
ISO 8859-3:1988
Other Latin Script Languages
iso-8859-4
ISO
ISO 8859-4:1988
North Europe Languages
iso-8859-5
ISO
ISO 8859-5:1988
Cyrillic
iso-8859-6
ISO
ISO 8859-6:1987
Arabic
iso-8859-7
ISO
ISO 8859-7:1987
Greek
iso-8859-8
ISO
ISO 8859-8:1988
Hebrew
iso-8859-9
ISO
ISO 8859-9:1989
Turkish
iso-10646-1
ISO
ISO 10646-1:1993
UCS
x-cp437
Microsoft
-
DOS Latin US
x-cp850
Microsoft
-
DOS Latin 1
x-cp852
Microsoft
-
DOS Latin 2
x-cp1252
Microsoft
-
Windows Latin 1
ISONET MANUAL 1998
4
LIST OF DATA ELEMENTS
00
DATA ELEMENTS FOR THE FILE LABEL
All of the data elements in group 00 are mandatory, except 00.001 in the case
of using SGML.
The Max. size data element value has been left blank for data elements in
group 00 since these values are not expected to be stored in a database.
00.001 Character set
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Character set
00.001
Code for the character set used in accordance with table 2
Text
1
A(12)
EXAMPLE:
iso-8859-2
This element is not required for SGML since character definitions are part of this
language (see ISO 8879:1986)
Identification codes in table 2
The use of a character set based on an ISO standard is recommended
M (except for SGML)
00.003 Date of creation of file
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Date of creation of file
00.003
The date when the attached file was created for exchange
Date
1
CCYYMMDD
EXAMPLE:
19961222
<E00.003> <DATE> ... </DATE> </E00.003>
EXAMPLE:
<E00.003> <DATE> 19961222 </DATE> </E00.003>
In accordance with ISO 8601:1988
This date may be different to the date of transmission
M
13
00.004 Data element group
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Data element group
00.004
Number of the data element group in this manual
Table code
1
XX
EXAMPLES:
10
20
30
70
<E00.004> <TAB.CODE> ... </TAB.CODE> </E00.004>
EXAMPLE:
<E00.004> <TAB.CODE> 10 </TAB.CODE> </E00.004>
Data element groups, see 2.2 in this manual
A file label is required for each of the data element groups
M
00.006 File owner identifier
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
14
File owner identifier
00.006
Unique alphanumeric part of the file owner identifier of the organization recording
the data, as allocated by the ISO 9070 registration authority (see annex A or the
current ISO Catalogue for the name and address of this registration authority). If
the organization is not registered with the ISO 9070 registration authority, the
acronym of the organization should be used.
Alphanumeric part of the identifier
1
A(15)
EXAMPLES:
A01054
BSI
<E00.006>
<ORG.ID> ... </ORG.ID>
<ORG.ACR> ... </ORG.ACR>
</E00.006>
EXAMPLE:
<E00.006> <ORG.ID> A01054 </ORG.ID> <ORG.ACR> </ORG.ACR>
</E00.006>
Identifiers as in 80.001 or acronym as in 80.102
80.001, 80.102
M
ISONET MANUAL 1998
00.009 Number of data elements
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Number of data elements
00.009
Number of data elements in the attached file
Integer
1
I(3)
EXAMPLE:
25
<E00.009> <INT> ... </INT> </E00.009>
EXAMPLE:
<E00.009> <INT> 25 </INT> </E00.009>
M
00.011 Number of records
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Number of records
00.011
Number of records in the attached file
Integer
1
I(7)
EXAMPLE:
636785
<E00.011> <INT> ... </INT> </E00.011>
EXAMPLE:
<E00.011> <INT> 636785 </INT> </E00.011>
M
00.013 Size of uncompressed file
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Size of uncompressed file
00.013
Size of the uncompressed file, in bytes. Note that the file label is a separate
uncompressed file (see 3.2).
Integer
1
I(12)
EXAMPLE:
150000
15
Permissible values:
See also:
Comments:
Field obligation:
<E00.013> <INT> ... </INT> </E00.013>
EXAMPLE:
<E00.013> <INT> 150000 </INT> </E00.013>
M
00.015 File name
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
File name
00.015
The name of the attached file
Text
1
A(30)
EXAMPLES:
file102
rev70-2
<E00.015> <FILE.NAME> ... </FILE.NAME> </E00.015>
EXAMPLE:
<E00.015> <FILE.NAME> file102 </FILE.NAME> </E00.015>
If the file name has an extension, it should be included. Extensions should be in
accordance with the MIME specification (see annex B). It is recommended that
the file name itself should not be exceed 8 characters.
M
00.017 Compression method
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
16
Compression method
00.017
The method that has been used to compress the file, including version number.
Note that the file label is a separate uncompressed file.
Text
1
A(30)
EXAMPLES:
PKZIP
ARJ
Z
<E00.017> <TEXT LANG=AA> ... </TEXT> </E00.017>
EXAMPLE:
<E00.017> <TEXT LANG=en> PKZIP </TEXT> </E00.017>
NC (not compressed) should be entered if the file is not compressed
(See ITSIG recommendation - to be made)
M
ISONET MANUAL 1998
10
DATA ELEMENTS FOR PROJECTS
The following data elements are mandatory: 10.001, 10.002, 10.100, 10.200,
10.202, 10.204, 10.300, 10.302, 10.502
10.001 Record identifier (project)
Name:
Synonyms:
Identifier:
Definition:
Record identifier (project)
10.001
A unique identification of the record to be allocated to each new record and used
for identification whenever a record is changed or deleted. The record identifier is
different to the item number (10.100) and is allocated by the centre creating the
record.
The identifier should be made up from three elements:
a) Registered file owner identifier allocated by the ISO 9070 registration
authority, with 6 characters, or acronym of the organization (00.006)
b) Data element group (see 00.004)
c) Project item number (10.100)
Organization identifier : group number : integer
Maximum occurrence:
1
30
A(15):XX:I(20)
EXAMPLES:
BSI:10:77682
A01054:10:77682
<E10.001>
<REC.ID> ... </REC.ID>
</E10.001>
EXAMPLE:
<E10.001> <REC.ID> A01054:10:77682 </REC.ID> </E10.001>
Permissible data element values: See also:
00.006, 10.100
Comments:
Field obligation:
M
10.002 Alteration date of record (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Alteration date of record (project)
10.002
The latest date when the project record was altered or changed in any way
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.002>
<DATE> ... </DATE>
</E10.002>
EXAMPLE:
<E10.002> <DATE> 19961220 </DATE> </E10.002>
17
Permissible values:
See also:
Comments:
Field obligation:
This data element can be used to construct different update flags when combined
with information about the type of alteration. (There is no data element for update
flags but they may be present in the database.)
M
10.004 Creation date of record (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Creation date of record (project)
10.004
The date when the project record was created
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.004>
<DATE> ... </DATE>
</E10.004>
EXAMPLE:
<E10.004> <DATE> 19961220 </DATE> </E10.004>
-
10.100 Item number (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
18
Item number (project)
Project number; work item number
10.100
Unique number as allocated by the originating body of the project item
Integer
1
20
I(20)
EXAMPLE:
77682
<E10.100>
<INT> ... </INT>
</E10.100>
EXAMPLE:
<E10.100> <INT> 77682 </INT> </E10.100>
10.001, 10.104
This could be a computer generated number
M
ISONET MANUAL 1998
10.102 Current document reference
Name:
Synonyms
Identifier:
Definition:
Current document reference
Currrent product reference
10.102
Reference as written on the document, which may be a product. The reference
may include the organization prefix and reference number of the current
document or product that the project has produced
Text
Maximum occurrence:
4
150
A(150)
EXAMPLES:
Please note the following examples are not necessarily valid documents
ETS 300999:1994-08
DIN 1045
IEC 335-2-35:1993
NFZ 44-001
Amendments and correction sheets:
IEC 335-2-35:1993/prA1:1993
IEC 335-2-35:1993/A1:1993
IEC 335-2-35:1993/C1:1994
Correction of an amendment:
IEC 335-2-35:1993/A1:1993/C1:1994
<E10.102>
<! Includes optional pointer to record identifier >
<DOC.REF>
<TEXT LANG=AA> ... </TEXT>
</DOC.REF>
</E10.102>
EXAMPLES:
<E10.102> <DOC.REF> <TEXT LANG=en> IEC 335-2-35:1993/A1:1993
</TEXT> </DOC.REF> </E10.102>
<E10.102> <DOC.REF> <TEXT LANG=fr> CEI 335-2-35:1993/A1:1993
</TEXT> </DOC.REF> </E10.102>
Comments:
For standards, the use of the year of publication after a colon is recommended.
Some organizations publish more than one edition per year, in these cases, the
month of publication should be stated after the year of publication and separated
by a hyphen.
Field obligation:
-
10.104 Project reference
Name:
Synonyms
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Project reference
10.104
Reference used for the project
Text
1
80
A(80)
EXAMPLES:
A123F/FGT/67
0035NL
19
<E10.104>
<PRO.REF>
</PRO.REF>
</E10.104>
EXAMPLES:
<E10.104> <PRO.REF> <TEXT LANG=en> 0035NL </TEXT> </PRO.REF>
</E10.104>
10.100
Comments:
This may be coded from different aspects, for example a committe reference and
a number
Field obligation:
-
10.200 Title (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
20
Title (project)
10.200
Title of the project in full, transliterated or transcribed if necessary. All language
versions of titles are included in this data element. Either an English or a French
language version of the title must be included.
Text
4
600
A(600)
EXAMPLE:
#en=Freight containers - Information related to containers on board vessels Part 1: Bay plan system*fr=Conteneurs pour le transport de marchandises Informations relatives aux conteneurs à bord des navires - Partie 1: Système
du plan de chargement
<E10.200>
<TITLE>
<LANG.CODE> ... </LANG.CODE>
<COMP.1> ... </COMP.1>
<COMP.2> ... </COMP.2>
<COMP.3> ... </COMP.3>
<COMP.4> ... </COMP.4>
</TITLE>
</E10.200>
EXAMPLE:
<E10.200> <TITLE> <LANG.CODE> en </LANG.CODE> <COMP.1> Freight
containers </COMP.1> <COMP.2> Information related to containers on
board vessels </COMP.2> <COMP.3> Part 1: Bay plan system </COMP.3>
<COMP.4> </COMP.4> </TITLE> <TITLE> <LANG.CODE> fr
</LANG.CODE> <COMP.1> Conteneurs pour le transport de marchandises
</COMP.1> <COMP.2> Informations relatives aux conteneurs à bord des
navires </COMP.2> <COMP.3> Partie 1: Système du plan de chargement
</COMP.3> <COMP.4> </COMP.4> </TITLE> </E10.200>
For conventional data transfer, it is recommended to use a hyphen to indicate
different components in the title
M
ISONET MANUAL 1998
10.202 Project owner
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Project owner
10.202
The acronym of the organization which is the owner of the project
5
15
A(15)
EXAMPLE:
BSI
<E10.202>
</E10.202>
EXAMPLE:
<E10.202> <ORG.ACR> BSI </ORG.ACR> </E10.202>
20.704, 80.102
A reference table containing the names of standards institutes and international
bodies with their acronyms or codes should be maintained and provided by the
organization providing the data. In the case of language dependent acronyms, the
translation of the acronym in English and/or French should be in the reference
table.
M
10.204 Technical committee (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Technical committee (project)
TC; technical body
10.204
Reference number of the technical committee and/or subcommittee and/or
working group responsible for the project
5
50
A(50)
EXAMPLE:
ISO/TC 22
<E10.204>
<COMM.ID.CODE> ... </COMM.ID.CODE>
</E10.204>
EXAMPLE:
<E10.204> <COMM.ID.CODE> ISO/TC 22 </COMM.ID.CODE> </E10.204>
Numbers or abbreviations of technical committees as given in 40.104
20.510, 40.104
The name of this element was 'technical author'. When there are persons
mentioned as author in the document use data element 20.510.
See table 40 for more committee information.
In the case of more than one committee, the first committee mentioned should
be the main responsible committee.
M
21
10.206 Abstract (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Abstract (project)
10.206
Abstract or summary of the scope of the project
Text
4
3000
A(3000)
EXAMPLE:
en=The aim of this project is to revise the specifications for steel wire rope
<E10.206>
</E10.206>
EXAMPLE:
<E10.206> <TEXT LANG=en> The aim of this project is to revise the
specifications for steel wire rope </TEXT> </E10.206>
Where possible, an abstract in English or French should be included
-
10.300 Current stage code (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Current stage code (project)
10.300
The current stage code of a work item or project
1
5
XX.XX
EXAMPLE:
20.10
<E10.300>
<HSTAGE.CODE> ... </HSTAGE.CODE>
</E10.300>
EXAMPLE:
<E10.300> <HSTAGE.CODE > 20.10 </HSTAGE.CODE> </E10.300>
In accordance with group 30
10.302
M
10.302 Date of current stage (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
22
Date of current stage (project)
10.302
The date that the current stage was achieved or begun
Date
1
8
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
CCYYMMDD
EXAMPLE:
19961220
<E10.302>
<DATE> ... </DATE>
</E10.302>
EXAMPLE:
<E10.302> <DATE> 19961220 </DATE> </E10.302>
10.300
M
10.304 Target date for draft
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Target date for draft
10.304
The date when the draft for public comment is expected to be circulated (stage
code 40.20)
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.304>
<DATE> ... </DATE>
</E10.304>
EXAMPLE:
<E10.304> <DATE> 19961220 </DATE> </E10.304>
-
10.306 Latest date for comment (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Latest date for comment (project)
Latest date for vote
10.306
Latest date for comments or vote on documents issued for public enquiry
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.306>
<DATE> ... </DATE>
</E10.306>
EXAMPLE:
<E10.306> <DATE> 19961220 </DATE> </E10.306>
23
Permissible values:
See also:
Comments:
Field obligation:
In the database, there can be different data elements for national, regional and
international latest date for comment. For data exchange, the latest date should
be provided by the institute providing the data. A national institute should provide
the national latest date for comment. A regional institute should provide the
regional latest date for comment.
-
10.308 Target date for formal vote
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Target date for formal vote
10.308
The date when the formal vote document is expected to be circulated (stage code
50.20)
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.308>
<DATE> ... </DATE>
</E10.308>
EXAMPLE:
<E10.308> <DATE> 19961220 </DATE> </E10.308>
-
10.312 Latest date of implementation (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
24
Latest date of implementation (project)
DOP
10.312
The date by which the national implementation of a regional document should
occur by a national body
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.312>
<DATE> ... </DATE>
</E10.312>
EXAMPLE:
<E10.312> <DATE> 19961220 </DATE> </E10.312>
Used by CEN/CENELEC. This is usually a fixed time after the publication of the
regional document.
-
ISONET MANUAL 1998
10.314 Latest date for announcement (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Latest date for announcement (project)
DOA
10.314
Latest date for announcement of a national document that is an implementation
of a regional document
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.314>
<DATE> ... </DATE>
</E10.314>
EXAMPLE:
<E10.314> <DATE> 19961220 </DATE> </E10.314>
-
10.320 Target date for ratification (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Target date for ratification (project)
10.320
The date when it is expected that the ratification of the document will be
completed (harmonized stage code, 55.60)
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.320>
<DATE> ... </DATE>
</E10.320>
EXAMPLE:
<E10.320> <DATE> 19961220 </DATE> </E10.320>
-
10.322 Target date for official publication
Name:
Synonyms:
Identifier:
Definition:
ISONET MANUAL 1998
Target date for official publication
10.322
The date when it is expected that the document will be officially published
(harmonized stage code, 60.60)
Date
25
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.322>
<DATE> ... </DATE>
</E10.322>
EXAMPLE:
<E10.322> <DATE> 19961220 </DATE> </E10.322>
-
10.332 Latest date for withdrawal (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Latest date for withdrawal (project)
DOW
10.332
Latest date for withdrawal of existing national documents after implementing a
regional document
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.332>
<DATE> ... </DATE>
</E10.332>
EXAMPLE:
<E10.332> <DATE> 19961220 </DATE> </E10.332>
-
10.334 Date for existing products (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
26
Date for existing products (project)
10.334
Date until existing products or services can be produced based on withdrawn
documents
Date
1
8
EXAMPLE:
19961220
CCYYMMDD
<E10.334>
<DATE> ... </DATE>
</E10.334>
EXAMPLE:
<E10.334> <DATE> 19961220 </DATE> </E10.334>
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
Currently used by CENELEC. This data element should be a part of the new
document
-
10.336 Next stage (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Next stage (project)
10.336
The next stage code of a work item or project
1
5
XX.XX
EXAMPLE:
20.10
<E10.336>
</E10.336>
EXAMPLE:
10.338
-
10.338 Target date for next stage (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Target date for next stage (project)
10.338
Target date when the next stage is expected to be achieved or begun, depending
on which is more appropriate
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.338>
<DATE> ... </DATE>
</E10.338>
EXAMPLE:
<E10.338> <DATE> 19961220 </DATE> </E10.338>
10.336
-
27
10.340 Date of project initiation
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Date of project initiation
10.340
Date when the project was officially registered for the first time
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E10.340>
<DATE> ... </DATE>
</E10.340>
EXAMPLE:
<E10.340> <DATE> 19961220 </DATE> </E10.340>
-
10.400 Development status
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Development status
10.400
The status of the work item or project at the time of communication
Development status code
1
1
A
EXAMPLE:
P
<E10.400>
<DEV.STATUS.CODE > ... </DEV.STATUS.CODE>
</E10.400>
EXAMPLE:
<E10.400> <DEV.STATUS.CODE> P </DEV.STATUS.CODE> </E10.400>
A Active
C Cancelled
F Finished
P Pending/postponed
S Suspended
-
10.402 Track
Name:
Synonyms:
Identifier:
Definition:
28
Track
10.402
The route by which the project is proceeding through the standards development
ISONET MANUAL 1998
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
process.
Text
1
20
A(20)
EXAMPLES:
UAP (Unique Acceptance Procedure)
FST (fast-track
STL (streamlining)
<E10.402>
</E10.402>
EXAMPLE:
<E10.402> <TEXT LANG=en> UAP </TEXT> </E10.402>
-
10.404 Financial authority
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Financial authority
10.404
The name or acronym of the legal authority or organization which is funding the
project work.
Text
3
100
A(100)
EXAMPLES:
EC
Government
<E10.404>
</E10.404>
EXAMPLE:
<E10.404> <TEXT LANG=en> EC </TEXT> </E10.404>
-
10.406 Core reference document
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Core reference document
10.406
The identifier or title of the document that is being used as a basis for the project
(this may be a standard or something else).
Text
5
100
A(100)
EXAMPLE:
AB 2345
29
Permissible values:
See also:
Comments:
Field obligation:
<E10.406>
</E10.406>
EXAMPLE:
<E10.406> <TEXT LANG=en> AB 2345 </TEXT> </E10.406>
-
10.408 Type of project
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Type of project
10.408
Name or code of the type of project under development
Text
1
20
A(20)
EXAMPLES:
New
Revision
New edition
Amendment
Supplement
Corrigendum
<E10.408>
</E10.408>
EXAMPLE:
<E10.408> <TEXT LANG=en> New </TEXT> </E10.408>
This is not the same as track (10.402), but it may influence it
-
10.410 Type of publication
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
30
Type of publication
10.410
The type of publication which will result from the project
Text
1
20
A(20)
EXAMPLES:
Report
Guide
PAS
Code of Practice
Pre-standard
<E10.410>
</E10.410>
ISONET MANUAL 1998
EXAMPLE:
<E10.410> <TEXT LANG=en> Report </TEXT> </E10.410>
Permissible values:
See also:
Comments:
Field obligation:
The type of publication can also influence the track
-
10.500 Sorting key (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Sorting key (project)
10.500
Used for sorting of projects in a proper way by splitting up the project references
into parts of fixed length.
Sort code
1
150
X(150)
EXAMPLE:
030550000010000000000
<E10.500>
<SORT.CODE> ... </SORT.CODE>
</E10.500>
EXAMPLE:
<E10.500> <SORT.CODE> 030550000010000000000 </SORT.CODE>
</E10.500>
This field is primarily intended for sorting purposes. But in this way the computer
can also detect the different kinds of projects. Parts of the sorting key could also
be used for retrieval purposes.
Institutes should supply, on request, documentation on how the sort key is
constructed, together with examples, in a suitable file. In this file, a list of the
different elements should be included. For each element, the following should be
provided: the name, definition, code A for alpha-numeric or code N for numeric,
number of positions.
-
10.502 ICS (project)
Name:
Synonyms
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
ICS (project)
International Classification for Standards number
10.502
Subject classification system for standards and other technical documentation
ICS notation
4
9
XX
XX.XXX
XX.XXX.XX
EXAMPLES:
43.020
43.040.10
<E10.502>
<ICS.CODE> ... </ICS.CODE>
</E10.502>
31
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLE:
<E10.502> <ICS.CODE> 43.020 </ICS.CODE> </E10.502>
ICS notations as given in 50.001
See group 50 data elements.
National extensions should not be transferred.
M
10.504 TIT descriptors (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
TIT descriptors (project)
Keywords
10.504
Officially recognized descriptor names from the International Technical Thesaurus
(TIT) in English and/or other recognized language.
Text
100
80
A(80)
EXAMPLE:
en=paints;varnishes;tests;thermal tests
<E10.504>
</E10. 504>
EXAMPLE:
<E10. 504> <TEXT LANG=en> paints </TEXT> <TEXT LANG=en> varnishes
</TEXT> <TEXT LANG=en> tests </TEXT> <TEXT LANG=en> thermal tests
</TEXT> </E10. 504>
Descriptors from TIT thesaurus (group 60 data elements)
60.100, 60.105
Descriptor names must be given in at least English or French.
The most important descriptor names should be included first.
One of the two thesauri approved by ISONET should be used; the TIT thesaurus
(see table 60) or the ROOT thesaurus (see table 70).
-
10.506 ROOT descriptors (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
32
ROOT descriptors (project)
Keywords
10.506
Officially recognized descriptor names from the ROOT thesaurus in English and/or
other recognized language
Text
100
80
A(80)
EXAMPLE:
en=Paints;Varnishes;Testing;Thermal testing
<E10.506>
</E10.506>
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLE:
<E10.506> <TEXT LANG=en> Paints </TEXT> <TEXT LANG=en> Varnishes
</TEXT> <TEXT LANG=en> Testing </TEXT><TEXT LANG=en> Thermal
testing </TEXT> </E10.506>
Descriptors from ROOT thesaurus (group 70 data elements)
Descriptors must be present in at least English.
The most important descriptors should be included first.
(see table 60) or the ROOT thesaurus (see table 70).
-
10.508 Free descriptors (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Free descriptors (project)
10.508
Not officially recognized descriptors in English, French and/or other language
Text
100
80
A(80)
EXAMPLE:
en=metrological characteristics
<E10.508>
</E10.508>
EXAMPLE:
<E10.508> <TEXT LANG=en> metrological characteristics </TEXT>
<TEXT LANG= fr> caractéristique metrologique </TEXT> </E10.508>
Descriptors must be given in at least English or French.
-
10.606 Replaced by (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Replaced by (project)
10.606
Project reference of any item(s) which replace(s) the project. In the case of more
than one identifier, it is understood that all these projects replace the one project.
If the project number is not in the database, the identifier will not be available; in
such cases, text description should then be given.
Identifier or text
100
80
A(80)
EXAMPLE:
09702237/0001
<E10.606>
</E10.606>
33
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLES:
<E10.606> <REC.ID> A01054:20:10167 </REC.ID> <TEXT LANG=AA>
</TEXT> </E10.606>
<E10.606> <REC.ID> </REC.ID> <TEXT LANG=en> 8362NL </TEXT>
</E10.606>
Identifier as in 10.001 or text
10.001, 10.104, 10.610
-
10.610 Replaces (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Replaces (project)
10.610
Project reference of any item(s) which are replaced by the project. If the project is
not in the database, the identifier will not be available; in such cases, text
description should then be given.
Identifier or text
100
80
A(80)
EXAMPLES:
00010004
NFZ 44-001
<E10.610>
</E10.610>
EXAMPLES:
</TEXT> </E10.610>
<E10.610> <REC.ID> </REC.ID> <TEXT LANG=en> 00010004 </TEXT>
</E10.610>
<E10.610> <REC.ID> </REC.ID> <TEXT LANG=en> NFZ 44-001 </TEXT>
</E10.610>
10.001, 10.606
-
10.612 Corresponding documents (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
34
Corresponding documents (project)
Implementation of; relationship; relatedness; equivalence; international
relationship; foreign relationship
10.612
Document references of the corresponding international, regional or national
documents which have a degree of equivalence (codes for the degree of
equivalence to be in allocated in accordance with ISO/IEC Guides 3 and 21).
Please note that ISO Guides 3 and 21 are under revision.
Text / equivalence code
100
84
A(80),A(3)
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLE:
ISO 9001:1994, IDT
<E10.612>
<EQUIV.CODE> ... </EQUIV.CODE>
</E10.612>
EXAMPLES:
<E10.612> <REC.ID> </REC.ID> <TEXT LANG=en> ISO 9001:1994
</TEXT> <EQUIV.CODE> IDT </EQUIV.CODE> </E10.612>
</TEXT> <EQUIV.CODE> NEQ </EQUIV.CODE> </E10.612>
Identifier as in 20.104 or text, followed by one of the following codes:
IDT
Identical
EQV
Equivalent
MOD Modified
NEQ Not equivalent
20.616
When a standard is an implementation of more then one standard, and there are
no changes in the technical content, then EQV should be used for the reference
to each document implemented.
It is permissible to have an internal database structure which has separate fields
for IDT, EQV, MOD and NEQ, etc. but these must be combined for data transfer.
Modified is used in cases where the document contains all details of alterations.
for international, regional or foreign relatedness, but these must be combined for
data transfer.
If users use separate fields to hold this data then they should have a method of
separating the transferred data into these fields.
The use of the publication date after a colon is recommended.
Relationships to Harmonization Documents are also included in this data element.
-
10.617 Development obligation
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Development obligation
10.617
Reference of document in which the obligation to develop a project is stated
Text
10
250
A(250)
EXAMPLE:
BC/CEN/91/1.43
<E10.617>
</E10.617>
EXAMPLE:
<E10.617> <TEXT LANG=en> BC/CEN/91/1.43 </TEXT></E10.617>
Identifier as in 10.001 or text reference
-
35
10.619 Obligation development reference
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Obligation development reference
10.619
References of regulations which are connected with the obligation to develop a
project
Text
10
250
A(250)
EXAMPLE:
89/336/EEC
<E10.619>
</E10.619>
EXAMPLE:
<E10.619> <TEXT LANG=nl> 89/336/EEC </TEXT></E10.619>
-
10.900 General notes (project)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
36
General notes (project)
10.900
Any ancillary data, relating to the project, that cannot be entered in another field
Text
1
250
A(250)
EXAMPLE:
Ancilliary data
<E10.900>
</E10.900>
EXAMPLE:
<E10.900> <TEXT LANG=en> Ancilliary data </TEXT> </E10.900>
-
ISONET MANUAL 1998
20
DATA ELEMENTS FOR PRODUCTS
The following data elements are mandatory:
20.001, 20.002, 20.104, 20.110, 20.112, 20.200, 20.204, 20.208, 20.310, 20.330,
20.502, 20.606, 20.610, 20.612
20.001 Record identifier (product)
Name:
Synonyms:
Identifier:
Definition:
Record identifier (product)
20.001
A unique identification of the record to be allocated to each new record and used
for identification whenever a record is changed or deleted. The product record
identifier is independent of the stock number (20.106) and is allocated by the
centre creating the record.
The identifier should be made up from three elements:
a) Registered file owner identifier allocated by the ISO 9070 registration
authority, with 6 characters, or acronym of the organization (00.006)
b) Data element group (see 00.004)
c) Stock number (20.106)
Organization identifier:group number:integer
Maximum occurrence:
1
30
A(15):XX:I(20)
EXAMPLES:
BSI:20:77682
A01054:20:77682
<E20.001>
</E20.001>
EXAMPLE:
<E20.001> <REC.ID> A01054:20:77682 </REC.ID> </E20.001>
00.004, 00.006, 20.104, 20.106
Comments:
Field obligation:
M
20.002 Alteration date of record (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Alteration date of record (product)
20.002
The latest date when the product record was altered or changed in any way
Date
1
8
37
Permissible values:
See also:
Comments:
Field obligation:
CCYYMMDD
EXAMPLE:
19961220
<E20.002>
<DATE> ... </DATE>
</E20.002>
EXAMPLE:
<E20.002> <DATE> 19961220 </DATE> </E20.002>
M
20.004 Creation date of record (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Creation date of record (product)
20.004
The date when the product record was created
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.004>
<DATE> ... </DATE>
</E20.004>
EXAMPLE:
<E20.004> <DATE> 19961220 </DATE> </E20.004>
M
20.100 Project reference (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
38
Project reference (product)
20.100
Reference used for the project connected to this document
Text
1
80
A(80)
EXAMPLES:
A123F/FGT/67
0035NL
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
<E20.100>
<Includes optional pointer to record identifier>
<PRO.REF>
</PRO.REF>
</E20.100>
EXAMPLES:
</TEXT> </E20.100>
<E20.100> <PRO.REF> <TEXT LANG=AA> A123/FGT/67 </TEXT>
</PRO.REF> </E20.100>
10.100, 10.104
-
20.104 Product reference
Name:
Synonyms
Identifier:
Definition:
Maximum occurrence:
Product reference
Document reference; document identifier
20.104
Reference as written on the product
Text
4
150
A(150)
EXAMPLES:
ETS 300999:1994-08
DIN 1045
IEC 335-2-35:1993
NFZ 44-001
Amendments and correction sheets:
IEC 335-2-35:1993/prA1:1993
IEC 335-2-35:1993/A1:1993
IEC 335-2-35:1993/C1:1994
Correction of an amendment:
IEC 335-2-35:1993/A1:1993/C1:1994
<E20.104>
<DOC.REF>
</DOC.REF>
</E20.104>
EXAMPLE:
<E20.104> <DOC.REF> <TEXT LANG=en> ETS 300999:1994-08 </TEXT>
</DOC.REF> </E20.104>
Comments:
For standards, the use of the year of publication after a colon is recommended.
Some organizations publish more than one edition per year, in these cases, the
month of publication should be stated after the year of publication and separated
by a hyphen.
Refer to sort key (20.500) for sorting information.
Field obligation:
M
ISONET MANUAL 1998
39
20.106 Stock number
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Stock number
Product identifier; UPI; product code; shelf number; item identifier
20.106
A numeric identifier used to distinguish products. Products may be documents,
combinations of documents or other articles.
Text
1
20
A(20)
EXAMPLE:
4567867545
<E20.106>
<TEXT> ... </TEXT>
</E20.106>
EXAMPLE:
<E20.106> <TEXT> 4567867545 </TEXT> </E20.106>
This number is usually related to an individual product. It is possible that the value
recorded may, in certain circumstances, be the same as that in other elements
e.g. edition identifier (20.220).
This number may be a stock number used for sales purposes.
-
20.108 Amendment type
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
40
Amendment type
20.108
A code which shows if the document is an amendment or correction sheet
Amendment code
1
3
A(3)
EXAMPLE:
Amd
<E20.108>
<AMEND.CODE> ... </AMEND.CODE>
</E20.108>
EXAMPLE:
<E20.108> <AMEND.CODE> Amd </AMEND.CODE> </E20.108>
Add
Addendum
Amd
Amendment
Cor
Correction sheet / Corrigendum
Supplement
Sup
20.112
-
ISONET MANUAL 1998
20.110 Amended by
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Amended by
20.110
Product reference of any item(s) which amend the document being indexed; for
an amendment in the future, code F should be used. If the document is not in the
database, the product reference (20.104) will not be available; in such cases, text
description should then be given.
Identifier or text / F-code
100
250
A(250)
A(250),A
EXAMPLES:
IEC 543:1992/A1:1994
CEI 543:1992/A1:1994
<E20.110>
<F.CODE > ... </F.CODE>
</E20.110>
EXAMPLES:
</TEXT> <F.CODE > F </F.CODE> </E20.110>
<E20.110> <REC.ID> </REC.ID> <TEXT LANG=en> IEC 543:1992/A1:1994
</TEXT> <F.CODE > </F.CODE> </E20.110>
20.104, 20.112
The use of the publication date after a colon is recommended
M
20.112 Amends
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Amends
20.112
Product reference of any item(s) which are amended (or supplemented) by the
document being indexed; for an amendment in the future, code F should be used.
If the document is not in the database, the product reference (20.104) will not be
available; in such cases, text description should then be given.
Identifier or text
100
250
A(250)
A(250),A
EXAMPLES:
IEC 543:1992
CEI 543:1992
41
Permissible values:
See also:
Comments:
Field obligation:
<E20.112>
<F-CODE > ... </F-CODE>
</E20.112>
EXAMPLES:
</TEXT> <F-CODE > </F-CODE></E20.112>
<E20.112> <TEXT LANG=en> IEC 543:1992 </TEXT> <F-CODE >
</F-CODE></E20.112>
20.104, 20.110
M
20.114 ISBN
Name:
Synonyms:
Identifier:
Version
Definition:
Maximum occurrence:
Permissible values:
See also
Comments:
Field obligation:
ISBN
International Standard Book Number for product
20.114
1
Unique number for a published document in accordance with ISO 2108.
ISBN code
1
13
X(2)-X(5)-X(5)-A
EXAMPLES:
0-395-20360-0
0 571 08989 5
90-70002-34-5
<E20.114>
<ISBN.CODE> ... </ISBN.CODE>
</E20.114>
EXAMPLE:
<E20.114> <ISBN.CODE> 0-395-20360-0 </ISBN.CODE> </E20.114>
Four components:
1) group identifier
2) publisher identifier
3) title identifier
4) check character/check digit
See annex A for details of the ISBN registration authority
-
20.116 ISSN
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
42
ISSN
International Standard Serial Number for product
20.116
Unique number for a published periodical in accordance with ISO 3297
ISSN code
1
9
XXXX-XXXA
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLE:
0007-1267
<E20.116>
<ISSN.CODE> ... </ISSN.CODE>
</E20.116>
EXAMPLE:
<E20.116> <ISSN.CODE> 0007-1267</ISSN.CODE> </E20.116>
Two groups of four numeric characters, except the last one which may be a
numeric character or an X.
See annex A for details of the ISSN registration authority
-
20.200 Title (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Title (product)
20.200
Title of the document in full, transliterated or transcribed if necessary. All language
versions of titles are included in this field. Either an English or a French language
version of the title must be included.
Title
4
600
A(600)
EXAMPLES:
#en=Freight containers - Information related to containers on board vessels Part 1: Bay plan system*fr=Conteneurs pour le transport de marchandises Informations relatives aux conteneurs à bord des navires - Partie 1: Système
du plan de chargement
<E20.200>
<TITLE>
<COMP.1> ... </COMP.1>
<COMP.2> ... </COMP.2>
<COMP.3> ... </COMP.3>
<COMP.4> ... </COMP.4>
</TITLE>
</E20.200>
EXAMPLE:
<E20.200> <TITLE> <LANG.CODE> en </LANG.CODE> <COMP.1> Freight
containers </COMP.1> <COMP.2> Information related to containers on
board vessels </COMP.2> <COMP.3> Part 1: Bay plan system </COMP.3>
<COMP.4> </COMP.4> </TITLE> <TITLE> <LANG.CODE> fr
</LANG.CODE> <COMP.1> Conteneurs pour le transport de marchandises
</COMP.1> <COMP.2> Informations relatives aux conteneurs à bord des
navires </COMP.2> <COMP.3> Partie 1: Système du plan de chargement
</COMP.3> <COMP.4> </COMP.4> </TITLE> </E20.200>
For SGML, the title can be split into components for each language version. For
conventional data transfer, it is recommended to use a hyphen to indicate
different components of the title.
M
43
20.204 Technical committee (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Technical committee (product)
TC; committee reference
20.204
Reference of the technical committee and/or subcommittee and/or working group
responsible for the product
5
50
A(50)
EXAMPLES:
ISO/TC 22
JIEC/TC 999/SC 999A/WG 99
JISO/IEC/JTC 1/SC 999/WG 99
<E20.204>
<COMM.ID.CODE> ... </COMM.ID.CODE>
</E20.204>
EXAMPLE:
<E20.204><COMM.ID.CODE> ISO/TC 22 </COMM.ID.CODE> </E20.204>
Numbers or abbreviations of technical committees
20.510, 40.104
The name of this element was 'technical author'. When there are persons
mentioned as author in the document use data element 20.510.
See table 40 for more committee information.
In the case of more committees, the first committee mentioned should be the
main responsible committee.
M
20.206 Abstract (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
44
Abstract (product)
20.206
Abstract or summary of the content of the product: for standards, this can be
based on the "scope" and "field of application" clauses
Text
4
3000
A(3000)
EXAMPLE:
en=This part of ISO 31 gives names and symbols for quantities and units of
solid state physics. Where appropriate, conversion factors are also given.
<E20.206>
</E20. 206>
EXAMPLE:
<E20. 206> <TEXT LANG=en> This part of ISO 31 gives names and symbols
for quantities and units of solid state physics. Where appropriate, conversion
factors are also given.</TEXT> </E20. 206>
Where possible an abstract in English or French should be included
-
ISONET MANUAL 1998
20.208 Languages
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Languages
20.208
The language or languages in which the text of the document is published
Language code
25
2
AA
EXAMPLE:
en*fr
<E20.208>
</E20.208>
EXAMPLE:
<E20.208> <LANG.CODE> en </LANG.CODE> <LANG.CODE> fr
</LANG.CODE> </E20.208>
Language symbols in accordance with ISO 639
20.210, 20.604
If only part of the document is in another language this should be stated in the
notes (20.210)
-
20.210 Languages notes
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Languages notes
10.210
Explanation in text to the language or languages in which the text of the
document is published
Text
4
250
A(250)
EXAMPLE:
en=multilingual edition
<E20.210>
</E20.210>
EXAMPLE:
<E20.210> <TEXT LANG=en> multilingual edition </TEXT> </E20.210>
20.200, 20.604
Use this data element to state that only part of the document is in another
language
-
20.212 Number of pages
Name:
Synonyms:
Identifier:
ISONET MANUAL 1998
Number of pages
20.212
45
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
The number of pages of the paper document
Integer
1
4
I(4)
EXAMPLE:
15
<E20.212>
<INT> ... </INT>
</E20.212>
EXAMPLE:
<E20.212> <INT> 15 </INT> </E20.212>
20.236
For documents that are published in loose-leaf format and are subject to regular
updates (for instance, government regulations), it is permissible that the number
of pages is not included.
No guidelines are given as to whether blank pages are to be included, or not.
For other physical characteristics see 20.236.
-
20.214 Document status
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Document status
20.214
Characteristics representing the life cycle of the document
Document status code
1
1
A
EXAMPLE:
F
<E20.214>
<DOC.STATUS.CODE> ... </DOC.STATUS.CODE>
</E20.214>
EXAMPLE:
<E20.214> <DOC.STATUS.CODE> F </DOC.STATUS.CODE> </E20.214>
C
Committee or working document
D
Draft for public comment
F
Formal or final draft
P
Published document
R
Retained or partially retained (withdrawn but valid for legal, or other,
purposes)
W
Withdrawn
20.216
This element can be linked to the harmonized system for stage codes.
The list or permissible values is not intended to be exhaustive, other values may
be used if appropriate.
-
20.216 Document type (product)
Name:
Synonyms:
Identifier:
Definition:
46
Document type (product)
20.216
Characteristics representing the type of document
ISONET MANUAL 1998
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Type code
1
3
A(3)
EXAMPLE:
SB
<E20.216>
<TYPE.CODE> ... </TYPE.CODE>
</E20.216>
EXAMPLE:
<E20.216> <TYPE.CODE> SB </TYPE.CODE> </E20.216>
AMD Amendment
CA
Certification or accreditation document
CD Committee document
CP
Code of practice
DC Draft for public comment
HD Harmonization document
GD Guide
IP
International Standardized Profile
LD
Legal document (other than technical regulations)
OT
Other miscellaneous documents
PA
Product Approval Specification
PA
Publicly Available Specification
SB
Standard Handbook
SP
Prestandard
SR
Standard Technical Report
ST
Standard
SUP Supplement
TL
Technical literature
TR
Technical regulation
TS
Technical specification
TTA Technical Trend Assessment
20.214
be used if appropriate
-
20.218 Document series
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
ISONET MANUAL 1998
Document series
20.218
Characteristics representing the document series or special collections which are
unique to the originating body
Text
1
80
A(80)
EXAMPLES:
B45 series
Automobile series
<E20.218>
</E20.218>
EXAMPLE:
<E20.218> <TEXT LANG=en> B45 series </TEXT> </E20.218>
-
47
See also:
Comments:
Field obligation:
-
20.220 Edition
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Edition
20.220
This element is an indication of the edition of the document
Text
1
5
A(5)
EXAMPLES:
2
2.0
2.1
B
<E20.220>
</E20.220>
EXAMPLE:
<E20.220> <TEXT LANG=en> 2 </TEXT> </E20.220>
20.222, 20.224
When there is a need for some explanations, for example reprints, use the data
element 20.222.
This data element should be used for published documents only, for versions of
draft documents use 20.224.
Note that this edition information may occur in 20.104.
It is recommended that numbers are used to denote editions.
-
20.222 Edition notes
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
48
Edition notes
20.222
Explanation in text of the edition of the document
Text
4
100
A(100)
EXAMPLE:
en=unchanged reprint 1991
<E20.222>
</E20.222>
EXAMPLE:
<E20.222> <TEXT LANG=en> unchanged reprint 1991 </TEXT> </E20.222>
20.220, 20.224
This field should be used for published documents only, for versions of draft
documents use 20.224.
-
ISONET MANUAL 1998
20.224 Version
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Version
20.224
The version number of a draft document (see comments)
Real number
1
5
R(5)
EXAMPLES:
2
3.1
<E20.224>
<REAL> ... </REAL>
</E20.224>
EXAMPLES:
<E20.224> <REAL> 2 </REAL> </E20.224>
<E20.224> <REAL> 3.1 </REAL> </E20.224>
20.220, 20.222
This element should be used for versions of drafts only. For editions of published
documents, use 20.220.
-
20.226 Price and currency
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments
Field obligation:
ISONET MANUAL 1998
Price and currency
20.226
Price of the document or product in a specific currency, tax excluded, as
determined by the supplier
Currency code and real number
1
25
AAA R(22)
EXAMPLE:
NLG67,20
<E20.226>
<CURR.CODE> ... </CURR.CODE>
<REAL> ... </REAL>
</E20.226>
EXAMPLE:
<E20.226> <CURR.CODE> NLG </CURR.CODE> <REAL> 67,20 </REAL>
<E/20.226>
For currency codes use alpha-3 codes in accordance with ISO 4217:1995. The
price information is a monetary value.
20.230, 20.228, 20.232
There is no space between the currency code and the numeric value
-
49
20.228 Price group
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments
Field obligation:
Price group
20.228
A code form of the price of the document or product as determined by the
supplier
Price code
1
15
A(15)
EXAMPLES:
16A
XZ
<E20.228>
<PRICE.CODE> ... </PRICE.CODE>
</E20.228>
EXAMPLE:
<E20.228> <PRICE.CODE> 16A </PRICE.CODE> </E20.228>
20.226, 20.230
Price information regarding multiple copies and special discounts are to be
included as text in 20.230.
If only price groups are provided (instead of prices in a currency), it is
recommended that a reference table giving the price in a specific currency for the
each code is provided.
-
20.230 Price notes
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments
Field obligation:
50
Price notes
20.230
Text information relating to the price of the document or product
Text
1
500
A(500)
EXAMPLE:
special discount of 25% until end of this year
<E20.230>
</E20.230>
EXAMPLE:
<E20.230> <TEXT LANG=en> special discount of 25% until end of this year
</TEXT> </E20.230>
20.226, 20.228
There may be a reference table for the price groups that refer to prices in a
specific currency
-
ISONET MANUAL 1998
20.232 Medium
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Medium
20.232
The medium or the combination of media on which the full content of the
document is available.
Medium code
15
6
A(3) or A(3),A(3)
EXAMPLE:
P,D
means partly on paper and partly diskette
P*D
means totally on paper and totally on diskette
<E20.232>
<MEDIUM.CODE> ... </MEDIUM.CODE>
</E20.232>
Example:
<E20.232> <MEDIUM.CODE> P,D </MEDIUM.CODE> </E20.232>
C
CD-ROM
CE
Cartridge tape
D
Floppy disk
DAT DAT tape
F
Microfiche
M
Microfilm
O
On line access (other than Web)
P
Paper
S
Satellite
SQ Syquest drive
T
Tape, magnetic
W
Web
WO Worm drive
Z
ZIP drive
20.238 for T, D, O, C
20.234 for notes to medium
P does not need to be included when it is self-evident that it is a paper version.
be used if appropriate.
It is possible that a part of a document is published on paper and another part on
diskette; for these documents, the codes should be separated by a comma.
When there more complex combinations use 20.234.
Where the complete product is available on different media, the relevant codes
should be separated with an asterisk.
-
20.234 Medium, notes
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Medium, notes
20.234
Explanation in text of the media on which the full text of the document is available
Text
1
250
A(250)
51
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLE:
The floppy disk is an optional extra when purchasing the paper version
<E20.234>
</E20.234>
EXAMPLE:
<E20.234> <TEXT LANG=en> The floppy disk is an optional extra when
purchasing the paper version </TEXT> </E20.234>
20.232 for medium codes allowed
For information concerning the physical characteristics of the paper version see
20.236
-
20.236 Collation
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Collation
20.236
The physical characteristics of the document, or product (other than an electronic
product). Details such as charts, colour charts, or illustrations may be included.
Paper size code and text
1
250
A(2):A(247)
EXAMPLE:
A4:with a sample of textile for the colours of the flag
<E20.236>
<PAPER.CODE> ... </PAPER.CODE>
</E20.236>
EXAMPLE:
<E20.236> <PAPER.CODE> A4 </PAPER.CODE> <TEXT LANG=en> with a
sample of textile for the colours of the flag </TEXT> </E20.236>
For size designation use ISO 216:1975. ISO-A series or ISO-B series
20.212
The number of pages is a separate data element (20.212)
-
20.238 Electronic format
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
52
Electronic format
20.238
Electronic format in which the full text of the document or product can be
delivered; the MIME specification is used to describe this format (see annex B)
MIME codes
1
50
A(50)
EXAMPLE:
application,msword,doc
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
<E20.238>
<MIME.CODE>
<MIME.TYPE> ... </MIME.TYPE>
<MIME.APP> ... </MIME.APP>
<MIME.EXT> ... </MIME.EXT>
</MIME.CODE>
</E20.238>
EXAMPLE:
<E20.238> <MIME.CODE> <MIME.TYPE> application </MIME.TYPE>
<MIME.APP> msword </MIME.APP> <MIME.EXT> doc </MIME.EXT>
</MIME.CODE> </E20.238>
Codes for the electronic format in accordance with the MIME specification (see
annex B)
20.240
When a document consists of different electronic formats this information should
be included as text
-
20.240 Electronic format notes
Name:
Synonyms:
Identifier:
Version:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Electronic format notes
20.240
1
Explanation in text of the electronic format in which the full text, or part of the
text, of the document or product can be delivered
Text
1
250
A(250)
EXAMPLE:
Introduction and scope also available as an HTML document
<E20.240>
</E20.240>
EXAMPLE:
<E20.240> <TEXT LANG=en> Introduction and scope also available as an
HTML document </TEXT> </E20.240>
20.238
Version numbers of software packages should be indicated
-
20.242 Electronic file size
Name:
Synonyms:
Identifier:
Version:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Electronic file size
20.242
1
Size in bytes of the uncompressed electronic file in which the full text of the
document or product can be delivered
Number
1
12
X(12)
EXAMPLE:
210000
53
Permissible values:
See also:
Comments:
Field obligation:
<E20.242>
<INT> ... </INT>
</E20.242>
EXAMPLE:
<E20.242> <INT> 210000 </INT> </E20.242>
-
20.300 Current stage code (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Current stage code (product)
20.300
The current stage code of a product
1
5
XX.XX
EXAMPLE:
20.10
<E20.300>
</E20.300>
EXAMPLE:
20.302
-
20.302 Date of current stage (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
54
Date of current stage (product)
20.302
The date that the current stage was achieved or begun
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.302>
<DATE> ... </DATE>
</E20.302>
EXAMPLE:
<E20.302> <DATE> 19961220 </DATE> </E20.302>
In accordance with ISO 8601
20.300
-
ISONET MANUAL 1998
20.306 Latest date for comment (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Latest date for comment (product)
Latest date for vote
20.306
Latest date for comments or vote on documents issued for public enquiry
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.306>
<DATE> ... </DATE>
</E20.306>
EXAMPLE:
<E20.306> <DATE> 19961220 </DATE> </E20.306>
In the database, there can be different data elements for national, regional and
international latest date for comment. For data exchange, the latest date should
be provided by the institute providing the data. A national institute should provide
the national latest date for comment. A regional institute should provide the
regional latest date for comment.
-
20.310 Date of publication
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Date of publication
DAV; date of availability; date of issue; publication date
20.101
The date a product was issued, published or otherwise made available
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.310>
<DATE> ... </DATE>
</E20.310>
EXAMPLE:
<E20.310> <DATE> 19961220 </DATE> </E20.310>
M
20.312 Latest date of implementation (product)
Name:
Synonyms:
Identifier:
Definition:
ISONET MANUAL 1998
Latest date of implementation (product)
DOP
20.312
The date by which the national implementation of a regional document should
55
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
occur by a national body
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.312>
<DATE> ... </DATE>
</E20.312>
EXAMPLE:
<E20.312> <DATE> 19961220 </DATE> </E20.312>
Used by CEN/CENELEC. This is usually a fixed time after the publication of the
regional document.
-
20.314 Latest date for announcement (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Latest date for announcement (product)
DOA
20.314
Latest date for announcement of a national document that is an implementation
of a regional document
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.314>
<DATE> ... </DATE>
</E20.314>
EXAMPLE:
<E20.314> <DATE> 19961220 </DATE> </E20.314>
20.316
-
20.316 Date of announcement
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
56
Date of announcement
NAPUBL
20.316
Date of announcement in an official publication of a national document that is an
implementation of a regional document
Date
1
8
EXAMPLE:
19961220
CCYYMMDD
<E20.316>
<DATE> ... </DATE>
</E20.316>
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLE:
<E20.316> <DATE> 19961220 </DATE> </E20.316>
20.314
-
20.318 Effective date
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Effective date
Valid from date
20.318
The date or dates on which the document or different parts of the document
enters into effect
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.318>
<DATE> ... </DATE>
</E20.318>
EXAMPLE:
<E20.318> <DATE> 19961220 </DATE> </E20.318>
20.324, 20.706
-
20.320 Target date for ratification (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Target date for ratification (product)
20.320
The date when it is expected that the ratification of the document will be
completed (harmonized stage code, 55.60)
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.320>
<DATE> ... </DATE>
</E20.320>
EXAMPLE:
<E20.320> <DATE> 19961220 </DATE> </E20.320>
-
57
20.324 Date of validation
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Date of validation
Date of approval; date of endorsement
20.324
Date on which the approved or endorsed document becomes valid
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.324>
<DATE> ... </DATE>
</E20.324>
EXAMPLE:
<E20.324> <DATE> 19961220 </DATE> </E20.324>
20.318
-
20.326 Confirmation date
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Confirmation date
DOC; date of reaffirmation
20.326
The date on which the issuing body or the validating authority confirms or
reaffirms the validity of the document
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.326>
<DATE> ... </DATE>
</E20.326>
EXAMPLE:
<E20.326> <DATE> 19961220 </DATE> </E20.326>
-
20.328 Date of expiration of validity
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
58
Date of expiration of validity
Expiry date
20.328
The date after which the document will cease to be in force
Date
1
8
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
CCYYMMDD
EXAMPLE:
19961220
<E20.328>
<DATE> ... </DATE>
</E20.328>
EXAMPLE:
<E20.328> <DATE> 19961220 </DATE> </E20.328>
20.214
Can also be used for retained editions of withdrawn documents.
New edition should have a note field mentioning the retention of the withdrawn
document.
-
20.330 Withdrawal date (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Withdrawal date (product)
20.330
The date on which the product is withdrawn
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.330>
<DATE> ... </DATE>
</E20.330>
EXAMPLE:
<E20.330> <DATE> 19961220 </DATE> </E20.330>
M
20.332 Latest date for withdrawal (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Latest date for withdrawal (product)
DOW
20.332
Latest date for withdrawal of existing national documents after implementing a
regional document
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E20.332>
<DATE> ... </DATE>
</E20.332>
EXAMPLE:
<E20.332> <DATE> 19961220 </DATE> </E20.332>
59
Permissible values:
See also:
Comments:
Field obligation:
-
20.334 Date for existing products
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Date for existing products
DOX
20.334
Date until which existing products or services can be produced based on
withdrawn documents
Date
1
8
EXAMPLE:
19961220
CCYYMMDD
<E20.334>
<DATE> ... </DATE>
</E20.334>
EXAMPLE:
<E20.334> <DATE> 19961220 </DATE> </E20.334>
Currently used by CENELEC. This data element should be a part of the new
document
-
20.500 Sorting key (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
60
Sorting key (product)
20.500
Used for sorting of products in a proper way by splitting up the product reference
in parts with a fixed length
Sort code
1
150
A(150)
EXAMPLE:
030550000010000000000
<E20.500>
<SORT.CODE> ... </SORT.CODE>
</E20.500>
EXAMPLE:
<E20.500> <SORT.CODE> 030550000010000000000 </SORT.CODE>
</E20.500>
-
ISONET MANUAL 1998
Comments:
Field obligation:
This field is primarily intended for sorting purposes. But in this way the computer
can also detect the different kinds of products. Parts of the sorting key could also
be used for retrieval purposes.
Institutes should supply, on request, documentation on how the sort key is
constructed, together with examples, in a suitable file. In this file a list of the
different elements should be included. For each element, the following should be
provided: the name, definition, code A for alpha-numeric or code N for numeric,
number of positions.
-
20.502 ICS (product)
Name:
Synonyms
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ICS (product)
International Classification for Standards number
20.502
Subject classification system for standards and other technical documentation
ICS notation
4
9
XX
XX.XXX
XX.XXX.XX
EXAMPLES:
43.020
43.040.10
<E20.502>
</E20.502>
EXAMPLE:
ICS notations as given in 50.001
National extensions should not be transferred.
M
20.504 TIT descriptors (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
ISONET MANUAL 1998
TIT descriptors (product)
Keywords
20.504
Officially recognized descriptor names from the International Technical Thesaurus
(TIT) in English and/or other recognized language.
TIT descriptors
100
80
A(80)
EXAMPLE:
en=paints;varnishes;tests;thermal tests
<E20.504>
<TEXT LANG = AA> ... </TEXT>
</E20.504>
EXAMPLE:
<E20.504> <TEXT LANG = en> paints </TEXT> <TEXT LANG = en>
varnishes </TEXT> <TEXT LANG = en> tests </TEXT> <TEXT LANG = en>
thermal tests </TEXT> </E20.504>
TIT
61
See also:
Comments:
Field obligation:
The descriptors are controlled with the help of group 60 data elements
(see group 60) or the ROOT thesaurus (see group 70).
-
20.506 ROOT descriptors (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ROOT descriptors (product)
Keywords
20.506
Officially recognized descriptor names from the ROOT thesaurus in English and/or
other recognized language
Text
100
80
A(80)
EXAMPLE:
en=Paints;Varnishes;Testing;Thermal testing
<E20.506>
</E20.506>
EXAMPLE:
<E20.506> <TEXT> <LANG = en> Paints </TEXT> <TEXT LANG = en>
Varnishes </TEXT> <TEXT LANG = en> Testing </TEXT> <TEXT LANG =
en> Thermal testing </TEXT> </E20.506>
BSI
Descriptors must be present in at least English
The descriptors are controlled with the help of group 70 data elements
(see group 60) or the ROOT thesaurus (see group 70).
-
20.508 Free descriptors (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
62
Free descriptors (product)
20.508
Not officially recognized descriptors in English, French and/or other language
Text
100
80
A(80)
EXAMPLE:
en=metrological characteristics
<E20.508>
</E20.508>
EXAMPLE:
<E20.508> <TEXT LANG=en> metrological characteristics </TEXT> <TEXT
LANG=fr> caractéristique metrologique </TEXT></E20.508>
-
ISONET MANUAL 1998
See also:
Comments:
Field obligation:
-
20.510 Authors
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Authors
20.510
Names of the authors of the product.
Text
5
200
A(200)
EXAMPLE:
Jones, A.H.;MacArthur, I.H.M.
<E20.510>
</E20.510>
EXAMPLE:
<E20.510> <TEXT LANG=en> Jones, A.H. </TEXT> <TEXT LANG=en>
MacArthur, I.H.M. </TEXT> </E20.510>
20.204, 20.700
State the language in which the names of the authors are given, if different to that
of the file label.
It is recommended to use the following format for names of authors: family
name, a comma, a space, then the initials separated by full stops.
-
20.600 Document source
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Document source
Published in
20.600
Document reference and/or title in which a document is initially published
Text
20
300
A(300)
EXAMPLE:
Official Journal of the European Communities Vol. 20, No. L229, pp. 12-32
<E20.600>

</E20.600>
EXAMPLES:
<E20.600> <REC.ID> A01054:20:575777 </REC.ID> </E20.600>
<E20.600> <TEXT LANG=en> Official Journal of the European Communities
Vol. 20, No. L229, pp. 12-32 </TEXT> </E20.600>
This element is used when a document is not published separately (for example,
technical regulations)
-
63
20.602 Republished in
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Republished in
20.602
Document reference or ISBN or title of the publication(s) in which the item has
been republished
Text
50
250
A(250)
EXAMPLE:
ISO Standards Handbook 1:1988
<E20.602>

<DOC.REF> ... </DOC.REF>
</E20.602>
EXAMPLE:
<E20.602> <TEXT LANG=en> ISO Standards Handbook 1:1988 </TEXT>
<DOC.REF> 1054:20:156701 </DOC.REF> </E20.602>
Product number, publication date and title of publication in which the item is
republished, in full with any other information needed to identify and obtain it
Used when a standard is republished in a handbook, CD-ROM or any other
collection.
-
20.604 Translations
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
64
Translations
20.604
Information on a language into which the item has been translated, including the
language code, the acronym of the organization that has made the translation, the
date of publication of the translation and the document reference of the translated
document
Language code : organization acronym : date : document reference
100
108
AA:A(15):CCYYMMDD:A(80)
EXAMPLE:
it:UNI:19860101:UNI ISO 6346:1986
<E20.604>
<! Includes optional pointer to document identifier >
<DATE> ... </DATE>
<DOC.REF> ... </DOC.REF>
</E20.604>
EXAMPLE:
<E20.604> <LANG.CODE> it </LANG.CODE> <ORG.ACR> UNI
</ORG.ACR> <DATE> 19860101 </DATE> <DOC.REF> UNI ISO 6346:1986
</DOC.REF> </E20.604>
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
ISO 639 language symbols.
Acronym in accordance with 80.102.
Date in accordance with ISO 8601:1988.
Product reference in accordance with 20.104
20.208
Language symbol, or language and organization may be used.
-
20.606 Replaced by (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Replaced by (product)
20.606
Document reference of any item(s) which replace(s) the document being indexed.
In the case of more than one identifier, it is understood that these documents
jointly replace the indexed item. This data element can also be used when a part
of the document is replaced; in this case, code P should be placed after the
number. This data element can also be used for a replacement in the (near)
future; in this case, the code F should be placed after the document number. For
part replacement in the future, use the code PF. If the document is not in the
database, the identifier will not be available; in such cases, text description should
then be given.
Identifier or text / replace codes
100
83
A(80),A(2)
EXAMPLE:
ETS 3000336:1993, F
<E20.606>
<REP.CODES> ... </REP.CODES>
</E20.606>
EXAMPLES:
</TEXT> <REP.CODES> P </REP.CODES> </E20.606>
<E20.606> <REC.ID> </REC.ID> <TEXT LANG=en> ETS 3000336:1993
</TEXT> <REP.CODES> F </REP.CODES> </E20.606>
Text; optional code P, F or PF (see 10.001 for SGML option)
10.100, 10.462
M
20.608 Included product
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Included product
20.608
Product reference(s) of any item(s) which are included in the product (e.g. a
handbook or collection) being indexed.
Identifier or text
100
80
A(80)
65
Permissible values:
See also:
Comments:
Field obligation:
EXAMPLES:
ETS 300001:1992-10
NFZ 44-001
<E20.608>
</E20.608>
EXAMPLES:
<E20.608> <REC.ID> A01054:20:4645101 </REC.ID> </E20.608>
<E20.608> <TEXT LANG=en> ETS 300001:1992-10 </TEXT> </E20.608>
<E20.608> <TEXT LANG=en> NFZ 44-001 </TEXT> </E20.608>
20.104, 20.606, 20.614
Use 20.614 for documents/products that are referenced, but not actually included,
in the document/product being indexed.
-
20.610 Replaces (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
66
Replaces (product)
20.610
Document reference of any item(s) which are replaced by the document being
indexed. This data element can also be used when a part of another document is
replaced; in this case, the code P should be placed after the number. This data
element can also be used for a replacement in the (near) future; in this case, the
code F should be placed after the document number. For part replacement in the
future, use the code PF. If the document is not in the database, the identifier will
not be available; in such cases, text description should then be given.
Identifier or text / replace code
100
83
A(80),A(2)
EXAMPLES:
ETS 300001:1992-10
NFZ 44-001, F
<E20.610>
<REP.CODES> ... </REP.CODES>
</E20.610>
EXAMPLES:
</TEXT> <REP.CODES> P </REP.CODES> </E20.610>
<E20.610> <REC.ID> </REC.ID> <TEXT LANG=en> ETS 300001:1992-10
</TEXT> </E20.610>
<E20.610> <REC.ID> </REC.ID> <TEXT LANG=en> NFZ 44-001 </TEXT>
<REP.CODES> F </REP.CODES> </E20.610>
Identifier as in 20.001 or text; optional code P, F or PF
20.104, 20.606
Superseded drafts may be in this data element.
for superseded drafts etc. but these must be combined for data transfer.
M
ISONET MANUAL 1998
20.612 Corresponding documents (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Corresponding documents (product)
Implementation of; relationship; relatedness; equivalence; international
relationship; foreign relationship
20.612
Document references of the corresponding international, regional or national
documents which have a degree of equivalence (codes for the degree of
equivalence to be in allocated in accordance with ISO/IEC Guides 3 and 21).
Please note that ISO Guides 3 and 21 are under revision.
Text / equivalence code
100
84
A(80),A(3)
EXAMPLE:
ISO 9001:1994, IDT
<E20.612>
</E20.612>
Examples:
<E20.612> <REC.ID> </REC.ID> <TEXT LANG=en> ISO 9001:1994
</TEXT> <EQUIV.CODE> IDT </EQUIV.CODE> </E20.612>
</TEXT> <EQUIV.CODE> NEQ </EQUIV.CODE> </E20.612>
Identifier as in 20.104 or text, followed by one of the following codes:
IDT
Identical
EQV
Equivalent
MOD Modified
NEQ Not equivalent
20.616
When a standard is an implementation of more then one standard, and there are
no changes in the technical content, then EQV should be used for the reference
to each document implemented.
for IDT, EQV, MOD and NEQ, etc. but these must be combined for data transfer.
Modified is used in cases where the document contains all details of alterations.
for international, regional or foreign relatedness, but these must be combined for
data transfer.
If users use separate fields to hold this data then they should have a method of
separating the transferred data into these fields.
Relationships to Harmonization Documents are also included in this data element.
M
67
20.614 Cross-references
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Cross-references
20.614
Identifiers of documents cited in the item being indexed but not categorized
among the conformity relationships of data element 20.612. The code 'I' should
be used to indicate informative references. If the documents are not in the
database, their record identifiers (20.001) will not be available; in such cases, text
descriptions should be given.
Identifiers or text / I-code
200
152
A(150),A
EXAMPLES:
NEN 7000:1989,I
ISO 1951:1973
<E20.614>
<I.CODE> ... </I.CODE>
</E20.614>
EXAMPLES:
</TEXT> <I.CODE> </I.CODE> </E20.614>
<E20.614> <REC.ID> </REC.ID> <TEXT LANG=en> NEN 7000:1989
</TEXT> <I.CODE> I </I.CODE> </E20.614>
Identifiers or document references (national, regional and international) and
optional I-code
In the case of regulations referring to standards or standards referring to
regulations, use data element 20.618 or 20.620
This will be a combined element for those users who use separate elements for
normative and informative cross references.
-
20.616 References to implementations
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
68
References to implementations
Implemented by
20.504
Identifiers of documents that are implementations of this international or regional
document with a code for the degree of equivalence. If the documents are not in
the database, their identifiers will not be available; in such cases, text descriptions
should be given.
Identifier or text / equivalence code
150
84
AAAAAA:XX:I(20),A(3) or A(80),A(3)
EXAMPLES:
A01054:20:101, MOD
NEN-EN-ISO 9001:1994,IDT
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
<E20.616>
<! Optional pointer to document identifier >
<DOC.ID> ... </DOC.ID>
</E20.616>
EXAMPLES:
<E20.616> <DOC.ID> A01054:20:101 <DOC.ID> <TEXT LANG=AA>
</TEXT> <EQUIV.CODE> MOD </EQUIV.CODE> </E20.616>
<E20.616> <DOC.ID> <DOC.ID> <TEXT LANG=en> NEN-ENISO 9001:1994 </TEXT> <EQUIV.CODE> IDT </EQUIV.CODE> </E20.616>
Text, followed by a comma and one of the following codes:
IDT
Identical
EQV
Equivalent
NEQ
Not equivalent
MOD
Modified (see comments)
20.612
Modified is used when documents contain all details of alterations to the
implemented document.
-
20.618 Regulations referred to
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Regulations referred to
Legislation referred to
20.618
Document references of government regulations which are referred to in the
document.
Text
100
250
A(250)
EXAMPLE:
89/336/EEC, PBC 328:1996
<E20.618>
</E20.618>
EXAMPLES:
</TEXT> </E20.618>
<E20.618> <REC.ID> </REC.ID> <TEXT LANG=en> 89/336/EEC,PBC
328:1996 </TEXT></E20.618>
20.104, 20.618
Where there is need for explanation, this should be placed after a comma.
Informative references to regulations should be included in 20.614
-
69
20.620 Documents referred to
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Documents referred to
20.620
Identifiers of documents referred to in government regulations. If the documents
are not in the database, their identifiers (as defined in 20.001) will not be available;
in such cases, text descriptions should be given to allow these documents to be
traced.
Text
100
250
A(250)
EXAMPLE:
NEN-EN 292-1:1994
<E20.620>
</E20.620>
EXAMPLES:
</TEXT> </E20.620>
<E20.620> <REC.ID> </REC.ID> <TEXT LANG=en> NEN-EN 292-1:1994
</TEXT></E20.620>
20.104, 20.620
When there is a need for some explanation, place this after a comma
-
20.622 Certification systems
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
70
Certification systems
20.622
Name of any certification system using this document
Text
20
80
A(80)
EXAMPLE:
Certification system X
<E20.622>
</E20.622>
EXAMPLE:
<E20.622> <TEXT LANG=en> Certification system X </TEXT> </E20.622>
-
ISONET MANUAL 1998
20.700 Issuing body
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Issuing body
Originating body; owner of the document
20.700
The acronym of the organization which is responsible for the development,
preparation and issuing of the document
5
15
A(15)
EXAMPLE:
BSI
<E20.700>
</E20.700>
EXAMPLE:
Acronyms as in 80.102
20.704, 80.102
A reference table containing the names of standards institutes and international
bodies with their acronyms or codes should be maintained and provided by the
organization providing the data. In the case of language dependent acronyms, the
translation of the acronym in English and/or French should be in the reference
table.
-
20.702 Supplier
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Supplier
20.702
The acronym of the organization which is the source of availability of the item. The
supplier of the document is not always the same as the issuing body.
100
15
A(15)
EXAMPLE:
BSI
<E20.702>
</E20.702>
EXAMPLE:
Acronyms as in 80.102
20.700, 80.102
A reference table (table 80) containing the names of standards institutes, other
organizations and international bodies with their acronyms should be maintained
and provided by the organization providing the data
-
71
20.704 Validating body
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Validating body
20.704
The acronym of the legal or official authority which validates or approves the
document
5
15
A(15)
EXAMPLE:
BSI
<E20.704>
</E20.704>
EXAMPLE:
Acronyms in accordance with 80.102
80.102
A reference table containing the names of standards institutes, other
organizations and and international bodies with their acronyms should be
maintained and provided by the organization providing the data.
-
20.706 Area of validity
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
72
Area of validity
20.706
Countries to which the item applies
Country code or WW (worldwide)
50
2
AA
EXAMPLE:
GB
<E20.706>
<COUNTRY.CODE> ... </COUNTRY.CODE>
</E20.706>
EXAMPLE:
<E20.706> <COUNTRY.CODE> GB </COUNTRY.CODE> </E20.706>
Alpha-2 country codes in accordance with ISO 3166-1:1997 or WW for worldwide
validity
20.708, 20.712, 20.714
-
ISONET MANUAL 1998
20.708 Area of validity, country notes
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Area of validity, country notes
20.708
Explanation in text for the countries to which the item applies
Country code / text
50
250
(AA)A(250)
EXAMPLE:
GB*This standard is only valid in GB
<E20.708>
</E20.708>
EXAMPLE:
<E20.708> <COUNTRY.CODE> GB </COUNTRY.CODE> <TEXT
LANG=en> This standard is only valid in GB </TEXT> </E20.708>
Alpha-2 country codes in accordance with ISO 3166-1:1997
20.706, 20.712, 20.714
-
20.712 Implementation not required
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Implementation not required
A-deviations in Europe
20.712
Countries in which implementation of the regional standard is not mandatory. This
is due to national regulation, the alteration of which is for the time being outside
the jurisdiction of the member of the regional organization.
Country code
50
2
AA
EXAMPLE:
NO
<E20.712>
<COUNTRY.CODE > ... </COUNTRY.CODE>
</E20.712>
EXAMPLE:
<E20.712> <COUNTRY.CODE > NO </COUNTRY.CODE> </E20.712>
20.706, 20.714, 20.716
See IR 2:1994 CEN/CENELEC Internal Regulations - Part 2: Common rules for
standards work, p 27-28.
-
73
20.714 Implementation delayed
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Implementation delayed
B-deviations in Europe
20.714
Countries in which implementation of the regional standard is not mandatory. This
is to reflect a technical difference found to be necessary. There must be a
proposed date for its withdrawal.
Country code / date
50
11
AA,CCYYMMDD
EXAMPLE:
NO*20020320
<E20.714>
<DATE> ... </DATE>
</E20.714>
EXAMPLE:
<E20.714> <COUNTRY.CODE> NO </COUNTRY.CODE> <DATE> ,
20020320 </DATE> </E20.714>
20.706, 20.712, 20.716
See IR 2:1994 CEN/CENELEC Internal Regulations - Part 2: Common rules for
standards work p.27-28.
-
20.716 Implementation notes
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
74
Implementation notes
Deviation notes
20.716
Explanation in text to deviations and why a regional standard is not implemented.
Notes or further information on why implementation of standards or other
documents is delayed or may otherwise not occur.
Country code / text
1
2003
(AA)A(2000)
EXAMPLE:
NO*A-deviation because of the existing law on low voltage electricity
<E20.716>
<COUNTRY.CODE > ... </COUNTRY.CODE>
</E20.716>
EXAMPLE:
<E20.716> <COUNTRY.CODE > NO </COUNTRY.CODE> <TEXT
LANG=en> A-deviation because of the existing law on low voltage electricity
</TEXT> </E20.716>
20.712, 20.714, 20.708
See IR 2:1994, CEN/CENELEC Internal Regulations - Part 2: Common rules for
standards work p.27-28.
-
ISONET MANUAL 1998
20.718 Mode of implementation
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Mode of implementation
Mode of publication
20.718
Mode of implementation of a regional or international standard. The code is used
to specify whether the standard has been implemented by publication or
endorsement. It can also be that it was only announced in an official magazine.
Implementation code
1
1
A
EXAMPLE:
E
<E20.718>
<IMP.CODE> ... </IMP.CODE>
</E20.718>
EXAMPLE:
<E20.718> <IMP.CODE> E </IMP.CODE> </E20.718>
P
Publication
A
Announcement
E
Endorsement
R
Publication of ratified text
C
Cover sheet
-
20.800 Linking
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Linking
Identifier links; linked record identifiers
20.800
Record identifiers of those products which are linked together because they are
available in more than one medium (see 20.232) or more than one electronic
format (see 20.238)
Organization identifier:group number:integer
100
30
AAAAAA:XX:I(20)
EXAMPLE
A01054:20:77682
<E20.800>
</E20.800>
EXAMPLE:
<E20.800> <REC.ID> A01054:20:77682 </REC.ID></E20.800>
Record identifiers as in 20.001
Can be used to re-arrange related products into a certain order
-
75
20.900 General notes (product)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
General notes (product)
20.900
Any ancillary data, relating to the product, which cannot be entered in another
field
Text
1
500
A(500)
EXAMPLE:
Ancilliary data
<E20.900>
</E20.900>
EXAMPLE:
<E20.900> <TEXT LANG=en> Ancilliary data </TEXT> </E20.900>
-
20.902 Notes to date field
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
76
Notes to date field
20.902
Any extra information which could aid the content of any of the date fields. The
date field must be identified.
Text
1
200
A(200)
EXAMPLE:
The effective date is only applicable when the appropriate legislation comes
into force
<E20.902>
</E20.902>
EXAMPLE:
<E20.902> <TEXT LANG=en> The effective date is only applicable when the
appropriate legislation comes into force </TEXT> </E20.902>
-
ISONET MANUAL 1998
20.910 Full text file names
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Full text file names
20.910
File names of attached file(s) with the complete text of the document in an
electronic format
Text
30
12
A(12)
EXAMPLE:
NFN3701.PDF
<E20.910>
<FILE.NAME> ... </FILE.NAME>
</E20.910>
EXAMPLE:
<E20.910> <FILE.NAME> NFN3701.PDF </FILE.NAME> </E20.910>
The MIME specification (see annex B) should for used for extensions to file
names
-
77
30
DATA ELEMENTS FOR HARMONIZED STAGE CODES
All the data elements in group 30 are mandatory
30.002 Alteration date of record (harmonized stage code)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Alteration date of record (harmonized stage code)
30.002
The latest date when the harmonized stage code record was altered or changed
in any way
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E30.002> <DATE> ... </DATE> </E30.002>
EXAMPLE:
<E30.002> <DATE> 19961220 </DATE> </E30.002>
M
30.100 Stage codes identifiers
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
78
Stage codes identifiers
Stage codes
30.100
Identifier for the stage pertaining to the history or planning of the project in code
format
Stage code
1
5
XX.XX
EXAMPLE:
20.20
<E30.100>
</E30.100>
EXAMPLE:
<E30.100> <HSTAGE.CODE> 40.20 </HSTAGE.CODE> </E30.100>
Harmonized stage codes
20.300, 10.300
See the document approved by ISO Council: International harmonized stage code
system for the development of standards
M
ISONET MANUAL 1998
30.110 Stage codes, names
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Stage codes, names
30.110
The name of the harmonized stage code pertaining to the current stage of the
project
Text
1
200
A(200)
EXAMPLE:
DIS ballot
<E30.110>
</E30.110>
EXAMPLE:
<E30.110> <TEXT LANG=en> DIS ballot </TEXT> </E30.110>
M
79
40
DATA ELEMENTS FOR COMMITTEE INFORMATION
40.002 Alteration date of record (committee information)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Alteration date record (committee information)
40.002
The latest date when the record for committee information was altered or
changed in any way
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E40.002>
<DATE> ... </DATE>
</E40.002>
EXAMPLE:
<E40.002> <DATE> 19961220 </DATE> </E40.002>
M
40.104 Committee identifier
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
80
40.104
Complete reference of the technical board, technical committee,
subcommittee or working group responsible for the work item or document
(see 40.140)
Text
1
50
A(50)
EXAMPLES:
ISO/TC 20/SC 22
ISO/IEC JTC 1/SWG-RA
<E40.104>
<COMM.ID.CODE>
</COMM.ID.CODE>
</E40.104>
ISONET MANUAL 1998
EXAMPLES:
<E40.104> <COMM.ID.CODE> <TEXT LANG=en> ISO/TC 20/SC 22
</TEXT> </COMM.ID.CODE> </E40.104>
<E40.104> <COMM. ID.CODE> <TEXT LANG=en> ISO/IEC JTC 1/SWGRA </TEXT> </COMM. ID.CODE> </E40.104>
Permissible values:
See also:
Comments:
Field obligation:
20.204
M
40.110 Committee record number
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Committee record number
Record identifier
40.110
A unique identification of the record to be allocated to each new record and
used for identification whenever a record is changed or deleted. The record
identifier is allocated by the centre creating the record.
Integer
1
15
A(15)
EXAMPLE:
525353
<E40.110>
</E40.110>
EXAMPLE:
<E40.110> <TEXT LANG=en> 525353 </TETX> </E40.110>
M
40.130 Committee name
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Committee name
40.130
Name of the committee; a code P may be used to indicate provisional
Text / P-code
1
502
A(500),A
EXAMPLE:
Aircraft and space vehicles
<E40.130>
<P.CODE> ... </P.CODE>
</E40.130>
EXAMPLE:
<E40.130> <TEXT LANG=en> Aircraft and space vehicles </TEXT>
</E40.130>
M
81
40.140 Committee type
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Committee type
40.140
Code for status of the committee
Committee code
1
20
A(20)
EXAMPLE:
TC
<E40.140>
<COMM.STATUS.CODE> ... </COMM.STATUS.CODE>
</E40.140>
EXAMPLE:
<E40.140> <COMM.STATUS.CODE> TC </COMM.STATUS.CODE>
</E40.140>
CS
ISO Central Secretariat
MB
Management Board
SB
Sectoral Board
SC
Subcommittee
SG
Steering Group
SWG
Special Working Group
TAG
Technical Assessment Group
TC
Technical Committee
WG
Working Group
M
40.150 Reporting committee
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
82
Reporting committee
40.150
The identifier (see 40.104) of the committee reported to (at an upper level in
the hierarchy)
Text
1
50
A(50)
EXAMPLE:
ISO/TC 20
<E40.150>
</E40.150>
EXAMPLE:
<E40.150> <TEXT LANG=en> ISO/TC 20 </TEXT> </E40.150>
Identifier in accordance with 40.104
40.104
M
ISONET MANUAL 1998
40.160 Date of creation of committee
Name:
Synonyms:
Identifier:
Version:
Definition:
Maximum occurrence:
Permissible values:
Responsible organization:
See also:
Comments:
Field obligation:
Date of creation of committee
40.160
1
Date of creation of the committee
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E40.160>
<DATE> ... </DATE>
</E40.160>
EXAMPLE:
<E40.160> <DATE> 19961220 </DATE> </E40.160>
In cases where a committee has been disbanded and subsequently
reactivated, this field contains the reactivation date. Where the exact day is
uncertain, the day should be '01'. In cases where the month is also uncertain,
the entry should be '01-01'.
M
40.168 Current status
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Current status
40.168
Current status of the committee
Text
1
10
A(20)
EXAMPLES:
Active
Dormant
Disbanded
<E40.168>
</E40.168>
EXAMPLE:
<E40.168> <TEXT LANG=en> Active </TEXT> </E40.168>
-
83
40.169 Status date
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Status date
40.169
Date when the status of the committee changed
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E40.169>
<DATE> ... </DATE>
</E40.169>
EXAMPLE:
<E40.169> <DATE> 19961220 </DATE> </E40.169>
According to ISO 8601:1988
-
40.170 Scope of the committee
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Scope of the committee
40.170
The scope of the committee
Text
1
2000
A(2000)
EXAMPLE:
Standardization in the field of information technology
<E40.170>
</E40.170>
EXAMPLE:
<E40.170> <TEXT LANG=en> Standardization in the field of information
technology </TEXT> </E40.170>
Where possible the scope of the committee should be given in English or
French
M
40.180 Committee chairman
Name:
Synonyms:
Identifier:
Definition:
84
Committee chairman
40.180
Name of the chairman of the committee including title (if known) and other
names (if known) or initials (if known).
Text
ISONET MANUAL 1998
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
1
100
A(100)
EXAMPLE:
Mrs M.A. Lawler
<E40.180>
</E40.180>
EXAMPLE:
<E40.180> <TEXT LANG=en> Mrs. M.A. Lawler </TEXT> </E40.180>
May be vacant - in this case indicate with the word "vacant"
M
40.182 Country of the chairman
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Country of the chairman
40.182
Country code for the country of the chairman of the committee
Country code
1
2
AA
EXAMPLE
GB
<E40.182>
</E40.182>
EXAMPLE:
<E40.182> <COUNTRY.CODE> GB </COUNTRY.CODE> </E40.182>
M
40.185 Committee secretary
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
ISONET MANUAL 1998
Committee secretary
40.185
Name of the secretary/convenor responsible for the committee; note that it is
possible to have more than one secretary per committee. Include title (if
known) and other names (if known) or initials (if known)
Text
3
100
A(100)
EXAMPLES:
Ms L. Rajchel
Mr Rodney Smith
<E40.185>
</E40.185>
85
EXAMPLE:
<E40.185> <TEXT LANG=en> Ms L. Rajchel </TEXT> </E40.185>
Permissible values:
See also:
Comments:
Field obligation:
M
40.190 Organization holding the secretariat
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Organization holding the secretariat
40.190
Acronym of the organization carrying out the work of the secretariat when
entrusted by the organization responsible for the secretariat (40.192)
1
15
A(15)
EXAMPLE:
ANSI
<E40.190>
</E40.190>
EXAMPLE:
<E40.190> <ORG.ID> BSI </ORG.ID> </E40.190>
Acronym as in 80.102
80.102
M
40.192 Organization responsible for the secretariat
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
86
Organization responsible for the secretariat
40.192
Acronym of the organization officially representing the secretariat
1
15
A(15)
EXAMPLE:
ANSI
<E40.192>
</E40.192>
EXAMPLE:
Acronym as in 80.102
80.102
The organization responsible for the secretariat would normally carry out the
work of the secretariat itself. However, in certain cases, the organization
responsible for the secretariat may entrust the work to another organization
(see 40.190).
M
ISONET MANUAL 1998
40.200 Technical officer in charge of committee
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Technical officer in charge of committee
40.200
Name of the technical officer in charge. Include title (if known), other names (if
known) or initials (if known).
Text
1
100
A(100)
EXAMPLE:
Mr Keith Brannon
<E40.200>
</E40.200>
EXAMPLE:
<E40.200> <TEXT LANG=en> Mr Keith Brannon </TEXT> </E40.200>
This data element can be used for regional or international committees. It can
also be used when the secretary is not a member of the staff of the
standardization institute, but there is internally a technical officer in charge for
the contacts.
M
87
50
DATA ELEMENTS FOR ICS
50.001 ICS notation
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ICS notation
50.001
ICS classification number
ICS notation
1
9
XX
XX.XXX
XX.XXX.XX
EXAMPLES:
79.020
79.060.10
<E50.001>
</E50.001>
EXAMPLES:
<E50.001> <ICS.CODE> 79.060.10 </ICS.CODE> </E50.001>
ICS notations
10.502
See International Classification for Standards, Third edition, 1996
M
50.002 Alteration date of record (ICS)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
88
Alteration date of record (ICS)
50.002
The latest date when the ICS record was altered or changed in any way
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E50.002> <DATE> ... </DATE> </E50.002>
EXAMPLE:
<E50.002> <DATE> 19961220 </DATE> </E50.002>
M
ISONET MANUAL 1998
50.110 ICS FGS name
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ICS FGS name
Field, group, sub-group name
50.110
Full name corresponding to the ICS classification number of a field, group or
sub-group. All language versions of titles are included in this field. Either an
English or a French language version of the name must be included. Each
language version is recognized by its own language code.
Text
5
250
A(250)
EXAMPLE:
Wood technology processes
<E50.110>
<E/50.110>
EXAMPLE:
<E50.110> <TEXT LANG=en> Wood technology processes </TEXT>
<TEXT LANG=fr> Procédés technologiques du bois </TEXT> <E/50.110>
Descriptors in accordance with the International Classification for Standards
M
50.120 Note for scope of ICS notation
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Note for scope of ICS notation
50.120
A scope note, as a rule, lists subjects covered by a given field, group or subgroup or defines the subject of a given field, group or sub-group
Text
10
250
A(250)
EXAMPLE:
Including logging and wood treatment
<! If other ICS numbers are referenced, they should also be coded >
<E50.120>
</E50.120>
EXAMPLE:
<E50.120> <TEXT LANG=en> Including logging and wood treatment
</TEXT> <TEXT LANG=fr> Y compris bûcheronnage et traitement du
bois </TEXT> </E50.120>
M
89
50.122 Reference notes
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
90
Reference notes
50.122
A reference note refers to a subject, related to a given group/sub-group, of
another group/sub-group
Text
10
250
A(250)
EXAMPLE:
Wood-protecting chemicals, see 71.100.50
<E50.122>
</E50.122>
EXAMPLE:
<E50.122> <TEXT LANG=en> Wood-protecting chemicals, see
<ICS.CODE> 71.100.50 </ICS.CODE> </TEXT> </E50.122>
M
ISONET MANUAL 1998
60
DATA ELEMENTS FOR TIT THESAURUS
All the data elements in group 60 are mandatory.
60.001 Descriptor identifier, TIT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Descriptor identifier, TIT
Concept number
60.001
Unique code or number that is the identifier for each leading term used for
identification in the TIT thesaurus
TIT code
1
7
X(7)
EXAMPLE:
1242506
<E60.001>
<TIT.CODE> ... </ TIT.CODE>
</E60.001>
EXAMPLE:
<E60.001> < TIT.CODE> 1242506 </ TIT.CODE> </E60.001>
M
60.002 Alteration date of record (TIT thesaurus)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Alteration date of record (TIT thesaurus)
60.002
The latest date when the TIT thesaurus record was altered or changed in any way
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E60.002> <DATE> ... </DATE> </E60.002>
EXAMPLE:
<E60.002> <DATE> 19961220 </DATE> </E60.002>
M
91
60.005 TIT subject number
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
TIT subject number
60.005
Code number that is used for classifaction by subject in the TIT thesaurus
TIT subject code
3
3
XXX
EXAMPLE:
027*092
<E60.005>
<SUB.CODE> ... </SUB.CODE>
</E60.005>
EXAMPLE:
<E60.005> <SUB.CODE> 027 </SUB.CODE> <SUB.CODE> 092
</SUB.CODE> </E60.005>
Codes given in TIT thesaurus
M
60.105 Descriptor name, TIT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
92
Descriptor name, TIT
Leading term; LT; descriptor item; preferred term
60.105
Official descriptors of the TIT thesaurus in English or French
Text
1
80
A(80)
EXAMPLE:
fluid power
<E60.105>
</E60.105>
EXAMPLE:
<E60.105> <TEXT LANG=en> fluid flow </TEXT> </E60.105>
Descriptor from TIT
20.504
M
ISONET MANUAL 1998
60.110 Synonym, TIT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Synonym, TIT
UF, non-preferred term; used for
60.110
The synonym of a descriptor from the TIT thesaurus. A synonym is not
assigned to documents, but it is provided as an entry point in a thesaurus or
alphabetical index, the user being directed by an instruction (for example
'USE')
Text
100
80
A(80)
EXAMPLE:
physical properties
<E60.110>
</E60.110>
EXAMPLE:
<E60.110> <TEXT LANG=en> physical properties </TEXT> </E60.110>
For a synonym it is not necessary to be translated in another language
M
60.120 Scope note, TIT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Scope note, TIT
SN
60.120
A note attached to a descriptor, from the TIT thesaurus, to indicate its meaning
within an indexing language
Text
1
250
A(250)
EXAMPLE:
Includes threaded fittings and connecting pipe units
<E60.120>
</E60.120>
EXAMPLE:
<E60.120> <TEXT LANG=en> Includes threaded fittings and connecting
pipe units </TEXT> </E60.120>
M
60.140 Narrower term, TIT
Name:
Synonyms:
Identifier:
ISONET MANUAL 1998
Narrower term, TIT
NT
60.140
93
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Identifier of a descriptor, from the TIT thesaurus, which refers to a concept
with a more specific meaning (subordination)
Text
100
80
A(80)
EXAMPLE:
pipe flow
<E60.140>
</E60.140>
EXAMPLE:
<E60.140> <TEXT LANG=en> pipe flow </TEXT> </E60.140>
Existing descriptors
60.155
Because of the reciprocity between the narrower term (NT) and the broader
term (BT), for exchange purposes it may be sufficient to give only the narrower
term. Thesaurus software may be able to handle it automatically.
M
60.150 Related term, TIT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Related term, TIT
RT
60.150
A term that is associated to this descriptor (neither a synonym nor a narrower
term) from the TIT thesaurus
Text
100
80
A(80)
EXAMPLE:
cavitation
<E60.150>
</E60.150>
EXAMPLE:
<E60.150> <TEXT LANG=en> cavitation </TEXT> </E60.150>
M
60.155 Broader term, TIT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
94
Broader term, TIT
BT
60.155
Identifier of a descriptor, from the TIT thesaurus, which refers to a concept
with a more general meaning
Text
100
80
A(80)
EXAMPLE:
concrete products
ISONET MANUAL 1998
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
<E60.155>
</E60.155>
EXAMPLE:
<E60.155> <TEXT LANG=en> concrete products </TEXT> </E60.155>
60.140
M
95
70
DATA ELEMENTS FOR ROOT THESAURUS
All the data elements in group 70 are mandatory.
70.001 ROOT identifier
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ROOT identifier
Facet code; notation
70.001
Unique code or number that is the identifier for each descriptor, from the ROOT
thesaurus, used for identification and/or classification
ROOT code
1
20
A(20)
EXAMPLE:
BNL.C
<E70.001>
<ROOT.CODE> ... </ROOT.CODE>
</E70.001>
EXAMPLE:
<E70.001> <ROOT.CODE> BNL.C </ROOT.CODE> </E70.001>
M
70.002 Alteration date of record (ROOT thesaurus)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
96
Alteration date of record (ROOT thesaurus)
70.002
The latest date when the ROOT thesaurus record was altered or changed in any
way
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E70.002>
<DATE> ... </DATE>
</E70.002>
EXAMPLE:
<E70.002> <DATE> 19961220 </DATE> </E70.002>
M
ISONET MANUAL 1998
70.105 Descriptor name, ROOT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Descriptor name, ROOT
LT; descriptors; preferred terms; leading term
70.105
Official descriptors of the ROOT thesaurus in at least English
Text
1
100
A(100)
EXAMPLE:
en=Paints;Varnishes;Tests;Thermal testing
<E70.105>
</E70.105>
EXAMPLE:
<E70.105> <TEXT LANG=en> Paints <TEXT LANG=en> Varnishes </TEXT>
<TEXT LANG=en> Testing </TEXT> <TEXT LANG=en> Thermal testing
</TEXT> </E70.105>
Descriptors in ROOT
20.506
M
70.110 Non-preferred term, ROOT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Non-preferred term, ROOT
UF, non-preferred synonym; used for
70.110
The synonym of a descriptor from the ROOT thesaurus. A synonym is not
assigned to documents, but it is provided as an entry point in a thesaurus or
alphabetical index, the user being directed by an instruction (for example 'USE').
Text
100
100
A(100)
EXAMPLE:
en=Dilution methods (tracers)
<E70.110>
</E70.110>
EXAMPLE:
<E70.110> <TEXT LANG=en> Dilution methods (tracers) </TEXT>
</E70.110>
For a synonym, it is not necessary that a translation in another language is
available
M
97
70.120 Scope note, ROOT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Scope note, ROOT
SN
70.120
A note attached to a descriptor, from the ROOT thesaurus, to indicate its meaning
within an indexing language
Text
1
500
A(500)
EXAMPLE:
For specific types synthesize, for example
<E70.120>
</E70.120>
EXAMPLE:
<E70.120> <TEXT LANG=en> For specific types synthesize, for example
</TEXT> </E70.120>
M
70.130 Synthesis note, ROOT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
98
Synthesis note, ROOT
70.130
Indicates the terms to be used when the term given in 70.105 (Descriptor name)
is a synthesized term made up of the existing terms. It indicates that the main
term given in 70.105 is not to be used.
Text
5
100
A(500)
EXAMPLE:
Diseases, Heart
<E70.130>
</E70.130>
EXAMPLE:
<E70.130> <TEXT LANG=en> For specific types synthesize, for example
</TEXT> </E70.130>
Descriptors in ROOT
Usually two terms, but can be more
M
ISONET MANUAL 1998
70.140 Narrower term, ROOT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Narrower term, ROOT
NT
70.140
Descriptor from the ROOT thesaurus, which refers to a concept with a more
specific meaning (subordination)
Text
100
100
A(100)
EXAMPLE:
Thermal-cycling tests
<E70.140>
</E70.140>
EXAMPLE:
<E70.140> <TEXT LANG.=en> Thermal-cycling tests </TEXT> </E70.140>
70.100
M
70.150 Related term, ROOT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Related term, ROOT
RT
70.150
Identifier of another descriptor which is associated to this descriptor (neither a
synonym nor a narrower term) in the ROOT thesaurus
Text
100
100
A(100)
EXAMPLE:
<E70.150>
</E70.150>
EXAMPLE:
<E70.150> <TEXT LANG=en> Thermal-cycling tests </TEXT> </E70.150>
M
70.152 Broader term, ROOT
Name:
Synonyms:
Identifier:
Definition:
ISONET MANUAL 1998
Broader term, ROOT
BT
70.152
Identifier of a broader descriptor (neither a synonym nor a narrower term) from
the ROOT thesaurus
Text
99
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
100
100
A(100)
EXAMPLE:
<E70.152>
</E70.152>
EXAMPLE:
<E70.152> <TEXT LANG=en> Thermal-cycling tests </TEXT> </E70.152>
M
70.154 Facet indicator, ROOT
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
100
Facet indicator, ROOT
RT
70.154
Facet indicator from the ROOT thesaurus
Text
100
100
A(100)
EXAMPLE:
By active element
<E70.154>
</E70.154>
EXAMPLE:
<E70.154> <TEXT LANG=en> en=By active element </TEXT> </E70.154>
This applies to the first term under the facet indicator
M
ISONET MANUAL 1998
80
DATA ELEMENTS FOR ORGANIZATIONS
All the data elements in group 80, except 80.001, are mandatory
80.001 Organization identifier
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
80.001
Identifier for the organization which comprises the registered owner name
according to ISO 9070
1
15
A(15)
EXAMPLE:
A01054
<E80.001>
<ORG.ID> ... </ORG.ID>
</E80.001>
EXAMPLE:
<E80.001> <ORG.ID> A01054 </ORG.ID> </E80.001>
In accordance with ISO/IEC 9070:1991
-
80.002 Alteration date of record (organizations)
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Alteration date of record (organizations)
80.002
The latest date when the organizations record was altered or changed in any way
Date
1
8
CCYYMMDD
EXAMPLE:
19961220
<E80.002>
<DATE> ... </DATE>
</E80.002>
EXAMPLE:
<E80.002> <DATE> 19961220 </DATE> </E80.002>
M
101
80.102 Acronym
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Acronym
80.102
Acronym of organization (responsible for issuing / validating / supplying /
translating documents etc.). If an acronym is language dependent, the
language code is included.
3
15
A(15)
EXAMPLES:
AFNOR
en=IEC
fr=CEI
<E80.102>
</E80.102>
EXAMPLES:
<E80.102> <ORG.ACR> IEC </ORG.ACR> <LANG.CODE> en
</LANG.CODE> </E80.102>
<E80.102> <ORG.ACR> CEI </ORG.ACR> <LANG.CODE> fr
</LANG.CODE> </E80.102>
20.700, 20.704, 20.702, 20.604, 40.190
For standardization institutes, the official acronyms are mandatory
M
80.110 Name of organization
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
102
Name of organization
80.110
Name, in full, of the organization responsible for issuing/and or supplying
documents
Text
1
250
A(250)
EXAMPLE:
United Nations
<E80.110>
</E80.110>
EXAMPLE:
<E80.110> <TEXT LANG=en> United Nations </TEXT> <TEXT
LANG=nl> Verenigde naties </TEXT> </E80.110>
In the case of language dependent names, the official French and/or English
names should also be provided (if available).
M
ISONET MANUAL 1998
80.120 Scope
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Scope
80.120
Scope of the organization. Abstract which contains a brief survey of the
activities and responsibilities of the organization.
Text
1
1500
A(1500)
EXAMPLE:
Standardization in the field of welding
<E80.120>
</E80.120>
EXAMPLE:
<E80.120> <TEXT LANG=en> Standardization in the field of welding
</TEXT> </E80.120>
M
80.130 Postal address
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Postal address
80.130
Postal address of the organization (may be identical to 80.140)
Text
4
200
A(200)
EXAMPLE:
Case postale 56*CH-1211 Genève 20*Switzerland
<E80.130>
<TEXT LANG=AA> .... </TEXT>
</E80.130>
EXAMPLE:
<E80.130> <TEXT LANG=en> Case postale 56 </TEXT> <TEXT
LANG=en> CH-1211 Genève 20 </TEXT> <TEXT LANG=en> Switzerland
</TEXT> </E80.130>
80.140
The different parts of the address may be separated by the delimiter for subelements, which indicates a new line
M
103
80.140 Visiting address
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Visiting address
80.140
Visiting address of the organization
Text
4
200
A(200)
EXAMPLE:
1, rue de Varembé*Geneva*Switzerland
<E80.140>
</E80.140>
EXAMPLE:
<E80.140> <TEXT LANG=en> 1, rue de Varembé </TEXT> <TEXT
LANG=en> Geneva </TEXT> <TEXT LANG=en> Switzerland </TEXT>
</E80.140>
80.130
Could be the same as postal address.
The different parts of the address may be separated by the code for subelements which indicates that the part should begin on a new line
M
80.150 Telephone number
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
104
Telephone number
80.150
Main telephone number of the organization for information on documents
and/or work items
Integer
1
20
N(20)
EXAMPLE:
41227490111
<E80.150>
<TELNUMB>
<INT> ... </INT>
<INT> ... </INT>
<INT> ... </INT>
</TELNUMB>
</E80.150>
EXAMPLE:
<E80.150> <TELNUMB> <INT> 41 </INT> <INT> 22 </INT> <INT>
7490111 </INT> </TELNUMB> </E80.150>
Must include the country number and the district number
M
ISONET MANUAL 1998
80.160 Fax number
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Fax number
80.160
Fax number of the organization for information on documents and/or work
items
Numeric
1
20
N(20)
EXAMPLE:
41227333430
<E80.160>
<FAXNUMB>
<INT> ... </INT>
<INT> ... </INT>
<INT> ... </INT>
</FAXNUMB>
</E80.160>
EXAMPLE:
<E80.160> <FAXNUMB> <INT> 41 </INT> <INT> 22 </INT> <INT>
7333430 </INT> </FAXNUMB> </E80.160>
Must include the country number and the district number
M
80.165 Telex number
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
Telex number
80.165
Telex number of the organization for information on documents and/or work
items
Text
1
20
A(20)
EXAMPLE:
41 22 05 iso ch
<E80.165>
</E80.165>
EXAMPLE:
<E80.165> <TEXT LANG=en> 41 22 05 iso ch </TEXT> </E80.165>
M
105
80.170 X.400 e-mail address
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
X.400 e-mail address
e-mail, X-400
80.170
X.400 electronic mail address of the organization for information on documents
and/or work items, in the form:
S=A(?);O=A(?);P=A(?);A=A(?);C=(CC)
Text
1
150
A(150)
EXAMPLE:
X.400: c=ch; a=400net; p=iso; o=isocs; s=central
<E80.170>
<X.400CODE> ... </X.400CODE >
</E80.170>
EXAMPLE:
<E80.170> <X.400.CODE> c=ch; a=400net; p=iso; o=isocs; s=central
</X.400.CODE > </E80.170>
M
80.180 Internet e-mail address
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
106
Internet e-mail address
e-mail, internet; internet number
80.180
Electronic mail address on the Internet of the organization for information on
documents and/or work items; usually in the form A(?)@A(?).AA or
A(?)@A(?).AAA
Text
1
150
A(150)
EXAMPLES:
[email protected]
[email protected]
<E80.180>
</E80.180>
EXAMPLE:
<E80.180> <TEXT LANG=en> [email protected] </TEXT> </E80.180>
M
ISONET MANUAL 1998
80.190 Other electronic mail address
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
Other electronic mail address
e-mail (others)
70.190
Electronic mail address (other than Internet or X400) of the organization for
information on documents and/or work items
Text
1
100
A(100)
EXAMPLE:
Minitel : 3616 AFNOR
<E80.190>
<TEXT LANG=AA> Minitel : 3616 AFNOR </TEXT>
</E80.190>
EXAMPLE:
<E80.190> <TEXT LANG=en> Minitel : 3616 AFNOR </TEXT>
</E80.190>
M
80.200 URL
Name:
Synonyms:
Identifier:
Definition:
Maximum occurrence:
Permissible values:
See also:
Comments:
Field obligation:
ISONET MANUAL 1998
URL
URL; Unique Resource Locator
80.200
Unique Resource Locator on the Internet of the organization for information on
documents and/or work items
Text
1
200
A(200)
EXAMPLE:
http://www.iso.ch
<E80.200>
</E80.200>
EXAMPLE:
<E80.200> <TEXT LANG=en> http://www.iso.ch </TEXT> </E80.200>
URL of WWW home page, FTP-server, gopher-server, telnet-session or news
group.
M
107
ANNEX A — CONTACT INFORMATION FOR ISO MAINTENANCE AGENCIES
AND REGISTRATION AUTHORITIES
ISO/INFCO ICS Maintenance Agency
ISO 3297:1986
ISO Central Secretariat
1, rue de Varembé
CH-1211 GENEVE 20
ISSN International Centre
20, rue Bachaumont
F-75002 PARIS
Tel.
Fax
E-mail
Tel.
Fax
E-mail
+41 22 749 01 11
+41 22 733 66 26
[email protected]
+33 1 44 88 22 13
+33 1 40 26 32 43
[email protected]
ISO 2108:1992
ISO/IEC 9070:1991
Internationale ISBN-Agentur
Staatsbibliothek zu Berlin
Preussischer Kulturbesitz
Graphic Communications Association (GCA)
100 Dangerfield Road
Alexandria, VA 22314
Potsdamer Strasse 33
D-10785 BERLIN
Tel.
+1 703 519-8160
WWW: http://www.gca.org
Tel.
Fax
E-mail
+49 30 266 24 98
+49 30 266 23 78
[email protected]
ISO 3166-1:1997
ISO 3166 Maintenance Agency
c/o DIN Deutsches Institut für Normung
Burggrafenstrasse 6
D-10787 BERLIN
Tel.
Fax
E-mail
108
+49 30 2601 2791
+49 30 2601 1231
[email protected]
ISONET MANUAL 1998
ANNEX B — MIME SPECIFICATION
This annex is included for the purposes of identifying valid codes for the data element 20.238,
"electronic format".
MIME type
Application
Filename extensions
<MIME.TYPE>
<MIME.APP>
<MIME.EXT>
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
application
audio
audio
audio
image
image
image
ISONET MANUAL 1998
activemessage
andrew-inset
applefile
atomicmail
dca-rft
dec-dx
mac-binhex40
macwriteii
msword
news-message-id
news-transmission
octet-stream
oda
pdf
postscript
remote-printing
rtf
slate
x-mif
wita
wordperfect5.1
x-csh
x-dvi
x-hdf
x-latex
x-netcdf
x-sh
x-tcl
x-tex
x-texinfo
x-troff
x-troff-man
x-troff-me
x-troff-ms
x-wais-source
zip
x-bcpio
x-cpio
x-gtar
x-shar
x-sv4cpio
x-sv4crc
x-tar
x-ustar
basic
x-aiff
x-wav
gif
ief
jpeg
doc
bin
oda
pdf
ai eps ps
rtf
mif
csh
dvi
hdf
latex
nc cdf
sh
tcl
tex
texinfo texi
t tr roff
man
me
ms
src
zip
bcpio
cpio
gtar
shar
sv4cpio
sv4crc
tar
ustar
au snd
aif aiff aifc
wav
gif
ief
jpeg jpg jpe
109
image
image
image
image
image
image
image
image
image
image
message
message
message
message
multipart
multipart
multipart
multipart
multipart
text
text
text
text
text
text
video
video
video
video
110
tiff
x-cmu-raster
x-portable-anymap
x-portable-bitmap
x-portable-graymap
x-portable-pixmap
x-rgb
x-xbitmap
x-xpixmap
x-xwindowdump
external-body
news
partial
rfc822
alternative
appledouble
digest
mixed
parallel
html
x-sgml
sgml sgm
plain
richtext
tab-separated-values
x-setext
mpeg
quicktime
x-msvideo
x-sgi-movie
tiff tif
ras
pnm
pbm
pgm
ppm
rgb
xbm
xpm
xwd
html htm
txt
rtx
tsv
etx
mpeg mpg mpe
qt mov
avi
movie
ISONET MANUAL 1998
ANNEX C — EXAMPLES
NOTE - Data elements are shown on separate lines for presentation purposes only (i.e. there are no
new line characters in actual files used for data exchange).
C.1
Example of project information
a)
Conventional representation
Note that all mandatory (and other agreed) data elements are transferred - see subclause 3.3.2.
i)
File label
<E00.001> iso-8859-1
<E00.003> 19970429
<E00.004> 10
<E00.006> A01000
<E00.009> 13
<E00.011> 1
<E00.013> 11432
<E00.015> file546.txt
<E00.017> PKZIP
ii)
Project information
<E10.001> A01000:10:27915
<E10.002> 19970429
<E10.004> <E10.100> 27915
<E10.102> ISO/CD 2475
<E10.104> <E10.200> en=Chloroprene rubber (CR) - General-purpose types - Evaluation procedure
<E10.202> ISO
<E10.204> ISO/TC45
<E10.300> 30.99
<E10.302> 19970422
<E10.400> P
<E10.502> 83.060
b)
SGML representation
Note that all data elements are transferred even if "empty", in accordance with subclause 3.3.1.
i)
File label
<E00.003> <DATE> 19970429 </DATE> </E00.003>
<E00.006> <ORG.ID> A01000 </ORG.ID> </E00.006>
<E00.009> <INT> 13 </INT> </E00.009>
<E00.011> <INT> 1 </INT> </E00.011>
<E00.013> <INT> 11432 </INT> </E00.013>
<E00.015> <FILE.NAME> file546.txt </FILE.NAME> </E00.015>
<E00.017> <TEXT LANG=AA> PKZIP </TEXT> </E00.017>
ISONET MANUAL 1998
111
ii)
Project information
<E10.001> <REC.ID> A01000:10:27915 </REC.ID> </E10.001>
<E10.002> <DATE> 19970429 </DATE> </E10.002>
<E10.100> <INT> 27915 </INT> </E10.100>
<E10.102> <DOC.REF> <TEXT LANG=en> ISO/CD 2475 </TEXT> </DOC.REF> </E10.102>
<E10.104> <PRO.REF> <TEXT LANG=AA> </TEXT> <PRO.REF> </E10.104>
<E10.200> <TITLE> <LANG.CODE> en </LANG.CODE> <COMP.1> Chloroprene rubber (CR) </COMP.1>
<COMP.2> General-purpose types </COMP.2> <COMP.3> Evaluation procedure </COMP.3> </TITLE>
</E10.200>
<E10.202> <ORG.ACR> ISO </ORG.ACR> </E10.202>
<E10.204> <COMM.ID.CODE> ISO/TC45 </COMM.ID.CODE> </E10.204>
<E10.206> <TEXT LANG=AA> </TEXT> </E10.206>
<E10.300> <HSTAGE.CODE> 30.99 </HSTAGE.CODE> </E10.300>
<E10.302> <DATE> 19970422 </DATE> </E10.302>
<E10.304> <DATE> </DATE> </E10.304>
<E10.306> <DATE> </DATE> </E10.306>
<E10.308> <DATE> </DATE> </E10.308>
<E10.312> <DATE> </DATE> </E10.312>
<E10.314> <DATE> </DATE> </E10.314>
<E10.320> <DATE> </DATE> </E10.320>
<E10.322> <DATE> </DATE> </E10.322>
<E10.332> <DATE> </DATE> </E10.332>
<E10.334> <DATE> </DATE> </E10.334>
<E10.336> <HSTAGE.CODE> </HSTAGE.CODE> </E10.336>
<E10.338> <DATE> </DATE> </E10.338>
<E10.340> <DATE> </DATE> </E10.340>
<E10.400> <DEV.STATUS.CODE> P </DEV.STATUS.CODE> </E10.400>
<E10.500> <SORT.CODE> </SORT.CODE> </E10.500>
<E10.606> <REC.ID> </REC.ID> <TEXT LANG=AA> </TEXT> </E10.606>
<E10.610> <REC.ID> </REC.ID> <TEXT LANG=AA> </TEXT> </E10.610>
<E10.612> <REC.ID> <REC.ID> <TEXT LANG=AA> </TEXT> <EQUIV.CODE> </EQUIV.CODE></E10.612>
C.2
Example of product information
a)
Note that all mandatory (and other agreed) data elements for the different languages are
transferred in the file using appropriate separators, see subclause 3.3.2.
i)
File label
<E00.001> iso-8859-1
<E00.003> 19970425
<E00.004> 20
<E00.006> A01170
<E00.009> 78
112
ISONET MANUAL 1998
<E00.011> 1
<E00.013> 15334
<E00.015> file242.txt
<E00.017> PKZIP
ii)
Product information
<E20.001> A01070:20:5823
<E20.002> 19970901
<E20.004> 19970601
<E20.100> <E20.104> NF T 45-030
<E20.106> 46346346
<E20.110> <E20.112> <E20.116> ISSN 0335-3931
<E20.200>#fr=Matières premières pour l'industrie du caoutchouc - Accélérateurs du type
mercaptobenzothiazole (MBT) et disulfure de mercaptobenzothiazyle (MBTS) - Méthodes
d'essai*en=Rubber compounding ingredients - Accelerators, mercaptobenzothiazole (MBT) and
mercaptobenzothiazyl disulfide (MBTS) type - Test methods*de=Rohstoffe für die Gummiindustrie Merkaptobenzothiazol (MBT) und Merkaptobenzothiazyl-Disulfid (MBTS) - Prüfverfahren
<E20.204> <E20.206> fr=Le présent document décrit les méthodes d'essai des accélérateurs du type
mercaptobenzothiazole (MBT) et disulfure de mercaptobenzothiazyle (MBTS) qui sont parmi les plus
utilisés dans l'industrie du caoutchouc. La mesure du titre est réalisée par voie chimique et
chromatographie liquide haute performance qui assure une bonne reproductibilité des résultats. Le présent
document doit faciliter le dialogue entre l'utilisateur et le producteur et favoriser le passage éventuel en
assurance qualité.
<E20.208> <E20.212> 25
<E20.214> P
<E20.216> ST
<E20.220> 1
<E20.226> FFR323
<E20.230> prix HT
<E20.310> 19961200
<E20.330> <E20.502> 83.040.30
<E20.504> fr=industrie du caoutchouc;matière première;accélérateur de
résine;essai;dosage;cendre;matière volatile;détermination du titre;chromatographie liquide haute
performance*en=rubber industry;raw materials;resin hardeners;tests;determination of
content;ashes;volatile matter;titration;high performance liquid chromatography* de=kunststoff- und
kautschuktechnologie;rohstoff;zusatzstoff;kunststoff;pruefverfahren;gehaltsbestimmung;asche; bestim
mung der fluechtigen bestandteile;volumetrische analyse;fluessigkeitschromatographie
<E20.606> <E20.610> <E20.612> -
b)
SGML representation
i)
File label
<E00.003> <DATE> 19970425 </DATE> </E00.003>
<E00.006> <ORG.ID> A01170 </ORG.ID> </E00.006>
<E00.009> <INT> 78 </INT> </E00.009>
<E00.011> <INT> 1 </INT> </E00.011>
ISONET MANUAL 1998
113
<E00.013> <INT> 15334 </INT> </E00.013>
<E00.015> <FILE.NAME> file242.txt </FILE.NAME> </E00.015>
<E00.017> <COMP.METHOD> PKZIP </COMP.METHOD> </E00.017>
ii)
Product information
<E20.001> <REC.ID> A01070:20:5823 </REC.ID> </E20.001>
<E20.002> <DATE> 19970901 </DATE> </E20.002>
<E20.004> <DATE> 19970601 </DATE> </E20.004>
<E20.100> <PRO.REF> <TEXT LANG=AA> </TEXT> </PRO.REF> </E20.100>
<E20.104> <DOC.REF> <TEXT LANG=fr> NF T 45-030 </TEXT> </DOC.REF> </E20.104>
<E20.106> <TEXT> 46346346 </TEXT> </E20.106>
<E20.108> <AMEND.CODE> </AMEND.CODE> </E20.108>
<E20.110> <! Includes optional pointer to record identifier > <REC.ID> </REC.ID> <TEXT LANG=AA>
</TEXT> <F.CODE > </F.CODE> </E20.110>
</TEXT> <F-CODE> </F-CODE> </E20.112>
<E20.114> <ISBN.CODE> </ISBN.CODE> </E20.114>
<E20.116> <ISSN.CODE> ISSN 0335-3931 </ISSN.CODE> </E20.116>
<E20.200> <TITLE><LANG.CODE> fr </LANG.CODE> <COMP.1> Matières premières pour l'industrie du
caoutchouc </COMP.1> <COMP.2> Accélérateurs du type mercaptobenzothiazole (MBT) et disulfure de
mercaptobenzothiazyle (MBTS) </COMP.2> <COMP.3> Méthodes d'essai </COMP.3> </TITLE> <TITLE>
<LANG.CODE> en </LANG.CODE> <COMP.1> Rubber compounding ingredients </COMP.1> <COMP.2>
Accelerators, mercaptobenzothiazole (MBT) and mercaptobenzothiazyl disulfide (MBTS) type </COMP.2>
<COMP.3> Test methods </COMP.3> <COMP.4> </COP.4> <COMP.5> </COMP.5> <COMP.6>
</COMP.6> </TITLE> <TITLE> <LANG.CODE> de </LANG.CODE> <COMP.1> Rohstoffe für die
Gummiindustrie </COMP.1> <COMP.2> Merkaptobenzothiazol (MBT) und Merkaptobenzothiazyl-Disulfid
(MBTS) </COMP.2> <COMP.3> Prüfverfahren </COMP.3> </TITLE></E20.200>
<E20.204> <COMM.ID.CODE> </COMM.ID.CODE> </E20.204>
<E20.206> <TEXT LANG=fr> Le présent document décrit les méthodes d'essai des accélérateurs du type
mercaptobenzothiazole (MBT) et disulfure de mercaptobenzothiazyle (MBTS) qui sont parmi les plus utilisés
dans l'industrie du caoutchouc. La mesure du titre est réalisée par voie chimique et chromatographie liquide
haute performance qui assure une bonne reproductibilité des résultats. Le présent document doit faciliter le
dialogue entre l'utilisateur et le producteur et favoriser le passage éventuel en assurance qualité.</TEXT>
</E20. 206>
<E20.208> <LANG.CODE> </LANG.CODE> <LANG.CODE> </LANG.CODE> </E20.208>
<E20.212> <INT> 25 </INT> </E20.212>
<E20.214> <DOC.STATUS.CODE> P </DOC.STATUS.CODE> </E20.214>
<E20.216> <TYPE.CODE> ST </TYPE.CODE> </E20.216>
<E20.220> <TEXT LANG=AA> 1 </TEXT> </E20.220>
<E20.224> <REAL> </REAL> </E20.224>
<E20.226> <CURR.CODE> FFR </CURR.CODE> <REAL> 323 </REAL> <E/20.226>
<E20.228> <PRICE.CODE> </PRICE.CODE> </E20.228>
<E20.230> <TEXT LANG=fr> prix HT </TEXT> </E20.230>
<E20.232> <MEDIUM.CODE> </MEDIUM.CODE> </E20.232>
<E20.236> <PAPER.CODE> </PAPER.CODE> <TEXT LANG=AA> </TEXT> </E20.236>
<E20.238> <MIME.CODE> <MIME.TYPE> </MIME.TYPE> <MIME.APP> </MIME.APP> <MIME.EXT>
</MIME.EXT> </MIME.CODE> </E20.238>
<E20.242> <INT> </INT> </E20.242>
<E20.300> <HSTAGE.CODE> </HSTAGE.CODE> </E20.300>
<E20.302> <DATE> </DATE> </E20.302>
<E20.306> <DATE> </DATE> </E20.306>
<E20.310> <DATE> 19961200 </DATE> </E20.310>
<E20.312> <DATE> </DATE> </E20.312>
<E20.314> <DATE> </DATE> </E20.314>
<E20.316> <DATE> </DATE> </E20.316>
<E20.318> <DATE> </DATE> </E20.318>
114
ISONET MANUAL 1998
<E20.320> <DATE> </DATE> </E20.320>
<E20.324> <DATE> </DATE> </E20.324>
<E20.326> <DATE> </DATE> </E20.326>
<E20.328> <DATE> </DATE> </E20.328>
<E20.330> <DATE> </DATE> </E20.330>
<E20.332> <DATE> </DATE> </E20.332>
<E20.334> <DATE> </DATE> </E20.334>
<E20.500> <SORT.CODE> </SORT.CODE> </E20.500>
<E20.502> <ICS.CODE> 83.040.30 </ICS.CODE> </E20.502>
<E20.504> <TEXT LANG.= fr> industrie du caoutchouc </TEXT> <TEXT LANG = fr> matière première
</TEXT> <TEXT LANG = fr> accélérateur de résine </TEXT> <TEXT LANG = fr> essai </TEXT> <TEXT LANG
= fr> dosage </TEXT> <TEXT LANG = fr> cendre </TEXT> <TEXT LANG = fr> matière volatile </TEXT>
<TEXT LANG = fr> détermination du titre </TEXT> <TEXT LANG = fr> chromatographie liquide haute
performance </TEXT> <TEXT LANG = en> rubber industry </TEXT> <TEXT LANG = en> raw materials
</TEXT> <TEXT LANG = en> resin hardeners </TEXT> <TEXT LANG = en> tests </TEXT> <TEXT LANG =
en> determination of content </TEXT> <TEXT LANG = en> ashes </TEXT> <TEXT LANG = en> volatile
matter </TEXT> <TEXT LANG = en> titration </TEXT> <TEXT LANG = en> high performance liquid
chromatography </TEXT> <TEXT LANG = en> <TEXT LANG = de> kunststoff- und kautschuktechnologie
</TEXT> <TEXT LANG = de> rohstoff </TEXT> <TEXT LANG = de> zusatzstoff </TEXT> <TEXT LANG =
de> kunststoff </TEXT> <TEXT LANG = de> pruefverfahren </TEXT> <TEXT LANG = de>
gehaltsbestimmung </TEXT> <TEXT LANG = de> asche </TEXT> <TEXT LANG = de> bestim mung der
fluechtigen bestandteile </TEXT> <TEXT LANG = de> volumetrische analyse </TEXT> <TEXT LANG = de>
fluessigkeitschromatographie </TEXT> </E20.504>
</TEXT></E20.600>
<E20.602> <! Includes optional pointer to record identifier > <TEXT LANG=AA> </TEXT> <DOC.REF>
</DOC.REF> </E20.602>
<E20.604> <! Includes optional pointer to document identifier > <LANG.CODE> </LANG.CODE>
<ORG.ACR> </ORG.ACR> <DATE> </DATE> <DOC.REF> </DOC.REF> </E20.604>
</TEXT> <REP.CODES> <REP.CODES> </E20.606>
</TEXT> </E20.608>
</TEXT> <REP.CODES> <REP.CODES> </E20.610>
</TEXT> <EQUIV.CODE> </EQUIV.CODE> </E20.612>
<E20.614> <REC.ID> </REC.ID> <TEXT LANG=AA> </TEXT> <I.CODE> </I.CODE> </E20.614>
<E20.616> <DOC.ID> </DOC.ID> <TEXT LANG=AA> </TEXT> <EQUIV.CODE> </EQUIV.CODE>
</E20.616>
</TEXT> </E20.618>
</TEXT> </E20.620>
<E20.700> <ORG.ACR> </ORG.ACR> </E20.700>
<E20.702> <ORG.ACR> </ORG.ACR> </E20.702>
<E20.704> <ORG.ACR> </ORG.ACR> </E20.704>
<E20.706> <COUNTRY.CODE> </COUNTRY.CODE> </E20.706>
<E20.708> <COUNTRY.CODE> </COUNTRY.CODE> <TEXT LANG=AA> </TEXT> </E20.708>
<E20.712> <COUNTRY.CODE> </COUNTRY.CODE> </E20.712>
<E20.714> <COUNTRY.CODE> </COUNTRY.CODE> <DATE> </DATE> </E20.714>
<E20.716> <COUNTRY.CODE> </COUNTRY.CODE> <TEXT LANG=AA> </TEXT> </E20.716>
<E20.718> <IMP.CODE> </IMP.CODE> </E20.718>
<E20.800> <REC.ID> </REC.ID> </E20.800>
<E20.910> <FILE.NAME> </FILE.NAME> </E20.910>
ISONET MANUAL 1998
115
C.3
Example of committee information
a)
Conventional
i)
File label
<E00.001> iso-8859-1
<E00.003> 19970731
<E00.004> 40
<E00.006> A01170
<E00.009> 15
<E00.011> 22115
<E00.013> 15334
<E00.015> fileX.txt
<E00.017> Z
ii)
<E40.002> 19970423
<E40.104> ISO/TC 92/SC 1
<E40.110> 568386
<E40.130> en=Reaction to fire*fr=Réaction au feu
<E40.140> SC
<E40.150> ISO/TC 92
<E40.160> <E40.168> <E40.169> <E40.170> <E40.180> Mr. B. Sundström
<E40.182> S
<E40.185> Mrs. M. Di Carlo
<E40.190> BSI
<E40.192> BSI
<E40.200> Mr. Jean-Rémy Alessi
b)
SGML representation
i)
File label
<E00.003> <DATE> 19970731 </DATE> </E00.003>
<E00.006> <ORG.ID> A01170 </ORG.ID> </E00.006>
<E00.009> <INT> 15 </INT> </E00.009>
<E00.011> <INT> 22115 </INT> </E00.011>
<E00.013> <INT> 15334 </INT> </E00.013>
<E00.015> <FILE.NAME> fileX.txt </FILE.NAME> </E00.015>
<E00.017> <COMP.METHOD> Z </COMP.METHOD> </E00.017>
ii)
<E40.002> <DATE> 19970423 </DATE> </E40.002>
<E40.104> <COMM.ID.CODE> <TEXT LANG=en> ISO/TC 92/SC 1 </TEXT> </COMM.ID.CODE>
</E40.104>
116
ISONET MANUAL 1998
<E40.110> <TEXT LANG=en> 568386 </TEXT> </E40.110>
<E40.130> <TEXT LANG=en> Reaction to fire </TEXT> <P.CODE> </P.CODE> <TEXT LANG=fr> Réaction
au feu </TEXT> <P.CODE> </P.CODE> </E40.130>
<E40.140> <COMM.STATUS.CODE> SC <COMM.STATUS.CODE> </E40.140>
<E40.150> <TEXT LANG=en> ISO/TC 92 </TEXT> </E40.150>
<E40.160> <DATE> </DATE> </E40.160>
<E40.169> <DATE> </DATE> </E40.169>
<E40.180> <TEXT LANG=en> Mr. B. Sundström </TEXT> </E40.180>
<E40.182> <COUNTRY.CODE> S </COUNTRY.CODE> </E40.182>
<E40.185> <TEXT LANG=en> Mrs. M. Di Carlo </TEXT> </E40.185>
<E40.200> <TEXT LANG=en> Mr. Jean-Rémy Alessi </TEXT> </E40.200>
C.4
Example of organizations information
a)
i)
File labels
<E00.001> iso-8859-1
<E00.003> 19961225
<E00.004> 80
<E00.006> A01000
<E00.009> 14
<E00.011> 1
<E00.013> 3245
<E00.015> data112.dat
<E00.017> PKZIP
ii)
<E80.001> A01000
<E80.002> 19970424
<E80.102> #en=ISO*fr=ISO
<E80.110> #en=International Organization for Standardizaton*fr=Organisation internationale de
normalisation
<E80.120> en=ISO (International Organization for Standardization) is a worldwide federation of national
standards bodies, at present comprising 120 members, one in each country. The object of ISO is to
promote the development of standardization and related activities in the world with a view to facilitating
international exchange of goods and services, and to developing cooperation in the spheres of intellectual,
scientific, technological and economic activity. The results of ISO technical work are published as
International Standards
<E80.130> Case postale 56*1211 Geneva 20*Switzerland
<E80.140> 1, rue Varembé*1211 Geneva 20*Switzerland
<E80.150> 41227490111
<E80.160> 41227333430
<E80.165> 41 22 05 iso ch
<E80.170> c=ch; a=400net; p=iso; o=isocs; s=central
<E80.180> [email protected]
<E80.190> <E80.200> http://www.iso.ch
ISONET MANUAL 1998
117
b)
SGML representation
i)
File label
<E00.003> <DATE> 19961225 </DATE> </E00.003>
<E00.006> <ORG.ID> A01000 </ORG.ID> </E00.006>
<E00.009> <INT> 14 </INT> </E00.009>
<E00.011> <INT> 1 </INT> </E00.011>
<E00.013> <INT> 3245 </INT> </E00.013>
<E00.015> <FILE.NAME> data112.dat </FILE.NAME> </E00.015>
<E00.017> <COMP.METHOD> PKZIP </COMP.METHOD> </E00.017>
ii)
<E80.001> <ORG.ID> A01000 </ORG.ID> </E80.001>
<E80.002> <DATE> 19970424 </DATE> </E80.002>
<E80.102> <ORG.ACR> ISO </ORG.ACR> <LANG.CODE> en </LANG.CODE> <ORG.ACR> ISO
</ORG.ACR> <LANG.CODE> fr </LANG.CODE></E80.102>
<E80.110> <TEXT LANG=en> International Organization for Standardizaton </TEXT> <TEXT LANG=fr>
Organisation internationale de normalisation </TEXT> </E80.110>
<E80.120> <TEXT LANG=en> ISO (International Organization for Standardization) is a worldwide federation
of national standards bodies, at present comprising 120 members, one in each country. The object of ISO is
to promote the development of standardization and related activities in the world with a view to facilitating
international exchange of goods and services, and to developing cooperation in the spheres of intellectual,
scientific, technological and economic activity. The results of ISO technical work are published as International
Standards </TEXT> </E80.120>
<E80.130> <TEXT LANG=en> Case postale 56 </TEXT> <TEXT LANG=en> 1211 Geneva 20 </TEXT>
<TEXT LANG=en> Switzerland </TEXT> </E80.130>
<E80.140> <TEXT LANG=en> 1, rue Varembé </TEXT> <TEXT LANG=en> 1211 Geneva 20 </TEXT> <TEXT
LANG=en> Switzerland </TEXT> </E80.140>
<E80.150> <TELNUMB> <INT> 41 </INT> <INT> 22 </INT> <INT> 7490111 </INT> </TELNUMB>
</E80.150>
<E80.160> <FAXNUMB> <INT> 41 </INT> <INT> 22 </INT> <INT> 7333430 </INT> </FAXNUMB>
</E80.160>
<E80.165> <TEXT LANG=en> 41 22 05 iso ch </TEXT> </E80.165>
<E80.170> <X.400CODE> c=ch; a=400net; p=iso; o=isocs; s=central </X.400CODE ></E80.170>
<E80.180> <TEXT LANG=en> [email protected] </TEXT> </E80.180>
<E80.200> <TEXT LANG=en> http://www.iso.ch </TEXT> </E80.200>
118
ISONET MANUAL 1998
ALPHABETICAL INDEX OF DATA ELEMENTS
—A—
Abstract (product) ....................................................... 44
Abstract (project) ........................................................ 22
Acronym ................................................................... 102
Alteration date of record (committee information) ..... 80
Alteration date of record (harmonized stage code) ..... 78
Alteration date of record (ICS) .................................... 88
Alteration date of record (organizations) ................... 101
Alteration date of record (product) .............................. 37
Alteration date of record (project) ............................... 17
Alteration date of record (ROOT thesaurus) ............... 96
Alteration date of record (TIT thesaurus) .................... 91
Amended by ............................................................... 41
Amendment type ........................................................ 40
Amends ...................................................................... 41
Area of validity ............................................................ 72
Area of validity, country notes .................................... 73
Authors ....................................................................... 63
—B—
Broader term, ROOT ................................................... 99
Broader term, TIT ....................................................... 94
—C—
Certification systems .................................................. 70
Character set .............................................................. 13
Collation ...................................................................... 52
Committee chairman .................................................. 84
Committee identifier ................................................... 80
Committee name ........................................................ 81
Committee record number ......................................... 81
Committee secretary .................................................. 85
Committee type .......................................................... 82
Compression method ................................................. 16
Confirmation date ....................................................... 58
Core reference document .......................................... 29
Corresponding documents (product) .......................... 67
Corresponding documents (project) ........................... 34
Country of the chairman ............................................. 85
Creation date of record (product) ................................ 38
Creation date of record (project) ................................. 18
Cross-references ........................................................ 68
Current document reference ...................................... 19
Current stage code (product) ...................................... 54
Current stage code (project) ....................................... 22
Current status ............................................................. 83
—D—
Data element group .................................................... 14
Date for existing products .......................................... 60
Date for existing products (project) ............................ 26
Date of announcement ............................................... 56
Date of creation of committee ................................... 83
Date of creation of file ................................................ 13
Date of current stage (product) .................................. 54
ISONET MANUAL 1998
Date of current stage (project) .................................... 22
Date of expiration of validity ....................................... 58
Date of project initiation .............................................. 28
Date of publication ...................................................... 55
Date of validation ........................................................ 58
Descriptor identifier, TIT ............................................. 91
Descriptor name, ROOT ............................................. 97
Descriptor name, TIT .................................................. 92
Development obligation .............................................. 35
Development status .................................................... 28
Document series ......................................................... 47
Document source ....................................................... 63
Document status ........................................................ 46
Document type (product) ............................................ 46
Documents referred to ............................................... 70
—E—
Edition ......................................................................... 48
Edition notes ............................................................... 48
Effective date .............................................................. 57
Electronic file size ....................................................... 53
Electronic format ......................................................... 52
Electronic format notes ............................................... 53
—F—
Facet indicator, ROOT ............................................... 100
Fax number ............................................................... 105
File name .................................................................... 16
File owner identifier .................................................... 14
Financial authority ....................................................... 29
Free descriptors (product) ........................................... 62
Free descriptors (project) ............................................ 33
Full text file names ...................................................... 77
—G—
General notes (product) .............................................. 76
General notes (project) ................................................ 36
—I—
ICS (product) ............................................................... 61
ICS (project) ................................................................ 31
ICS FGS name ............................................................. 89
ICS notation ................................................................ 88
Implementation delayed ............................................. 74
Implementation not required ...................................... 73
Implementation notes ................................................. 74
Included product ......................................................... 65
Internet e-mail address ............................................. 106
ISBN ............................................................................ 42
ISSN ............................................................................ 42
Issuing body ................................................................ 71
Item number (project) ................................................. 18
—L—
Languages ................................................................... 45
Languages notes ......................................................... 45
119
Latest date for announcement (product) .....................56
Latest date for announcement (project) ......................25
Latest date for comment (product) .............................55
Latest date for comment (project) ...............................23
Latest date for withdrawal (product) ...........................59
Latest date for withdrawal (project) ............................26
Latest date of implementation (product) .....................55
Latest date of implementation (project) ......................24
Linking .........................................................................75
—M—
Medium .......................................................................51
Medium, notes ............................................................51
Mode of implementation .............................................75
—N—
Name of organization ................................................102
Narrower term, ROOT .................................................99
Narrower term, TIT ......................................................93
Next stage (project) .....................................................27
Non-preferred term, ROOT ..........................................97
Note for scope of ICS notation ....................................89
Notes to date field .......................................................76
Number of data elements ...........................................15
Number of pages .........................................................45
Number of records ......................................................15
—O—
Obligation development reference ..............................36
Organization holding the secretariat ............................86
Organization identifier ...............................................101
Organization responsible for the secretariat ................86
Other electronic mail address ...................................107
—P—
Postal address ...........................................................103
Price and currency .......................................................49
Price group ..................................................................50
Price notes ..................................................................50
Product reference ........................................................39
Project owner ..............................................................21
Project reference .........................................................19
Project reference (product) ..........................................38
—R—
Record identifier (product) ...........................................37
Record identifier (project ) ...........................................17
Reference notes ..........................................................90
References to implementations ..................................68
Regulations referred to ................................................69
Related term, ROOT ....................................................99
Related term, TIT .........................................................94
Replaced by (product) ..................................................65
Replaced by (project) ...................................................33
Replaces (product) .......................................................66
Replaces (project) ........................................................34
Reporting committee ..................................................82
Republished in .............................................................64
120
ROOT descriptors (product) ........................................ 62
ROOT descriptors (project) ......................................... 32
ROOT identifier ........................................................... 96
—S—
Scope ........................................................................ 103
Scope note, ROOT ...................................................... 98
Scope note, TIT ........................................................... 93
Scope of the committee ............................................. 84
Size of uncompressed file .......................................... 15
Sorting key (product) ................................................... 60
Sorting key (project) .................................................... 31
Stage codes identifiers ............................................... 78
Stage codes, names ................................................... 79
Status date .................................................................. 84
Stock number ............................................................. 40
Supplier ....................................................................... 71
Synonym, TIT .............................................................. 93
Synthesis note, ROOT ................................................ 98
—T—
Target date for draft .................................................... 23
Target date for formal vote ......................................... 24
Target date for next stage (project) ............................ 27
Target date for official publication .............................. 25
Target date for ratification (product) ........................... 57
Target date for ratification (project) ............................. 25
Technical committee (product) ................................... 44
Technical committee (project) .................................... 21
Technical officer in charge of committee ................... 87
Telephone number .................................................... 104
Telex number ............................................................ 105
TIT descriptors (product) ............................................. 61
TIT descriptors (project) .............................................. 32
TIT subject number ..................................................... 92
Title (product) .............................................................. 43
Title (project) ............................................................... 20
Track ........................................................................... 28
Translations ................................................................ 64
Type of project ............................................................ 30
Type of publication ..................................................... 30
—U—
URL ........................................................................... 107
—V—
Validating body ........................................................... 72
Version ........................................................................ 49
Visiting address ........................................................ 104
—W—
Withdrawal date (product) .......................................... 59
—X—
X.400 e-mail address ................................................ 106
ISONET MANUAL 1998
ISONET MANUAL 1998
121

ISONET Manual

Transcription

Documents pareils

DESADV - Carrefour.net