ISO/IEC TR 10000-1:1998
(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)
TECHNICAL ISO/IEC
REPORT TR 10000-1
Fourth edition
1998-11-01
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
Reference number
B C
ISO/IEC TR 10000-1:1998(E)
---------------------- Page: 1 ----------------------
ISO/IEC TR 10000-1:1998(E)
Contents
Foreword .iii
Introduction.iv
1 Scope. 1
2 References . 1
3 Definitions . 1
3.1 Terms defined in this part of ISO/IEC TR 10000. 1
3.2 Terms defined in ISO/IEC TR 14252. 2
3.3 Conformance Terminology . 2
4 Abbreviations . 2
5 Pupose of profiles . 2
6 Concept of a profile. 3
6.1 The relationship to base standards .3
6.2 Registration in ISPs . 4
6.3 Principles of profile content . 5
6.4 The meaning of conformance to a profile. 6
6.5 Conformance requirements of profiles . 6
7 Framework of the taxonomy of profiles . 7
7.1 Nature and purpose of the taxonomy . 7
7.2 Profile elements. 7
8 Structure of documentation for profiles. 7
8.1 Principles . 7
8.2 Multi-part ISPs . 8
8.3 Structure of ISPs . 8
8.4 Profile Object Identifiers . 9
Annex A. 10
Rules for the drafting and presentation of International Standardized Profiles. 10
A.1 Introduction. 10
A.2 General arrangement (Rules 2.1). 10
A.3 Preliminary elements. 10
A.4 General normative elements .11
A.5 Technical normative elements.12
A.6 Supplementary elements. 13
A.7 Editorial and layout information . 13
© ISO/IEC 1998
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced
or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office • Case postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
©
ISO/IEC ISO/IEC TR 10000-1:1998(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations, governmental and non-
governmental, in liaison with ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.
The main task of technical committees is to prepare International Standards, but 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 Standards. 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 fourth edition cancels and replaces the third edition (ISO/IEC TR 10000-1:1995), which has been
technically revised.
ISO/IEC TR 10000 consists of the following parts, under the general title Information technology — Framework
and taxonomy of International Standardized Profiles:
— Part 1: General principles and documentation framework
— Part 2: Principles and Taxonomy for OSI Profiles
— Part 3: Principles and Taxonomy for Open System Environment Profiles
Other parts to be defined as necessary.
iii
---------------------- Page: 3 ----------------------
ISO/IEC TR 10000-1:1998(E) © ISO/IEC
Introduction
The context of Functional Standardization is one part of the overall field of IT standardization activities covering
• Base Standards, which define fundamentals and generalized procedures. They provide an
infrastructure that can be used by a variety of applications, each of which can make its own selection
from the options offered by them.
• 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.
• Registration Mechanisms, which provide the means to specify detailed parameterization within the
framework of the base standards or profiles.
Within ISO/IEC JTC 1, the process of Functional Standardization is concerned with the methodology of
defining profiles, and their publication in documents called "International Standardized Profiles" (ISPs) 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 Standardization maintains
a standing document (SD-4) entitled "Directory of ISPs and Profiles contained therein". This is a factual record
of which ISPs 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 ISO/IEC TR 10000-1:1998(E)
Information technology — Framework and taxonomy of
International Standardized Profiles —
Part 1:
General principles and documentation framework
1 Scope 2 References
This part of ISO/IEC TR 10000 defines the concept of ISO/IEC 9834-1:1993, Information technology - Open
profiles, and the way in which they are documented in Systems Interconnection - Procedures for the operation
International Standardized Profiles. It gives guidance to of OSI Registration Authorities: General procedures.
organizations making proposals for Draft International (Corresponds to ITU-T Recommendation X.660)
Standardized Profiles on the nature and content of the
documents they are producing. ISO/IEC TR 10000-2:1998, Information technology -
Framework and taxonomy of International Standardized
This part of ISO/IEC TR 10000 outlines concepts of
Profiles - Part 2: Principles and Taxonomy for OSI
profiles and taxonomies (or Classification Schemes),
Profiles.
and the format and content of ISPs. Annex A gives
details of the format and the content of ISPs as required
ISO/IEC TR 10000-3:1998, Information technology -
by ISO/IEC JTC 1.
Framework and taxonomy of International Standardized
Profiles - Part 3: Principles and Taxonomy for Open
ISO/IEC TR 10000-2 provides principles and a classifi-
System Environment Profiles.
cation scheme for OSI profiles which may be or have
been submitted for ratification as International Stan-
ISO/IEC Directives Part 3:1997, Drafting and pres-
dardized Profiles.
entation of International Standards.
NOTE - These OSI profiles specify OSI base standards, and those
ISO/IEC JTC 1 Directives:1995, Procedures for the
base standards concerned with interchange formats and data
technical work of ISO/IEC JTC 1 on Information Tech-
representation which are expected to be used in conjunction with
nology.
them.
ISO/IEC TR 10000-3 provides the context for functional
standardization in support of Open System Environ-
3 Definitions
ments (OSE), and principles and a classification
scheme for OSE profiles which may be or have been
For the purposes of this part of ISO/IEC TR 10000, the
submitted for ratification as International Standardized
following definitions apply.
Profiles. It outlines the basic OSE objectives and
concepts, and defines an approach and format for OSE
3.1 Terms defined in this part of ISO/IEC
profiles specified by International Standardized Profiles
TR 10000
and, along with this part of ISO/IEC TR 10000, gives
guidance to organizations making proposals for Draft
3.1.1 Base Standard: An approved International
ISPs on the nature and content of the documents they
Standard or ITU-T Recommendation.
produce.
3.1.2 International Standardized Profile: An
Part 2 and Part 3 may be extended for OSI and OSE
internationally agreed-to, harmonized document which
profiles respectively and further parts of ISO/IEC
describes one or more profiles.
TR 10000 may be developed to define other classes of
profiles.
3.1.3 IT System: A set of IT resources providing
services at one or more interfaces.
ISO/IEC TR 10000 is applicable to all International
Standardized Profiles of ISO and IEC. Its primary focus
3.1.4 Profile: A set of one or more base standards
is the area of competence of ISO/IEC JTC 1, but by
and/or ISPs, and, where applicable, the identification of
mutual agreement with JTC 1, other Technical Commit-
chosen classes, conforming subsets, options and
tees may undertake similar functional standardization
parameters of those base standards, or ISPs necessary
activities leading to the inclusion of additional material in
to accomplish a particular function.
this Technical Report.
1
---------------------- Page: 5 ----------------------
©
ISO/IEC TR 10000-1:1998(E) ISO/IEC
NOTE - ISPs may contain normative references to specifications
erability) or to support a class of applications
other than International Standards; see document JTC 1 N 4047: The
(e.g. Transaction Processing applications);
Normative Referencing of Specifications other than International
Standards in JTC 1 International Standardized Profiles - Guidelines
• providing a scheme of referencing the various
for ISP Submitters.
uses of standards and ISPs which is mean-
ingful to both users and suppliers in response
3.1.5 Taxonomy: A classification scheme for refer-
to a systematic identification and analysis of
encing profiles or sets of profiles unambiguously.
user requirements;
3.2 Terms defined in ISO/IEC TR 14252
• providing a means to enhance the availability
for procurement of consistent implementations
The following terms are defined in ISO/IEC
of functionally defined groups of standards and
TR 14252:1996, Information technology — Guide to the
ISPs, which are expected to be the major
POSIX Open System Environment (OSE), and are in-
components of real IT systems, and which
cluded here for convenience.
realise the intentions of the corresponding
reference models or frameworks with which the
3.2.1 Interoperability: The ability of two or more IT
standards are associated;
systems to exchange information and to make mutual
use of the information that has been exchanged.
• promoting uniformity in the development of
conformance tests for IT systems that imple-
3.2.2 Open System Environment: The compre-
ment the functions associated with the profiles.
hensive set of interfaces, services, and supporting
formats, plus user aspects, for interoperability and/or
Underlying all these purposes is the assumption that
portability of applications, data, or people, as specified
there exists a requirement for the definition, stan-
by information technology standards and profiles.
dardization, implementation, and testing of such a
profile. The processes employed shall therefore include
3.3 Conformance Terminology
the identification, recording, and monitoring of such
requirements, as expressed by the eventual users of
This part of ISO/IEC TR 10000 uses the following term
the profile.
related to conformance:
Various bodies throughout the world are undertaking
3.3.1 Implementation Conformance Statement
work, in either regional or topic-oriented groups, in the
[ICS]: A statement made by the supplier of an imple-
area of functional standardization. Various names are
mentation or IT system claimed to conform to one or
given to the results of this work (such as profiles,
more specifications, stating which capabilities have
functional standards, implementation agreements,
been implemented, specifically including the relevant
specifications) and various approaches are being taken
optional capabilities and limits.
to the scope of the profiles and to the style in which they
are documented. This Documentation Framework of
NOTE - The ICS can take several forms (e.g. in OSI it can be a profile
ICS, protocol ICS, information object ICS or profile specific ICS, as International Standardized Profiles has been developed
defined in ITU-T Rec. X.290 | ISO/IEC 9646-1, and in POSIX it is a
by ISO/IEC JTC 1 in order to create a consistent
POSIX Conformance Document as defined in ISO/IEC 13210:1994).
classification scheme (a taxonomy), and a consistent
documentation scope and style, into which the work of
functional standardization bodies can be submitted,
4 Abbreviations
along with corresponding work from the members,
technical committees and subcommittees of ISO and
ICS Implementation Conformance Statement
IEC.
ISP International Standardized Profile
It is not sufficient, however, just to create a docu-
mentation framework of this sort. Product development
OSE Open System Environment
and procurement need to be seen on a global, and not
just on a national, regional or sectoral scale. Therefore
OSI Open Systems Interconnection
an objective of ISO/IEC JTC 1 is to create the climate
for the production of harmonized profiles, where a wide
measure of agreement is reached before proposals are
5 Purpose of profiles
submitted to ISO/IEC JTC 1.
Profiles define combinations of base standards or other
Profiles should provide a clear identification of the
profiles for the purpose of
specific user requirements which are satisfied by the
profiles. Occasionally, satisfaction of some of these
• identifying the standards and ISPs, together
requirements may identify functionality that is not
with appropriate classes, conforming subsets,
covered by accepted base standards. This is defined as
options and parameters, which are necessary
a "gap" in available standards.
to accomplish identified functions (e.g. interop-
2
---------------------- Page: 6 ----------------------
©
ISO/IEC ISO/IEC TR 10000-1:1998(E)
One purpose of identifying gaps in profiles is to define Profiles promote integration of base standards by
areas where standardization activities are needed.
defining how to use a combination of base standards for
Gaps should be identified by describing the missing
a given function and environment. In addition to the
functionality.
selection of base standards, a choice is made of
permitted options for each base standard and of
NOTE - ISPs may contain normative references to specifications
suitable values for parameters left unspecified in the
other than International Standards; see document JTC 1 N 4047: The
Normative Referencing of Specifications other than International
base standard.
Standards in JTC 1 International Standardized Profiles - Guidelines
for ISP Submitters.
Profiles shall not contradict base standards but shall
make specific choices where options and ranges of
One of the most important roles for an International
values are available. The choice of the base standard
Standardized Profile is to serve as the basis for the
options should be restricted so as to maximise the
establishment of internationally recognized conform-
ance test suites and test methods. ISPs are produced probability of achieving the objective of the profile.
not simply to legitimize a particular choice of base
Subclause 6.3.1 states the requirements for deriving the
standards and options, but to promote the imple-
functionality of a profile from the functionality of a base
mentation of the referenced standards and ISPs in real
standard.
IT systems in such a way as to achieve their intended
goals - for example, interoperability and application
6.1.2 Use of normative References
portability. The development and widespread accept-
ance of conformance tests for profiles specified in ISPs
An approved ISP shall make normative reference only
is important to the successful realization of this goal.
to base standards or other ISPs.
In exceptional circumstances, described below, norma-
6 Concept of a profile
tive reference may be made to ISO/IEC Technical
Reports. Such reference, which requires that the
The concept of a profile, which fulfils the purposes
following conditions are met, shall be justified on a case-
defined in clause 5, is considered first in an abstract
by-case basis:
sense, with particular emphasis on the significance of
the claim of conformance to a profile. This concept of an
• no base standard addressing the requirements
individual profile is then extended to include defining its
is available, but a Technical Report is;
relationship to other profiles, i.e. the concept of a
taxonomy of profiles, and its place within it. Finally,
• the use is identified and discussed in the
since a profile has to have a concrete existence in order
Explanatory Report which accompanies the
for it to be used effectively, these conceptual aspects
proposed draft for an ISP, justifying that use;
are related to a formal documentation scheme.
• the JTC 1 body responsible for that Technical
Clauses 6 and 7 concentrate on defining the concept
Report agrees that a normative reference is an
and taxonomy of the profiles, independently of the way
appropriate use of that Technical Report;
they are documented in ISPs. Clause 8 defines the
actual documentation scheme and shows how there is
• the National Bodies approve this usage in the
not necessarily one separate document (ISP) for each
draft ISP ballot.
profile definition.
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 have
systems which implement them. The practical impli- been accepted according to the criteria given above.
cations of these relationships are developed in the
6.1.3 Use of informative References
following sub-clauses, some of which specify require-
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
a) Reference may be made to applicable regional
or national standards. Examples of the
Some base standards provide options, anticipating the
functionality which may require the use of this
needs of a variety of applications of the functionality
expedient are:
described.
3
---------------------- Page: 7 ----------------------
©
ISO/IEC TR 10000-1:1998(E) ISO/IEC
• physical connectors a) Postpone the creation of the ISP until it has
been possible to modify or to add to the requir-
• electrical characteristics ements specified in a base standard, or to
create new base standards. In this case, it is
• safety requirements necessary for the ISP developer to liaise with
the standards group responsible for that base
• character repertoires standard so that the required changes may be
made through established methods such as
Such reference to regional or national stan- defect reporting, amendment procedures, or
dards shall be placed within informative text the introduction of new work.
within an ISP, or in a separate, informative, part
of a multi-part ISP. Such usage shall be justified b) Propose a change to a taxonomy to add a
on a case-by-case basis, either as a further profile identifier with a scope which
consequence of the lack of appropriate matches the available base standards, and
functionality in International Standards, or progress an ISP to specify a profile with this
because of the existence of national or regional revised scope.
regulatory requirements. It shall be
accompanied by details of the body responsible c) Draft the ISP in such a way that it clearly
for the distribution and maintenance of the identifies what required functionality of the
standard. profile is missing, and, if possible, makes
informative reference to examples of possible
b) There may be a need to define some aspect of specifications which the user of the ISP may
the required functionality of a profile where choose to implement.
suitable base standards or ISPs do not yet
exist. Informative reference to the missing
material may be made (see 6.1.4 c). 6.2 Registration in ISPs
This should only be done where the missing 6.2.1 General provisions
functionality is a relatively small proportion of
the total scope of the profile. Where larger The application of base standards may involve refer-
sections of the functionality are missing (see ence to specifications that are subject to registration
6.1.4 b). procedures (for example, for abstract syntaxes). Profiles
that reference such base standards must define the use
c) There may be a need to provide a reference to of such specifications (i.e. indicate whether they are
background material helpful in understanding included in the specification or not).
the profile, suitable for citation in the Bibliogra-
phy (as provided for in A.4.3 and A.6.1). Where such a specification is already registered, the
profile specification shall refer to it using its registered
name. Where the registered specification allows, the
6.1.4 Other Factors profile specification may define particular parameter
values.
Approval of an ISP by ISO/IEC members does not
change the status of any documents referenced by it. Where such a specification is not already registered,
then action must be taken to register it according to the
Entry of a profile identifier into a taxonomy may occur procedures defined by the base standard itself or by an
before the referenced base standards are all stable and associated registration procedure standard, in accord-
approved. In these circumstances, regional or sectoral ance with the general registration requirements of the
bodies may make use of interim or preliminary draft ISO/IEC JTC 1 Directives.
versions of profiles in their own controlled environment.
6.2.2 Provisions of ITU-T Rec. X.660-series |
In those cases where the specification of a required ISO/IEC 9834
element of functionality for a profile does not exist in an
approved base standard or in a set of approved base Where a requirement for registration is covered by the
standards cited by an ISP, there are a number of provisions of ITU-T Rec. X.660-series | ISO/IEC 9834,
possible approaches, one or more of which can be then an ISP may act as the registration authority,
adopted in the writing of ISPs: provided that an international registration authority does
not exist, and the type of specification to be registered
4
---------------------- Page: 8 ----------------------
©
ISO/IEC ISO/IEC TR 10000-1:1998(E)
falls within the scope of one of the classes of profile profile; for example to facilitate interworking
defined in a taxonomy in this Technical Report. The ISP between IT systems, or porting an application
concerned may be the ISP in which the specification is between them, where they have implemented
used, or a multi-part ISP may be used as the different selections of options of the profile.
registration authority. In such a case, the general Thus a profile may retain base standard options
registration requirements of the ISO/IEC JTC 1 as options of the profile provided that they do
Directives, the provisions of this part of ISO/IEC not affect interworking or portability.
TR 10000, and the provisions of ITU-T Rec. X.660 |
ISO/IEC 9834-1, and of any other part or parts of ITU-T
b) shall not specify any requirements that would
Rec. X.660-series | ISO/IEC 9834 that concern this type
contradict or cause non-conformance to the
of specification, are all applicable.
base standards to which it refers;
Where the provisions of ITU-T Rec. X.660-series |
c) may contain conformance requirements which
ISO/IEC 9834 apply, an ISP may also act as a regis-
are more specific and limited in scope than
tration authority for derivative and/or composite specifi-
those of the base standards to which it refers.
cations contained in the ISP. Such objects may be
Whilst the capabilities and behaviour specified
created:
in a profile will always be valid in terms of the
base standards, a profile may exclude some
a) by the selection of specific optional elements in
valid optional capabilities and optional behav-
a registered specification of the same type in a
iour permitted in those base standards.
base standard or another ISP, or
Thus conformance to a profile implies by definition
b) as a composition of registered specifications of
conformance to the set of base standards which it
the same type from multiple base standards or
references. However, conformance to that set of base
ISPs, or
standards does not necessarily imply conformance to
the profile.
c) by a combination of a) and b).
6.3.2 Main elements of a profile definition
NOTE - 1 The referenced specifications must be of the same type as
the new specification. Only the selection of optional elements makes
the specification new.
The definition of a profile shall comprise the following
elements:
NOTE - 2 Proliferation of registered specifications is strongly
discouraged because it creates 'islands of isolation' i.e. registered
specifications that differ in only the slightest manner are perceived as a) a concise definition of the scope of the function
being to
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.