ISO/IEC TR 10000-1:1995
(Main)Information technology — Framework and taxonomy of International Standardized Profiles — Part 1: General principles and documentation framework
Information technology — Framework and taxonomy of International Standardized Profiles — Part 1: General principles and documentation framework
Technologies de l'information — Cadre et taxinomie des profils normalisés internationaux — Partie 1: Principes généraux et cadre de documentation
General Information
Relations
Standards Content (Sample)
ISO/IEC
TECHNICAL
REPORT
TR 10000-1
Third editipn
1995-1 2-1 5
Corrected and reprinted
1997-03-01
Information technology - Framework and
taxonomy of International Standardized
-
Profiles
Part 1:
General principles and documentation
framework
Technologies de l’information - Cadre et taxonomie des profils
normalisés internationaux -
Partie I: Principes généraux et cadre de documentation
Reference number
ISO/IEC/TR 10000-1 :1995(E)
---------------------- Page: 1 ----------------------
ISO/IEC TR 10000-1 : 1995(E)
Contents Page
Foreword .
iii
Introduction .
iv
1 Scope . 1
2 References .
1
3 Definitions .
2
3.1
Terms defined in this part of ISO/IEC TR 10000 . 2
3.2 Terms defined in ISO/IEC PDTR 14252. "Guide to the POSIX Open System
Environment (OSE)" .
2
3.3 Conformance terminology . 1. . 2
Abbreviations . 2
Purpose of profiles .
Concept of a profile .
6.1 The relationship to base standards .
6.2 Registration in lSPs .
6.3 Principles of profile content .
6.4 The meaning of conformance to a profile .
6.5 Conformance requirements of profiles .
7
Framework of the taxonomy of profiles .
8
7.1 Nature and purpose of the taxonomy .
8
7.2 Profile elements . 8
8 Structure of documentation for profiles .
8
8.1 Principles .
8
8.2 Multi-part lSPs .
8
8.3 Structure of lSPs .
9
8.4 Profile Object Identifiers .
9
AnnexA .
a
Rules for the drafting and presentation of International Standardized Profiles . 11
A.l Introduction .
11
A.2 General arrangement (Rules 2.1) .
11
A.3 Preliminary elements .
11
A.4 General normative elements .
12
A.5 Technical normative elements .
13
A.6 Supplementary elements .
14
A.7 Editorial and layout information .
14
O ISOAEC 1995
All rights reserved . Unless otherwise specified. no part of this publication may be reproduced or
utilized in any form or by any means. electronic or mechanical. including protocopying and micro-
film. without permission in writing from the publisher .
ISO/IEC Copyright Office Case postale 56 CH-1 21 1 Genève 20 Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISO/IEC TR 10000-1 : 1995(E)
@ ISOllEC
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide stan-
dardization. National bodies that are members of IS0 or IEC participate in the
development of International Standards through technical committees estab-
lished by the respective organization to deal with particular fields of technical
activity. IS0 and IEC technical committees collaborate in fields of mutual
interest. Other international organizations, governmental and non-governmental,
in liaison with IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint
technical committee, ISO/IEC JTC 1.
The main task of technical committees is to prepare International Standards. In
exceptional circumstances a technical committee may propose the publication
of a Technical Report of one of the following types:
- type 1, when the required support cannot be obtained for the publication of
an International Standard, despite repeated efforts;
-
type 2, when the subject is still under technical development or where for
any other reason there is the future but not immediate possibility of an
agreement on an International Standard;
-
type 3, when a technical committee has collected data of a different kind
from that which is normally published as an International Standard ("state
of the art", for example).
Technical reports of types 1- and 2 are subject to-review within three years of
publication, to decide whether they can be transformed into International Stan-
dards. Technical Reports of type 3 do not necessarily have to be reviewed until
the data they provide are considered to be no longer valid or useful.
ISO/IEC TR 10000-1, which is a Technical Report of type 3, was prepared by
Joint Technical Committee ISO/IEC JTC 1, Information technology.
This third edition cancels and replaces the second edition (ISO/IEC
TR 10000-1 :I 9921, which has been technically revised.
ISO/IEC TR 10000 consists of the following parts, under the general title Infor-
mation technology - Framework and taxonomy of International Standardized
Profiles:
-
Part I: General principles and documentation framework
-
Part 2: Principles and Taxonomy for OS1 profiles
-
Part 3: Principles and Taxonomy for Open System Environment profiles
...
111
---------------------- Page: 3 ----------------------
ISO/IEC TR 10000-1 :1995(E) @ ISO/IEC
Introduction
The context of Functional Standardization is one part of the overall field of IT standardization activities
covering
e
Base Standards, which define fundamentals and generalized procedures. They provide d)
infrastructure that Can be used by a variety of applications, each of which can make its own
selection from the options offered by them.
e
Profiles, which define conforming subsets or combinations of base standards used to provide
specific functions. Profiles identify the use of particular options available in the base standards, and
provide a basis for the development of uniform, internationally recognized, conformance tests.
e
Registration Mechanisms, which provide the means to specify detailed parameterization within the
framework of the base standards or profiles.
ISO/IEC JTC 1, the process of Functional Standardization is concerned with the methodology of
Within
defming profiles, and their publication in documents called "International Standardized Profiles" (ISPSI in
accordance with procedures contained in the Directives of JTC 1. The scope of Information Technology
standardization to which this process is being applied is that which corresponds to the generally understood,
but loosely defined, concept of "Open Systems". The objective is to facilitate the specification of IT systems
characterized by a high degree of interoperability and portability of their components.
In addition to ISO/IEC TR 10000, the secretariat of the Special Group on Functional Standardizati
maintains a standing document (SD-4) entitled "Directory of lSPs and Profiles contained therein". This "i%
a factual record of which lSPs exist, or are in preparation, together with an executive summary of each
profile. It is subject to regular updating by the Secretariat of ISO/IEC JTC 1 /SGFS.
iv
---------------------- Page: 4 ----------------------
TECHNICAL REPORT ISO/IEC TR 10000-1:1995(E)
Information technology - Framework and taxonomy of International
Standardized Prof iles -
Part 1:
General principles and documentation framework
focus is the area of competence of ISO/IEC JTC 1,
but by mutual agreement with JTC 1, other Technical
1 Scope
Committees may undertake similar functional stan-
This part of ISO/IEC TR 10000 defines the concept dardization activities leading to the inclusion of
of profiles, and the way in which they are docu- additional material in this Technical Report.
ented in International Standardized Profiles. It gives
uidance to organizations making proposals for Draft
International Standardized Profiles on the nature and 2 References
content of the documents they are producing.
The following standards contain provisions which,
through reference in this text, constitute provisions
This part of ISO/IECITR 1 O000 outlines concepts of
of this part of ISO/IEC TR 10000. At the time of
profiles and taxonomies (or Classification Schemes),
and the format and content of ISPs. Annex A gives publication, the editions indicated were valid. All
details of the format and the content of ISPs as standards are subject to revision, and parties to
required by ISO/IEC JTC 1. agreements based on this part of ISO/IEC TR 1 O000
are encouraged to investigate the possibility of
ISO/IEC TR 10000-2 provides principles and a applying the most recent editions of the standards
classification scheme for OS1 profiles which may be indicated below. Members of IEC and IS0 maintain
or have been submitted for ratification as Interna- registers of currently valid International Standards.
tional Standardized Profiles.
ISO/IEC 9834-1 : 1993 Information technoiogy- Open
NOTE - These OS1 profiles specify OS1 base standards, and those
Systems Interconnection - Procedures for the oper-
base standards concerned with interchange formats and data
ation of OS1 Registration Authorities - Part I: General
representation which are expected to be used in conjunction with
procedures. (Corresponds to ITU- T Recommendation
X. 660)
ISO/IEC TR 10000-3 provides the context for func-
ISO/IEC TR 10000-2: 1995, Information technology-
tional standardization in support of Open System
Framework and taxonom y of International Standard-
Environments (OSE), and principles and a classifica-
ized Profiles - Part 2: Principles and Taxonomy for
tion scheme for OSE profiles which may be or have
OS/ profiles.
been submitted for ratification as International
Standardized Profiles. It outlines the basic OSE
ISO/IEC TR 10000-3: 1995, Information technology-
objectives and concepts, and defines an approach
Frame work and taxonom y of International Stan-
and format for OSE profiles specified by International
dardized Profiles - Part 3: Principles and Taxonom y
Standardized Profiles and, along with this part of
far Open System Environment profiles.
ISO/IEC TR 10000, gives guidance to organizations
making proposals for Draft lSPs on the nature and
IEC/ISO Directives Part 3: 1989, Draftins and pres-
content of the documents they produce.
entation of International Standards.
Part 2 and Part 3 may be extended for OS1 and OSE
ISO/IEC JTC 1 Directives: 1995, Procedures for the
profiles respectively and further parts of ISO/IEC
technical work of ISO/lEC JTC 1 on Information
TR 1 O000 may be developed to define other classes
Technolog y.
of profiles.
ISO/IEC TR 10000 is applicable to all International
Standardized Profiles of IS0 and IEC. Its primary
1
---------------------- Page: 5 ----------------------
@ ISO/IEC
ISO/IEC TR 10000-1 :1995(E)
3.3.1 Implementation Conformance Statement
3 Definitions
A statement made by the supplier of an
[ICSI:
For the purposes of this part of ISO/IEC TR 10000, implementation or IT system claimed to conform to
the following definitions apply. or more specifications, stating which capabilities
one
have been implemented, specifically including the
Terms defined in this part of ISO/IEC relevant optional capabilities and limits.
3.1
TR 10000
NOTE - The ICs can take several forms (e.g. in OS1 it can be a
profile ICs, protocol ICs, information object ICs or profile specific
3.1 - 1 base standard: An approved International
ICs, as defined in ITU-T Rec. X.290 1 ISO/IEC 9646-1, and in
Standard or ITU-T Recommendation.
POSlX it is a POSlX Conformance Document as defined in lSO/lEC
DIS 13210).
3.1.2 International Standardized Profile: An
internationally agreed-to, harmonized document
4 Abbreviations
which describes one or more profiles.
3.1.3 IT system: A set of IT resources providing I cs Implementation Conformance State-
services at one or more interfaces. ment
3.1 -4 profile: A set of one or more base standards
ISP International Standardized Profile 0
and/or ISPs, and, where applicable, the identification
of chosen classes, conforming subsets, options and
OSE Open System Environment
parameters of those base standards, or lSPs necess-
ary to accomplish a particular function. os1 Open Systems Interconnection
NOTE - JTC 1 allows on exceptional basis references to other
specifications.
3.1.5 taxonomy: A classification scheme for
referencing profiles or sets of profiles unambiguously.
3.2 Terms defined in ISO/IEC PDTR 14252,
"Guide to the POSlX Open System Environment
(OSE)"
The following terms are defined in ISO/IEC PDTR
14252, "Guide to the POSlX OSE", and are included
here for convenience.
NOTE - Since PDTR 14252 is currently under ballot, this text will
be updated when the ballot resolution process is completed.
3.2.1 interoperability: The ability of two or more
IT systems to exchange information and to make
mutual use of the information that has been
exchanged.
3.2.2 Open System Environment: The compre-
hensive set of interfaces, services, and supporting
formats, plus user aspects, for interoperability and/or
portability of applications, data, or people, as spec-
ified by information technology standards and pro-
files.
3.3 Conformance terminology
This part of ISO/IEC TR 10000 uses the following
term related to conformance:
2
---------------------- Page: 6 ----------------------
@ ISO/iEC tSO/IEC TR 10000-1 : 1995(E)
It is not sufficient, however, just to create a docu-
5 Purpose of profiles mentation framework of this sort. Product develop-
ment and procurement need to be seen on a global,
Profiles define combinations of base standards or
and not just on a national, regional or sectoral scale.
other profiles for the purpose of
Therefore an objective of ISO/IEC JTC 1 is to create
the climate for the production of harmonized profiles,
identifying the standards and ISPs, together where a wide measure of agreement is reached
with appropriate classes, conforming sub- before proposals are submitted to ISO/IEC JTC 1.
sets, options and parameters, which are
necessary to accomplish identified functions Profiles should provide a clear identification of the
(e.g. interoperability) or to support a class of specific user requirements which are satisfied by the
applications (e.g. Transaction Processing
profiles. Occasionally, satisfaction of some of these
applications); requirements may identify functionality that is not
covered by accepted base standards. This is defined
providing a scheme of referencing the various as a "gap" in available standards.
uses of standards and lSPs which is mean-
ingful to both users and suppliers in response One purpose of identifying gaps in profiles is to
to a systematic identification and analysis of define areas where standardization activities are
user requirements; needed. Gaps should be identified by describing the
missing functionality.
providing a means to enhance the availability
NOTE - JTC 1 allows on exceptional basis references to other
for procurement of consistent implementa-
specifications.
tions of functionally defined groups of stan-
dards and ISPs, which are expected to be the
One of the most important roles for an International
major components of real IT systems, and
Standardized Profile is to serve as the basis for the
which realise the intentions of the correspon-
establishment of internationally recognized
ding reference models or frameworks with
conformance test suites and test methods. lSPs are
which the standards are associated;
produced not simply to legitimize a particular choice
of base standards and options, but to promote the
promoting uniformity in the development of
implementation of the referenced standards and lSPs
conformance tests for IT systems that imple-
in real IT systems in such a way as to achieve their
ment the functions associated with the pro-
intended goals - for example, interoperability and
files.
application portability. The development and wide-
spread acceptance of conformance tests for profiles
Underlying all these purposes is the assumption that
specified in ISPs is important to the successful
there exists a requirement for the definition, stan-
realization of this goal.
ardization, implementation, and testing of such a
8 rofile. The processes employed shall therefore
6 Concept of a profile
include the identification, recording, and monitoring
of such requirements, as expressed by the eventual
The concept of a profile, which fulfils the purposes
users of the profile.
defined in clause 5, is considered first in an abstract
sense, with particular emphasis on the significance of
Various bodies throughout the world are undertaking
the claim of conformance to a profile. This concept
work, in either regional or topic-oriented groups, in
of an individual profile is then extended to include
the area of functional standardization. Various names
defining its relationship to other profiles, i.e. the
are given to the results of this work (such as profiles,
concept of a taxonomy of profiles, and its place
functional standards, implementation agreements,
within it. Finally, since a profile has to have a con-
specifications) and various approaches are being
crete existence in order for it to be used effectively,
taken to the scope of the profiles and to the style in
these conceptual aspects are related to a formal
which they are documented. This Documentation
documentation scheme.
Framework of International Standardized Profiles has
been developed by tSO/IEC JTC 1 in order to create
Clauses 6 and 7 concentrate on defining the concept
a consistent classification scheme (a taxonomy), and
and taxonomy of the profiles, independently of the
a consistent documentation scope and style, into
way they are documented in ISPs. Clause 8 defines
which the work of functional standardization bodies
the actual documentation scheme and shows how
can be submitted, along with corresponding work
there is not necessarily one separate document (ISP)
from the members, technical committees and sub-
for each profile definition.
committees of IS0 and IEC.
3
---------------------- Page: 7 ----------------------
@ ISO/IEC
ISO/lEC TR 10000-1 : 1995(E)
NOTE - In this Technical Report, any text which describes the
Profiles are related to Base Standards, to Registration
relationship of an ISP to a base standard, shall be taken to be
Mechanisms, and to Conformance Tests of the IT
referring also to its relationship to any Technical Reports which
systems which implement them. The practical impli-
have been accepted according to the criteria given above.
cations of these relationships are developed in the
following sub-clauses, some of which specify require-
6.1 -3 Sise of informative References
ments that shall be satisfied by profiles defined in
ISPS.
It may be useful to make informative reference to
other documents in the process of defining a profile.
6.1 The relationship to base standards
For example:
6.1.1 Reduction of options
Reference may be made to applicable regional
a)
Some base standards provide options, anticipating
or national standards. Examples of the
the needs of a variety of applications of the
functionality which may require the use of
functionality described.
this expedient are:
Profiles promote integration of base standards by
O physical connectors
defining how to use a combination of base standards
for a given function and environment. In addition to
O electrical characteristics
the selection of base standards, a choice is made of
permitted options for each base standard and of
O safety requirements
suitable values for parameters left unspecified in the
base stahdard.
O character repertoires
Profiles shall not contradict base standards but shall
Such reference to regional or national stan-
make specific choices where options and ranges of
dards shall be placed within informative text
values are available. The choice of the base standard
within an ISP, or in a separate, informative,
options should be restricted so as to maximise the
part of a multi-part ISP. Such usage shall be
probability of achieving the objective of the profile.
justified on a case-by-case basis, either as a
Clause 6.3.1 states the requirements for deriving the
consequence of the lack of appropriate
functionality of a profile from the functionality of a
functionality in International Standards, or
base standard.
because of the existence of national or
regional regulatory requirements. It shall be
6.1 -2 Use of normative References
accompanied by details of the body respon-
sible for the distribution and maintenance of
An approved ISP shall make normative reference only
the standard.
to base standards or other ISPs.
There may be a need to define some aspec c
b)
In exceptional circumstances, described below,
of the required functionality of a profile
normative reference may be made to ISO/IEC Techni-
where suitable base standards or lSPs do not
cal Reports. Such reference, which requires that the
yet exist. Informative reference to the miss-
following conditions are met, shall be justified on a
ing material may be made (see 6.1.4 d.
case-by-case basis:
This should pnly be done where the missing
O no base standard addressing the require-
functionality is a relatively small proportion of
ments is available, but a Technical Report is;
the total scope of the profile. Where larger
sections of the functionality are missing (see
O the use is identified and discussed in the
6.1.4 b).
Explanatory Report which accompanies the
proposed draft for an ISP, justifying that use;
There may be a need to provide a reference
C)
to background material helpful in understand-
O
the JTC 1 body responsible for that Techni-
ing the profile, suitable for citation in the
cal Report agrees that a normative reference
Bibliography (as provided for in Annex A.4.3
is an appropriate use of that Technical
and A.6.1).
Report;
O
the National Bodies approve this usage in the
draft ISP ballot.
4
---------------------- Page: 8 ----------------------
ISO/IEC TR 10000-1 :1995(E)
ISO/IEC
tered name. Where the registered specification
6.1 -4 Other Factors
allows, the profile specification may define particular
Approval of an ISP by ISO/IEC members does not parameter values.
change the status of any documents referenced by it.
Where such a specification is not already registered,
Entry of a profile identifier into a taxonomy may then action must be taken to register it according to
occur before the referenced base standards are all the procedures defined by the base standard itself or
stable and approved. In these circumstances, regional by an associated registration procedure standard, in
or sectoral bodies may make use of interim or prelimi-
accordance with the general registration requirements
nary draft versions of profiles in their own controlled of the ISO/IEC JTC 1 Directives.
environment
In those cases where the specification of a required
6.2.2 Provisions of ITU-T Rec. X.660-series I
element of functionality for a profile does not exist in
ISOAEC 9834
an approved base standard or in a set of approved
base standards cited by an ISP, there are a number Where a requirement for registration is covered by
of possible approaches, one or more of which can be the provisions of ITU-T Rec. X.660-series 1 ISO/IEC
@opted in the writing of ISPs: 9834, then an ISP may act as the registration author-
ity, provided that an international registration author-
Postpone the creation of the ISP until it has
a) ity does not exist, and the type of specification to be
been possible to modify or to add to the registered falls within the scope of one of the classes
requirements specified in a base standard, or of profile defined in a taxonomy in this Technical
to create new base standards. In this case, it Report. The ISP concerned may be the ISP in which
is necessary for the ISP developer to liaise the specification is used, or a multi-part ISP may be
with the standards group responsible for that used as the registration authority. In such a case, the
base standard SO that the required changes general registration requirements of the ISO/IEC
may be made through established methods JTC 1 Directives, the provisions of this part of EO/-
such as defect reporting, amendment pro- IEC TR 10000, and the provisions of ITU-T Rec.
cedures, or the introduction of new work. X.660 I ISOAEC 9834-1, and of any other part or
parts of ITU-T Rec. X.660-series 1 ISO/IEC 9834 that
Propose a change to a taxonomy to add a concern this type of specification, are all applicable.
b)
further profile identifier with a scope which
matches the available base standards, and Where the provisions of ITU-T Rec. X.660-series I
progress an ISP to specify a profile with this ISO/IEC 9834 apply, an ISP may also act as a regis-
revised scope. tration authority for derivative and/or composite
specifications contained in the ISP. Such objects may
Draft the ISP in such a way that it clearly
be created:
(E'
identifies what required functionality of the
profile is missing, and, if possible, makes by the selection of specific optional elements
a)
informative reference to examples of possible in a registered specification of the same type
specifications which the user of the ISP may in a base standard or another ISP, or
choose to implement.
as a composition of registered specifications
b)
of the same type from multiple base stan-
dards or ISPs, or
6.2 Registration in lSPs
6.2. General provisions by a combination of a) and b).
C)
NOTE - 1 The referenced specifications must be of the same type
The application of base standards may involve
as the new specification. Only the selection of optional elements
reference to specifications that are subject to regis-
makes the specification new.
tration procedures (for example, for abstract syn-
taxes). Profiles that reference such base standards
NOTE - 2 Proliferation of registered specifications is strongly
must define the use of such specifications (i.e.
it creates 'islands of isolation' i.e. registered
discouraged because
indicate whether they are included in the specifica- specifications that differ in only the slightest manner are perceived
as being totally different. Every attempt should be made to develop
tion or not).
composite specifications with the broadest possible fields of use
to promote interoperability.
Where such a specification is already registered, the
profile specification shall refer to it using its regis-
5
---------------------- Page: 9 ----------------------
ISO/IEC TR 10000-1 : 1995(E) @ ISOAEC
6.3 Principles of profile content is capable of being used as an Executive
Summary of the profile;
6.3.1 General Principles
an illustration of the scenario within which
A profile makes explicit the relationships within a set the profile is applicable, giving, where poss-
of base standards used together (relationships which ible, a diagrammatic representation of the IT
can be implicit in the definitions of the base stan-
systems, applications and interfaces which
dards themselves), and may also specify particular
are relevant;
details of each base standard being used.
normative reference to a single set of base
A profile may refer to other International Standard- standards or ISPs, including precise identifi-
ized Profiles in order to make use of the functions cation of the actual texts of the base stan-
and interfaces already defined by them, and thus limit dards or lSPs being used; also identification
its own direct reference to base standards. of any approved amendments and technical
corrigenda (errata), conformance to which is
It follows that a profile identified as potentially having an impact on
achieving interoperability or portability using
a) shall restrict the choice of base standard the profile;
options to the extent necessary to maximise
the probability of achieving the objective of specifications of the application of each
the profile; for example to facilitate referenced base standard or ISP, stating the
interworking between IT systems, or porting choice of classes or conforming subsets, and
an application between them, where they
the selection of options, ranges of parameter
have implemented different selections of
values, etc, and reference to registered
options of the profile. Thus a profile may objects;
retain base standard options as options of
the profile provided that they do not affect a statement defining the requirements to be
interworking or portability.
observed by IT systems claiming
conformance to the profile, including any
shall not specify any requirements that would remaining permitted options of the referenced
b)
contradict or cause non-conformance to the
base standards or ISPs, which thus become
base standards to which it refers; options of the profile;
C) may contain conformance requirements if relevant, a reference to the spec
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.