ISO 19103:2015
(Main)Geographic information — Conceptual schema language
Geographic information — Conceptual schema language
ISO 19103:2015 provides rules and guidelines for the use of a conceptual schema language within the context of geographic information. The chosen conceptual schema language is the Unified Modeling Language (UML). ISO 19103.2015 provides a profile of the Unified Modelling Language (UML). The standardization target type of this standard is UML schemas describing geographic information.
Information géographique — Langage de schéma conceptuel
Geografske informacije - Jezik za konceptualno shemo
Ta mednarodni standard določa pravila in smernice za uporabo jezika za konceptualno shemo v kontekstu geografskih informacij. Izbrani jezik za konceptualno shemo je poenoteni jezik modeliranja (UML). Ta mednarodni standard določa profil poenotenega jezika modeliranja (UML). Vrsta cilja standardizacije za ta standard so sheme poenotenega jezika modeliranja, ki opisujejo geografske informacije.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-januar-2020
Nadomešča:
SIST-TS ISO/TS 19103:2009
Geografske informacije - Jezik za konceptualno shemo
Geographic information -- Conceptual schema language
Information géographique -- Langage de schéma conceptuel
Ta slovenski standard je istoveten z: ISO 19103:2015
ICS:
07.040 Astronomija. Geodezija. Astronomy. Geodesy.
Geografija Geography
35.060 Jeziki, ki se uporabljajo v Languages used in
informacijski tehniki in information technology
tehnologiji
35.240.70 Uporabniške rešitve IT v IT applications in science
znanosti
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
INTERNATIONAL ISO
STANDARD 19103
First edition
2015-12-01
Geographic information — Conceptual
schema language
Information géographique — Langage de schéma conceptuel
Reference number
©
ISO 2015
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Conformance . 1
2.1 Introduction . 1
2.2 UML version conformance . 1
2.2.1 UML 2 conformance class. 1
2.2.2 UML 1 to UML2 mapping conformance class . 1
2.2.3 Conformant schema conformance class . 2
2.3 Data types conformance . 2
2.3.1 Introduction . 2
2.3.2 Core types conformance class . 2
2.3.3 Core and extension types conformance class . 2
2.4 Model documentation conformance . 3
2.4.1 Introduction . 3
2.4.2 Model documentation conformance class . 3
3 Normative references . 3
4 Terms and definitions . 4
5 Presentation and abbreviations . 8
5.1 Presentation . 8
5.2 Backwards compatibility to previous version of ISO 19103 . 8
5.3 Abbreviations . 8
6 The ISO 19103 UML Profile – Use of UML . 9
6.1 Introduction . 9
6.2 General use of UML . 9
6.3 Classifiers .10
6.4 Attributes .10
6.5 Enumerations and codelists .11
6.5.1 General rules .11
6.5.2 Enumerations .11
6.5.3 Code lists .12
6.6 Data types .13
6.7 Operations .13
6.8 Relationships .13
6.8.1 General.13
6.8.2 Associations .13
6.8.3 Generalizations.14
6.8.4 Realizations .14
6.9 Services .15
6.10 Stereotypes and keywords .16
6.10.1 Introduction .16
6.10.2 Stereotypes and keywords .16
6.11 Optional, conditional and mandatory attributes and association ends .16
6.11.1 Mandatory .16
6.11.2 Optional .17
6.11.3 Conditional .17
6.12 Naming and namespaces .17
6.13 Packages .18
6.14 Notes .18
6.15 Constraints .19
6.16 Documentation of models .19
7 Core data types .20
7.1 Introduction .20
7.2 Primitive types .20
7.2.1 General.20
7.2.2 Date .21
7.2.3 Time .21
7.2.4 DateTime .22
7.2.5 Number .22
7.2.6 Decimal . .24
7.2.7 Integer .24
7.2.8 Real .24
7.2.9 Vector .25
7.2.10 CharacterString .25
7.2.11 Boolean .27
7.3 Collections .27
7.3.1 General.27
7.3.2 Collection templates .28
7.3.3 Set .28
7.3.4 Bag .28
7.3.5 Sequence .29
7.4 Enumerated types .29
7.4.1 General.29
7.4.2 Bit .30
7.4.3 Digit .30
7.4.4 Sign .30
7.5 Name types .30
7.5.1 General.30
7.5.2 NameSpace .31
7.5.3 GenericName .33
7.5.4 ScopedName .33
7.5.5 LocalName .34
7.5.6 TypeName .35
7.5.7 MemberName .35
7.6 Any type .36
7.7 Record types .36
7.7.1 General.36
7.7.2 Record .36
7.7.3 RecordType .37
7.7.4 Field.37
7.7.5 FieldType .37
7.8 NULL and EMPTY values .37
Annex A (normative) Abstract test suite .38
Annex B (normative) Rules for mapping UML 1 models to UML 2 models .40
Annex C (normative) Data types – extension types .41
Annex D (normative) Formal UML profile .48
Annex E (informative) On conceptual schema languages .50
Annex F (informative) Modelling guidelines .58
Annex G (informative) Introduction to UML .67
Annex H (informative) Backwards compatibility .79
Bibliography .81
iv © ISO 2015 – All rights reserved
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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2. www.iso.org/directives
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. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received. www.iso.org/patents
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 211, Geographic information/Geomatics.
This first edition of ISO 19103:2015 cancels and replaces the first edition (ISO/TS 19103:2005).
Introduction
This International Standard of the ISO geographic information suite of 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 suite
of 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 International Standard. First, a CSL is selected that meets the requirements
for rigorous representation of geographic information. This International Standard 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 International Standard provides guidelines
on how UML should be used to create geographic information models that are a basis for achieving the
goal of interoperability.
One goal of the ISO geographic information suite of standards using UML models is that they will
provide a basis for model based mapping to encoding schemas like the ones defined in ISO 19118, as
well as a basis for creating implementation specifications for implementation profiles for various other
environments.
This International Standard describes the general metamodel for use of UML in the context of the
ISO geographic information series of standards. Aspects specifically dealing with the modelling of
application schemas are described in ISO 19109.
This International Standard is a revision of a previous version from 2005. Changes are documented in
Clause 5.
vi © ISO 2015 – All rights reserved
INTERNATIONAL STANDARD ISO 19103:2015(E)
Geographic information — Conceptual schema language
1 Scope
This International Standard provides rules and guidelines for the use of a conceptual schema language
within the context of geographic information. The chosen conceptual schema language is the Unified
Modeling Language (UML).
This International Standard provides a profile of the Unified Modelling Language (UML).
The standardization target type of this standard is UML schemas describing geographic information.
2 Conformance
2.1 Introduction
This International Standard defines three levels of conformance classes:
— UML version
— Data types
— Model documentation
To conform to this International Standard, the usage of a conceptual schema language shall satisfy
all of the requirements specified in one of the three levels of conformance described below, with the
corresponding abstract test suite in Annex A.
2.2 UML version conformance
2.2.1 UML 2 conformance class
Table 1 describes the conformance class for UML 2.
Table 1 — UML 2 conformance class
Conformance class identifier UML2
Standardization target type UML2 schemas for geographic information
Dependency ISO/IEC 19505-2:2012, Clause 2
OCL 2.3.1
Requirements All requirements in 6.2 to 6.12 except Requirement
2, and including Requirement 26.
Tests All tests in A.1.2
2.2.2 UML 1 to UML2 mapping conformance class
Table 2 describes the conformance class for mapping from UML 1.
Table 2 — UML 1 to UML 2 mapping conformance class
Conformance class identifier UML1
Standardization target type UML1 schemas for geographic information
Dependency UML2
ConformantSchema
ISO/IEC 19501:2005, Clause 2
Requirements All requirements in Annex B
Tests All tests in A.1.3
2.2.3 Conformant schema conformance class
Table 3 describes the conformance class for non-UML schemas.
NOTE Non-UML schemas are 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.
Table 3 — Conformant schema conformance class
Conformance class identifier ConformantSchema
Standardization target type Schemas for geographic information
Dependency UML2
Requirements Requirement 2 in 6.2.
Tests All tests in A.1.4
2.3 Data types conformance
2.3.1 Introduction
Conceptual schemas that claim conformance with this International Standard may also state that they
conform to a named subset of the concepts in the standard. These subsets may be used to document
different levels of capabilities or complexities. This International Standard describes two levels of
capabilities for the use of data types which are defined in Table 4 and 5.
2.3.2 Core types conformance class
Table 4 describes the conformance class for core data types.
Table 4 — Core types conformance class
Conformance class identifier CoreTypes
Standardization target type Core types for geographic information
Dependency UML2
ISO/IEC 11404:2007
ISO 8601:2004
Requirements All requirements in Clause 7
Tests All tests in A.2.1
2.3.3 Core and extension types conformance class
Table 5 describes the conformance class for core and extension data types.
2 © ISO 2015 – All rights reserved
Table 5 — Core and extension types conformance class
Conformance class identifier CoreExtendedTypes
Standardization target type Core and extension types for geographic information
Dependency CoreTypes
ISO 639
ISO 3166
RFC 3986
Requirements All requirements in Annex C
Tests All tests in A.2.2
2.4 Model documentation conformance
2.4.1 Introduction
The UML diagrams and textual description of model elements in a model are most often presented in
a document. The specific requirements in this International Standard for presentation of geographic
information is an extension of the requirements imposed by UML 2. A separate conformance class is
defined for this in Table 6.
2.4.2 Model documentation conformance class
Table 6 describes the conformance class for model documentation.
Table 6 — Model documentation conformance class
Conformance class identifier ModelDocumentation
Standardization target type Documentation of UML schemas for geographic
information
Dependency UML2
Requirements All requirements in 6.16
Tests All tests in A.3
3 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 639 (all parts), Codes for the representation of names and languages
ISO 3166 (all parts), Codes for the representation of names of countries and their subdivisions
ISO 8601:2004, Data elements and interchange formats — Information interchange — Representation of
dates and times
ISO/IEC 11404:2007, Information technology — General-Purpose Datatypes (GPD)
ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified Modeling
Language (UML) Version 1.4.2
ISO/IEC 19505-2:2012, Information technology — Object Management Group Unified Modeling Language
(OMG UML) — Part 2: Superstructure
NOTE Unified Modeling Language (UML), version 2.4.1, available at http://www.omg.org/spec/UML/
OCL 2.3.1, OMG Object Constraint Language (OCL), version 2.3.1, available at
org/spec/OCL/>
RFC 3986 dated January 2005 on URI Syntax, available at
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
aggregation
special form of association (4.4) that specifies a whole-part relationship (4.30) between the
aggregate (whole) and a component (4.9) part
Note 1 to entry: See composition (4.10).
[SOURCE: UML 1]
4.2
application
manipulation and processing of data in support of user requirements
[SOURCE: ISO 19101-1:2014, 4.1.1]
4.3
application schema
conceptual schema (4.12) for data required by one or more applications (4.2)
[SOURCE: ISO 19101-1:2014, 4.1.2]
4.4
association
semantic relationship (4.30) that can occur between typed instances (4.20)
Note 1 to entry: A binary association is an association among exactly two classifiers (4.8) (including the
possibility of an association from a classifier to itself).
[SOURCE: UML 2]
4.5
attribute
feature (4.17) within a classifier (4.8) that describes a range of values that instances (4.20) of the
classifier may hold
[SOURCE: UML 1]
4.6
cardinality
number of elements in a set
Note 1 to entry: Contrast with multiplicity (4.24), which is the range of possible cardinalities a set can hold.
[SOURCE: UML 1]
4.7
class
description of a set of objects (4.25) that share the same attributes (4.5), operations (4.26), methods,
relationships (4.30), and semantics
[SOURCE: UML 1]
4 © ISO 2015 – All rights reserved
4.8
classifier
mechanism that describes behavioural and structural features (4.17) in any combination
[SOURCE: UML 1]
4.9
component
representation of a modular part of a system that encapsulates its contents and whose
manifestation is replaceable within its environment
[SOURCE: UML 2]
4.10
composition
aggregation (4.1) where the composite object (4.25) (whole) has responsibility for the existence
and storage of the composed objects (parts)
[SOURCE: UML 2]
4.11
conceptual model
model (4.23) that defines concepts of a universe of discourse
[SOURCE: ISO 19101-1:2014, 4.1.5]
4.12
conceptual schema
formal description of a conceptual model (4.11)
[SOURCE: ISO 19101-1:2014, 4.1.6]
4.13
constraint
condition or restriction expressed in natural language text or in a machine readable language
for the purpose of declaring some of the semantics of an element
[SOURCE: UML 2]
4.14
data type
specification of a value domain (4.37) with operations (4.26) allowed on values in this domain
EXAMPLE Integer, Real, Boolean, String and Date.
Note 1 to entry: Data types include primitive predefined types (4.36) and user definable types.
4.15
dependency
relationship (4.30) that signifies that a single or a set of model elements requires other model
elements for their specification or implementation
Note 1 to entry: This means that the complete semantics of the depending elements is either semantically or
structurally dependent on the definition of the supplier element(s).
[SOURCE: UML 2]
4.16
feature
abstraction of real world phenomena
Note 1 to entry: A feature can occur as a class (4.7) or an instance (4.20). The full term feature type or feature
instance can be used when only one is meant.
Note 2 to entry: In UML 2 the term feature is used for a property, such as operation (4.26) or attribute (4.5), which
is encapsulated as part of a list within a classifier (4.8), such as interface (4.21), class or data type (4.14).
Note 3 to entry: See Annex D.2.
[SOURCE: ISO 19101-1:2014, 4.1.11 modified — Notes 1-3 have been added.]
4.17
feature
property of a classifier (4.8)
[SOURCE: UML 2]
4.18
generalization
taxonomic relationship (4.30) between a more general element and a more specific element of
the same element type
Note 1 to entry: An instance (4.20) of the more specific element can be used where the more general element is
allowed. See: inheritance (4.19).
[SOURCE: UML 2]
4.19
inheritance
mechanism by which more specific classifiers (4.8) incorporate structure and behaviour defined by
more general classifiers
Note 1 to entry: See generalization (4.18).
4.20
instance
individual entity having its own value and possibly its own identity
Note 1 to entry: A classifier (4.8) specifies the form and behaviour of a set of instances with similar properties.
4.21
interface
classifier (4.8) that represents a declaration of a set of coherent public features (4.17)
and obligations
Note 1 to entry: An interface specifies a contract; any classifier that realizes the interface must fulfil that
contract. The obligations that can be associated with an interface are in the form of various kinds of constraints
(4.13) (such as pre- and post-conditions) or protocol specifications, which can impose ordering restrictions on
interactions through the interface.
[SOURCE: UML 2]
4.22
metamodel
model (4.23) that defines the language for expressing other models
Note 1 to entry: A model is an instance (4.20) of a metamodel, and a metamodel is an instance of a meta-metamodel.
[SOURCE: UML 2]
4.23
model
abstraction of some aspects of reality
[SOURCE: ISO 19109:2015, 4.15]
6 © ISO 2015 – All rights reserved
4.24
multiplicity
specification of the range of allowable cardinalities (4.6) that a set may assume
4.25
object
entity with a well defined boundary and identity that encapsulates state and behaviour
[SOURCE: UML 1]
4.26
operation
behavioural feature (4.17) of a classifier (4.8) that specifies the name, type (4.36),
parameters, and constraints (4.13) for invoking an associated behaviour
[SOURCE: UML 2]
4.27
package
general purpose mechanism for organizing elements into groups
[SOURCE: UML 2]
4.28
profile
definition of a limited extension to a reference metamodel (4.22) with the purpose of adapting
the metamodel to a specific platform or domain
[SOURCE: UML 2]
4.29
realization
specialized abstraction relationship (4.30) between two sets of model elements, one representing
a specification (the supplier) and the other representing an implementation of the latter (the client)
Note 1 to entry: Realization indicates inheritance (4.19) of behaviour without inheritance of structure.
[SOURCE: UML 2]
4.30
relationship
semantic connection among model elements
[SOURCE: UML 1]
4.31
schema
formal description of a model (4.23)
[SOURCE: ISO 19101-1:2014, 4.1.34]
4.32
service
distinct part of the functionality that is provided by an entity through interfaces (4.21)
[SOURCE: ISO 19119:2005, 4.1]
4.33
stereotype
extension of an existing metaclass that enables the use of platform or domain specific
terminology or notation in place of, or in addition to, the ones used for the extended metaclass
[SOURCE: UML 2]
4.34
tagged value
attribute (4.5) on a stereotype (4.33) used to extend a model element
[SOURCE: UML 2]
4.35
template
parameterized model element
[SOURCE: UML 2]
4.36
type
stereotyped class (4.7) that specifies a domain of objects (4.25) together with the operations
(4.26) applicable to the objects, without defining the physical implementation of those objects
Note 1 to entry: A type can have attributes (4.5) and associations (4.4). See relationship to interface in Annex B.
[SOURCE: UML 1]
4.37
value domain
set of accepted values
EXAMPLE The range 3–28, all integers, any ASCII character, enumeration of values (green, blue, white).
5 Presentation and abbreviations
5.1 Presentation
The main technical content of this International Standard is found in Clauses 6 and 7. Clause 6 describes
the profile of UML for modelling geographic information. Clause 7 defines a set of classes to be used as
common elements, as standard UML does not prescribe the use of specific data types.
Annex A describes an abstract test suite for checking that the normative aspects of UML models are
made according to the rules of this International Standard. Annex B defines rules for mapping a UML
1 model to a UML 2 model making the model conformant with this International Standard. Annex C
describes additional extended data types for this profile. Annex D defines the UML profile formally. An
introduction to conceptual schema languages can be found in Annex E. A set of modelling guidelines for
information modelling and service modelling is described in Annex F. The general UML as defined in
UML 2 is briefly described in Annex G.
5.2 Backwards compatibility to previous version of ISO 19103
A list of general descriptions of main additions, removals and changes can be found in Annex H.
The verb “deprecate” provides notice that the referenced portion of this International Standard is being
retained for backwards compatibility with earlier versions but may be removed from a future version
of this International Standard without further notice.
Text describing deprecated elements is written in italics.
5.3 Abbreviations
API Application Programming Interface
CSL Conceptual schema language
8 © ISO 2015 – All rights reserved
CSMF Conceptual Schema Modelling Facility
EMOF Essential Meta Object Facility
GFM General Feature Model
IANA Internet Assigned Numbers Authority
MOF Meta Object Facility
OCL Object Constraint Language
OMG Object Management Group
ODP Open Distributed Processing
SRS Spatial Reference System
UML Unified Modeling Language
UML 1 Unified Modeling Language version 1.4.2
UML 2 Unified Modeling Language version 2.4.1
uom Unit of Measure
URI Uniform Resource Identifier
url Uniform Resource Locator
XML eXtensible Markup Language
XMI XML Metamodel Interchange
6 The ISO 19103 UML Profile – Use of UML
6.1 Introduction
This International Standard contains a UML Profile for geographic information. Clause 6 provides rules
and guidelines on the use of UML for specifying conceptual models within the domain of geographic
information. It is based on general UML as defined in UML 2. Annex G contains an introduction to UML and
follows the same structure as this clause, to make it easy to refer to the relevant standard UML concepts.
The profile is guidance for a set of limited additions to the UML standard to adapt it for geographic
information. It should be noted that profiles are a lightweight extension mechanism to UML and if the
need is a precise metamodel of allowed modelling constructs other approaches may be considered.
One such approach is EMOF (Essential MOF) which is a precise metamodel for simple class modelling
[7]
defined in the Meta Object Facility (MOF) Core Specification .
6.2 General use of UML
Requirement 1. The conceptual schema shall be modelled in conformance with UML 2.
[1] [2]
NOTE 1 Books, such as “UML User Guide” and “UML Reference Manual” contain further information. The
[4]
book “UML Distilled” is a shorter introductory text. More recent books on UML 2 are recommended.
Requirement 2. Conceptual schemas modelled in another CSL shall specify a mapping from the
CSL to UML 2. If the conceptual schema is transformed into a UML 2 schema using the mapping, the
resulting UML 2 schemas shall conform to the UML2 conformance class.
Non-UML schemas are 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.
Requirement 3. All normative class models shall contain definitions sufficient for understanding
of all classes, attributes, associations, operations and appropriate data type definitions.
It is the need for this completeness that makes it necessary to define this UML profile, as UML in general
can be used on various levels of precision and completeness. Other kinds of UML diagrams may also be
used as normative models.
Requirement 4. Each model shall have documented a clear description of its level of abstraction
and class stereotypes may be added to help express the chosen abstraction level.
The main abstraction levels are ‘Abstract Schema’ and ‘Application Schema’. See Figure 4 for an example
of types of content in these levels.
NOTE 2 UML 2 can also be used to specify schemas on the levels ‘Metamodel’ and ‘Implementation Schema’.
a) Metamodel level
b) Abstract Schema level
c) Application Schema level
d) Implementation Schema level
6.3 Classifiers
Classifiers may serve different purposes in different contexts and models can be at different levels
of abstraction. Classifiers defined according to this International Standard may represent abstract
specifications where the characteristics of the classifier do not have
...
INTERNATIONAL ISO
STANDARD 19103
First edition
2015-12-01
Geographic information — Conceptual
schema language
Information géographique — Langage de schéma conceptuel
Reference number
©
ISO 2015
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Conformance . 1
2.1 Introduction . 1
2.2 UML version conformance . 1
2.2.1 UML 2 conformance class. 1
2.2.2 UML 1 to UML2 mapping conformance class . 1
2.2.3 Conformant schema conformance class . 2
2.3 Data types conformance . 2
2.3.1 Introduction . 2
2.3.2 Core types conformance class . 2
2.3.3 Core and extension types conformance class . 2
2.4 Model documentation conformance . 3
2.4.1 Introduction . 3
2.4.2 Model documentation conformance class . 3
3 Normative references . 3
4 Terms and definitions . 4
5 Presentation and abbreviations . 8
5.1 Presentation . 8
5.2 Backwards compatibility to previous version of ISO 19103 . 8
5.3 Abbreviations . 8
6 The ISO 19103 UML Profile – Use of UML . 9
6.1 Introduction . 9
6.2 General use of UML . 9
6.3 Classifiers .10
6.4 Attributes .10
6.5 Enumerations and codelists .11
6.5.1 General rules .11
6.5.2 Enumerations .11
6.5.3 Code lists .12
6.6 Data types .13
6.7 Operations .13
6.8 Relationships .13
6.8.1 General.13
6.8.2 Associations .13
6.8.3 Generalizations.14
6.8.4 Realizations .14
6.9 Services .15
6.10 Stereotypes and keywords .16
6.10.1 Introduction .16
6.10.2 Stereotypes and keywords .16
6.11 Optional, conditional and mandatory attributes and association ends .16
6.11.1 Mandatory .16
6.11.2 Optional .17
6.11.3 Conditional .17
6.12 Naming and namespaces .17
6.13 Packages .18
6.14 Notes .18
6.15 Constraints .19
6.16 Documentation of models .19
7 Core data types .20
7.1 Introduction .20
7.2 Primitive types .20
7.2.1 General.20
7.2.2 Date .21
7.2.3 Time .21
7.2.4 DateTime .22
7.2.5 Number .22
7.2.6 Decimal . .24
7.2.7 Integer .24
7.2.8 Real .24
7.2.9 Vector .25
7.2.10 CharacterString .25
7.2.11 Boolean .27
7.3 Collections .27
7.3.1 General.27
7.3.2 Collection templates .28
7.3.3 Set .28
7.3.4 Bag .28
7.3.5 Sequence .29
7.4 Enumerated types .29
7.4.1 General.29
7.4.2 Bit .30
7.4.3 Digit .30
7.4.4 Sign .30
7.5 Name types .30
7.5.1 General.30
7.5.2 NameSpace .31
7.5.3 GenericName .33
7.5.4 ScopedName .33
7.5.5 LocalName .34
7.5.6 TypeName .35
7.5.7 MemberName .35
7.6 Any type .36
7.7 Record types .36
7.7.1 General.36
7.7.2 Record .36
7.7.3 RecordType .37
7.7.4 Field.37
7.7.5 FieldType .37
7.8 NULL and EMPTY values .37
Annex A (normative) Abstract test suite .38
Annex B (normative) Rules for mapping UML 1 models to UML 2 models .40
Annex C (normative) Data types – extension types .41
Annex D (normative) Formal UML profile .48
Annex E (informative) On conceptual schema languages .50
Annex F (informative) Modelling guidelines .58
Annex G (informative) Introduction to UML .67
Annex H (informative) Backwards compatibility .79
Bibliography .81
iv © ISO 2015 – All rights reserved
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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2. www.iso.org/directives
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. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received. www.iso.org/patents
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 211, Geographic information/Geomatics.
This first edition of ISO 19103:2015 cancels and replaces the first edition (ISO/TS 19103:2005).
Introduction
This International Standard of the ISO geographic information suite of 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 suite
of 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 International Standard. First, a CSL is selected that meets the requirements
for rigorous representation of geographic information. This International Standard 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 International Standard provides guidelines
on how UML should be used to create geographic information models that are a basis for achieving the
goal of interoperability.
One goal of the ISO geographic information suite of standards using UML models is that they will
provide a basis for model based mapping to encoding schemas like the ones defined in ISO 19118, as
well as a basis for creating implementation specifications for implementation profiles for various other
environments.
This International Standard describes the general metamodel for use of UML in the context of the
ISO geographic information series of standards. Aspects specifically dealing with the modelling of
application schemas are described in ISO 19109.
This International Standard is a revision of a previous version from 2005. Changes are documented in
Clause 5.
vi © ISO 2015 – All rights reserved
INTERNATIONAL STANDARD ISO 19103:2015(E)
Geographic information — Conceptual schema language
1 Scope
This International Standard provides rules and guidelines for the use of a conceptual schema language
within the context of geographic information. The chosen conceptual schema language is the Unified
Modeling Language (UML).
This International Standard provides a profile of the Unified Modelling Language (UML).
The standardization target type of this standard is UML schemas describing geographic information.
2 Conformance
2.1 Introduction
This International Standard defines three levels of conformance classes:
— UML version
— Data types
— Model documentation
To conform to this International Standard, the usage of a conceptual schema language shall satisfy
all of the requirements specified in one of the three levels of conformance described below, with the
corresponding abstract test suite in Annex A.
2.2 UML version conformance
2.2.1 UML 2 conformance class
Table 1 describes the conformance class for UML 2.
Table 1 — UML 2 conformance class
Conformance class identifier UML2
Standardization target type UML2 schemas for geographic information
Dependency ISO/IEC 19505-2:2012, Clause 2
OCL 2.3.1
Requirements All requirements in 6.2 to 6.12 except Requirement
2, and including Requirement 26.
Tests All tests in A.1.2
2.2.2 UML 1 to UML2 mapping conformance class
Table 2 describes the conformance class for mapping from UML 1.
Table 2 — UML 1 to UML 2 mapping conformance class
Conformance class identifier UML1
Standardization target type UML1 schemas for geographic information
Dependency UML2
ConformantSchema
ISO/IEC 19501:2005, Clause 2
Requirements All requirements in Annex B
Tests All tests in A.1.3
2.2.3 Conformant schema conformance class
Table 3 describes the conformance class for non-UML schemas.
NOTE Non-UML schemas are 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.
Table 3 — Conformant schema conformance class
Conformance class identifier ConformantSchema
Standardization target type Schemas for geographic information
Dependency UML2
Requirements Requirement 2 in 6.2.
Tests All tests in A.1.4
2.3 Data types conformance
2.3.1 Introduction
Conceptual schemas that claim conformance with this International Standard may also state that they
conform to a named subset of the concepts in the standard. These subsets may be used to document
different levels of capabilities or complexities. This International Standard describes two levels of
capabilities for the use of data types which are defined in Table 4 and 5.
2.3.2 Core types conformance class
Table 4 describes the conformance class for core data types.
Table 4 — Core types conformance class
Conformance class identifier CoreTypes
Standardization target type Core types for geographic information
Dependency UML2
ISO/IEC 11404:2007
ISO 8601:2004
Requirements All requirements in Clause 7
Tests All tests in A.2.1
2.3.3 Core and extension types conformance class
Table 5 describes the conformance class for core and extension data types.
2 © ISO 2015 – All rights reserved
Table 5 — Core and extension types conformance class
Conformance class identifier CoreExtendedTypes
Standardization target type Core and extension types for geographic information
Dependency CoreTypes
ISO 639
ISO 3166
RFC 3986
Requirements All requirements in Annex C
Tests All tests in A.2.2
2.4 Model documentation conformance
2.4.1 Introduction
The UML diagrams and textual description of model elements in a model are most often presented in
a document. The specific requirements in this International Standard for presentation of geographic
information is an extension of the requirements imposed by UML 2. A separate conformance class is
defined for this in Table 6.
2.4.2 Model documentation conformance class
Table 6 describes the conformance class for model documentation.
Table 6 — Model documentation conformance class
Conformance class identifier ModelDocumentation
Standardization target type Documentation of UML schemas for geographic
information
Dependency UML2
Requirements All requirements in 6.16
Tests All tests in A.3
3 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 639 (all parts), Codes for the representation of names and languages
ISO 3166 (all parts), Codes for the representation of names of countries and their subdivisions
ISO 8601:2004, Data elements and interchange formats — Information interchange — Representation of
dates and times
ISO/IEC 11404:2007, Information technology — General-Purpose Datatypes (GPD)
ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified Modeling
Language (UML) Version 1.4.2
ISO/IEC 19505-2:2012, Information technology — Object Management Group Unified Modeling Language
(OMG UML) — Part 2: Superstructure
NOTE Unified Modeling Language (UML), version 2.4.1, available at http://www.omg.org/spec/UML/
OCL 2.3.1, OMG Object Constraint Language (OCL), version 2.3.1, available at
org/spec/OCL/>
RFC 3986 dated January 2005 on URI Syntax, available at
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
aggregation
special form of association (4.4) that specifies a whole-part relationship (4.30) between the
aggregate (whole) and a component (4.9) part
Note 1 to entry: See composition (4.10).
[SOURCE: UML 1]
4.2
application
manipulation and processing of data in support of user requirements
[SOURCE: ISO 19101-1:2014, 4.1.1]
4.3
application schema
conceptual schema (4.12) for data required by one or more applications (4.2)
[SOURCE: ISO 19101-1:2014, 4.1.2]
4.4
association
semantic relationship (4.30) that can occur between typed instances (4.20)
Note 1 to entry: A binary association is an association among exactly two classifiers (4.8) (including the
possibility of an association from a classifier to itself).
[SOURCE: UML 2]
4.5
attribute
feature (4.17) within a classifier (4.8) that describes a range of values that instances (4.20) of the
classifier may hold
[SOURCE: UML 1]
4.6
cardinality
number of elements in a set
Note 1 to entry: Contrast with multiplicity (4.24), which is the range of possible cardinalities a set can hold.
[SOURCE: UML 1]
4.7
class
description of a set of objects (4.25) that share the same attributes (4.5), operations (4.26), methods,
relationships (4.30), and semantics
[SOURCE: UML 1]
4 © ISO 2015 – All rights reserved
4.8
classifier
mechanism that describes behavioural and structural features (4.17) in any combination
[SOURCE: UML 1]
4.9
component
representation of a modular part of a system that encapsulates its contents and whose
manifestation is replaceable within its environment
[SOURCE: UML 2]
4.10
composition
aggregation (4.1) where the composite object (4.25) (whole) has responsibility for the existence
and storage of the composed objects (parts)
[SOURCE: UML 2]
4.11
conceptual model
model (4.23) that defines concepts of a universe of discourse
[SOURCE: ISO 19101-1:2014, 4.1.5]
4.12
conceptual schema
formal description of a conceptual model (4.11)
[SOURCE: ISO 19101-1:2014, 4.1.6]
4.13
constraint
condition or restriction expressed in natural language text or in a machine readable language
for the purpose of declaring some of the semantics of an element
[SOURCE: UML 2]
4.14
data type
specification of a value domain (4.37) with operations (4.26) allowed on values in this domain
EXAMPLE Integer, Real, Boolean, String and Date.
Note 1 to entry: Data types include primitive predefined types (4.36) and user definable types.
4.15
dependency
relationship (4.30) that signifies that a single or a set of model elements requires other model
elements for their specification or implementation
Note 1 to entry: This means that the complete semantics of the depending elements is either semantically or
structurally dependent on the definition of the supplier element(s).
[SOURCE: UML 2]
4.16
feature
abstraction of real world phenomena
Note 1 to entry: A feature can occur as a class (4.7) or an instance (4.20). The full term feature type or feature
instance can be used when only one is meant.
Note 2 to entry: In UML 2 the term feature is used for a property, such as operation (4.26) or attribute (4.5), which
is encapsulated as part of a list within a classifier (4.8), such as interface (4.21), class or data type (4.14).
Note 3 to entry: See Annex D.2.
[SOURCE: ISO 19101-1:2014, 4.1.11 modified — Notes 1-3 have been added.]
4.17
feature
property of a classifier (4.8)
[SOURCE: UML 2]
4.18
generalization
taxonomic relationship (4.30) between a more general element and a more specific element of
the same element type
Note 1 to entry: An instance (4.20) of the more specific element can be used where the more general element is
allowed. See: inheritance (4.19).
[SOURCE: UML 2]
4.19
inheritance
mechanism by which more specific classifiers (4.8) incorporate structure and behaviour defined by
more general classifiers
Note 1 to entry: See generalization (4.18).
4.20
instance
individual entity having its own value and possibly its own identity
Note 1 to entry: A classifier (4.8) specifies the form and behaviour of a set of instances with similar properties.
4.21
interface
classifier (4.8) that represents a declaration of a set of coherent public features (4.17)
and obligations
Note 1 to entry: An interface specifies a contract; any classifier that realizes the interface must fulfil that
contract. The obligations that can be associated with an interface are in the form of various kinds of constraints
(4.13) (such as pre- and post-conditions) or protocol specifications, which can impose ordering restrictions on
interactions through the interface.
[SOURCE: UML 2]
4.22
metamodel
model (4.23) that defines the language for expressing other models
Note 1 to entry: A model is an instance (4.20) of a metamodel, and a metamodel is an instance of a meta-metamodel.
[SOURCE: UML 2]
4.23
model
abstraction of some aspects of reality
[SOURCE: ISO 19109:2015, 4.15]
6 © ISO 2015 – All rights reserved
4.24
multiplicity
specification of the range of allowable cardinalities (4.6) that a set may assume
4.25
object
entity with a well defined boundary and identity that encapsulates state and behaviour
[SOURCE: UML 1]
4.26
operation
behavioural feature (4.17) of a classifier (4.8) that specifies the name, type (4.36),
parameters, and constraints (4.13) for invoking an associated behaviour
[SOURCE: UML 2]
4.27
package
general purpose mechanism for organizing elements into groups
[SOURCE: UML 2]
4.28
profile
definition of a limited extension to a reference metamodel (4.22) with the purpose of adapting
the metamodel to a specific platform or domain
[SOURCE: UML 2]
4.29
realization
specialized abstraction relationship (4.30) between two sets of model elements, one representing
a specification (the supplier) and the other representing an implementation of the latter (the client)
Note 1 to entry: Realization indicates inheritance (4.19) of behaviour without inheritance of structure.
[SOURCE: UML 2]
4.30
relationship
semantic connection among model elements
[SOURCE: UML 1]
4.31
schema
formal description of a model (4.23)
[SOURCE: ISO 19101-1:2014, 4.1.34]
4.32
service
distinct part of the functionality that is provided by an entity through interfaces (4.21)
[SOURCE: ISO 19119:2005, 4.1]
4.33
stereotype
extension of an existing metaclass that enables the use of platform or domain specific
terminology or notation in place of, or in addition to, the ones used for the extended metaclass
[SOURCE: UML 2]
4.34
tagged value
attribute (4.5) on a stereotype (4.33) used to extend a model element
[SOURCE: UML 2]
4.35
template
parameterized model element
[SOURCE: UML 2]
4.36
type
stereotyped class (4.7) that specifies a domain of objects (4.25) together with the operations
(4.26) applicable to the objects, without defining the physical implementation of those objects
Note 1 to entry: A type can have attributes (4.5) and associations (4.4). See relationship to interface in Annex B.
[SOURCE: UML 1]
4.37
value domain
set of accepted values
EXAMPLE The range 3–28, all integers, any ASCII character, enumeration of values (green, blue, white).
5 Presentation and abbreviations
5.1 Presentation
The main technical content of this International Standard is found in Clauses 6 and 7. Clause 6 describes
the profile of UML for modelling geographic information. Clause 7 defines a set of classes to be used as
common elements, as standard UML does not prescribe the use of specific data types.
Annex A describes an abstract test suite for checking that the normative aspects of UML models are
made according to the rules of this International Standard. Annex B defines rules for mapping a UML
1 model to a UML 2 model making the model conformant with this International Standard. Annex C
describes additional extended data types for this profile. Annex D defines the UML profile formally. An
introduction to conceptual schema languages can be found in Annex E. A set of modelling guidelines for
information modelling and service modelling is described in Annex F. The general UML as defined in
UML 2 is briefly described in Annex G.
5.2 Backwards compatibility to previous version of ISO 19103
A list of general descriptions of main additions, removals and changes can be found in Annex H.
The verb “deprecate” provides notice that the referenced portion of this International Standard is being
retained for backwards compatibility with earlier versions but may be removed from a future version
of this International Standard without further notice.
Text describing deprecated elements is written in italics.
5.3 Abbreviations
API Application Programming Interface
CSL Conceptual schema language
8 © ISO 2015 – All rights reserved
CSMF Conceptual Schema Modelling Facility
EMOF Essential Meta Object Facility
GFM General Feature Model
IANA Internet Assigned Numbers Authority
MOF Meta Object Facility
OCL Object Constraint Language
OMG Object Management Group
ODP Open Distributed Processing
SRS Spatial Reference System
UML Unified Modeling Language
UML 1 Unified Modeling Language version 1.4.2
UML 2 Unified Modeling Language version 2.4.1
uom Unit of Measure
URI Uniform Resource Identifier
url Uniform Resource Locator
XML eXtensible Markup Language
XMI XML Metamodel Interchange
6 The ISO 19103 UML Profile – Use of UML
6.1 Introduction
This International Standard contains a UML Profile for geographic information. Clause 6 provides rules
and guidelines on the use of UML for specifying conceptual models within the domain of geographic
information. It is based on general UML as defined in UML 2. Annex G contains an introduction to UML and
follows the same structure as this clause, to make it easy to refer to the relevant standard UML concepts.
The profile is guidance for a set of limited additions to the UML standard to adapt it for geographic
information. It should be noted that profiles are a lightweight extension mechanism to UML and if the
need is a precise metamodel of allowed modelling constructs other approaches may be considered.
One such approach is EMOF (Essential MOF) which is a precise metamodel for simple class modelling
[7]
defined in the Meta Object Facility (MOF) Core Specification .
6.2 General use of UML
Requirement 1. The conceptual schema shall be modelled in conformance with UML 2.
[1] [2]
NOTE 1 Books, such as “UML User Guide” and “UML Reference Manual” contain further information. The
[4]
book “UML Distilled” is a shorter introductory text. More recent books on UML 2 are recommended.
Requirement 2. Conceptual schemas modelled in another CSL shall specify a mapping from the
CSL to UML 2. If the conceptual schema is transformed into a UML 2 schema using the mapping, the
resulting UML 2 schemas shall conform to the UML2 conformance class.
Non-UML schemas are 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.
Requirement 3. All normative class models shall contain definitions sufficient for understanding
of all classes, attributes, associations, operations and appropriate data type definitions.
It is the need for this completeness that makes it necessary to define this UML profile, as UML in general
can be used on various levels of precision and completeness. Other kinds of UML diagrams may also be
used as normative models.
Requirement 4. Each model shall have documented a clear description of its level of abstraction
and class stereotypes may be added to help express the chosen abstraction level.
The main abstraction levels are ‘Abstract Schema’ and ‘Application Schema’. See Figure 4 for an example
of types of content in these levels.
NOTE 2 UML 2 can also be used to specify schemas on the levels ‘Metamodel’ and ‘Implementation Schema’.
a) Metamodel level
b) Abstract Schema level
c) Application Schema level
d) Implementation Schema level
6.3 Classifiers
Classifiers may serve different purposes in different contexts and models can be at different levels
of abstraction. Classifiers defined according to this International Standard may represent abstract
specifications where the characteristics of the classifier do not have to be directly implemented or can
also represent concrete implementation models. Stereotypes provide a means to define different types
of classifiers, which can also define the intended abstraction level of a model.
Stereotypes defined for this UML profile are described in 6.10.2. Specification (abstract) models
may be realized in different ways and how this is done should be expressed in each case. See 6.8.4
on realization relationships for a common description of how to realize and use abstract models in
implementation models.
The notion of abstract models and classifiers defined in models is that they are abstract, in the sense
that the characteristics of the classifier do not have to be directly implementable. An abstract UML
model must not be confused with a UML classifier marked as abstract. Marking a UML classifier
abstract means that the classifier cannot be instantiated; only specializations of the classifier can occur
as instances. Such abstract classifiers may be defined in models at different levels of abstraction.
Classifiers with keyword <> (lacking identity) are usually defined in application or
implementation sc
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...