ANSI INCITS ISO TS 19103-2010 Geographic information - Conceptual schema language.pdf

1、 INCITS/ISO TS 19103-2010 Geographic information - Conceptual schema language (identical national adoption of ISO/TS 19103:2005) INCITS/ISO TS 19103-2010 PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but sh

2、all 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 Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area

3、. 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

4、 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. Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard. Date of ANSI Approval: 9/28/2010 Publ

5、ished by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2010 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copyright claims of International Standardization Organization (ISO), International Elect

6、rotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission of ITI. All request

7、s pertaining to this standard should be submitted to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America ii ITIC 2010 All rights reserved INCITS/ISO TS 19103-2010 ITIC 2010 All rights reserved iiiContents Page Foreword iv Introduction.v 1 1 Scope2 .1 Conformance3 1

8、 Normative references4 1 Terms, definitions and abbreviations4.1 .1 ISO/TS 19103 terms4.2 3 UML terms4.3 .7 Abbreviations5 .7 Organization6 .8 The ISO/TS 19103 UML Profile6.1 8 Introduction6.2 .8 General usage of UML6.3 .9 Classes6.4 9 Attributes6.5 9 Data types6.6 28 Operations6.7 .28 Relationships

9、 and associations6.8 .29 Stereotypes and tagged values6.9 29 Optional, conditional and mandatory attributes and associations6.10 30 Naming and name spaces6.11 31 Packages6.12 .32 Notes6.13 .32 Constraints6.14 32 Documentation of modelsAnnex A (normative) Abstract test suite.34 Annex B (informative)

10、On conceptual schema languages35 Annex C (informative) Modeling guidelines .45 Annex D (informative) Introduction to UML54 Bibliography67 INCITS/ISO TS 19103-2010 iv ITIC 2010 All rights reservedForeword ISO (the International Organization for Standardization) is a worldwide federation of national s

11、tandards 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

12、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 gi

13、ven 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

14、 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) re presents an agreement bet

15、ween 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) repres ents an agreement between the members of a technical committee and is accepted for

16、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 co

17、nfirmed, 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 responsib

18、le for identifying any or all such patent rights. IISO/TS 19103 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics. INCITS/ISO TS 19103-2010 ITIC 2010 All rights reserved vIntroduction This Technical Specification of the ISO geographic information standards is concerned

19、 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 interchan

20、ge 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 spec

21、ify 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 combinat

22、ion 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 ho

23、w 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 we

24、ll as a basis for creating implementation specifications for implementation profiles for various environments. TECHNICAL SPECIFICATION INCITS/ISO TS 19103-2010 ITIC 2010 All rights reserved 1Geographic information Conceptual schema language 1 Scope This Technical Specification provides rules and gui

25、delines 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 informatio

26、n. 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 sh

27、all 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

28、 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 mod

29、el 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 proce

30、ssing 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 INCITS/ISO TS 19103-2010 2 ITIC 2010 All rights reserved4.1.3 conceptual model model that defines concepts of a universe of discourse ISO 19101 4

31、.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 pr

32、imitive 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. Featu

33、re type or feature instance should be used when only one is meant. NOTE 2 In UML 8a 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 o

34、f 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

35、.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

36、an instance. Feature attribute type or feature attribute instance should be used when only one is meant. INCITS/ISO TS 19103-2010 ITIC 2010 All rights reserved 34.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 ra

37、ise the dam. The result of this operation is to raise the level of water in a reservoir. EXAMPLE 2 An operation by a “dam” might be to block vessels from navigating along a “watercourse”. NOTE Feature operations provide a basis for feature type definition. 4.1.11 metadata data about data ISO 19115 4

38、.1.12 metadata element discrete unit of metadata ISO 19115 NOTE 1 Metadata elements are unique within a metadata entity. NOTE 2 Equivalent to an attribute in UML terminology. 4.1.13 schema formal description of a model ISO 19101 4.1.14 service distinct part of the functionality that is provided by a

39、n entity through interfaces ISO/IEC TR 14252 4.1.15 value domain set of accepted values EXAMPLE The range 3-28, all integers, any ASCII character, enumeration of all accepted values (green, blue, white). 4.2 UML terms The following are UML terms that are adapted from ISO/IEC 19501. 4.2.1 actor coher

40、ent set of roles that users of use cases play when interacting with these use cases NOTE An actor may be considered to play a separate role with regard to each use case with which it communicates. INCITS/ISO TS 19103-2010 4 ITIC 2010 All rights reserved4.2.2 aggregation special form of association t

41、hat specifies a whole-part relationship between the aggregate (whole) and a component part NOTE See composition. 4.2.3 association semantic relationship between two or more classifiers that specifies connections among their instances NOTE A binary association is an association among exactly two clas

42、sifiers (including the possibility of an association from a classifier to itself). 4.2.4 attribute feature within a classifier that describes a range of values that instances of the classifier may hold NOTE 1 An attribute is semantically equivalent to a composition association; however, the intent a

43、nd usage is normally different. NOTE 2 “Feature” used in this definition is the UML meaning of the term and is not meant as defined in 4.1 of this Technical Specification. 4.2.5 behaviour observable effects of an operation or event, including its results 4.2.6 cardinality number of elements in a set

44、 NOTE Contrast: multiplicity. 4.2.7 class description of a set of objects that share the same attributes, operations, methods, relationships and semantics NOTE A class may use a set of interfaces to specify collections of operations it provides to its environment. See: interface. 4.2.8 classifier me

45、chanism that describes behavioural and structural features NOTE Classifiers include interfaces, classes, datatypes, and components. 4.2.9 component modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces NOTE A component represents a phy

46、sical piece of implementation of a system, including software code (source, binary or executable) or equivalents such as scripts or command files. 4.2.10 composition form of aggregation which requires that a part instance be included in at most one composite at a time, and that the composite object

47、is responsible for the creation and destruction of the parts INCITS/ISO TS 19103-2010 ITIC 2010 All rights reserved 5NOTE Parts with non-fixed multiplicity may be created after the composite itself, but once created they live and die with it (i.e. they share lifetimes). Such parts can also be explic

48、itly removed before the death of the composite. Composition may be recursive. Synonym: composite aggregation. 4.2.11 constraint semantic condition or restriction NOTE Certain constraints are predefined in the UML, others may be user defined. Constraints are one of three extensibility mechanisms in U

49、ML. See: tagged value, stereotype. 4.2.12 dependency relationship between two modeling elements, in which a change to one modeling element (the independent element) will affect the other modeling element (the dependent element) 4.2.13 generalization taxonomic relationship between a more general element and a more specific element that is fully consistent with the more general element and contains additional informatio