SIST-TS ISO/TS 19103:2009

TECHNICAL ISO/TS
SPECIFICATION 19103
First edition
2005-07-15
Geographic information — Conceptual
schema language
Information géographique — Schéma de language conceptuel

Reference number
©
ISO 2005
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2005
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 either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2005 – All rights reserved

Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Conformance. 1
3 Normative references . 1
4 Terms, definitions and abbreviations. 1
4.1 ISO/TS 19103 terms . 1
4.2 UML terms . 3
4.3 Abbreviations . 7
5 Organization . 7
6 The ISO/TS 19103 UML Profile. 8
6.1 Introduction . 8
6.2 General usage of UML. 8
6.3 Classes . 9
6.4 Attributes . 9
6.5 Data types. 9
6.6 Operations . 28
6.7 Relationships and associations . 28
6.8 Stereotypes and tagged values. 29
6.9 Optional, conditional and mandatory attributes and associations . 29
6.10 Naming and name spaces. 30
6.11 Packages . 31
6.12 Notes . 32
6.13 Constraints . 32
6.14 Documentation of models. 32
Annex A (normative) Abstract test suite. 34
Annex B (informative) On conceptual schema languages. 35
Annex C (informative) Modeling guidelines. 45
Annex D (informative) Introduction to UML. 54
Bibliography . 67

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
 an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
 an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting
a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a
further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is
confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an
International Standard or be withdrawn.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
IISO/TS 19103 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
iv © ISO 2005 – All rights reserved

Introduction
This Technical Specification of the ISO geographic information standards is concerned with the adoption and
use of a conceptual schema language (CSL) for developing computer-interpretable models, or schemas, of
geographic information. Standardization of geographic information requires the use of a formal CSL to specify
unambiguous schemas that can serve as a basis for data interchange and the definition of interoperable
services. An important goal of the ISO geographic information standards is to create a framework in which
data interchange and service interoperability can be realized across multiple implementation environments.
The adoption and consistent use of a CSL to specify geographic information is of fundamental importance in
achieving this goal.
There are two aspects to this Technical Specification. First, a CSL must be selected that meets the
requirements for rigorous representation of geographic information. This Technical Specification identifies the
combination of the Unified Modeling Language (UML) static structure diagram with its associated Object
Constraint Language (OCL) and a set of basic type definitions as the conceptual schema language for
specification of geographic information. Secondly, this Technical Specification provides guidelines on how
UML should be used to create geographic information and service models that are a basis for achieving the
goal of interoperability.
One goal of the ISO geographic information standards using UML models is that they will provide a basis for
mapping to encoding schemas as defined in ISO 19118, as well as a basis for creating implementation
specifications for implementation profiles for various environments.

TECHNICAL SPECIFICATION ISO/TS 19103:2005(E)

Geographic information — Conceptual schema language
1 Scope
This Technical Specification provides rules and guidelines for the use of a conceptual schema language within
the ISO geographic information standards. The chosen conceptual schema language is the Unified Modeling
Language (UML).
This Technical Specification provides a profile of the Unified Modeling Language (UML) for use with
geographic information. In addition, it provides guidelines on how UML should be used to create standardized
geographic information and service models.
2 Conformance
Any conceptual schema written for a specification, including a profile or functional standard, that claims
conformance with this Technical Specification shall pass all of the requirements described in the abstract test
suite in Annex A. Non-UML schemas shall be considered conformant if there is a well-defined mapping from a
model in the source language into an equivalent model in UML and that this model in UML is conformant.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 19101:2002, Geographic Information — Reference model
ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified Modeling Language
(UML) Version 1.4.2
4 Terms, definitions and abbreviations
4.1 ISO/TS 19103 terms
For the purposes of this document, the following terms and definitions apply.
4.1.1
application
manipulation and processing of data in support of user requirements
[ISO 19101]
4.1.2
application schema
conceptual schema for data required by one or more applications
[ISO 19101]
4.1.3
conceptual model
model that defines concepts of a universe of discourse
[ISO 19101]
4.1.4
conceptual schema
formal description of a conceptual model
[ISO 19101]
4.1.5
data type
specification of a value domain with operations allowed on values in this domain
EXAMPLE Integer, Real, Boolean, String, Date and SG Point (conversion of data into a series of codes).
NOTE Data types include primitive predefined types and user-definable types.
4.1.6
domain
well-defined set
NOTE Domains are used to define the domain set and range set of attributes, operators and functions.
4.1.7
feature
abstraction of real world phenomena
[ISO 19101]
NOTE 1 A feature may occur as a type or an instance. Feature type or feature instance should be used when only one
is meant.
[8]
NOTE 2 In UML a feature is a property, such as operation or attribute, which is encapsulated as part of a list within a
classifier, such as interface, class or data type.
4.1.8
feature association
relationship that links instances of one feature type with instances of the same or a different feature type
[ISO 19109]
NOTE 1 A feature association may occur as a type or an instance. Feature association type or feature association
instance is used when only one is meant.
NOTE 2 Feature associations include aggregation of features.
4.1.9
feature attribute
characteristic of a feature
[ISO 19101]
NOTE 1 A feature attribute has a name, a data type, and a value domain associated to it. A feature attribute for a
feature instance also has an attribute value taken from the value domain.
NOTE 2 A feature attribute may occur as a type or an instance. Feature attribute type or feature attribute instance
should be used when only one is meant.
2 © ISO 2005 – All rights reserved

4.1.10
feature operation
operation that every instance of a feature type may perform
[ISO 19110]
EXAMPLE 1 An operation upon a “dam” is to raise the dam. The result of this operation is to raise the level of water in
a reservoir.
EXAMPLE 2 An operation by a “
...