ISO/FDIS INTERNATIONAL STANDARD FINAL DRAFT. Geographic information Metadata ISO/TC 211. Secretariat: NSF. Voting begins on:

Transcription

1 FINAL DRAFT INTERNATIONAL STANDARD ISO/FDIS ISO/TC 211 Secretariat: NSF Voting begins on: Geographic information Metadata Information géographique Métadonnées Voting terminates on: Please see the administrative notes on page ii-1 RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT, WITH THEIR COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE AND TO PROVIDE SUPPORT- ING DOCUMENTATION. IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO- LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME STAN- DARDS TO WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS. Reference number ISO/FDIS 19115:2003(E) ISO 2003

2 ISO/FDIS 19115:2003(E) 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. Copyright notice This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording or otherwise, without prior written permission being secured. Requests for permission to reproduce should be addressed to 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 Fax copyright@iso.org Web Reproduction may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. ii ISO 2003 All rights reserved

3 ISO/FDIS 19115:2003(E) In accordance with the provisions of Council Resolution 15/1993, this document is circulated in the English language only. ISO 2003 All rights reserved ii-1

4 ISO/FDIS 19115:2003(E) ii-2 ISO 2003 All rights reserved

5 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Contents Page Foreword... vii Introduction... viii 1 Scope Conformance Conformance requirements Metadata Profiles Obligation and condition Normative references Terms and definitions Symbols and abbreviated terms Abbreviations UML notations UML model relationships Associations Generalization Instantiation/Dependency Roles UML model stereotypes Package abbreviations UML model/data dictionary relationships Requirements Metadata for geographic data requirement Metadata application information Metadata packages Metadata package and entity relationship Package descriptions Metadata datatypes Extent information (EX_Extent) Citation and responsible party information (CI_Citation and CI_ResponsibleParty) Core metadata for geographic datasets Unified Modelling Language (UML) diagrams Data dictionary Metadata extensions and profiles Abstract test suite Comprehensive dataset metadata application profile Metadata extension methodology Metadata implementation Hierarchical levels of metadata Implementation examples Multilingual support for free text fields...17 Annex A (normative) Metadata schemas...18 A.1 Metadata UML models...18 A.2 Metadata package UML diagrams...19 A.2.1 Metadata entity set information...19 A.2.2 Identification information...19 A.2.3 Constraint information...21 A.2.4 Data quality information...22 A.2.5 Maintenance information...25 A.2.6 Spatial representation information...26 ISO 2003 All rights reserved iii

6 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A.2.7 Reference system information A.2.8 Content information A.2.9 Portrayal catalogue information A.2.10 Distribution information A.2.11 Metadata extension information A.2.12 Application schema information A.3 Metadata data types A.3.1 Extent information A.3.2 Citation and responsible party information Annex B (normative) Data dictionary for geographic metadata B.1 Data dictionary overview B.1.1 Introduction B.1.2 Name/role name B.1.3 Short name and domain code B.1.4 Definition B.1.5 Obligation/Condition B.1.6 Maximum B.1.7 Data type B.1.8 Domain B.2 Metadata package data dictionaries B.2.1 Metadata entity set information B.2.2 Identification information (includes data and service identification) B.2.3 Constraint information (includes legal and security) B.2.4 Data quality information B.2.5 Maintenance information B.2.6 Spatial representation information (includes grid and vector representation) B.2.7 Reference system information (includes temporal, coordinate and geographic identifiers) B.2.8 Content information (includes Feature catalogue and Coverage descriptions) B.2.9 Portrayal catalogue information B.2.10 Distribution information B.2.11 Metadata extension information B.2.12 Application schema information B.3 Data type information B.3.1 Extent information B.3.2 Citation and responsible party information B.4 Externally referenced entities B.4.1 Introduction B.4.2 Date and DateTime information B.4.3 Distance, angle, measure, number, record, recordtype, scale and UomLength information B.4.4 Feature type, property type, and attribute type information B.4.5 PeriodDuration and temporal primitive information B.4.6 Point and Object information B.4.7 Set and Sequence information B.4.8 Type name information B.4.9 Vertical datum information B.5 CodeLists and enumerations B.5.1 Introduction B.5.2 CI_DateTypeCode <<CodeList>> B.5.3 CI_OnLineFunctionCode <<CodeList>> B.5.4 CI_PresentationFormCode <<CodeList>> B.5.5 CI_RoleCode <<CodeList>> B.5.6 DQ_EvaluationMethodTypeCode <<CodeList>> B.5.7 DS_AssociationTypeCode <<CodeList>> B.5.8 DS_InitiativeTypeCode <<CodeList>> B.5.9 MD_CellGeometryCode <<CodeList>> B.5.10 MD_CharacterSetCode <<CodeList>> B.5.11 MD_ClassificationCode <<CodeList>> B.5.12 MD_CoverageContentTypeCode <<CodeList>> B.5.13 MD_DatatypeCode <<CodeList>> iv ISO 2003 All rights reserved

7 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.5.14 MD_DimensionNameTypeCode <<CodeList>>...97 B.5.15 MD_GeometricObjectTypeCode <<CodeList>>...97 B.5.16 MD_ImagingConditionCode <<CodeList>>...98 B.5.17 MD_KeywordTypeCode <<CodeList>>...98 B.5.18 MD_MaintenanceFrequencyCode <<CodeList>>...99 B.5.19 MD_MediumFormatCode <<CodeList>>...99 B.5.20 MD_MediumNameCode <<CodeList>>...99 B.5.21 MD_ObligationCode <<Enumeration>> B.5.22 MD_PixelOrientationCode <<Enumeration>> B.5.23 MD_ProgressCode <<CodeList>> B.5.24 MD_RestrictionCode <<CodeList>> B.5.25 MD_ScopeCode <<CodeList>> B.5.26 MD_SpatialRepresentationTypeCode <<CodeList>> B.5.27 MD_TopicCategoryCode << Enumeration>> B.5.28 MD_TopologyLevelCode <<CodeList>> Annex C (normative) Metadata extensions and profiles C.1 Background C.2 Types of extensions C.3 Creating an extension C.4 Rules for creating an extension C.5 Community profile C.6 Rules for creating a profile Annex D (normative) Abstract test suite D.1 Abstract test suite D.2 Metadata test suite D.2.1 Test case identifier: Completeness test D.2.2 Test case identifier: Maximum test D.2.3 Test case identifier: Short name test D.2.4 Test case identifier: Data type test D.2.5 Test case identifier: Domain test D.2.6 Test case identifier: Schema test D.3 r-defined extension metadata test suite D.3.1 Test case identifier: Exclusiveness test D.3.2 Test case identifier: Definition test D.3.3 Test case identifier: Standard metadata test D.4 Metadata profiles D.4.1 Test case identifier: Metadata profiles Annex E (normative) Comprehensive dataset metadata application profile E.1 Comprehensive dataset metadata application schema E.2 Comprehensive dataset metadata profile UML model Annex F (informative) Metadata extension methodology F.1 Metadata extensions methodology F.2 Review of existing metadata elements (Stage 1) F.3 Definition of a new metadata section (Stage 2) F.4 Definition of a new metadata codelist (Stage 3) F.5 Definition of a new metadata codelist element (Stage 4) F.6 Definition of a new metadata element (Stage 5) F.7 Definition of a new metadata entity (Stage 6) F.8 Definition of a more stringent metadata obligation (Stage 7) F.9 Definition of more restrictive metadata codelist (Stage 8) F.10 Documentation of metadata extensions (Stage 9) Annex G (informative) Metadata implementation G.1 Background G.1.1 Problem statement G.1.2 Scope and ives G.1.3 Granularity of spatial data supported G.2 Metadata hierarchy levels ISO 2003 All rights reserved v

8 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL G.2.1 Dataset series metadata (optional) G.2.2 Dataset metadata G.2.3 Feature type metadata (optional) G.2.4 Feature instance metadata (optional) G.2.5 Attribute type metadata (optional) G.2.6 Attribute instance metadata (optional) Annex H (informative) Hierarchical levels of metadata H.1 Levels of metadata H.2 Example Annex I (informative) Implementation examples I.1 Metadata examples I.2 Example 1 Exploration Licences for Minerals I.3 Example 2 Example of extended metadata I.4 Data dictionary for the extended elements I.5 MD_KeywordType (Modified) Annex J (informative) Multilingual support for free text metadata element J.1 Free text metadata elements J.2 Data structure for handling multi-languages support in free text metadata elements J.3 Example of multi-languages free text in a metadata element Bibliography vi ISO 2003 All rights reserved

9 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) 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. 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. ISO was prepared by Technical Committee ISO/TC 211, Geographic information/geomatics. ISO 2003 All rights reserved vii

10 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Introduction A revival in the awareness of the importance of geography and how things relate spatially, combined with the advancement of electronic technology, have caused an expansion in the use of digital geographic information and geographic information systems worldwide. Increasingly, individuals from a wide range of disciplines outside of the geographic sciences and information technologies are capable of producing, enhancing, and modifying digital geographic information. As the number, complexity, and diversity of geographic datasets grow, a method for providing an understanding of all aspects of this data grows in importance. Digital geographic data is an attempt to model and describe the real world for use in computer analysis and graphic display of information. Any description of reality is always an abstraction, always partial, and always just one of many possible "views". This "view" or model of the real world is not an exact duplication; some things are approximated, others are simplified, and some things are ignored. There is seldom perfect, complete, and correct data. To ensure that data is not misused, the assumptions and limitations affecting the creation of data must be fully documented. Metadata allows a producer to describe a dataset fully so that users can understand the assumptions and limitations and evaluate the dataset's applicability for their intended use. Typically, geographic data is used by many people other than the producer. It is often produced by one individual or organization and used by another. Proper documentation will provide those unfamiliar with the data with a better understanding, and enable them to use it properly. As geographic data producers and users handle more and more data, proper documentation will provide them with a keener knowledge of their holdings and will allow them to better manage data production, storage, updating, and reuse. The ive of this International Standard is to provide a structure for describing digital geographic data. This International Standard is intended to be used by information system analysts, program planners, and developers of geographic information systems, as well as others in order to understand the basic principles and the overall requirements for standardization of geographic information. This International Standard defines metadata elements, provides a schema and establishes a common set of metadata terminology, definitions, and extension procedures. When implemented by a data producer, this International Standard will: 1) Provide data producers with appropriate information to characterize their geographic data properly. 2) Facilitate the organization and management of metadata for geographic data. 3) Enable users to apply geographic data in the most efficient way by knowing its basic characteristics. 4) Facilitate data discovery, retrieval and reuse. rs will be better able to locate, access, evaluate, purchase and utilize geographic data. 5) Enable users to determine whether geographic data in a holding will be of use to them. This International Standard defines general-purpose metadata, in the field of geographic information. More detailed metadata for geographic datatypes and geographic services are defined in other ISO series standards and user extensions. viii ISO 2003 All rights reserved

11 FINAL DRAFT / PROJET FINAL INTERNATIONAL STANDARD ISO 19115:2003(E) Geographic information Metadata 1 Scope This International Standard defines the schema required for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data. This International Standard is applicable to: the cataloguing of datasets, clearinghouse activities, and the full description of datasets; geographic datasets, dataset series, and individual geographic features and feature properties. This International Standard defines: mandatory and conditional metadata sections, metadata entities, and metadata elements; the minimum set of metadata required to serve the full range of metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data); optional metadata elements to allow for a more extensive standard description of geographic data, if required; a method for extending metadata to fit specialized needs. Though this International Standard is applicable to digital data, its principles can be extended to many other forms of geographic data such as maps, charts, and textual documents as well as non-geographic data. NOTE Certain mandatory metadata elements may not apply to these other forms of data. 2 Conformance 2.1 Conformance requirements Metadata shall be provided as specified in Clause 6 and Annexes A and B. r-defined metadata shall be defined and provided as specified in Annex C. Any metadata claiming conformance with this International Standard shall pass the requirements described in the abstract test suite presented in Annex D. 2.2 Metadata Profiles Any profile conforming to this International Standard shall conform to the rules in Annex C, Clause C.6. ISO 2003 All rights reserved 1

12 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL 2.3 Obligation and condition For the purposes of conformance testing using the abstract test suite in Annex D, metadata entities and elements shall be considered to be mandatory, conditional or optional as specified in the applicable profile. 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 639 (all parts), Code for the representation of names of languages ISO 3166 (all parts), Codes for the representation of names of countries and their subdivisions ISO 4217:2001, Codes for the representation of currencies and funds ISO 8859 (parts 1 to 16), Information technology 8-bit single-byte coded graphic character sets ISO 8879, Information processing Text and office systems Standard Generalized Markup Language (SGML) ISO/IEC , Information technology Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture and Basic Multilingual Plane ISO/IEC (all parts), Information technology Specification and standardization of data elements ISO 19106: 1), Geographic information Profiles ISO 19107: 1), Geographic information Spatial schema ISO 19108:2002, Geographic information Temporal schema ISO 19109: 1), Geographic information Rules for application schema ISO 19110: 1), Geographic information Methodology for feature cataloguing ISO 19111: 1), Geographic information Spatial referencing by coordinates ISO 19112: 1), Geographic information Spatial referencing by geographic identifiers ISO 19113:2002, Geographic information Quality principles ISO 19114: 1), Geographic information Quality evaluation procedures ISO 19117: 1), Geographic information Portrayal ISO 19118: 1), Geographic information Encoding 1) To be published. 2 ISO 2003 All rights reserved

13 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) 4 Terms and definitions For the purposes of this document, the following terms and definitions apply. NOTE The terms and definitions used in conjunction with the UML models are addressed in Clause data type specification of a value domain with operations allowed on values in this domain [ISO 19103] EXAMPLE NOTE Integer, Real, Boolean, String, Date, and GM_Point. A data type is identified by a term, e.g. Integer. 4.2 dataset identifiable collection of data NOTE A dataset may be a smaller grouping of data which, though limited by some constraint such as spatial extent or feature type, is located physically within a larger dataset. Theoretically, a dataset may be as small as a single feature or feature attribute contained within a larger dataset. A hardcopy map or chart may be considered a dataset. 4.3 dataset series collection of datasets sharing the same product specification 4.4 grid network composed of two or more sets of curves in which the member of each set intersect the members of the other sets in an algorithmic way [ISO 19123] 4.5 metadata data about data 4.6 metadata element discrete unit of metadata NOTE 1 NOTE 2 Metadata elements are unique within a metadata entity. Equivalent to an attribute in UML terminology. 4.7 metadata entity set of metadata elements describing the same aspect of data NOTE 1 NOTE 2 May contain one or more metadata entities. Equivalent to a class in UML terminology. 4.8 metadata section subset of metadata which consists of a collection of related metadata entities and metadata elements NOTE Equivalent to a package in UML terminology. 4.9 model abstraction of some aspects of a universe of discourse [ISO 19109] ISO 2003 All rights reserved 3

14 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL 4.10 resource asset or means that fulfils a requirement EXAMPLE Dataset, service, document, person or organization temporal reference system reference system against which time is measured [ISO 19108] 5 Symbols and abbreviated terms 5.1 Abbreviations DTD IDL OCL SGML UML XML Document Type Definition Interface Definition Language Object Constraint Language Standard Generalized Markup Language Unified Modelling Language Extensible Markup Language 5.2 UML notations The diagrams that appear in this International Standard are presented using the Unified Modelling Language (UML) static structure diagram with the ISO Interface Definition Language (IDL) basic type definitions and the UML Object Constraint Language (OCL) as the conceptual schema language. The UML notations used in this International Standard are described in the Figure 1. Association Aggregation Composition Generalization Dependency Figure 1 UML notation 4 ISO 2003 All rights reserved

15 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) 5.3 UML model relationships Associations An association is used to describe a relationship between two or more classes. UML defines three different types of relationships, called association, aggregation and composition. The three types have different semantics. An ordinary association shall be used to represent a general relationship between two classes. The aggregation and composition associations shall be used to create part-whole relationships between two classes. The direction of an association must be specified. If the direction is not specified, it is assumed to be a two-way association. If one-way associations are intended, the direction of the association can be marked by an arrow at the end of the line. An aggregation association is a relationship between two classes in which one of the classes plays the role of container and the other plays the role of a containee. A composition association is a strong aggregation. In a composition association, if a container is deleted, then all of its containee s are deleted as well. The composition association shall be used when the s representing the parts of a container cannot exist without the container Generalization A generalization is a relationship between a superclass and the subclasses that may be substituted for it. The superclass is the generalized class, while the subclasses are specified classes Instantiation/Dependency A dependency relationship shows that the client class depends on the supplier class/interface to provide certain services, such as: Client class accesses a value (constant or variable) defined in the supplier class/interface; Operations of the client class invoke operations of the supplier class/interface; Operations of the client class have signatures whose return class or arguments are instances of the supplier class/interface. An instantiated relationship represents the act of substituting actual values for the parameters of a parameterized class or parameterized class utility to create a specialized version of the more general item Roles If an association is navigable in a particular direction, the model shall supply a role name that is appropriate for the role of the target in relation to the source. Thus in a two-way association, two role names will be supplied. Figure 2 represents how role names and cardinalities are expressed in UML diagrams. ISO 2003 All rights reserved 5

16 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Association between classes Association name Class #1 Class #2 role-1 role-2 Association cardinality 1 Class Exactly one 1..* Class One or more 0..* Class Zero or more n Class Specific number 0..1 Class Optional (zero or one) Aggregation between classes Aggregate class Class Inheritance (subtyping of classes) Superclass Component class #1 Component class #2... Component class #n Subclass #1 Subclass #2 Subclass #n... Figure 2 UML roles 5.4 UML model stereotypes A UML stereotype is an extension mechanism for existing UML concepts. It is a model element that is used to classify (or mark) other UML elements so that they in some respect behave as if they were instances of new virtual or pseudo metamodel classes whose form is based on existing base metamodel classes. Stereotypes augment the classification mechanisms on the basis of the built-in UML metamodel class hierarchy. Below are brief descriptions of the stereotypes used in this International Standard, for more detailed descriptions consult ISO/TS In this International Standard the following stereotypes are used: a) <<Type>> class used for specification of a domain of instances (s), together with the operations applicable to the s. A type may have attributes and associations. b) <<Enumeration>> data type whose instances form a list of named literal values. Both the enumeration name and its literal values are declared. Enumeration means a short list of well-understood potential values within a class. c) <<DataType>> a descriptor of a set of values that lack identity and whose operations do not have side effects. Datatypes include primitive pre-defined types and user-definable types. Pre-defined types include numbers, string, and time. r-definable types include enumerations. d) <<CodeList>> used to describe a more open enumeration. <<CodeList>> is a flexible enumeration. Code lists are useful for expressing a long list of potential values. If the elements of the list are completely known, an enumeration should be used; if the only likely values of the elements are known, a code list should be used. 6 ISO 2003 All rights reserved

17 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) e) <<Union>> describes a selection of one of the specified types. This is useful to specify a set of alternative classes/types that can be used, without the need to create a common super-type/class. f) <<Abstract>> class (or other classifier) that cannot be directly instantiated. UML notation for this to show the name in italics. g) <<Metaclass>> class whose instances are classes. Metaclasses are typically used in the construction of metamodels. A metaclass is an class whose primary purpose is to hold metadata about another class. h) <<Interface>> named set of operations that characterize the behaviour of an element. i) <<Package>> cluster of logically related components, containing sub-packages. j) <<Leaf>> package that contains definitions, without any sub-packages. 5.5 Package abbreviations Two letter abbreviations are used to denote the package that contains a class. Those abbreviations precede class names, connected by a _. The standard that those classes are located in is indicated in parentheses. A list of those abbreviations follows. CC Changing Coordinates (ISO 19111) CI Citation (ISO 19115) CV Coverages (ISO 19123) DQ Data quality (ISO 19115) DS Dataset (ISO 19115) EX Extent (ISO 19115) FC Feature Catalogue (ISO 19110) FE Feature (ISO 19109) FT Feature Topology (ISO 19107) GF General Feature (ISO 19109) GM Geometry (ISO 19107) GR Graph (ISO 19107) LI Lineage (ISO 19115) MD Metadata (ISO 19115) PF Feature Portrayal (ISO 19117) PS Positioning Services (ISO 19116) RS Reference System (ISO 19115) SC Spatial Coordinates (ISO 19111) ISO 2003 All rights reserved 7

18 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL SI Spatial Identification (ISO 19112) SV Services (ISO 19119) TM Temporal (ISO 19108) TP Topology (ISO 19107) TS Simple Topology (ISO 19107) 5.6 UML model/data dictionary relationships Table 1 illustrates the relationship between the terminology of the UML models and the data dictionary. Table 1 Relationship between UML model and data dictionary UML Model Package Generalized Class Specified Class Class Attribute Association Section Entity Entity Entity Element Element Data Dictionary 6 Requirements 6.1 Metadata for geographic data requirement This International Standard identifies the metadata required to describe digital geographic data. Metadata is applicable to independent datasets, aggregations of datasets, individual geographic features, and the various classes of s that compose a feature. Metadata shall be provided for geographic datasets and may, optionally, be provided for aggregations of datasets, features, and attributes of features. Metadata is composed of one or more Metadata Sections (UML Packages) containing one or more Metadata Entities (UML classes). 6.2 Metadata application information Figure 3 is a UML class diagram defining the classes of geographic information to which metadata applies. It specifies that a dataset (DS_DataSet) must have one or more related Metadata entity sets (MD_Metadata). Metadata may optionally relate to a Feature, Feature Attribute, Feature Type, Feature Property Type (a Metaclass instantiated by Feature association role, Feature attribute type, and Feature operation), and aggregations of datasets (DS_Aggregate). Dataset aggregations may be specified (subclassed) as a general association (DS_OtherAggregate), a dataset series (DS_Series), or a special activity (DS_Initiative). MD_Metadata also applies to other classes of information and services not shown in this diagram (see MD_ScopeCode, B.5.25). 8 ISO 2003 All rights reserved

19 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) <<Metaclass>> GF_FeatureType (from General Feature Model) <<Metaclass>> GF_AttributeType +featuretype +featureattribute 0..* 0..* 0..* +featuretypemetadata 0..* +featureattributemetadata <<Metaclass>> GF_PropertyType (from General Feature Model) +propertytypemetadata +propertytype 0..* MD_Metadata (from Metadata entity set information) 0..* +seriesmetadata 1..* +has 1..* MultipleAggregation +superset +subset 0..* 0..* +series 0..* <<Abstract>> DS_Aggregate +partof 0..* +composedof 1..* +describes 0..* DS_DataSet DS_OtherAggregate DS_Series DS_Initiative DS_StereoMate DS_Platform DS_Sensor DS_ProductionSeries Figure 3 Metadata application 6.3 Metadata packages Metadata package and entity relationship In this International Standard, metadata for geographic data is presented in UML Packages. Each package contains one or more entities (UML Classes), which can be specified (subclassed) or generalized (superclassed). Entities contain elements (UML class attributes) which identify the discrete units of metadata. Entities may be related to one or more other entities. Entities can be aggregated and repeated as necessary to meet: (1) the mandatory requirements stated in this International Standard; (2) additional user requirements. Figure 4 illustrates the layout of the packages. The metadata is fully specified in the UML model diagrams and data dictionary for each package, which can be found in Annexes A and B respectively. If a discrepancy between the two annexes exists, Annex A shall be considered authoritative. ISO 2003 All rights reserved 9

20 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL <<Leaf>> Portrayal catalogue information <<Leaf>> Constraint information <<Leaf>> Content information <<Leaf>> Citation and responsible party information <<Leaf>> Maintenance information <<Leaf>> Distribution information <<Leaf>> Application schema information <<Leaf>> Metadata entity set information <<Leaf>> Metadata extension information <<Leaf>> Data quality information <<Leaf>> Identification information <<Leaf>> Reference system information <<Leaf>> Spatial representation information <<Leaf>> Units of Measure (from Derived) <<Leaf>> Extent information Figure 4 Metadata packages The relationship between packages of metadata and metadata entities is shown in Table 2. The packages of metadata are listed in the Package column and the aggregate entity of metadata contained within the corresponding package is listed in the Entity column. The entities contained within the packages are further defined in through Each package has a corresponding subclause, which is listed in the Subclause Number column. 10 ISO 2003 All rights reserved

21 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Table 2 Relationship between packages of metadata and metadata entities Subclause Number Package Entity UML Diagram Data Dictionary Metadata entity set information MD_Metadata A.2.1 B Identification information MD_Identification A.2.2 B Constraint information MD_Constraints A.2.3 B Data quality information DQ_DataQuality A A A B B B Maintenance information MD_MaintenanceInformation A.2.5 B Spatial representation information MD_SpatialRepresentation A.2.6 B Reference system information MD_ReferenceSystem A.2.7 B Content information MD_ContentInformation A.2.8 B Portrayal catalogue information MD_PortrayalCatalogueReference A.2.9 B Distribution information MD_Distribution A.2.10 B Metadata extension information MD_MetadataExtensionInformation A.2.11 B Application schema information MD_ApplicationSchemaInformation A.2.12 B Extent information EX_Extent A.3.1 B Citation and responsible party information CI_Citation CI_ResponsibleParty A.3.2 B Package descriptions Metadata entity set information (MD_Metadata) Metadata entity set information consists of the entity (UML class) MD_Metadata, which is mandatory. The MD_Metadata entity contains both mandatory and optional metadata elements (UML attributes). The MD_Metadata entity is an aggregate of the following entities (which are further explained in the following subclauses): MD_Identification MD_Constraints DQ_DataQuality MD_MaintenanceInformation MD_SpatialRepresentation MD_ReferenceSystem MD_ContentInformation MD_PortrayalCatalogueReference MD_Distribution MD_MetadataExtensionInformation MD_ApplicationSchemaInformation ISO 2003 All rights reserved 11

22 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Identification information (MD_Identification) Identification information contains information to uniquely identify the data. Identification information includes information about the citation for the resource, an abstract, the purpose, credit, the status and points of contact. The MD_Identification entity is mandatory. It contains mandatory, conditional, and optional elements. The MD_Identification entity may be specified (subclassed) as MD_DataIdentification when used to identify data and as MD_ServiceIdentification when used to identify a service. MD_ServiceIdentification provides a high level description of a service, for further information see ISO MD_Identification is an aggregate of the following entities: MD_Format, format of the data MD_BrowseGraphic, graphic overview of the data MD_Usage, specific uses of the data MD_Constraints, constraints placed on the resource MD_Keywords, keywords describing the resource MD_MaintenanceInformation, how often the data is scheduled to be updated and the scope of the update MD_AggregateInformation, information about datasets that are aggregate parts of the dataset that the metadata describes The extent element of MD_DataIdentification is conditional; either the EX_GeographicBoundingBox or the EX_GeographicDescription subclass of extent s geographicelement Role shall be included if the dataset is spatially referenced. If necessary both may be used. The characterset element of MD_DateIdentification is conditional; it is documented if ISO/IEC is not used Constraint information (MD_Constraints) This package contains information concerning the restrictions placed on data. The MD_Constraints entity is optional and may be specified as MD_LegalConstraints and/or MD_SecurityConstraints. The otherconstraint element of MD_LegalConstraints shall be non-zero (used) only if accessconstraints and/or useconstraints elements have a value of otherrestrictions, which is found in the MD_RestrictionCode codelist Data quality information (DQ_DataQuality) This package contains a general assessment of the quality of the dataset. The DQ_DataQuality entity is optional and contains the scope of the quality assessment. DQ_DataQuality is an aggregate of LI_Lineage and DQ_Element. DQ_Element can be specified as DQ_Completeness, DQ_LogicalConsistency, DQ_PositionalAccuracy, DQ_ThematicAccuracy and DQ_TemporalAccuracy. Those five entities represent Elements of data quality and can be further subclassed to the sub-elements of data quality. rs may add additional elements and sub-elements of data quality by sub-classing DQ_Element or the appropriate subelement. This package also contains information about the sources and production processes used in producing a dataset. The LI_Lineage entity is optional and contains a statement about the lineage. LI_Lineage is an aggregate of LI_ProcessStep and LI_Source. Either the report or lineage roles of DQ_DataQuality must be present if DQ_DataQuality.scope.DQ_Scope.level has a value of dataset. 12 ISO 2003 All rights reserved

23 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) The leveldescription element of DQ_Scope is mandatory if the level element of DQ_Scope does not have a value of dataset or series. The statement element of LI_Lineage is mandatory if DQ_DataQuality.scope.DQ_Scope.level has a value of dataset or series and the LI_Lineage roles of source and processstep are not documented. The source role of LI_Lineage is mandatory if the statement element and the processstep role of LI_Lineage are not documented. The processstep role of LI_Lineage is mandatory if the statement element and the source role of LI_Lineage are not documented. Either the description or sourceextent element of LI_Source must be documented Maintenance information (MD_MaintenanceInformation) This package contains information about the scope and frequency of updating data. The MD_MaintenanceInformation entity is optional and contains mandatory and optional metadata elements Spatial representation information (MD_SpatialRepresentation) This package contains information concerning the mechanisms used to represent spatial information in a dataset. The MD_SpatialRepresentation entity is optional and can be specified as MD_GridSpatialRepresentation and MD_VectorSpatialRepresentation. Each of the specified entities contains mandatory and optional metadata elements. When further description is necessary, MD_GridSpatialRepresentation may be specified as MD_Georectified and/or MD_Georeferenceable. Metadata for Spatial data representation are derived from ISO Reference system information (MD_ReferenceSystem) This package contains the description of the spatial and temporal reference system(s) used in a dataset. MD_ReferenceSystem contains an element to identify the reference system used. MD_ReferenceSystem may be subclassed as MD_CRS, which is an aggregate of MD_ProjectionParameters and MD_EllipsoidParameters. MD_ProjectionParameters is an aggregate of MD_ObliqueLineAzimuth and MD_ObliqueLinePoint Content information (MD_ContentInformation) This package contains information identifying the feature catalogue used (MD_FeatureCatalogueDescription) and/or information describing the content of a coverage dataset (MD_CoverageDescription). Both description entities are subclasses of the MD_ContentInformation entity. MD_CoverageDescription may be subclassed as MD_ImageDescription, and has an aggregate of MD_RangeDimension. MD_RangeDimension may additionally be subclassed as MD_Band Portrayal catalogue information (MD_PortrayalCatalogueReference) This package contains information identifying the portrayal catalogue used. It consists of the optional entity MD_PortrayalCatalogueReference. This entity contains the mandatory element used to specify which portrayal catalogue is used by the dataset Distribution information (MD_Distribution) This package contains information about the distributor of, and options for obtaining, a resource. It contains the optional MD_Distribution entity. MD_Distribution is an aggregate of the options for the digital distribution of a dataset (MD_DigitalTransferOptions), identification of the distributor (MD_Distributor) and the format of the distribution (MD_Format), which contains mandatory and optional elements. MD_DigitalTransferOptions contains the medium used for the distribution (MD_Medium) of a dataset, and is an aggregate of ISO 2003 All rights reserved 13

24 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL MD_Distributor. MD_Distributor s other aggregate is the process for ordering a distribution (MD_StandardOrderProcess). The distributionformat role of MD_Distribution is mandatory if the distributorformat role of MD_Distributor is not documented. The distributorformat role of MD_Distributor is mandatory if the distributionformat role of MD_Distribution is not documented Metadata extension information (MD_MetadataExtensionInformation) This package contains information about user specified extensions. It contains the optional MD_MetadataExtensionInformation entity. MD_MetadataExtensionInformation is an aggregate of information describing the extended metadata elements (MD_ExtendedElementInformation). If the datatype element of MD_ExtendedElementInformation does not have a value of codelist, enumeration or codelistelement ; then the obligation, maximumoccurence and domainvalue elements are mandatory. If the datatype element of MD_ExtendedElementInformation has a value of codelistelement, then the domaincode element is mandatory. If the datatype element of MD_ExtendedElementInformation does not have a value of codelistelement, then the shortname element is mandatory. If the obligation element of MD_ExtendedElementInformation has a value of conditional, then the condition element is mandatory Application schema information (MD_ApplicationSchemaInformation) This package contains information about the application schema used to build a dataset. It contains the optional entity MD_ApplicationSchemaInformation. The entity contains mandatory and optional elements. 6.4 Metadata datatypes Extent information (EX_Extent) The datatype in this package is an aggregate of the metadata elements that describe the spatial and temporal extent of the referring entity. The EX_Extent entity contains information about the geographic (EX_GeographicExtent), temporal (EX_TemporalExtent) and the vertical (EX_VerticalExtent) extent of the referring entity. EX_GeographicExtent can be subclassed as EX_BoundingPolygon, EX_GeographicBoundingBox and EX_GeographicDescription. The combined spatial and temporal extent (EX_SpatialTemporalExtent) is an aggregate of EX_GeographicExtent. EX_SpatialTemporalExtent is a subclass of EX_TemporalExtent. The EX_Extent entity has three optional roles named geographicelement, temporalelement, and verticalelement and an element called description. At least one of the four shall be used. The entity stereotype DataType is defined in ISO 2003 All rights reserved

25 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Citation and responsible party information (CI_Citation and CI_ResponsibleParty) This package of datatypes provides a standardized method (CI_Citation) for citing a resource (dataset, feature, source, publication, etc.), as well as information about the party responsible (CI_ResponsibleParty) for a resource. The CI_ResponsibleParty datatype contains the identity of person(s), and/or position, and/or organization(s) associated with the resource. The location (CI_Address) of the responsible person or organization is also defined here. The entity stereotype DataType is defined in Core metadata for geographic datasets This International Standard defines an extensive set of metadata elements; typically only a subset of the full number of elements is used. However, it is essential that a basic minimum number of metadata elements be maintained for a dataset. Listed are the core metadata elements required to identify a dataset, typically for catalogue purposes. This list contains metadata elements answering the following questions: Does a dataset on a specific topic exist ( what )?, For a specific place ( where )?, For a specific date or period ( when )? and A point of contact to learn more about or order the dataset ( who )?. Using the recommended optional elements in addition to the mandatory elements will increase interoperability, allowing users to understand without ambiguity the geographic data and the related metadata provided by either the producer or the distributor. Dataset metadata profiles of this International Standard shall include this core. Listed below (see Table 3) are the core metadata elements (mandatory and recommended optional) required for describing a dataset. An M indicates that the element is mandatory. An O indicates that the element is optional. A C indicates that the element is mandatory under certain conditions. ISO 2003 All rights reserved 15

26 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Table 3 Core metadata for geographic datasets Dataset title (M) (MD_Metadata > MD_DataIdentification.citation > CI_Citation.title) Dataset reference date (M) (MD_Metadata > MD_DataIdentification.citation > CI_Citation.date) Dataset responsible party (O) (MD_Metadata > MD_DataIdentification.pointOfContact > CI_ResponsibleParty) Geographic location of the dataset (by four coordinates or by geographic identifier) (C) (MD_Metadata > MD_DataIdentification.extent > EX_Extent > EX_GeographicExtent > EX_GeographicBoundingBox or EX_GeographicDescription) Dataset language (M) (MD_Metadata > MD_DataIdentification.language) Dataset character set (C) (MD_Metadata > MD_DataIdentification.characterSet) Dataset topic category (M) (MD_Metadata > MD_DataIdentification.topicCategory) Spatial resolution of the dataset (O) (MD_Metadata > MD_DataIdentification.spatialResolution > MD_Resolution.equivalentScale or MD_Resolution.distance) Abstract describing the dataset (M) (MD_Metadata > MD_DataIdentification.abstract) Distribution format (O) (MD_Metadata > MD_Distribution > MD_Format.name and MD_Format.version) Additional extent information for the dataset (vertical and temporal) (O) (MD_Metadata > MD_DataIdentification.extent > EX_Extent > EX_TemporalExtent or EX_VerticalExtent) Spatial representation type (O) (MD_Metadata > MD_DataIdentification.spatialRepresentationType) Reference system (O) (MD_Metadata > MD_ReferenceSystem) Lineage (O) (MD_Metadata > DQ_DataQuality.lineage > LI_Lineage) On-line resource (O) (MD_Metadata > MD_Distribution > MD_DigitalTransferOption.onLine > CI_OnlineResource) Metadata file identifier (O) (MD_Metadata.fileIdentifier) Metadata standard name (O) (MD_Metadata.metadataStandardName) Metadata standard version (O) (MD_Metadata.metadataStandardVersion) Metadata language (C) (MD_Metadata.language) Metadata character set (C) (MD_Metadata.characterSet) Metadata point of contact (M) (MD_Metadata.contact > CI_ResponsibleParty) Metadata date stamp (M) (MD_Metadata.dateStamp) 6.6 Unified Modelling Language (UML) diagrams Annex A provides the metadata schemas in the form of Unified Modelling Language (UML) diagrams. These diagrams, in conjunction with the data dictionary presented in Annex B, serve to fully define the total abstract model for metadata. 6.7 Data dictionary Annex B contains the element and entity definitions for the metadata schemas. This dictionary, in conjunction with the diagrams presented in Annex A, serve to fully define the total abstract model for metadata. Codelists and their values provided in this International Standard (B.5 and A.2) are normative. r extensions to codelists shall follow the rules as described in Annex C and ISO/IEC ISO/IEC defines the information to be specified, conditions to be fulfilled and procedure(s) to be followed for registering data elements. 16 ISO 2003 All rights reserved

27 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) 6.8 Metadata extensions and profiles Annex C provides the rules for defining and applying additional metadata to better serve special user needs. 6.9 Abstract test suite Annex D defines the tests that must be passed to claim conformance with this International Standard Comprehensive dataset metadata application profile Annex E defines a comprehensive metadata application schema, which provides an implementable metadata profile. It incorporates the mandatory and optional metadata required to document a geographic data resource completely (independent dataset, dataset series, or individual geographic features). This schema fully defines the complete range of metadata required to identify, evaluate, extract, employ, and manage geographic information. Data producers typically provide comprehensive metadata. This schema is provided as a UML model Metadata extension methodology Annex F provides guidance on extending metadata. Additional metadata elements shall be defined according to the rules described in Annex C Metadata implementation Annex G provides an overview of methods and ideas for the implementation and management of metadata for the purposes of search and retrieval, metadata exchange, and presentation Hierarchical levels of metadata Annex H provides methods for efficiently handling metadata for datasets with metadata requirements at different levels Implementation examples Annex I provides an example of the use of this International Standard, utilizing the core components of the comprehensive profile, for a geographic dataset. An example of extended metadata elements, as may be developed by a specific information community, is provided (I.3) Multilingual support for free text fields Annex J provides a structure to implement the free text fields of this International Standard in multiple languages. ISO 2003 All rights reserved 17

28 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Annex A (normative) Metadata schemas A.1 Metadata UML models Metadata for describing geographic data is defined using an abstract model in the Unified Modelling Language (UML). The diagrams in the following subclauses provide views, which are portions of the total abstract model for metadata. Each diagram defines a metadata section (UML package) of related entities, elements, data types, and code lists. Related entities, which are defined in another diagram, are shown with elements suppressed and the defining package specified under the entity name in parenthesis. Throughout the following models, entities may have mandatory and/or optional elements and associations. In some cases, optional entities may have mandatory elements; those elements become mandatory only if the optional element is used. 18 ISO 2003 All rights reserved

29 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A.2 Metadata package UML diagrams A.2.1 Metadata entity set information Figure A.1 defines the class MD_Metadata and shows containment relationships with the other metadata classes which, in aggregate, define metadata for geographic data. The other metadata class diagrams can be found on the following pages. The data dictionary for this diagram is located in B.2.1. <<Abstract>> MD_SpatialRepresentation (from Spatial representation information) +spatialrepresentationinfo DQ_DataQuality (from Data quality information) +dataqualityinfo 0..* MD_Distribution (from Distribution information) +contentinfo 0..* <<Abstract>> MD_ContentInformation (from Content information) +portrayalcatalogueinfo 0..* MD_PortrayalCatalogueReference (from Portrayal catalogue information) MD_ReferenceSystem (from Reference system information) +referencesysteminfo 0..* 0..* +distributioninfo metadataextensioninfo 0..* MD_Metadata + fileidentifier [0..1] : CharacterString + language [0..1] : CharacterString + characterset [0..1] : MD_CharacterSetCode = "utf8" + parentidentifier [0..1] : CharacterString + hierarchylevel [0..*] : MD_ScopeCode = "dataset" + hierarchylevelname [0..*] : CharacterString + contact [1..*] : CI_ResponsibleParty + datestamp : Date + metadatastandardname [0..1] : CharacterString + metadatastandardversion [0..1] : CharacterString + dataseturi [0..1] : CharacterString MD_MetadataExtensionInformation (from Metadata extension information) +identificationinfo +metadataconstraints 0..* MD_MaintenanceInformation (from Maintenance information) * +metadatamaintenance +resourcemaintenance 1..* <<Abstract>> MD_Identification (from Identification information) +resourceconstraints 0..* MD_Constraints (from Constraint information) +applicationschemainfo 0..* MD_ApplicationSchemaInformation (from Application schema information) Conditional statements: language: documented if not defined by the encoding standard characterset: documented if ISO not used and not defined by the encoding standard hierarchylevel: documented if hierarchylevel not = "dataset" hierarchylevelname: documented if hierarchylevel not = "dataset" A.2.2 Identification information Figure A.1 Metadata entity set information Figure A.2 defines the metadata classes required to identify a resource. It also defines separate specialization sub-classes for identifying data and services. The data dictionary for this diagram is located in B.2.2. ISO 2003 All rights reserved 19

30 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL MD_Usage + specificusage : CharacterString + usagedatetime [0..1] : DateTime + userdeterminedlimitations [0..1] : CharacterString + usercontactinfo [1..*] : CI_ResponsibleParty MD_Metadata (from Metadata entity set information) +resourceconstraints MD_Constraints (from Constraint information) 0..* Either "aggregatedatasetname" or "aggregatedatasetidentifier" must be documented MD_BrowseGraphic + filename : CharacterString + filedescription [0..1] : CharacterString + filetype [0..1] : CharacterString MD_Format (from Distribution information) <<CodeList>> MD_KeywordTypeCode + dicipline + place + stratum + temporal + theme +resourcespecificusage 0..* +identificationinfo 1..* +graphicoverview 0..* +resourceformat 0..* <<Abstract>> MD_Identification + citation : CI_Citation + abstract : CharacterString + purpose [0..1] : CharacterString + credit [0..*] : CharacterString + status [0..*] : MD_ProgressCode + poinofcontact [0..*] : CI_ResponsibleParty characterset: documented if ISO is not used {MD_Metadata.hierarchyLevel = "dataset" implies count (extent.geographicelement.ex_geographicboundingbox) + count (extent.geographicelement.ex_geographicdescription) >=1} aggregationinfo 0..* +descriptivekeywords {MD_Metadata.hierarchyLevel notequal "dataset" implies topiccategory is not mandatory} <<DataType>> MD_AggregateInformation + aggregatedatasetname [0..1] : CI_Citation + aggregatedatasetidentifier [0..1] : MD_Identifier + associationtype : DS_AssociationTypeCode + initiativetype [0..1] : DS_InitiativeTypeCode 0..* MD_Keywords + keyword [1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusname [0..1] : CI_Citation 0..* +resourcemaintenance MD_MaintenanceInformation (from Maintenance information) MD_DataIdentification + spatialrepresentationtype [0..*] : MD_SpatialRepresentationTypeCode + spatialresolution [0..*] : MD_Resolution + language [1..*] : CharacterString + characterset [0..*] : MD_CharacterSetCode = "utf8" + topiccategory [0..*] : MD_TopicCategoryCode + environmentdescription [0..1] : CharacterString + extent [0..*] : EX_Extent + supplementalinformation [0..1] : CharacterString <<Union>> MD_Resolution + equivalentscale : MD_RepresentativeFraction + distance : Distance <<CodeList>> MD_InitiativeTypeCode + campaign + collection + exercise + experiment + investigation + mission + sensor + operation + platform + process + program + project + study + task + trial <<CodeList>> DS_AssociationTypeCode + crossreference + largerworkcitation + partofseamlessdatabase + source + stereomate <<Enumeration>> MD_TopicCategoryCode + farming + biota + boundaries + climatologymeteorologyatmosphere + economy + elevation + environment + geoscientificinformation + health + imagerybasemapsearthcover + intelligencemilitary + inlandwaters + location + oceans + planningcadastre + society + structure + transportation + utilitiescommunication <<CodeList>> MD_SpatialRepresentationTypeCode + vector + grid + texttable + tin + stereomodel + video <<CodeList>> MD_CharacterSetCode + ucs2 + ucs4 + utf7 + utf8 + utf part part part part part part part part part part part11 + (reserved for future use) part part part part16 + jis + shiftjis + eucjp + usascii + ebcdic + euckr + big5 + GB2312 MD_ServiceIdentification <<CodeList>> MD_ProgressCode + completed + historicalarchive + obsolete + ongoing + planned + required + underdevelopment <<DataType>> MD_RepresentativeFraction + denominator : Integer Figure A.2 Identification information 20 ISO 2003 All rights reserved

31 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A.2.3 Constraint information Figure A.3 defines the metadata required for managing rights to information including restrictions on access and use. The data dictionary for this diagram is located in B.2.3. <<Abstract>> MD_Identification (from Identification information) MD_Metadata (from Metadata entity set information) +resourceconstraints 0..* MD_Constraints + uselimitation [0..*] : CharacterString 0..* +metadataconstraints <<CodeList>> MD_ClassificationCode + unclassified + restricted + confidential + secret + topsecret MD_LegalConstraints + accessconstraints [0..*] : MD_RestrictionCode + useconstraints [0..*] : MD_RestrictionCode + otherconstraints [0..*] : CharacterString MD_SecurityConstraints + classification : MD_ClassificationCode + usernote [0..1] : CharacterString + classificationsystem [0..1] : CharacterString + handlingdescription [0..1] : CharacterString <<CodeList>> MD_RestrictionCode + copyright + patent + patentpending + trademark + license + intellectualpropertyrights + restricted + otherrestrictions otherconstraints: documented if accessconstraints or useconstraints = "otherrestrictions" Figure A.3 Constraint information ISO 2003 All rights reserved 21

32 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A.2.4 Data quality information A General Figure A.4 defines the metadata required to give a general assessment of the quality of a resource. The data dictionary for this diagram is located in B.2.4. MD_Metadata (from Metadata entity set information) +dataqualityinfo 0..* DQ_DataQuality + scope : DQ_Scope linage LI_Linage "report" or "linage" role is mandatory if scope.dq_scope.level = 'dataset' <<DataType>> DQ_Scope + level : MD_ScopeCode + extent [0..1] : EX_Extent + leveldescription [0..*] : MD_ScopeDescription <<CodeList>> MD_EvaluationMethodTypeCode + directinternal + directexternal + indirect "leveldescription" is mandatoryif "level" notequal 'dataset' or 'series' +report 0..* <<Abstract>> DQ_Element + nameofmeasure [0..*] : CharacterString + measureidentification [0..1] : MD_Identifier + measuredescription [0..1] : CharacterString + evaluationmethodtype [0..1] : DQ_EvaluationMethodTypeCode + evaluationmethoddescription [0..1] : CharacterString + evaluationprocedure [0..1] : CI_Citation + datetime [0..*] : DateTime + result [1..2] : DQ_Result <<Abstract>> DQ_Result DQ_ConformanceResult + specification : CI_Citation + explanation : CharacterString + pass : Boolean DQ_QuantitativeResult + valuetype [0..1] : RecordType + valueunit : UnitOfMeasure + errorstatistic [0..1] : CharacterString + value [1..*] : Record Figure A.4 Data quality information 22 ISO 2003 All rights reserved

33 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A Lineage information Figure A.5 defines metadata required to describe the sources and production processes used in producing a dataset. The data dictionary for this diagram is located in B DQ_DataQuality + scope : DQ_Scope If(count(source) + count(processstep) =0) and (DQ_DataQuality.cope.level = 'dataset' or 'series') then statement is mandatory +linage 0..1 LI_Lineage + statement [0..1] : CharacterString "source" role is mandatory if LI_Lineage.statement and "processstep" role are not documented "processstep" role is mandatory if LI_Lineage.statement and "source" role are not documented +source 0..* LI_Source + description [0..1] : CharacterString + scaledenominator [0..1] : MD_RepresentativeFraction + sourcereferencesystem [0..1] : MD_ReferenceSystem + sourcecitation [0..1] : CI_Citation + sourceextent [0..*] : EX_Extent +source 0..* 0..* +sourcestep 0..* +processstep LI_ProcessStep + description : CharacterString + rationale [0..1] : CharacterString + datetime [0..1] : DateTime + processor [0..*] : CI_ResponsibleParty "description" is mandatory if "soruceextent" is not documented "sourceextent" is mandatory if "description" is not documented Figure A.5 Lineage information ISO 2003 All rights reserved 23

34 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A Data quality classes and subclasses Figure A.6 defines the classes and subclasses of data quality used in the data quality diagram. The data dictionary for this diagram is located in B DQ_DataQuality + scope : DQ_Scope LI_Lineage lineage +report 0..* <<Abstract>> DQ_Element <<Abstract>> DQ_Completeness <<Abstract>> DQ_LogicalConsistency <<Abstract>> DQ_PositionalAccuracy DQ_CompletenessCommission DQ_ConceptualConsistency DQ_AbsoluteExternalPositionalAccuracy DQ_CompletenessOmission DQ_DomainConsistency DQ_GriddedDataPositionalAccuracy DQ_FormatConsistency DQ_RelativeInternalPositionalAccuracy DQ_TopologicalConsistency <<Abstract>> DQ_ThematicAccuracy <<Abstract>> DQ_TemporalAccuracy DQ_ThematicClassificationCorrectness DQ_AccuracyOfATimeMeasurement DQ_NonQuantitativeAttributeAccuracy DQ_TemporalConsistency DQ_QuantitativeAttributeAccuracy DQ_TemporalValidity Figure A.6 Data quality classes and subclasses 24 ISO 2003 All rights reserved

35 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A.2.5 Maintenance information Figure A.7 defines the metadata required to describe the maintenance and update practices for information. The data dictionary for this diagram is located in B.2.5. MD_Metadata (from Metadata entity set information) +metadatamaintenance 0..1 MD_MaintenanceInformation + maintenanceandupdatefrequency : MD_MaintenanceFrequencyCode + dateofnextupdate [0..1] : Date + userdefinedmaintenancefrequency [0..1] : TM_PeriodDuration + updatescope [0..*] : MD_ScopeCode + updatescopedescription [0..*] : MD_ScopeDescription + maintenancenote [0..*] : CharacterString + contact [0..*] : CI_ResponsibleParty <<CodeList>> MD_ScopeCode + attribute + attributetype + collectionhardware + collectionsession + dataset + series + nongeographicdataset + dimensiongroup + feature + featuretype + propertytype + fieldsession + software + service + model + tile <<CodeList>> MD_MaintenanceFrequencyCode + continual + daily + weekly + forthnightly + monthly + quarterly + biannually + annually + asneeded + irregular + notplanned + unknown <<Union>> MD_ScopeDescription + attributes : Set<GF_AttributeType> + features : Set<GF_FeatureType> + featureinstances : Set<GF_FeatureType> + attributeinstances : Set<GF_AttributeType> + dataset : CharacterString + other : CharacterString Figure A.7 Maintenance information ISO 2003 All rights reserved 25

36 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A.2.6 Spatial representation information Figure A.8 defines metadata required to describe the mechanism used to represent spatial information. The data dictionary for this diagram is located in B.2.6. MD_Metadata (from Metadata entity set information) +spatialrepresentationinfo 0..* <<Abstract>> MD_SpatialRepresentation MD_GridSpatialRepresentation + numberofdimensions : Integer + axisdimensionproperties : Sequence<MD_Dimension> + cellgeometry : MD_CellGeometryCode + transformationparameteravailability : Boolean MD_VectorSpatialRepresentation + topologylevel [0..1] : MD_TopologyLevelCode + geometricobjects [0..*] : MD_GeometricObjects MD_Georectified + checkpointavailability: Boolean + checkpointdescription [0..1] : CharacterString + cornerpoints : Sequence<GM_Point> + centerpoint [0..1] : GM_Point + pointinpixel : MD_PixelOrientationCode + transformationdimensiondescription [0..1] : CharacterString + transformationdimensionmapping [0..2] : CharacterString MD_Georeferenceable + controlpointavailability: Boolean + orientationparameteravailability : Boolean + orientationparameterdescription [0..1] : CharacterString + georeferencedparameters : Record + parametercitation [0..*] : CI_Citation "checkpointdescription" is mandatory if "checkpointavaliability" = 1 <<DataType>> MD_Dimension + dimensionname : MD_DimensionNameTypeCode + dimensionsize : Integer + resolution [0..1] : Measure <<CodeList>> MD_GeometricObjectTypeCode + complex + composite + curve + point + solid + surface <<CodeList>> MD_DimensionTypeCode + row + column + vertical + track + crosstrack + line + sample + time <<DataType>> MD_GeometricObjects + geometricobjecttype : MD_GeometricObjectTypeCode + geometricobjectcount [0..1] : Integer <<Enumeration>> MD_PixelOrientationCode + center + lowerleft + lowerright + upperright + upperleft <<CodeList>> MD_TopologyLevelCode + geometryonly + topology1d + planargraph + fullplanargraph + surfacegraph + fullsurfacegraph + topology3d + fulltopology3d + abstract <<CodeList>> MD_CellGeometryCode + point + area Figure A.8 Spatial representation information 26 ISO 2003 All rights reserved

37 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A.2.7 Reference system information Figure A.9 defines metadata required to describe the spatial and temporal reference system used. The data dictionary for this diagram is located in B.2.7. MD_Metadata (from Metadata entity set information) "referencesystemidentifier" is mandatory if MD_CRS.projection, MD_CRS.ellipsoid and MD_CRS.datum are not documented <<DataType>> MD_Identifier + authority [0..1] : CI_Citation + code : CharacterString +referencesysteminfo 0..* MD_ReferenceSystem + referencesystemidentifier [0..1] : RS:Identifier RS_Identifier + codespace [0..1] : CharacterString + version [0..1] : CharacterString MD_CRS + projection [0..1] : RS_Identifier + ellipsoid [0..1] : RS_Identifier + datum [0..1] : RS_Identifier <<Abstract>> RS_ReferenceSystem + name : RS_Identifier + domainofvalidity [0..*] : EX_Extent +ellipsoidparameters 0..1 MD_EllipsoidParameters + semimajoraxis : Real + axisunits : UomLength + denominatorofflatteningratio [0..1] : Real +projectionparameters 0..1 MD_ProjectionParameters + zone [0..1] : Integer + standardparallel [0..2] : Real + longitudeofcentralmeridian [0..1] : Real + latitudeofprojectionorigin [0..1] : Real + falseeasting [0..1] : Real + falsenorthing [0..1] : Real + falseeastingnorthingunits [0..1] : UomLength + scalefactoratequator [0..1] : Real + heightofprospectivepointabovesurface [0..1] : Real + longitudeofprojectioncenter [0..1] : Real + latitudeofprojectioncenter [0..1] : Real + scalefactoratcenterline [0..1] : Real + straightverticallongitudefrompole [0..1] : Real + scalefactoratprojectionorigin [0..1] : Real +obliquelineazimuthparameter 0..1 "denominatorofflatteningratio" is mandatory if not a spheroid MD_ObliqueLineAzimuth + azimuthangle : Real + azimuthmeasurepointlongitude : Real +obliquelinepointparameter 0,2 MD_ObliqueLinePoint + azimuthlinelatitude : Real + azimuthlinelongitude : Real Figure A.9 Reference system information ISO 2003 All rights reserved 27

38 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A.2.8 Content information Figure A.10 defines metadata about the content of a coverage and the feature catalogue(s) used to define features. The data dictionary for this diagram is located in B.2.8. MD_Metadata (from Metadata entity set information) +contentinfo 0..* <<Abstract>> MD_ContentInformation MD_CoverageDescription + attributedescription : RecordType + contenttype : MD_CoverageContentTypeCode MD_FeatureCatalogueDescription + compliancecode [0..1] : Boolean + language [0..*] : CharacterString + includewithdataset : Boolean + featuretypes [0..*] : GenericName + featurecataloguecitation [1..*] : CI_Citation +dimension 0..* MD_RangeDimension + sequenceidentifier [0..1] : MemberName + descriptor [0..1] : CharacterString MD_Band + maxvalue [0..1] : Real + minvalue [0..1] : Real + units [0..1] : UomLength + peakresponse [0..1] : Real + bitspervalue [0..1] : Integer + tonegradation [0..1] : Integer + scalefactor [0..1] : Real + offset [0..1] : Real "units" is mandatory if "maxvalue" or "minvalue" are provided MD_ImageDescription + illuminationelevationangel [0..1] : Real + illuminationazimuthangel [0..1] : Real + imagingcondition [0..1] : MD_ImagingConditionCode + imagequalitycode [0..1] : MD_Identifier + cloudcoverpercentage [0..1] : Real + processinglevelcode [0..1] : MD_Identifer + compressiongenerationquantity [0..1] : Integer + triangulationindicator [0..1] : Boolean + radiometriccalibrationdataavailability [0..1] : Boolean + cameracalibrationinformationavailability [0..1] : Boolean + filmdistortioninformationavailability [0..1] : Boolean + lensdistortioninformationavailability [0..1] : Boolean <<CodeList>> MD_CoverageContentTypeCode + image + thematicclassification + physicalmeasurement <<CodeList>> MD_ImagingConditionCode + blurredimage + cloud + degradingobliquity + fog + heavysmokeordust + night + rain + semindarkness + shadow + snow + terrainmasking Figure A.10 Content information 28 ISO 2003 All rights reserved

39 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A.2.9 Portrayal catalogue information Figure A.11 defines metadata about the portrayal catalogue(s) used to display data. The data dictionary for this diagram is located in B.2.9. MD_Metadata (from Metadata entity set information) +portrayalcatalogueinfo 0..* MD_PortrayalCatalogueReference + portrayalcataloguecitation [1..*] : CI_Citation Figure A.11 Portrayal catalogue information ISO 2003 All rights reserved 29

40 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A.2.10 Distribution information Figure A.12 defines metadata required for accessing a resource. The data dictionary for this diagram is located in B MD_Metadata (from Metadata entity set information) count (distributionformat + distributorformat) > 0 +distributioninfo 0..1 MD_Distribution +distributionformat 0..* MD_Format + name : CharacterString + version : CharacterString + amendmentnumber [0..1] : CharacterString + specification [0..1] : CharacterString + filedecompressiontechnique [0..1] : CharacterString +transferoptions 0..* MD_DigitalTransferOptions + unitsofdistribution [0..1] : CharacterString + transfersize [0..1] : Real + online [0..*] : CI_OnlineResource + offline [0..1] : MD_Medium <<DataType>> MD_Medium + name [0..1] : MD_MediumNameCode + density [0..*] : Real + densityunits [0..1] : CharacterString + volumes [0..1] : Integer + mediumformat [0..*] : MD_MediumFormatCode + mediumname [0..1] : CharacterString "densityunits" is mandatory if "density" is provided 0..* +distributortransferoptions +distributor 0..* +distributorformat 0..* +FormatDistributor 0..* MD_Distributor + distributorcontact : CI_ResponsibleParty 0..* +distributionorderprocess MD_StandardOrderProcess + fees [0..1] : CharacterString + plannedavailabledatetime [0..1] : DateTime + orderinginstructions [0..1] : CharacterString + turnaround [0..1] : CharacterString <<CodeList>> MD_MediumFormatCode + cpio + tar + highsierra + iso iso9660rockridge + iso9660applehfs <<CodeList>> MD_MediumNameCode + cdrom + dvd + dvdrom + 3halfInchFloppy + 5quarterInchFloppy + 7trackTape + 9trackTape Cartridge Cartridge Cartridge + 4mmCartridgeTape + 8mmCartridgeTape + 1quarterInchCartridgeTape + digitallineartape + online + satellite + telephonelink + hardcopy Figure A.12 Distribution information 30 ISO 2003 All rights reserved

41 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A.2.11 Metadata extension information Figure A.13 defines the extended metadata elements. The data dictionary for this diagram is located in B MD_Metadata (from Metadata entity set information) <<Enumeration>> MD_ObligationCode + mandatory + optional + conditional 0..* +metadataextentioninfo MD_MetadataExtensionInformation + extensiononlineresource [0..1] : CI_OnlineResource +extendedelementinformation 0..* MD_ExtendedElementInformation + name : CharacterString + shortname [0..1] : CharacterString + domaincode [0..1] : Integer + definition : CharacterString + obligation [0..1] : MD_ObligationCode + condition [0..1] : CharacterString + datatype : MD_DatatypeCode + maximumoccurence [0..1] : CharacterString + domainvalue [0..1] : CharacterString + parententity [1..*] : CharacterString + rule : CharacterString + rationale [0..*] : CharacterString + source [1..*] : CI_ResponsibleParty <<CodeList>> MD_DatatypeCode + class + codelist + enumeration + codelistelement + abstractclass + aggregateclass + specifiedclass + datatypeclass + interfaceclass + unionclass + metaclass + typeclass + characterstring + integer + association if "datatype" = 'codelistelement' then "domaincode" is mandatory if "datatype" notequal 'codelistelement' then "shortname" is mandatory if "datatype" notequal 'codelist', 'enumeration' or 'codelistelement' then "obligation", "maximumoccurence" and "domainvalue" are mandatory if "obligation" = 'conditional' then "condition" is mandatory Figure A.13 Metadata extension information ISO 2003 All rights reserved 31

42 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A.2.12 Application schema information Figure A.14 defines the application schema used. The data dictionary for this diagram is located in B MD_Metadata (from Metadata entity set information) +applicationschemainfo 0..* MD_ApplicationSchemaInformation + name : CI_Citation + schemalanguage : CharacterString + constraintlanguage : CharacterString + schemaascii [0..1] : CharacterString + graphicsfile [0..1] : Binary + softwaredevelopmentfile [0..1] : Binary + softwaredevelopmentfileformat [0..1] : CharacterString Figure A.14 Application schema information 32 ISO 2003 All rights reserved

43 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) A.3 Metadata data types A.3.1 Extent information Figure A.15 defines metadata describing the spatial and temporal extent covered by a resource. The data dictionary for this diagram is located in B geographicelement 0..* <<Abstract>> EX_GeographicExtent + extenttypecode [0..1] : Boolean = "1" EX_BoundingPolygon + polygon [1..*] : GM_Object +spatialextent 1..* EX_GeographicBoundingBox + westboundlongitude : Angle + eastboundlongitude : Angle + southboundlatitude : Angle + northboundlatitude : Angle <<DataType>> EX_Extent + description [0..1] : CharacterString +temporalelement 0..* EX_TemporalExtent + extent : TM_Primitive EX_SpatialTemporalExtent EX_GeographicDescription + geographicidentifier : MD_Identifier count(description + geographicelement + temporalelement + verticalelement) > 0 +verticalelement 0..* EX_VerticalExtent + minimumvalue : Real + maximumvalue : Real + unitofmeasure : UomLength +verticaldatum 1 SC_VerticalDatum (from Spatial Referencing by Coordinates) Figure A.15 Extent information ISO 2003 All rights reserved 33

44 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL A.3.2 Citation and responsible party information Figure A.16 defines metadata describing authoritative reference information, including responsible party and contact information. The data dictionary for this diagram is located in B.3.2. <<DataType>> CI_Citation + title : CharacterString + alternatetitle [0..*] : CharacterString + date [1..*] : CI_Date + edition [0..1] : CharacterString + editiondate [0..1] : Date + identifier [0..*] : MD_Identifier + citedresponsibleparty [0..*] : CI_ResponsibleParty + presentationform [0..*] : CI_PresentationFormCode + series [0..1] : CI_Series + othercitationdetails [0..1] : CharacterString + collectivetitle [0..1] : CharacterString + ISBN [0..1] : CharacterString + ISSN [0..1] : CharacterString <<DataType>> CI_Series + name [0..1] : CharacterString + issueidentification [0..1] : CharacterString + page [0..1] : CharacterString <<DataType>> CI_Date + date : Date + datetype : CI_DateTypeCode <<CodeList>> CI_DateTypeCode + creation + publication + revision URL <<CodeList>> CI_PresentationFormCode + documentdigital + documenthardcopy + imagedigital + imagehardcopy + mapdigial + maphardcopy + modeldigital + modelhardcopy + profiledigital + profilehardcopy + tabledigital + tablehardcopy + videodigital + videohardcopy <<DataType>> CI_ResponsibleParty + individualname [0..1] : CharacterString + organisationname [0..1] : CharacterString + positionname [0..1] : CharacterString + contactinfo [0..1] : CI_Contact + role : CI_RoleCode <<DataType>> CI_Contact + phone [0..1] : CI_Telephone + address [0..1] : Address + onlineresource [0..1] : CI_OnlineResource + hoursofservice [0..1] : CharacterString + contactinstructions [0..1] : CharacterString <<DataType>> CI_OnlineResource + linkage : URL + protocol [0..1] : CharacterString + applicationprofile [0..1] : CharacterString + name [0..1] : CharacterString + description [0..1] : CharacterString + function [0..1] : CI_OnLineFunctionCode <<DataType>> CI_Address + deliverypoint [0..*] : CharacterString + city [0..1] : CharacterString + adminitrativearea [0..1] : CharacterString + postalcode [0..1] : CharacterString + country [0..1] : CharacterString + electronicmailaddress [0..*] : CharacterString count of (individualname + organisationname + positionname) > 0 <<DataType>> CI_Telephone + voice [0..*] : CharacterString + facsimile [0..*] : CharacterString <<CodeList>> CI_RoleCode + resourceprovider + custodian + owner + user + distributor + originator + pointofcontact + principalinvestigator + processor + publisher + author <<CodeList>> CI_OnLineFunctionCode + download + information + offlineaccess + order + search Figure A.16 Citation and responsible party information 34 ISO 2003 All rights reserved

45 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Annex B (normative) Data dictionary for geographic metadata B.1 Data dictionary overview B.1.1 Introduction This data dictionary describes the characteristics of the metadata defined in Clause 6 and Annex A. The dictionary is specified in a hierarchy to establish relationships and an organization for the information. The dictionary is categorised into sections by UML model package diagram: Metadata Entity Set, Identification, Resource Constraints, Data Quality, Maintenance, Spatial Representation, Reference System, Content, Portrayal Catalogue, Distribution, Metadata Extension, Application Schema, Extent, Citation and Responsible Party and Metadata Application. The clause titles of several of the tables have been expanded to reflect class specification within the respective diagram. Each model diagram from Annex A has a section within the data dictionary. Each UML model class equates to a data dictionary entity. Each UML model class attribute equates to a data dictionary element. The shaded rows define entities. The entities and elements within the data dictionary are defined by seven attributes (those attributes are listed below and are based on those specified in ISO/IEC for the description of data element concepts, i.e. data elements without representation). The term dataset when used as part of a definition is synonymous with all types of geographic data resources (aggregations of datasets, individual features and the various classes that compose a feature). B.1.2 Name/role name A label assigned to a metadata entity or to a metadata element. Metadata entity names start with an upper case letter. Spaces do not appear in a metadata entity name. Instead, multiple words are concatenated, with each new subword starting with a capital letter (example: XnnnYmmm). Metadata entity names are unique within the entire data dictionary of this International Standard. Metadata element names are unique within a metadata entity, not the entire data dictionary of this International Standard. Metadata element names are made unique, within an application, by the combination of the metadata entity and metadata element names (example: MD_Metadata.characterSet). Role names are used to identify metadata abstract model associations and are preceded by Role name: to distinguish them from other metadata elements. Names and role names may be in a language other than that used in this International Standard. B.1.3 Short name and domain code Those classes that are not CodeList or Enumeration stereotypes are provided with a Short Name for each element. These short names are unique within this International Standard and may be used with the Extensible MarkUp Language (XML) and ISO 8879 (SGML) or other similar implementation techniques. A naming convention similar to that used to create the longer entity and element names was used to create the short names. NOTE Implementation using SGML and XML is not mandatory; other implementation methods may be accommodated. For CodeList and Enumeration stereotypes, a code is provided for each possible selection. These domain codes are numerical, unique within the codelist and 3 digits long. Row one of each CodeList and Enumeration contains an alphabetic short name, described above, as row one is the name of the CodeList or Enumeration. B.1.4 Definition The metadata entity/element description. ISO 2003 All rights reserved 35

46 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B.1.5 Obligation/Condition B General This is a descriptor indicating whether a metadata entity or metadata element shall always be documented in the metadata or sometimes be documented (i.e. contains value(s)). This descriptor may have the following values: M (mandatory), C (conditional), or O (optional). B Mandatory (M): The metadata entity or metadata element shall be documented. B Conditional (C): Specifies an electronically manageable condition under which at least one metadata entity or a metadata element is mandatory. Conditional is used for one of the three following possibilities: Expressing a choice between two or more options. At least one option is mandatory and must be documented. Documenting a metadata entity or a metadata element if another element has been documented. Documenting a metadata element if a specific value for another metadata element has been documented. To facilitate reading by humans, the specific value is used in plain text (ex. table in Clause B.2, row 3 "C/not defined by encoding? ). However, the code shall be used to verify the condition in an electronical user interface. If the answer to the condition is positive, then the metadata entity or the metadata element shall be mandatory. B Optional (O): The metadata entity or the metadata element may be documented or may not be documented. Optional metadata entities and optional metadata elements have been defined to provide a guide to those looking to fully document their data. ( of this common set of defined elements will help promote interoperability among geographic data users and producers world-wide.) If an optional entity is not used, the elements contained within that entity (including mandatory elements) will also not be used. Optional entities may have mandatory elements; those elements only become mandatory if the optional entity is used. B.1.6 Maximum Specifies the maximum number of instances the metadata entity or the metadata element may have. Single s are shown by 1 ; repeating s are represented by N. Fixed number s other than one are allowed, and will be represented by the corresponding number (i.e. 2, 3 etc). B.1.7 Data type Specifies a set of distinct values for representing the metadata elements; for example, integer, real, string, DateTime, and Boolean. The data type attribute is also used to define metadata entities, stereotypes, and metadata associations. NOTE Data types are defined in ISO/TS 19103, B.1.8 Domain For an entity, the domain indicates the line numbers covered by that entity. 36 ISO 2003 All rights reserved

47 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) For a metadata element, the domain specifies the values allowed or the use of free text. Free text indicates that no restrictions are placed on the content of the field. Integer-based codes shall be used to represent values for domains containing codelists. ISO 2003 All rights reserved 37

48 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B.2 Metadata package data dictionaries B.2.1 Metadata entity set information UML model shown in Figure A.1. Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 1 MD_Metadata Metadata root entity which defines metadata about a resource or resources M 1 Class Lines fileidentifier mdfileid unique identifier for this metadata file O 1 CharacterString Free text 3 language mdlang language used for documenting metadata C / not defined by encoding? 1 CharacterString ISO 639-2, other parts may be used 4 characterset mdchar full name of the character coding standard used for the metadata set C / ISO/IEC not used and not defined by encoding? 1 Class MD_CharacterSetCode <<CodeList>> (B.5.10) 5 parentidentifier mdparentid file identifier of the metadata to which this metadata is a subset (child) C / hierarchylevel is not equal to "dataset"? 1 CharacterString Free text 6 hierarchylevel mdhrlv scope to which the metadata applies (see Annex H for more information about metadata hierarchy levels) C / hierarchylevel is not equal to "dataset"? N Class MD_ScopeCode <<CodeList>> (B.5.25) 7 hierarchylevelname mdhrlvname name of the hierarchy levels for which the metadata is provided C / hierarchylevel is not equal to "dataset"? N CharacterString Free text 8 contact mdcontact party responsible for the metadata information M N Class CI_ResponsibleParty (B.3.2) <<DataType>> 9 datestamp mddatest date that the metadata was created M 1 Class Date (B.4.2) 10 metadatastandardname mdstanname name of the metadata standard (including profile name) used O 1 CharacterString Free text 11 metadatastandardversion mdstanver version (profile) of the metadata standard used O 1 CharacterString Free text 38 ISO 2003 All rights reserved

49 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 11.1 dataseturi dataseturi Uniformed Resource Identifier (URI) of the dataset to which the metadata applies O 1 CharacterString Free text 12 Role name: spatialrepresentationinfo spatrepinfo digital representation of spatial information in the dataset O N Association MD_SpatialRepresentation <<Abstract>> (B.2.6) 13 Role name: referencesysteminfo refsysinfo description of the spatial and temporal reference systems used in the dataset O N Association MD_ReferenceSystem (B.2.7) 14 Role name: metadataextensioninfo mdextinfo information describing metadata extensions O N Association MD_MetadataExtension Information (B.2.11) 15 Role name: identificationinfo dataidinfo basic information about the resource(s) to which the metadata applies M N Association MD_Identification <<Abstract>> (B.2.2) 16 Role name: contentinfo continfo provides information about the feature catalogue and describes the coverage and image data characteristics O N Association MD_ContentInformation <<Abstract>> (B.2.8) 17 Role name: distributioninfo distinfo provides information about the distributor of and options for obtaining the resource(s) O 1 Association MD_Distribution (B.2.10) 18 Role name: dataqualityinfo dqinfo provides overall assessment of quality of a resource(s) O N Association DQ_DataQuality (B.2.4) 19 Role name: portrayalcatalogueinfo porcatinfo provides information about the catalogue of rules defined for the portrayal of a resource(s) O N Association MD_PortrayalCatalogue Reference (B.2.9) 20 Role name: metadataconstraints mdconst provides restrictions on the access and use of metadata O N Association MD_Constraints (B.2.3) 21 Role name: applicationschemainfo appschinfo provides information about the conceptual schema of a dataset O N Association MD_ApplicationSchema Information (B.2.12) 22 Role name: metadatamaintenance mdmaint provides information about the frequency of metadata updates, and the scope of those updates O 1 Association MD_MaintenanceInformation (B.2.5) ISO 2003 All rights reserved 39

50 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B.2.2 Identification information (includes data and service identification) B General UML model shown in Figure A.2 Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 23. MD_Identification Ident basic information required to uniquely identify a resource or resources obligation from referencing maximum from referencing Aggregated Class (MD_Metadata) <<Abstract>> Lines citation idcitation citation data for the resource(s) M 1 Class CI_Citation (B.3.2) <<DataType>> 25. abstract idabs brief narrative summary of the content of the resource(s) M 1 CharacterString Free text 26. purpose idpurp summary of the intentions with which the resource(s) was developed O 1 CharacterString Free text 27. credit idcredit recognition of those who contributed to the resource(s) O N CharacterString Free text 28. status idstatus status of the resource(s) O N Class MD_ProgressCode <<CodeList>> (B.5.23) 29. pointofcontact idpoc identification of, and means of communication with, person(s) and organization(s) associated with the resource(s) O N Class CI_ResponsibleParty (B.3.2) <<DataType>> 30. Role name: resourcemaintenance resmaint provides information about the frequency of resource updates, and the scope of those updates O N Association MD_MaintenanceInformation (B.2.5) 31. Role name: graphicoverview graphover provides a graphic that illustrates the resource(s) (should include a legend for the graphic) O N Association MD_BrowseGraphic (B.2.2.2) 32. Role name: resourceformat dsformat provides a description of the format of the resource(s) O N Association MD_Format (B ) 40 ISO 2003 All rights reserved

51 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 33. Role name: descriptivekeywords desckeys provides category keywords, their type, and reference source O N Association MD_Keywords (B.2.2.3) 34. Role name: resourcespecificusage idspec provides basic information about specific application(s) for which the resource(s) has/have been or is being used by different users O N Association MD_Usage (B.2.2.6) 35. Role name: resourceconstraints resconst provides information about constraints which apply to the resource(s) O N Association MD_Constraints (B.2.3) 35.1 Role name: aggregationinfo aggrinfo provides aggregate dataset information O N Association MD_AggregateInformation (B.2.2.7) 36. MD_DataIdentification DataIdent information required to identify a dataset obligation from referencing maximum from referencing Specified Class (MD_Identification) Lines and spatialrepresentationtype spatrptype method used to spatially represent geographic information O N Class MD_SpatialRepresentation TypeCode <<CodeList>> (B.5.26) 38. spatialresolution datascale factor which provides a general understanding of the density of spatial data in the dataset O N Class MD_Resolution <<Union>> (B.2.2.5) 39. language datalang language(s) used within the dataset M N CharacterString ISO 639-2, other parts may be used 40. characterset datachar full name of the character coding standard used for the dataset C/ISO/IEC not used? N Class MD_CharacterSetCode <<CodeList>> (B.5.10) 41. topiccategory tpcat main theme(s) of the dataset C / if hierarchylevel equals dataset? N Class MD_TopicCategoryCode <<Enumeration>> (B.5.27) 42. intentionally left blank 43. intentionally left blank ISO 2003 All rights reserved 41

52 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 44. environmentdescription envirdesc description of the dataset in the producer s processing environment, including items such as the software, the computer operating system, file name, and the dataset size O 1 CharacterString Free text 45. extent dataext extent information including the bounding box, bounding polygon, vertical, and temporal extent of the dataset C / if hierarchylevel equals dataset? either extent.geographic Element.EX_ GeographicBounding Box or extent.geographic Element.EX_ Geographic Description is required N Class EX_Extent <<DataType>> (B.3.1) 46. supplementalinformation suppinfo any other descriptive information about the dataset O 1 CharacterString Free text 47. MD_ServiceIdentification SerIdent identification of capabilities which a service provider makes available to a service user through a set of interfaces that define a behaviour - See ISO for further information obligation from referencing maximum from referencing Specified Class (MD_Identification) Lines B Browse graphic information Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 48. MD_BrowseGraphic BrowGraph graphic that provides an illustration of the dataset (should include a legend for the graphic) obligation from referencing maximum from referencing Aggregated Class (MD_Identification) Lines ISO 2003 All rights reserved

53 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 49. filename bgfilename name of the file that contains a graphic that provides an illustration of the dataset M 1 CharacterString Free text 50. filedescription bgfiledesc text description of the illustration O 1 CharacterString Free text 51. filetype bgfiletype format in which the illustration is encoded Examples: CGM, EPS, GIF, JPEG, PBM, PS, TIFF, XWD O 1 CharacterString Free text B Keyword information Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 52. MD_Keywords Keywords keywords, their type and reference source obligation from referencing maximum from referencing Aggregated Class (MD_Identification) Lines keyword keyword commonly used word(s) or formalised word(s) or phrase(s) used to describe the subject M N CharacterString Free text 54. Type keytyp subject matter used to group similar keywords O 1 Class MD_KeywordTypeCode <<CodeList>> (B.5.17) 55. ThesaurusName thesaname name of the formally registered thesaurus or a similar authoritative source of keywords O 1 Class CI_Citation (B.3.2) <<DataType>> ISO 2003 All rights reserved 43

54 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B Representative fraction information Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 56. MD_RepresentativeFraction RepFract derived from ISO Scale where MD_Representative Fraction.denominator = 1 / Scale. measure And Scale.targetUnits = Scale.sourceUnits obligation from referencing maximum from referencing Class <<DataType>> Line denominator rfdenom the number below the line in a vulgar fraction M 1 Integer Integer > intentionally left blank B Resolution information Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 59. MD_Resolution Resol level of detail expressed as a scale factor or a ground distance obligation from referencing maximum from referencing Class <<Union>> Lines equivalentscale equscale level of detail expressed as the scale of a comparable hardcopy map or chart C / distance not documented? 1 Class MD_RepresentativeFraction <<DataType>> (B.2.2.4) 61. distance scaledist ground sample distance C / equivalentscale not documented? 1 Class Distance (B.4.3) 44 ISO 2003 All rights reserved

55 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B Usage information Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 62. MD_Usage Usage brief description of ways in which the resource(s) is/are currently or has been used obligation from referencing maximum from referencing Aggregated Class (MD_Identification) Lines specificusage specusage brief description of the resource and/or resource series usage M 1 CharacterString Free text 64. usagedatetime usagedate date and time of the first use or range of uses of the resource and/or resource series O 1 Class DateTime (B.4.2) 65. userdeterminedlimitations usrdetlim applications, determined by the user for which the resource and/or resource series is not suitable O 1 CharacterString Free text 66. usercontactinfo usrcntinfo identification of and means of communicating with person(s) and organization(s) using the resource(s) M N Class CI_ResponsibleParty <<DataType>> (B.3.2) B Aggregation information Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 66.1 MD_AggregateInformation AggregateInfo aggregate dataset information obligation from referencing maximum from referencing Aggregated Class (MD_Identification) Lines aggregatedatasetname aggrdsname citation information about the aggregate dataset C / if aggregatedataset Identifier not documented? 1 Class CI_Citation (B.3.2) <<DataType>> ISO 2003 All rights reserved 45

56 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 66.3 aggregatedatasetidentifier aggrdsident identification information about aggregate dataset C / if aggregatedataset Name not documented? 1 Class MD_Identifier (B.2.7.3) <<DataType>> 66.4 associationtype assoctype association type of the aggregate dataset M 1 Class DS_AssociationTypeCode (B.5.7) <<CodeList>> 66.5 initiativetype inittype type of initiative under which the aggregate dataset was produced O 1 Class DS_InitiativeTypeCode (B.5.8) <<CodeList>> B.2.3 Constraint information (includes legal and security) UML model shown in Figure A.3 Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 67. MD_Constraints Consts restrictions on the access and use of a resource or metadata obligation from referencing maximum from referencing Aggregated Class (MD_Metadata and MD_Identification) Line uselimitation uselimit limitation affecting the fitness for use of the resource or metadata. Example, not to be used for navigation O N CharacterString Free text 69. MD_LegalConstraints LegConsts restrictions and legal prerequisites for accessing and using the resource or metadata obligation from referencing N Specified Class (MD_Constraints) Lines and accessconstraints accessconsts access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource or metadata O N Class MD_RestrictionCode <<CodeList>> (B.5.24) 46 ISO 2003 All rights reserved

57 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 71. useconstraints useconsts constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations or warnings on using the resource or metadata O N Class MD_RestrictionCode <<CodeList>> (B.5.24) 72. otherconstraints othconsts other restrictions and legal prerequisites for accessing and using the resource or metadata C / accessconstraints or useconstraints equal otherrestrictions? N CharacterString Free text 73. MD_SecurityConstraints SecConsts handling restrictions imposed on the resource or metadata for national security or similar security concerns obligation from referencing maximum from referencing Specified Class (MD_Constraints) Lines and classification class name of the handling restrictions on the resource or metadata M 1 Class MD_ClassificationCode <<CodeList>> (B.5.11) 75. usernote usernote explanation of the application of the legal constraints or other restrictions and legal prerequisites for obtaining and using the resource or metadata O 1 CharacterString Free text 76. classificationsystem classsys name of the classification system O 1 CharacterString Free text 77. handlingdescription handdesc additional information about the restrictions on handling the resource or metadata O 1 CharacterString Free text ISO 2003 All rights reserved 47

58 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B.2.4 Data quality information B General UML model shown in Figures A.4, A.5 (Lineage) and A.6 (Data quality classes and subclasses) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 78. DQ_DataQuality DataQual quality information for the data specified by a data quality scope obligation from referencing maximum from referencing Aggregated Class (MD_Metadata) Lines scope dqscope the specific data to which the data quality information applies M 1 Class DQ_Scope <<DataType>> (B.2.4.5) 80. Role name: report dqreport quantitative quality information for the data specified by the scope C / lineage not provided? N Association DQ_Element <<Abstract>> (B.2.4.3) 81. Role name: lineage datalineage non-quantitative quality information about the lineage of the data specified by the scope C / report not provided? 1 Association LI_Lineage (B.2.4.2) B Lineage information B General Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 82. LI_Lineage Lineage information about the events or source data used in constructing the data specified by the scope or lack of knowledge about lineage obligation from referencing maximum from referencing Aggregated Class (DQ_DataQuality) Lines ISO 2003 All rights reserved

59 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 83. statement statement general explanation of the data producer s knowledge about the lineage of a dataset C / (DQ_DataQuality.sco pe.dq_scope.level = dataset or series )? 1 CharacterString Free text 84. Role name: processstep prcstep information about events in the life of a dataset specified by the scope C / mandatory if statement and source not provided? N Association LI_ProcessStep (B ) 85. Role name: source datasource information about the source data used in creating the data specified by the scope C / mandatory if statement and processstep not provided? N Association LI_Source (B ) B Process step information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 86. LI_ProcessStep PrcessStep information about an event or transformation in the life of a dataset including the process used to maintain the dataset obligation from referencing maximum from referencing Aggregated Class (LI_Lineage and LI_Source) Lines description stepdesc description of the event, including related parameters or tolerances M 1 CharacterString Free Text 88. rationale steprat requirement or purpose for the process step O 1 CharacterString Free Text 89. datetime stepdatetm date and time or range of date and time on or over which the process step occurred O 1 Class DateTime (B.4.2) 90. processor stepproc identification of, and means of communication with, person(s) and organization(s) associated with the process step O N Class CI_ResponsibleParty <<DataType>> (B.3.2) ISO 2003 All rights reserved 49

60 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL 91. Role name: source stepsrc information about the source data used in creating the data specified by the scope O N Association LI_Source (B ) B Source information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 92. LI_Source Source information about the source data used in creating the data specified by the scope obligation from referencing maximum from referencing Aggregated Class (LI_Lineage and LI_ProcessStep) Lines description srcdesc detailed description of the level of the source data C / sourceextent not provided? 1 CharacterString Free Text 94. scaledenominator srcscale denominator of the representative fraction on a source map O 1 Class MD_RepresentativeFraction <<DataType>> (B.2.2.4) 95. sourcereferencesystem srcrefsys spatial reference system used by the source data O 1 Class MD_ReferenceSystem (B.2.7) 96. sourcecitation srccitatn recommended reference to be used for the source data O 1 Class CI_Citation <<DataType>> (B.3.2) 97. sourceextent srcext information about the spatial, vertical and temporal extent of the source data C / description not provided? N Class EX_Extent <<DataType>> (B.3.1) 98. Role name: sourcestep srcstep information about an event in the creation process for the source data O N Association LI_ProcessStep (B ) 50 ISO 2003 All rights reserved

61 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B Data quality element information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 99. DQ_Element DQElement aspect of quantitative quality information obligation from referencing maximum from referencing Aggregated Class (DQ_DataQuality) <<Abstract>> Lines nameofmeasure measname name of the test applied to the data O N CharacterString Free text 101. measureidentification measid code identifying a registered standard procedure O 1 Class MD_Identifier <<DataType>> (B.2.7.3) 102. measuredescription measdesc description of the measure O 1 CharacterString Free text 103. evaluationmethodtype evalmethtype type of method used to evaluate quality of the dataset O 1 Class DQ_EvaluationMethodType Code <<CodeList>> (B.5.6) 104. evaluationmethoddescription evalmethdesc description of the evaluation method O 1 CharacterString Free text 105. evaluationprocedure evalproc reference to the procedure information O 1 Class CI_Citation <<DataType>> (B.3.2) 106. datetime measdatetm date or range of dates on which a data quality measure was applied O N Class DateTime (B.4.2) 107. result measresult value (or set of values) obtained from applying a data quality measure or the outcome of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level M 2 Class DQ_Result <<Abstract>> (B.2.4.4) 108. DQ_Completeness DQComplete presence and absence of features, their attributes and their relationships obligation from referencing maximum from referencing Specified Class (DQ_Element) <<Abstract>> Lines ISO 2003 All rights reserved 51

62 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition 109. DQ_Completeness Commission DQCompComm excess data present in the dataset, as described by the scope obligation from referencing 110. DQ_CompletenessOmission DQCompOm data absent from the dataset, as described by the scope obligation from referencing 111. DQ_LogicalConsistency DQLogConsis degree of adherence to logical rules of data structure, attribution and relationships (data structure can be conceptual, logical or physical) obligation from referencing 112. DQ_ConceptualConsistency DQConcConsis adherence to rules of the conceptual schema obligation from referencing 113. DQ_DomainConsistency DQDomConsis adherence of values to the value domains obligation from referencing 114. DQ_FormatConsistency DQFormConsis degree to which data is stored in accordance with the physical structure of the dataset, as described by the scope obligation from referencing Maximum maximum from referencing maximum from referencing maximum from referencing maximum from referencing maximum from referencing maximum from referencing Data type Domain Specified Class (DQ_Completeness) Lines Specified Class (DQ_Completeness) Lines Specified Class (DQ_Element) <<Abstract>> Lines Specified Class (DQ_Logical Consistency) Lines Specified Class (DQ_Logical Consistency) Lines Specified Class (DQ_Logical Consistency) Lines ISO 2003 All rights reserved

63 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition 115. DQ_TopologicalConsistency DQTopConsis correctness of the explicitly encoded topological characteristics of the dataset as described by the scope obligation from referencing 116. DQ_PositionalAccuracy DQPosAcc accuracy of the position of features obligation from referencing 117. DQ_AbsoluteExternal PositionalAccuracy DQAbsExtPosAc c closeness of reported coordinate values to values accepted as or being true obligation from referencing 118. DQ_GriddedDataPositional Accuracy DQGridDataPos Acc closeness of gridded data position values to values accepted as or being true obligation from referencing 119. DQ_RelativeInternalPositional Accuracy DQRelIntPosAcc closeness of the relative positions of features in the scope to their respective relative positions accepted as or being true obligation from referencing 120. DQ_TemporalAccuracy DQTempAcc accuracy of the temporal attributes and temporal relationships of features obligation from referencing Maximum maximum from referencing maximum from referencing maximum from referencing maximum from referencing maximum from referencing maximum from referencing Data type Domain Specified Class (DQ_Logical Consistency) Lines Specified Class (DQ_Element) <<Abstract>> Lines Specified Class (DQ_Positional Accuracy) Lines Specified Class (DQ_Positional Accuracy) Lines Specified Class (DQ_Positional Accuracy) Lines Specified Class (DQ_Element) <<Abstract>> Lines ISO 2003 All rights reserved 53

64 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition 121. DQ_AccuracyOfATime Measurement DQAccTime Meas correctness of the temporal references of an item (reporting of error in time measurement) obligation from referencing 122. DQ_TemporalConsistency DQTempConsis correctness of ordered events or sequences, if reported obligation from referencing 123. DQ_TemporalValidity DQTempValid validity of data specified by the scope with respect to time obligation from referencing 124. DQ_ThematicAccuracy DQThemAcc accuracy of quantitative attributes and the correctness of nonquantitative attributes and of the classifications of features and their relationships obligation from referencing 125. DQ_ThematicClassification Correctness DQThemClass Cor comparison of the classes assigned to features or their attributes to a universe of discourse obligation from referencing 126. DQ_NonQuantitativeAttribute Accuracy DQNonQuanAtt Acc accuracy of non-quantitative attributes obligation from referencing Maximum maximum from referencing maximum from referencing maximum from referencing maximum from referencing maximum from referencing maximum from referencing Data type Domain Specified Class (DQ_Temporal Accuracy) Lines Specified Class (DQ_Temporal Accuracy) Lines Specified Class (DQ_Temporal Accuracy) Lines Specified Class (DQ_Element) <<Abstract>> Lines Specified Class (DQ_Thematic Accuracy) Lines Specified Class (DQ_Thematic Accuracy) Lines ISO 2003 All rights reserved

65 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 127. DQ_QuantitativeAttribute Accuracy DQQuanAttAcc accuracy of quantitative attributes obligation from referencing maximum from referencing Specified Class (DQ_Thematic Accuracy) Lines B Result information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 128. DQ_Result Result generalization of more specific result classes obligation from referencing maximum from referencing Class <<Abstract>> 129. DQ_ConformanceResult ConResult Information about the outcome of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level obligation from referencing maximum from referencing Specified Class (DQ_Result) Lines specification conspec citation of product specification or user requirement against which data is being evaluated M 1 Class CI_Citation <<DataType>> (B.3.2) 131. explanation conexpl explanation of the meaning of conformance for this result M 1 CharacterString Free text 132. pass conpass indication of the conformance result where 0 = fail and 1 = pass M 1 Boolean 1 = yes 0 = no 133. DQ_QuantitativeResult QuanResult the values or information about the value(s) (or set of values) obtained from applying a data quality measure obligation from referencing maximum from referencing Specified Class (DQ_Result) Lines ISO 2003 All rights reserved 55

66 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 134. valuetype quanvaltype value type for reporting a data quality result O 1 Class RecordType <<Metaclass>> (B.4.3) 135. valueunit quanvalunit value unit for reporting a data quality result M 1 Class UnitOfMeasure (B.4.3) 136. errorstatistic errstat statistical method used to determine the value O 1 CharacterString Free text 137. value quanval quantitative value or values, content determined by the evaluation procedure used M N Class Record (B.4.3) B Scope information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 138. DQ_Scope DQScope extent of characteristic(s) of the data for which quality information is reported obligation from referencing maximum from referencing Class <<DataType>> Lines level scplvl hierarchical level of the data specified by the scope M 1 Class MD_ScopeCode <<CodeList>> (B.5.25) 140. extent scpext information about the horizontal, vertical and temporal extent of the data specified by the scope O 1 Class EX_Extent <<DataType>> (B.3.1) 141. leveldescription scplvldesc detailed description about the level of the data specified by the scope C / level not equal dataset or series? N Class MD_ScopeDescription <<Union>> (B.2.5.2) 56 ISO 2003 All rights reserved

67 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.2.5 Maintenance information B General UML model shown in Figure A.7 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 142. MD_MaintenanceInformation MaintInfo information about the scope and frequency of updating obligation from referencing maximum from referencing Aggregated Class (MD_Metadata and MD_Identification) Lines maintenanceandupdate Frequency maintfreq frequency with which changes and additions are made to the resource after the initial resource is completed M 1 Class MD_MaintenanceFrequency Code <<CodeList>> (B.5.18) 144. dateofnextupdate datenext scheduled revision date for resource O 1 Class Date (B.4.2) 145. userdefinedmaintenance Frequency usrdeffreq maintenance period other than those defined O 1 Class TM_PeriodDuration (B.4.5) 146. updatescope maintscp scope of data to which maintenance is applied O N Class MD_ScopeCode <<CodeList>> (B.5.25) 147. updatescopedescription upscpdesc additional information about the range or extent of the resource O N Class MD_ScopeDescription <<Union>> (B.2.5.2) 148. maintenancenote maintnote information regarding specific requirements for maintaining the resource O N CharacterString Free text contact maintcont identification of, and means of communicating with, person(s) and organization(s) with responsibility for maintaining the metadata O N Class CI_ResponsibleParty <<DataType>> (B.3.2) ISO 2003 All rights reserved 57

68 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B Scope description information Name / Role Name Short Name Definition Obligation / Condition 149. MD_ScopeDescription ScpDesc description of the class of information covered by the information obligation from referencing 150. attributes attribset attributes to which the information applies C / features, featureinstances, attributeinstances, dataset and other not documented? 151. features featset features to which the information applies C / attributes, featureinstances, attributeinstances, dataset and other not documented? 152. featureinstances featintset feature instances to which the information applies C / attributes, features, attributeinstances, dataset and other not documented? 153. attributeinstances attribintset attribute instances to which the information applies C / attributes, features, featureinstances, dataset and other not documented? 154. dataset datasetset dataset to which the information applies C / attributes, features, featureinstances, attributeinstances, and other not documented? Maximum Data type Domain maximum from referencing Class <<Union>> Lines Set (B.4.7) GF_AttributeType (B.4.4) 1 Set (B.4.7) GF_FeatureType (B.4.4) 1 Set (B.4.7) GF_FeatureType (B.4.4) 1 Set (B.4.7) GF_AttributeType (B.4.4) 1 CharacterString Free text 58 ISO 2003 All rights reserved

69 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 155. other other class of information that does not fall into the other categories to which the information applies C / attributes, features, featureinstances, attributeinstances, and dataset not documented? 1 CharacterString Free text B.2.6 Spatial representation information (includes grid and vector representation) B General UML model shown in Figure A.8 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 156. MD_SpatialRepresentation SpatRep digital mechanism used to represent spatial information obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata) <<Abstract>> 157. MD_GridSpatial Representation GridSpatRep information about grid spatial s in the dataset obligation/condition from referencing maximum from referencing Specified Class (MD_Spatial Representation) Lines numberofdimensions numdims number of independent spatialtemporal axes M 1 Integer Integer 159. axisdimensionsproperties axdimprops information about spatial-temporal axis properties M 1 Sequence (B.4.7) MD_Dimension <<DataType>> (B.2.6.2) 160. cellgeometry cellgeo identification of grid data as point or cell M 1 Class MD_CellGeometryCode <<CodeList>> (B.5.9) ISO 2003 All rights reserved 59

70 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 161. transformationparameter Availability tranparaav indication of whether or not parameters for transformation between image coordinates and geographic or map coordinates exist (are available) M 1 Boolean 1 = yes 0 = no 162. MD_Georectified Georect grid whose cells are regularly spaced in a geographic (i.e., lat / long) or map coordinate system defined in the Spatial Referencing System (SRS) so that any cell in the grid can be geolocated given its grid coordinate and the grid origin, cell spacing, and orientation obligation/condition from referencing maximum from referencing Specified (MD_GridSpatial Representation) Lines and checkpointavailability chkptav indication of whether or not geographic position points are available to test the accuracy of the georeferenced grid data M 1 Boolean 1 = yes 0 = no 164. checkpointdescription chkptdesc description of geographic position points used to test the accuracy of the georeferenced grid data C / checkpointavailability equals yes? 1 CharacterString Free text 165. cornerpoints cornerpts earth location in the coordinate system defined by the Spatial Reference System and the grid coordinate of the cells at opposite ends of grid coverage along two diagonals in the grid spatial dimensions. There are four corner points in a georectified grid; at least two corner points along one diagonal are required M 1 Sequence (B.4.7) GM_Point <<Type>> (B.4.6) 166. centerpoint centerpt earth location in the coordinate system defined by the Spatial Reference System and the grid coordinate of the cell halfway between opposite ends of the grid in the spatial dimensions O 1 Class GM_Point <<Type>> (B.4.6) 167. pointinpixel ptinpixel point in a pixel corresponding to the Earth location of the pixel M 1 Class MD_PixelOrientationCode <<Enumeration>> (B.5.22) 60 ISO 2003 All rights reserved

71 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 168. transformationdimension Description transdimdesc general description of the transformation O 1 CharacterString Free text 169. transformationdimension Mapping transdimmap information about which grid axes are the spatial (map) axes O 2 CharacterString Free text 170. MD_Georeferenceable Georef grid with cells irregularly spaced in any given geographic/map projection coordinate system, whose individual cells can be geolocated using geolocation information supplied with the data but cannot be geolocated from the grid properties alone obligation/condition from referencing maximum from referencing Specified Class (MD_GridSpatial Representation) Lines and controlpointavailability ctrlptav indication of whether or not control point(s) exists M 1 Boolean 1 = yes 0 = no 172. orientationparameter Availability orieparaav indication of whether or not orientation parameters are available M 1 Boolean 1 = yes 0 = no 173. orientationparameter Description orieparads description of parameters used to describe sensor orientation O 1 CharacterString Free text 174. georeferencedparameters georefpars terms which support grid data georeferencing M 1 Class Record (B.4.3) 175. parametercitation paracit reference providing description of the parameters O N Class CI_Citation <<DataType>> (B.3.2) 176. MD_VectorSpatial Representation VectSpatRep information about the vector spatial s in the dataset obligation/condition from referencing maximum from referencing Specified Class (MD_Spatial Representation) Lines topologylevel toplvl code which identifies the degree of complexity of the spatial relationships O 1 Class MD_TopologyLevelCode <<CodeList>> (B.5.28) 178. geometricobjects geometobjs information about the geometric s used in the dataset O N Class MD_GeometricObjects <<DataType>> (B.2.6.3) ISO 2003 All rights reserved 61

72 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B Dimension information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 179. MD_Dimension Dimen axis properties obligation/condition from referencing maximum from referencing Class <<DataType>> Lines dimensionname dimname name of the axis M 1 Class MD_DimensionNameType Code <<CodeList>> (B.5.14) 181. dimensionsize dimsize number of elements along the axis M 1 Integer Integer 182. resolution dimresol degree of detail in the grid dataset O 1 Class Measure (B.4.3) B Geometric information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 183. MD_GeometricObjects GeometObjs number of s, listed by geometric type, used in the dataset obligation/condition from referencing maximum from referencing Class <<DataType>> Lines geometricobjecttype geoobjtyp name of point or vector s used to locate zero-, one-, two-, or three-dimensional spatial locations in the dataset M 1 Class MD_GeometricObjectType Code <<CodeList>> (B.5.15) 185. geometricobjectcount geoobjcnt total number of the point or vector type occurring in the dataset O 1 Integer > 0 62 ISO 2003 All rights reserved

73 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.2.7 Reference system information (includes temporal, coordinate and geographic identifiers) B General UML model shown in Figure A.9 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 186. MD_ReferenceSystem RefSystem information about the reference system obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata) Line referencesystemidentifier refsysid name of reference system C / MD_CRS.projection, MD_CRS.ellipsoid, and MD_CRS.datum not documented? 1 Class RS_Identifier (B.2.7.3) 188. intentionally left blank 189. MD_CRS MdCoRefSys metadata about a coordinate system in which attributes have been derived from SC_CRS as defined in ISO Spatial referencing by coordinates obligation/condition from referencing maximum from referencing Specified Class (MD_Reference System) Lines and projection projection identity of the projection used O 1 Class RS_Identifier (B.2.7.3) 191. ellipsoid ellipsoid identity of the ellipsoid used O 1 Class RS_Identifier (B.2.7.3) 192. datum datum identity of the datum used O 1 Class RS_Identifier (B.2.7.3) 193. role name: ellipsoidparameters ellparas set of parameters that describe the ellipsoid O 1 Association MD_EllipsoidParameters (B.2.7.2) 194. role name: projectionparameters projparas set of parameters that describe the projection O 1 Association MD_ProjectionParameters (B.2.7.6) ISO 2003 All rights reserved 63

74 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 195. RS_ReferenceSystem RefSys description of the spatial and temporal reference systems used in the dataset obligation/condition from referencing maximum from referencing Class <<Abstract>> Lines name refsysname name of reference system used M 1 Class RS_Identifier (B.2.7.3) 197. domainofvalidity domovalid range which is valid for the reference system O N Class EX_Extent <<DataType>> (B.3.1) 198. intentionally left blank 199. intentionally left blank 200. intentionally left blank B Ellipsoid parameter information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 201. MD_EllipsoidParameters EllParas set of parameters that describe the ellipsoid obligation/condition from referencing maximum from referencing Aggregated Class (MD_CRS) Lines semimajoraxis semimajax radius of the equatorial axis of the ellipsoid M 1 Real > 0, axisunits axisunits units of the semi-major axis M 1 Class UomLength (B.4.3) 204. denominatorofflatteningratio denflatrat ratio of the difference between the equatorial and polar radii of the ellipsoid to the equatorial radius when the numerator is set to 1 C / not a spheroid? 1 Real > 0,0 64 ISO 2003 All rights reserved

75 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B Identifier information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 205. MD_Identifier MdIdent value uniquely identifying an within a namespace obligation/condition from referencing maximum from referencing Class Lines authority identauth person or party responsible for maintenance of the namespace O 1 Class CI_Citation <<DataType>> (B.3.2) 207. code identcode alphanumeric value identifying an instance in the namespace M 1 CharacterString Free text 208. RS_Identifier RsIdent identifier used for reference systems obligation/condition from referencing maximum from referencing Specified Class (MD_Identifier) Lines and codespace identcodespace name or identifier of the person or organization responsible for namespace O 1 CharacterString Free text version identvrsn version identifier for the namespace O 1 CharacterString Free text B Oblique line azimuth information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 209. MD_ObliqueLineAzimuth ObLineAzi method used to describe the line along which an oblique mercator map projection is centred using the map projection origin and an azimuth obligation/condition from referencing maximum from referencing Aggregated Class (MD_Projection Parameters) Lines ISO 2003 All rights reserved 65

76 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 210. azimuthangle aziangle angle measured clockwise from north, and expressed in degrees M 1 Real Real 211. azimuthmeasurepoint Longitude aziptlong longitude of the map projection origin M 1 Real Real B Oblique line point information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 212. MD_ObliqueLinePoint ObLinePt method used to describe the line along which an oblique mercator map projection is centred using two points near the limits of the mapped region that define the centre line obligation/condition from referencing maximum from referencing Aggregated Class (MD_Projection Parameters) Lines obliquelinelatitude oblinelat latitude of a point defining the oblique line M 1 Real Real 214. obliquelinelongitude oblinelong longitude of a point defining the oblique line M 1 Real Real B Projection parameter information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 215. MD_ProjectionParameters ProjParas set of parameters that describe the projection obligation/condition from referencing maximum from referencing Aggregated Class (MD_CRS) Lines zone zone unique identifier for 100,000 metre grid zone O 1 Integer Integer 66 ISO 2003 All rights reserved

77 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 217. standardparallel stanparal line of constant latitude at which the surface of the Earth and the plane or developable surface intersect O 2 Real Real 218. longitudeofcentralmeridian longcntmer line of longitude at the centre of a map projection generally used as the basis for constructing the projection O 1 Real Real 219. latitudeofprojectionorigin latprojori latitude chosen as the origin of rectangular coordinates for a map projection O 1 Real Real 220. falseeasting faleastng value added to all x values in the rectangular coordinates for a map projection. This value frequently is assigned to eliminate negative numbers. Expressed in the unit of measure identified in Planar Coordinate Units O 1 Real Real 221. falsenorthing falnorthng value added to all y values in the rectangular coordinates for a map projection. This value frequently is assigned to eliminate negative numbers. Expressed in the unit of measure identified in Planar Coordinate Units O 1 Real Real 222. falseeastingnorthingunits falenunits units of false northing and false easting O 1 Class UomLength (B.4.3) 223. scalefactoratequator sclfacequ ratio between physical distance and corresponding map distance, along the equator O 1 Real > 0, heightofprospectivepoint AboveSurface hgtprospt height of viewpoint above the Earth, expressed in metres O 1 Real >0, longitudeofprojectioncenter longprojcnt longitude of the point of projection for azimuthal projections O 1 Real Real 226. latitudeofprojectioncenter latprojcnt latitude of the point of projection for azimuthal projections O 1 Real Real ISO 2003 All rights reserved 67

78 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 227. scalefactoratcenterline sclfaccnt ratio between physical distance and corresponding map distance, along the centre line O 1 Real Real 228. straightverticallongitudefrom Pole stvrlongpl longitude to be oriented straight up from the North or South Pole O 1 Real Real 229. scalefactoratprojectionorigin sclfacpror multiplier for reducing a distance obtained from a map by computation or scaling to the actual distance at the projection origin O 1 Real Real 230. role name: obliquelineazimuthparameter oblnazipars parameters describing the oblique line azimuth O 1 Association MD_ObliqueLineAzimuth (B.2.7.4) 231. role name: obliquelinepointparameter oblnptpars parameters describing the oblique line point O 2 Association MD_ObliqueLinePoint (B.2.7.5) B.2.8 Content information (includes Feature catalogue and Coverage descriptions) B General UML model shown in Figure A.10 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 232. MD_ContentInformation ContInfo description of the content of a dataset obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata) <<Abstract>> 68 ISO 2003 All rights reserved

79 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 233. MD_FeatureCatalogue Description FetCatDesc information identifying the feature catalogue or the conceptual schema obligation/condition from referencing maximum from referencing Specified Class (MD_Content Information) Lines compliancecode compcode indication of whether or not the cited feature catalogue complies with ISO O 1 Boolean 0-not compliant 1-compliant 235. language catlang language(s) used within the catalogue O N CharacterString ISO 639-2, other parts can be used 236. includedwithdataset incwithds indication of whether or not the feature catalogue is included with the dataset M 1 Boolean 0=no 1=yes 237. featuretypes catfettyps subset of feature types from cited feature catalogue occurring in dataset O N Class GenericName (B.4.8) 238. featurecataloguecitation catcitation complete bibliographic reference to one or more external feature catalogues M N Class CI_Citation <<DataType>> (B.3.2) 239. MD_CoverageDescription CovDesc information about the content of a grid data cell obligation/condition from referencing maximum from referencing Specified Class (MD_Content Information) Lines attributedescription attdesc description of the attribute described by the measurement value M 1 Class RecordType <<Metaclass>> (B.4.3) 241. contenttype contenttyp type of information represented by the cell value M 1 Class MD_CoverageContentType Code <<CodeList>> (B.5.12) 242. Role name: dimension covdim information on the dimensions of the cell measurement value O N Class MD_RangeDimension (B.2.8.2) ISO 2003 All rights reserved 69

80 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 243. MD_ImageDescription ImgDesc information about an image s suitability for use O maximum from referencing Specified Class (MD_Coverage Description) Lines and illuminationelevationangle illelevang illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the Earth s surface. For images from a scanning device, refer to the centre pixel of the image O 1 Real illuminationazimuthangle illaziang illumination azimuth measured in degrees clockwise from true north at the time the image is taken. For images from a scanning device, refer to the centre pixel of the image O 1 Real 0, imagingcondition imagcond conditions affected the image O 1 Class MD_ImagingConditionCode <<CodeList>> (B.5.16) 247. imagequalitycode imagqucode specifies the image quality O 1 Class MD_Identifier <<DataType>> (B.2.7.3) 248. cloudcoverpercentage cloudcovper area of the dataset obscured by clouds, expressed as a percentage of the spatial extent O 1 Real 0,0 100, processinglevelcode prctypcde image distributor s code that identifies the level of radiometric and geometric processing that has been applied O 1 Class MD_Identifier <<DataType>> (B.2.7.3) 250. compressiongeneration Quantity cmpgenquan count of the number of lossy compression cycles performed on the image O 1 Integer Integer 251. triangulationindicator trianind indication of whether or not triangulation has been performed upon the image O 1 Boolean 0-no 1-yes 70 ISO 2003 All rights reserved

81 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 252. radiometriccalibrationdata Availability radcaldatav indication of whether or not the radiometric calibration information for generating the radiometrically calibrated standard data product is available O 1 Boolean 0-no 1-yes 253. cameracalibrationinformation Availability camcalinav indication of whether or not constants are available which allow for camera calibration corrections O 1 Boolean 0-no 1-yes 254. filmdistortioninformation Availability filmdistinav indication of whether or not Calibration Reseau information is available O 1 Boolean 0-no 1-yes 255. lensdistortioninformation Availability lensdistinav indication of whether or not lens aberration correction information is available O 1 Boolean 0-no 1-yes B Range dimension information (includes Band information) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 256. MD_RangeDimension RangeDim information on the range of each dimension of a cell measurement value obligation/condition from referencing maximum from referencing Aggregated Class (MD_Coverage Description) Lines sequenceidentifier seqid number that uniquely identifies instances of bands of wavelengths on which a sensor operates O 1 Class MemberName (B.4.8) 258. descriptor dimdescrp description of the range of a cell measurement value O 1 CharacterString Free text ISO 2003 All rights reserved 71

82 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 259. MD_Band Band range of wavelengths in the electromagnetic spectrum obligation/condition from referencing maximum from referencing Specified Class (MD_RangeDimension) Lines and maxvalue maxval longest wavelength that the sensor is capable of collecting within a designated band O 1 Real Real 261. minvalue minval shortest wavelength that the sensor is capable of collecting within a designated band O 1 Real Real 262. units valunit units in which sensor wavelengths are expressed C / minvalue or maxvalue provided? 1 Class UomLength (B.4.3) 263. peakresponse pkresp wavelength at which the response is the highest O 1 Real Real 264. bitspervalue bitsperval maximum number of significant bits in the uncompressed representation for the value in each band of each pixel O 1 Integer Integer 265. tonegradation tonegrad number of discrete numerical values in the grid data O 1 Integer Integer 266. scalefactor sclfac scale factor which has been applied to the cell value O 1 Real Real 267. offset offset the physical value corresponding to a cell value of zero O 1 Real Real 72 ISO 2003 All rights reserved

83 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.2.9 Portrayal catalogue information UML model shown in Figure A.11 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 268. MD_PortrayalCatalogue Reference PortCatRef information identifying the portrayal catalogue used obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata) Line portrayalcataloguecitation portcatcit bibliographic reference to the portrayal catalogue cited M N Class CI_Citation <<DataType>> (B.3.2) B.2.10 Distribution information B General UML model shown in Figure A.12 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 270. MD_Distribution Distrib information about the distributor of and options for obtaining the resource obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata) Lines Role name: distributionformat distformat provides a description of the format of the data to be distributed C / MD_Distributor. distibutorformat not documented? N Association MD_Format (B ) 272. Role name: distributor distributor provides information about the distributor O N Association MD_Distributor (B ) ISO 2003 All rights reserved 73

84 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 273. Role name: transferoptions disttranops provides information about technical means and media by which a resource is obtained from the distributor O N Association MD_DigitalTransferOptions (B ) B Digital transfer options information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 274. MD_DigitalTransferOptions DigTranOps technical means and media by which a resource is obtained from the distributor obligation/condition from referencing maximum from referencing Aggregated Class (MD_Distribution and MD_Distributor) Lines unitsofdistribution unitsodist tiles, layers, geographic areas, etc., in which data is available O 1 CharacterString Free text 276. transfersize transsize estimated size of a unit in the specified transfer format, expressed in megabytes. The transfer size is > 0.0 O 1 Real > 0, online onlinesrc information about online sources from which the resource can be obtained O N Class CI_OnlineResource <<DataType>> (B.3.2.5) 278. offline offlinemed information about offline media on which the resource can be obtained O 1 Class MD_Medium <<DataType>> (B ) 74 ISO 2003 All rights reserved

85 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B Distributor information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 279. MD_Distributor Distributor information about the distributor obligation/condition from referencing maximum from referencing Aggregated Class (MD_Distribution and MD_Format) Lines distributorcontact distorcont party from whom the resource may be obtained. This list need not be exhaustive M 1 Class CI_ResponsibleParty <<DataType>> (B.3.2) 281. Role name: distributionorderprocess distorordprc provides information about how the resource may be obtained, and related instructions and fee information O N Association MD_StandardOrderProcess (B ) 282. Role name: distributorformat distorformat provides information about the format used by the distributor C / MD_Distribution. distributionformat not documented? N Association MD_Format (B ) 283. Role name: distributortransferoptions distortran provides information about the technical means and media used by the distributor O N Association MD_DigitalTransferOptions (B ) B Format information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 284. MD_Format Format description of the computer language construct that specifies the representation of data s in a record, file, message, storage device or transmission channel obligation/condition from referencing maximum from referencing Aggregated Class (MD_Distribution, MD_Identification, and MD_Distributor) Lines name formatname name of the data transfer format(s) M 1 CharacterString Free text 286. version formatver version of the format (date, number, etc.) M 1 CharacterString Free text ISO 2003 All rights reserved 75

86 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 287. amendmentnumber formatamdnum amendment number of the format version O 1 CharacterString Free text 288. specification formatspec name of a subset, profile, or product specification of the format O 1 CharacterString Free text 289. filedecompressiontechnique filedecmtech recommendations of algorithms or processes that can be applied to read or expand resources to which compression techniques have been applied O 1 CharacterString Free text 290. Role name: formatdistributor formatdist provides information about the distributor s format O N Association MD_Distributor (B ) B Medium information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 291. MD_Medium Medium information about the media on which the resource can be distributed obligation/condition from referencing maximum from referencing Class <<DataType>> Lines name medname name of the medium on which the resource can be received O 1 Class MD_MediumNameCode <<CodeList>> (B.5.20) 293. density meddensity density at which the data is recorded O N Real > 0, densityunits meddenunits units of measure for the recording density C / density documented? 1 CharacterString Free text 295. volumes medvol number of items in the media identified O 1 Integer > 0, mediumformat medformat method used to write to the medium O N Class MD_MediumFormatCode <<CodeList>> (B.5.19) 76 ISO 2003 All rights reserved

87 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 297. mediumnote mednote description of other limitations or requirements for using the medium O 1 CharacterString Free text B Standard order process information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 298. MD_StandardOrderProcess StanOrdProc common ways in which the resource may be obtained or received, and related instructions and fee information obligation/condition from referencing maximum from referencing Aggregated Class (MD_Distributor) Lines fees resfees fees and terms for retrieving the resource. Include monetary units (as specified in ISO 4217) O 1 CharacterString Free text 300. plannedavailabledatetime planavdttm date and time when the resource will be available O 1 Class DateTime (B.4.2) 301. orderinginstructions ordinstr general instructions, terms and services provided by the distributor O 1 CharacterString Free text 302. turnaround ordturn typical turnaround time for the filling of an order O 1 CharacterString Free text ISO 2003 All rights reserved 77

88 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B.2.11 Metadata extension information B General UML model shown in Figure A.13 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 303. MD_MetadataExtension Information MdExtInfo information describing metadata extensions obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata) Lines extensiononlineresource extonres information about on-line sources containing the community profile name and the extended metadata elements. Information for all new metadata elements O 1 Class CI_OnlineResource <<DataType>> (B.3.2.5) 305. Role name: extendedelementinformation exteleinfo provides information about a new metadata element, not found in ISO 19115, which is required to describe geographic data O N Association MD_ExtendedElement Information (B ) B Extended element information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 306. MD_ExtendedElemen tinformation ExtEleInfo new metadata element, not found in ISO 19115, which is required to describe geographic data obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata ExtensionInformation) Lines name extelename name of the extended metadata element M 1 CharacterString Free text 78 ISO 2003 All rights reserved

89 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 308. shortname extshortname short form suitable for use in an implementation method such as XML or SGML. NOTE other methods may be used C / datatype notequal codelistelement? 1 CharacterString Free text 309. domaincode extdomcode three digit code assigned to the extended element C / is datatype codelistelement? 1 Integer Integer 310. definition exteledef definition of the extended element M 1 CharacterString Free text 311. obligation exteleob obligation of the extended element C / datatype not codelist, enumeration or codelistelement? 1 Class MD_ObligationCode <<Enumeration>> (B.5.21) 312. condition extelecond condition under which the extended element is mandatory C / obligation = Conditional? 1 CharacterString Free text 313. datatype eledatatype code which identifies the kind of value provided in the extended element M 1 Class MD_DatatypeCode <<CodeList>> (B.5.13) 314. maximumoccurrence extelemxoc maximum of the extended element C / datatype not codelist, enumeration or codelistelement? 1 CharacterString N or any integer 315. domainvalue exteledomval valid values that can be assigned to the extended element C / datatype not codelist, enumeration or codelistelement? 1 CharacterString Free text 316. parententity exteleparent name of the metadata entity(s) under which this extended metadata element may appear. The name(s) may be standard metadata element(s) or other extended metadata element(s) M N CharacterString Free text 317. rule extelerule specifies how the extended element relates to other existing elements and entities M 1 CharacterString Free text 318. rationale extelerat reason for creating the extended element O N CharacterString Free text ISO 2003 All rights reserved 79

90 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 319. source extelesrc name of the person or organization creating the extended element M N Class CI_ResponsibleParty <<DataType>> (B.3.2) B.2.12 Application schema information UML model shown in Figure A.14 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 320. MD_ApplicationSchema Information AppSchInfo information about the application schema used to build the dataset obligation/condition from referencing maximum from referencing Aggregated Class (MD_Metadata) Lines name asname name of the application schema used M 1 Class CI_Citation <<DataType>> (B.3.2) 322. schemalanguage asschlang identification of the schema language used M 1 CharacterString Free text 323. constraintlanguage ascstlang formal language used in Application Schema M 1 CharacterString Free text 324. schemaascii asascii full application schema given as an ASCII file O 1 CharacterString Free text 325. graphicsfile asgrafile full application schema given as a graphics file O 1 Binary Binary 326. softwaredevelopmentfile asswdevfile full application schema given as a software development file O 1 Binary Binary 327. softwaredevelopmentfile Format asswdevfift software dependent format used for the application schema software dependent file O 1 CharacterString Free text 328. intentionally left blank 329. intentionally left blank 80 ISO 2003 All rights reserved

91 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition 330. intentionally left blank 331. intentionally left blank 332. intentionally left blank 333. intentionally left blank B.3 Data type information B.3.1 Extent information B General UML model shown in Figure A.15 Name / Role Name Short Name Definition Obligation / Condition 334. EX_Extent Extent information about horizontal, vertical, and temporal extent obligation/condition from referencing 335. description exdesc spatial and temporal extent for the referring C / geographicelement and temporalelement and verticalelement not documented? 336. Role name: geographicelement geoele provides geographic component of the extent of the referring C / description and temporalelement and verticalelement not documented? 337. Role name: temporalelement tempele provides temporal component of the extent of the referring C / description and geographicelement and verticalelement not documented? Maximum Data type Domain Maximum Data type Domain maximum from referencing Class <<DataType>> Lines CharacterString Free text N Association EX_GeographicExtent <<Abstract>> (B.3.1.2) N Association EX_TemporalExtent (B.3.1.3) ISO 2003 All rights reserved 81

92 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 338. Role name: verticalelement vertele provides vertical component of the extent of the referring C / description and geographicelement and temporalelement not documented? N Association EX_VerticalExtent (B.3.1.4) B Geographic extent information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 339. EX_GeographicExtent GeoExtent geographic area of the dataset obligation/condition from referencing maximum from referencing Aggregated Class (EX_Extent and EX_SpatialTemporal Extent) <<Abstract>> Line extenttypecode extypecode indication of whether the bounding polygon encompasses an area covered by the data or an area where data is not present O 1 Boolean 0 exclusion 1 inclusion 341. EX_BoundingPolygon BoundPoly boundary enclosing the dataset, expressed as the closed set of (x,y) coordinates of the polygon (last point replicates first point) obligation/condition from referencing maximum from referencing Specified Class (EX_GeographicExtent) Line 342 and polygon polygon sets of points defining the bounding polygon M N Class GM_Object (B.4.6) -90 to 90 latitude -180 to 360 longitude 343. EX_GeographicBoundingBox GeoBndBox geographic position of the dataset NOTE This is only an approximate reference so specifying the coordinate reference system is unnecessary obligation/condition from referencing maximum from referencing Specified Class (EX_GeographicExtent) Lines and ISO 2003 All rights reserved

93 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 344. westboundlongitude westbl western-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east) M 1 Angle (B.4.3) -180,0 <= West Bounding Longitude Value <= 180, eastboundlongitude eastbl eastern-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east) M 1 Class Angle (B.4.3) -180,0 <= East Bounding Longitude Value <= 180, southboundlatitude southbl southern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north) M 1 Class Angle (B.4.3) -90,0 <= South Bounding Latitude Value <= 90,0; South Bounding Latitude Value <= North bounding Latitude Value 347. northboundlatitude northbl northern-most, coordinate of the limit of the dataset extent expressed in latitude in decimal degrees (positive north) M 1 Class Angle (B.4.3) -90,0 <= North Bounding Latitude Value <= 90,0; North Bounding Latitude Value >= South Bounding Latitude Value 348. EX_GeographicDescription GeoDesc description of the geographic area using identifiers obligation/condition from referencing maximum from referencing Specified Class (EX_GeographicExtent) Line 349 and geographicidentifier geoid identifier used to represent a geographic area M 1 Class MD_Identifier (B.2.7.3) ISO 2003 All rights reserved 83

94 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B Temporal extent information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 350. EX_TemporalExtent TempExtent time period covered by the content of the dataset obligation/condition from referencing maximum from referencing Aggregated Class (EX_Extent) Line extent extemp date and time for the content of the dataset M 1 Class TM_Primitive (B.4.5) 352. EX_SpatialTemporalExtent SpatTempEx extent with respect to date/time and spatial boundaries obligation/condition from referencing maximum from referencing Specified Class (EX_TemporalExtent) Line 353 and role name: spatialextent exspat spatial extent component of composite spatial and temporal extent M N Association EX_GeographicExtent <<Abstract>> (B.3.1.2) B Vertical extent information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 354. EX_VerticalExtent VertExtent vertical domain of dataset obligation/condition from referencing maximum from referencing Aggregated Class (EX_Extent) Lines minimumvalue vertminval lowest vertical extent contained in the dataset M 1 Real Real 356. maximumvalue vertmaxval highest vertical extent contained in the dataset M 1 Real Real 84 ISO 2003 All rights reserved

95 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 357. unitofmeasure vertuom vertical units used for vertical extent information Examples: metres, feet, millimetres, hectopascals M 1 Class UomLength (B.4.3) 358. role name: verticaldatum vertdatum provides information about the origin from which the maximum and minimum elevation values are measured M 1 Association SC_VerticalDatum (B.4.9) B.3.2 Citation and responsible party information B General UML model shown in Figure A.16 Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 359. CI_Citation Citation standardized resource reference obligation/condition from referencing maximum from referencing Class <<DataType>> Lines title restitle name by which the cited resource is known M 1 CharacterString Free text 361. alternatetitle resalttitle short name or other language name by which the cited information is known. Example: "DCW" as an alternative title for "Digital Chart of the World O N CharacterString Free text 362. date resrefdate reference date for the cited resource M N Class CI_Date (B.3.2.4) <<DataType>> 363. edition resed version of the cited resource O 1 CharacterString Free text 364. editiondate reseddate date of the edition O 1 Class Date (B.4.2) ISO 2003 All rights reserved 85

96 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 365. identifier citid value uniquely identifying an within a namespace O N Class MD_Identifier <<DataType>> (B.2.7.3) 366. intentionally left blank 367. citedresponsibleparty citrespparty name and position information for an individual or organization that is responsible for the resource O N Class CI_ResponsibleParty <<DataType>> (B.3.2) 368. presentationform presform mode in which the resource is represented O N Class CI_PresentationFormCode <<CodeList>> (B.5.4) 369. series datasetseries information about the series, or aggregate dataset, of which the dataset is a part O 1 Class CI_Series <<DataType>> (B.3.2.6) 370. othercitationdetails othercitdet other information required to complete the citation that is not recorded elsewhere O 1 CharacterString Free text 371. collectivetitle colltitle common title with holdings note NOTE title identifies elements of a series collectively, combined with information about what volumes are available at the source cited O 1 CharacterString Free text 372. ISBN isbn international Standard Book Number O 1 CharacterString Free text 373. ISSN issn international Standard Serial Number O 1 CharacterString Free text 374. CI_ResponsibleParty RespParty identification of, and means of communication with, person(s) and organizations associated with the dataset obligation/condition from referencing maximum from referencing Class <<DataType>> Lines individualname rpindname name of the responsible personsurname, given name, title separated by a delimiter C / organisationname and positionname not documented? 1 CharacterString Free text 376. organisationname rporgname name of the responsible organization C / individualname and positionname not documented? 1 CharacterString Free text 86 ISO 2003 All rights reserved

97 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 377. positionname rpposname role or position of the responsible person C / individualname and organisationname not documented? 1 CharacterString Free text 378. contactinfo rpcntinfo address of the responsible party O 1 Class CI_Contact <<DataType>> (B.3.2.3) 379. role role function performed by the responsible party M 1 Class CI_RoleCode <<CodeList>> (B.5.5) B Address information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 380. CI_Address Address location of the responsible individual or organization obligation/condition from referencing maximum from referencing Class <<DataType>> Lines deliverypoint delpoint address line for the location (as described in ISO 11180, Annex A) O N CharacterString Free text 382. city city city of the location O 1 CharacterString Free text 383. administrativearea adminarea state, province of the location O 1 CharacterString Free text 384. postalcode postcode ZIP or other postal code O 1 CharacterString Free text 385. country country country of the physical address O 1 CharacterString ISO , other parts may be used 386. electronicmailaddress add address of the electronic mailbox of the responsible organization or individual O N CharacterString Free text ISO 2003 All rights reserved 87

98 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B Contact information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 387. CI_Contact Contact information required to enable contact with the responsible person and/or organization obligation/condition from referencing maximum from referencing Class <<DataType>> Lines phone cntphone telephone numbers at which the organization or individual may be contacted O 1 Class CI_Telephone <<DataType>> (B.3.2.7) 389. address cntaddress physical and address at which the organization or individual may be contacted O 1 Class CI_Address <<DataType>> (B.3.2.2) 390. onlineresource cntonlineres on-line information that can be used to contact the individual or organization O 1 Class CI_OnlineResource <<DataType>> (B.3.2.5) 391. hoursofservice cnthours time period (including time zone) when individuals can contact the organization or individual O 1 CharacterString Free text 392. contactinstructions cntinstr supplemental instructions on how or when to contact the individual or organization O 1 CharacterString Free text B Date information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 393. CI_Date DateRef reference date and event used to describe it obligation/condition from referencing maximum from referencing Class <<DataType>> Lines ISO 2003 All rights reserved

99 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 394. date refdate reference date for the cited resource M 1 Class Date (B.4.2) 395. datetype refdatetype event used for reference date M 1 Class CI_DateTypeCode <<CodeList>> (B.5.2) B OnLine resource information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 396. CI_OnlineResource OnlineRes information about on-line sources from which the dataset, specification, or community profile name and extended metadata elements can be obtained obligation/condition from referencing maximum from referencing Class <<DataType>> Lines linkage linkage location (address) for on-line access using a Uniform Resource Locator address or similar addressing scheme such as M 1 Class URL (IETF RFC1738 IETF RFC 2056) 398. protocol protocol connection protocol to be used O 1 CharacterString Free text 399. applicationprofile appprofile name of an application profile that can be used with the online resource O 1 CharacterString Free text 400. name orname name of the online resource O 1 CharacterString Free text 401. description ordesc detailed text description of what the online resource is/does O 1 CharacterString Free text 402. function orfunct code for function performed by the online resource O 1 Class CI_OnLineFunctionCode <<CodeList>> (B.5.3) ISO 2003 All rights reserved 89

100 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B Series information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 403. CI_Series DatasetSeries information about the series, or aggregate dataset, to which a dataset belongs obligation/condition from referencing maximum from referencing Class <<DataType>> Lines name seriesname name of the series, or aggregate dataset, of which the dataset is a part O 1 CharacterString Free text 405. issueidentification issid information identifying the issue of the series O 1 CharacterString Free text 406. page artpage details on which pages of the publication the article was published O 1 CharacterString Free text B Telephone information Name / Role Name Short Name Definition Obligation / Condition Maximum Data type Domain 407. CI_Telephone Telephone telephone numbers for contacting the responsible individual or organization obligation/condition from referencing maximum from referencing Class <<DataType>> Lines voice voicenum telephone number by which individuals can speak to the responsible organization or individual O N CharacterString Free text 409. facsimile faxnum telephone number of a facsimile machine for the responsible organization or individual O N CharacterString Free text 90 ISO 2003 All rights reserved

101 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.4 Externally referenced entities B.4.1 Introduction There are several entities referenced by this International Standard that are documented by another, external, standard. Those externally referenced entities are explained below. B.4.2 Date and DateTime information Date: gives values for year, month and day. Character encoding of a date is a string which shall follow the format for date specified by ISO This class is documented in full in ISO/TS DateTime: combination of a date and a time type (given by an hour, minute and second). Character encoding of a DateTime shall follow ISO This class is documented in full in ISO/TS B.4.3 Distance, angle, measure, number, record, recordtype, scale and UomLength information Distance: This class is documented in full in ISO/TS Angle: Amount of rotation need to bring one line or plane into coincidence with another, generally measured in radians or degrees. This class is documented in full in ISO/TS Measure: result from performing the act or process of ascertaining the extent, dimensions, or quantity of some entity. This class is documented in full in ISO/TS Number: abstract class that can be sub-typed to a specific number type (real, integer, decimal, double, float). This class is documented in full in ISO/TS Record: This class is documented in full in ISO/TS RecordType: This class is documented in full in ISO/TS Scale: This class is documented in full in ISO/TS UnitOfMeasure: This class is documented in full in ISO/TS UomLength: any of the measuring systems to measure the length, distance between two entities. This class is documented in full in ISO/TS B.4.4 Feature type, property type, and attribute type information GF_AttributeType: class of attribute definitions of a feature type. This class is fully documented in ISO GF_FeatureType: textual information describing the concept of a feature type, containing all feature types. This class is documented in full in ISO GF_PropertyType: textual information related to the feature type because its text comprises characteristics and behaviour of any property of a feature type, as well as its roles within associations between features. This class is documented in full in ISO B.4.5 PeriodDuration and temporal primitive information TM_PeriodDuration: duration of a period as specified by ISO This class is fully documented in ISO ISO 2003 All rights reserved 91

102 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL TM_Primitive: an abstract class representing a non-decomposed element of geometry or topology. This class is fully documented in ISO B.4.6 Point and Object information GM_Point: 0-dimensional geometric primitive, representing a position, but not having extent. This class is fully documented in ISO GM_Object: root class of the geometric taxonomy and supports interfaces common to all geographically referenced geometric s. This class is fully documented in ISO B.4.7 Set and Sequence information Set: finite collection of s, where each appears in the collection only once. A set shall not contain any duplicated instances. The order of the elements of the set is not specified. This class is documented in full in ISO/TS Sequence: A sequence refers to a collection of sequential ordering between its elements. Sequences can be repeated, and may be used as a list or an array. This class is documented in full in ISO/TS B.4.8 Type name information AttributeName: This class is documented in full in ISO/TS GenericName: This class is documented in full in ISO/TS MemberName: This class is documented in full in ISO/TS B.4.9 Vertical datum information SC_VerticalDatum: set of parameters describing the relation of gravity-related heights to the Earth. This class is fully documented in ISO B.5 CodeLists and enumerations B.5.1 Introduction The stereotype classes <<CodeList>> and <<Enumeration>> can be found below. These two stereotype classes do not contain obligation / condition, maximum, data type and domain attributes. These two stereotype classes also do not contain any other values as <<Enumeration>>s are closed (not extendable) and <<CodeList>>s are extendable. Consult Annex C and Annex F for information about how to extend <<CodeList>>s. B.5.2 CI_DateTypeCode <<CodeList>> Name Domain code Definition 1. CI_DateTypeCode DateTypCd identification of when a given event occurred 2. creation 001 date identifies when the resource was brought into existence 3. publication 002 date identifies when the resource was issued 4. revision 003 date identifies when the resource was examined or re-examined and improved or amended 92 ISO 2003 All rights reserved

103 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.5.3 CI_OnLineFunctionCode <<CodeList>> Name Domain code Definition 1. CI_OnLineFunctionCode OnFunctCd function performed by the resource 2. download 001 online instructions for transferring data from one storage device or system to another 3. information 002 online information about the resource 4. offlineaccess 003 online instructions for requesting the resource from the provider 5. order 004 online order process for obtaining the resource 6. search 005 online search interface for seeking out information about the resource B.5.4 CI_PresentationFormCode <<CodeList>> Name Domain code Definition 1. CI_PresentationFormCode PresFormCd mode in which the data is represented 2. documentdigital 001 digital representation of a primarily textual item (can contain illustrations also) 3. documenthardcopy 002 representation of a primarily textual item (can contain illustrations also) on paper, photographic material, or other media 4. imagedigital 003 likeness of natural or man-made features, s, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format 5. imagehardcopy 004 likeness of natural or man-made features, s, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user 6. mapdigital 005 map represented in raster or vector form 7. maphardcopy 006 map printed on paper, photographic material, or other media for use directly by the human user 8. modeldigital 007 multi-dimensional digital representation of a feature, process, etc. 9. modelhardcopy dimensional, physical model 10. profiledigital 009 vertical cross-section in digital form 11. profilehardcopy 010 vertical cross-section printed on paper, etc. 12. tabledigital 011 digital representation of facts or figures systematically displayed, especially in columns 13. tablehardcopy 012 representation of facts or figures systematically displayed, especially in columns, printed on paper, photographic material, or other media 14. videodigital 013 digital video recording 15. videohardcopy 014 video recording on film B.5.5 CI_RoleCode <<CodeList>> Name Domain code Definition 1. CI_RoleCode RoleCd function performed by the responsible party 2. resourceprovider 001 party that supplies the resource 3. custodian 002 party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource ISO 2003 All rights reserved 93

104 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name Domain code Definition 4. owner 003 party that owns the resource 5. user 004 party who uses the resource 6. distributor 005 party who distributes the resource 7. originator 006 party who created the resource 8. pointofcontact 007 party who can be contacted for acquiring knowledge about or acquisition of the resource 9. principalinvestigator 008 key party responsible for gathering information and conducting research 10. processor 009 party who has processed the data in a manner such that the resource has been modified 11. publisher 010 party who published the resource 12. author 011 party who authored the resource B.5.6 DQ_EvaluationMethodTypeCode <<CodeList>> Name Domain code Definition 1. DQ_EvaluationMethodTyp ecode EvalMethTypeCd type of method for evaluating an identified data quality measure 2. directinternal 001 method of evaluating the quality of a dataset based on inspection of items within the dataset, where all data required is internal to the dataset being evaluated 3. directexternal 002 method of evaluating the quality of a dataset based on inspection of items within the dataset, where reference data external to the dataset being evaluated is required 4. indirect 003 method of evaluating the quality of a dataset based on external knowledge B.5.7 DS_AssociationTypeCode <<CodeList>> Name Domain code Definition 1. DS_AssociationTypeCode AscTypeCd justification for the correlation of two datasets 2. crossreference 001 reference from one dataset to another 3. largerworkcitation 002 reference to a master dataset of which this one is a part 4. partofseamlessdatabase 003 part of same structured set of data held in a computer 5. source 004 mapping and charting information from which the dataset content originates 6. stereomate 005 part of a set of imagery that when used together, provides three-dimensional images B.5.8 DS_InitiativeTypeCode <<CodeList>> Name Domain code Definition 1. DS_InitiativeTypeCode InitTypCd type of aggregation activity in which datasets are related 2. campaign 001 series of organized planned actions 3. collection 002 accumulation of datasets assembled for a specific purpose 4. exercise 003 specific performance of a function or group of functions 5. experiment 004 process designed to find if something is effective or valid 6. investigation 005 search or systematic inquiry 94 ISO 2003 All rights reserved

105 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name Domain code Definition 7. mission 006 specific operation of a data collection system 8. sensor 007 device or piece of equipment which detects or records 9. operation 008 action that is part of a series of actions 10. platform 009 vehicle or other support base that holds a sensor 11. process 010 method of doing something involving a number of steps 12. program 011 specific planned activity 13. project 012 organized undertaking, research, or development 14. study 013 examination or investigation 15. task 014 piece of work 16. trial 015 process of testing to discover or demonstrate something B.5.9 MD_CellGeometryCode <<CodeList>> Name Domain code Definition 1. MD_CellGeometryCode CellGeoCd code indicating whether grid data is point or area 2. point 001 each cell represents a point 3. area 002 each cell represents an area B.5.10 MD_CharacterSetCode <<CodeList>> Name Domain code Definition 1. MD_CharacterSetCode CharSetCd name of the character coding standard used for the resource 2. ucs bit fixed size Universal Character Set, based on ISO/IEC ucs bit fixed size Universal Character Set, based on ISO/IEC utf bit variable size UCS Transfer Format, based on ISO/IEC utf bit variable size UCS Transfer Format, based on ISO/IEC utf bit variable size UCS Transfer Format, based on ISO/IEC part1 006 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 1: Latin alphabet No part2 007 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 2: Latin alphabet No part3 008 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 3: Latin alphabet No part4 009 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 4: Latin alphabet No part5 010 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 5: Latin/Cyrillic alphabet part6 011 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 6: Latin/Arabic alphabet part7 012 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 7: Latin/Greek alphabet part8 013 ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 8: Latin/Hebrew alphabet part9 014 ISO/IEC8859-9, Information technology 8-bit single-byte coded graphic character sets Part 9: Latin alphabet No. 5 ISO 2003 All rights reserved 95

106 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name Domain code Definition part ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 10: Latin alphabet No part ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 11: Latin/Thai alphabet 18. (reserved for future use) 017 a future ISO/IEC 8-bit single-byte coded graphic character set (e.g. possibly 8859 part 12) part ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 13: Latin alphabet No part ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 14: Latin alphabet No. 8 (Celtic) part ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 15: Latin alphabet No part ISO/IEC , Information technology 8-bit single-byte coded graphic character sets Part 16: Latin alphabet No jis 022 japanese code set used for electronic transmission 24. shiftjis 023 japanese code set used on MS-DOS based machines 25. eucjp 024 japanese code set used on UNIX based machines 26. usascii 025 united states ASCII code set (ISO 646 US) 27. ebcdic 026 ibm mainframe code set 28. euckr 027 korean code set 29. big5 028 traditional Chinese code set used in Taiwan, Hong Kong of China and other areas 30. GB simplified Chinese code set B.5.11 MD_ClassificationCode <<CodeList>> Name Domain code Definition 1. MD_ClassificationCode ClasscationCd name of the handling restrictions on the dataset 2. unclassified 001 available for general disclosure 3. restricted 002 not for general disclosure 4. confidential 003 available for someone who can be entrusted with information 5. secret 004 kept or meant to be kept private, unknown, or hidden from all but a select group of people 6. topsecret 005 of the highest secrecy B.5.12 MD_CoverageContentTypeCode <<CodeList>> Name Domain code Definition 1. MD_CoverageContentTyp ecode ContentTypCd specific type of information represented in the cell 2. image 001 meaningful numerical representation of a physical parameter that is not the actual value of the physical parameter 3. thematicclassification 002 code value with no quantitative meaning, used to represent a physical quantity 4. physicalmeasurement 003 value in physical units of the quantity being measured 96 ISO 2003 All rights reserved

107 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.5.13 MD_DatatypeCode <<CodeList>> Name Domain code Definition 1. MD_DatatypeCode DatatypeCd datatype of element or entity 2. class 001 descriptor of a set of s that share the same attributes, operations, methods, relationships, and behavior 3. codelist 002 flexible enumeration useful for expressing a long list of values, can be extended 4. enumeration 003 data type whose instances form a list of named literal values, not extendable 5. codelistelement 004 permissible value for a codelist or enumeration 6. abstractclass 005 class that cannot be directly instantiated 7. aggregateclass 006 class that is composed of classes it is connected to by an aggregate relationship 8. specifiedclass 007 subclass that may be substituted for its superclass 9. datatypeclass 008 class with few or no operations whose primary purpose is to hold the abstract state of another class for transmittal, storage, encoding or persistent storage 10. interfaceclass 009 named set of operations that characterize the behavior of an element 11. unionclass 010 class describing a selection of one of the specified types 12. metaclass 011 class whose instances are classes 13. typeclass 012 class used for specification of a domain of instances (s), together with the operations applicable to the s. A type may have attributes and associations 14. characterstring 013 free text field 15. integer 014 numerical field 16. association 015 semantic relationship between two classes that involves connections among their instances B.5.14 MD_DimensionNameTypeCode <<CodeList>> Name Domain code Definition 1. MD_DimensionNameType Code DimNameTypCd name of the dimension 2. row 001 ordinate (y) axis 3. column 002 abscissa (x) axis 4. vertical 003 vertical (z) axis 5. track 004 along the direction of motion of the scan point 6. crosstrack 005 perpendicular to the direction of motion of the scan point 7. line 006 scan line of a sensor 8. sample 007 element along a scan line 9. time 008 duration B.5.15 MD_GeometricObjectTypeCode <<CodeList>> Name Domain code Definition 1. MD_GeometricObjectType Code GeoObjTypCd name of point or vector s used to locate zero-, one-, two-, or threedimensional spatial locations in the dataset 2. complex 001 set of geometric primitives such that their boundaries can be represented as a union of other primitives ISO 2003 All rights reserved 97

108 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name Domain code Definition 3. composite 002 connected set of curves, solids or surfaces 4. curve 003 bounded, 1-dimensional geometric primitive, representing the continuous image of a line 5. point 004 zero-dimensional geometric primitive, representing a position but not having an extent 6. solid 005 bounded, connected 3-dimensional geometric primitive, representing the continuous image of a region of space 7. surface 006 bounded, connected 2-dimensional geometric primitive, representing the continuous image of a region of a plane B.5.16 MD_ImagingConditionCode <<CodeList>> Name Domain code Definition 1. MD_ImagingConditionCod e ImgCondCd code which indicates conditions which may affect the image 2. blurredimage 001 portion of the image is blurred 3. cloud 002 portion of the image is partially obscured by cloud cover 4. degradingobliquity 003 acute angle between the plane of the ecliptic (the plane of the Earth s orbit) and the plane of the celestial equator 5. fog 004 portion of the image is partially obscured by fog 6. heavysmokeordust 005 portion of the image is partially obscured by heavy smoke or dust 7. night 006 image was taken at night 8. rain 007 image was taken during rainfall 9. semidarkness 008 image was taken during semi-dark conditions twilight conditions 10. shadow 009 portion of the image is obscured by shadow 11. snow 010 portion of the image is obscured by snow 12. terrainmasking 011 the absence of collection data of a given point or area caused by the relative location of topographic features which obstruct the collection path between the collector(s) and the subject(s) of interest B.5.17 MD_KeywordTypeCode <<CodeList>> Name Domain code Definition 1. MD_KeywordTypeCode KeyTypCd methods used to group similar keywords 2. discipline 001 keyword identifies a branch of instruction or specialized learning 3. place 002 keyword identifies a location 4. stratum 003 keyword identifies the layer(s) of any deposited substance 5. temporal 004 keyword identifies a time period related to the dataset 6. theme 005 keyword identifies a particular subject or topic 98 ISO 2003 All rights reserved

109 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.5.18 MD_MaintenanceFrequencyCode <<CodeList>> Name Domain code Definition 1. MD_MaintenanceFrequen cycode MaintFreqCd frequency with which modifications and deletions are made to the data after it is first produced 2. continual 001 data is repeatedly and frequently updated 3. daily 002 data is updated each day 4. weekly 003 data is updated on a weekly basis 5. fortnightly 004 data is updated every two weeks 6. monthly 005 data is updated each month 7. quarterly 006 data is updated every three months 8. biannually 007 data is updated twice each year 9. annually 008 data is updated every year 10. asneeded 009 data is updated as deemed necessary 11. irregular 010 data is updated in intervals that are uneven in duration 12. notplanned 011 there are no plans to update the data 13. unknown 012 frequency of maintenance for the data is not known B.5.19 MD_MediumFormatCode <<CodeList>> Name Domain code Definition 1. MD_MediumFormatCode MedFormCd method used to write to the medium 2. cpio 001 CoPy In / Out (UNIX file format and command) 3. tar 002 Tape ARchive 4. highsierra 003 high sierra file system 5. iso information processing volume and file structure of CD-ROM 6. iso9660rockridge 005 rock ridge interchange protocol (UNIX) 7. iso9660applehfs 006 hierarchical file system (Macintosh) B.5.20 MD_MediumNameCode <<CodeList>> Name Domain code Definition 1. MD_MediumNameCode MedNameCd name of the medium 2. cdrom 001 read-only optical disk 3. dvd 002 digital versatile disk 4. dvdrom 003 digital versatile disk, read only 5. 3halfInchFloppy 004 3,5 inch magnetic disk 6. 5quarterInchFloppy 005 5,25 inch magnetic disk 7. 7trackTape track magnetic tape 8. 9trackTape track magnetic tape Cartridge cartridge tape drive Cartridge cartridge tape drive Cartridge cartridge tape drive ISO 2003 All rights reserved 99

110 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name Domain code Definition 12. 4mmCartridgeTape millimetre magnetic tape 13. 8mmCartridgeTape millimetre magnetic tape 14. 1quarterInchCartridgeTape 013 0,25 inch magnetic tape 15. digitallineartape 014 half inch cartridge streaming tape drive 16. online 015 direct computer linkage 17. satellite 016 linkage through a satellite communication system 18. telephonelink 017 communication through a telephone network 19. hardcopy 018 pamphlet or leaflet giving descriptive information B.5.21 MD_ObligationCode <<Enumeration>> Name Domain code Definition 1. MD_ObligationCode ObCd obligation of the element or entity 2. mandatory 001 element is always required 3. optional 002 element is not required 4. conditional 003 element is required when a specific condition is met B.5.22 MD_PixelOrientationCode <<Enumeration>> Name Domain code Definition 1. MD_PixelOrientationCode PixOrientCd point in a pixel corresponding to the Earth location of the pixel 2. center 001 point halfway between the lower left and the upper right of the pixel 3. lowerleft 002 the corner in the pixel closest to the origin of the SRS; if two are at the same distance from the origin, the one with the smallest x-value 4. lowerright 003 next corner counterclockwise from the lower left 5. upperright 004 next corner counterclockwise from the lower right 6. upperleft 005 next corner counterclockwise from the upper right B.5.23 MD_ProgressCode <<CodeList>> Name Domain code Definition 1. MD_ProgressCode ProgCd status of the dataset or progress of a review 2. completed 001 production of the data has been completed 3. historicalarchive 002 data has been stored in an offline storage facility 4. obsolete 003 data is no longer relevant 5. ongoing 004 data is continually being updated 6. planned 005 fixed date has been established upon or by which the data will be created or updated 7. required 006 data needs to be generated or updated 8. underdevelopment 007 data is currently in the process of being created 100 ISO 2003 All rights reserved

111 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) B.5.24 MD_RestrictionCode <<CodeList>> Name Domain code Definition 1. MD_RestrictionCode RestrictCd limitation(s) placed upon the access or use of the data 2. copyright 001 exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor 3. patent 002 government has granted exclusive right to make, sell, use or license an invention or discovery 4. patentpending 003 produced or sold information awaiting a patent 5. trademark 004 a name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer 6. license 005 formal permission to do something 7. intellectualpropertyrights 006 rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity 8. restricted 007 withheld from general circulation or disclosure 9. otherrestrictions 008 limitation not listed B.5.25 MD_ScopeCode <<CodeList>> Name Domain code Definition 1. MD_ScopeCode ScopeCd class of information to which the referencing entity applies 2. attribute 001 information applies to the attribute class 3. attributetype 002 information applies to the characteristic of a feature 4. collectionhardware 003 information applies to the collection hardware class 5. collectionsession 004 information applies to the collection session 6. dataset 005 information applies to the dataset 7. series 006 information applies to the series 8. nongeographicdataset 007 information applies to non-geographic data 9. dimensiongroup 008 information applies to a dimension group 10. feature 009 information applies to a feature 11. featuretype 010 information applies to a feature type 12. propertytype 011 information applies to a property type 13. fieldsession 012 information applies to a field session 14. software 013 information applies to a computer program or routine 15. service 014 information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case 16. model 015 information applies to a copy or imitation of an existing or hypothetical 17. tile 016 information applies to a tile, a spatial subset of geographic data ISO 2003 All rights reserved 101

112 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B.5.26 MD_SpatialRepresentationTypeCode <<CodeList>> Name Domain code Definition 1. MD_SpatialRepresentation TypeCode SpatRepTypCd method used to represent geographic information in the dataset 2. vector 001 vector data is used to represent geographic data 3. grid 002 grid data is used to represent geographic data 4. texttable 003 textual or tabular data is used to represent geographic data 5. tin 004 triangulated irregular network 6. stereomodel 005 three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images 7. video 006 scene from a video recording B.5.27 MD_TopicCategoryCode << Enumeration>> Name Domain code Definition 1. MD_TopicCategoryCode TopicCatCd high-level geographic data thematic classification to assist in the grouping and search of available geographic data sets. Can be used to group keywords as well. Listed examples are not exhaustive. NOTE It is understood there are overlaps between general categories and the user is encouraged to select the one most appropriate. 2. farming 001 rearing of animals and/or cultivation of plants Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock 3. biota 002 flora and/or fauna in natural environment Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat 4. boundaries 003 legal land descriptions Examples: political and administrative boundaries 5. climatologymeteorologyat mosphere 004 processes and phenomena of the atmosphere Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation 6. economy 005 economic activities, conditions and employment Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas 7. elevation 006 height above or below sea level Examples: altitude, bathymetry, digital elevation models, slope, derived products 8. environment 007 environmental resources, protection and conservation Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape 9. geoscientificinformation 008 information pertaining to earth sciences Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion 10. health 009 health, health services, human ecology, and safety Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services 102 ISO 2003 All rights reserved

113 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name Domain code Definition 11. imagerybasemapsearthco ver 010 base maps Examples: land cover, topographic maps, imagery, unclassified images, annotations 12. intelligencemilitary 011 military bases, structures, activities Examples: barracks, training grounds, military transportation, information collection 13. inlandwaters 012 inland water features, drainage systems and their characteristics Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts 14. location 013 positional information and services Examples: addresses, geodetic networks, control points, postal zones and services, place names 15. oceans 014 features and characteristics of salt water bodies (excluding inland waters) Examples: tides, tidal waves, coastal information, reefs 16. planningcadastre 015 information used for appropriate actions for future use of the land Examples: land use maps, zoning maps, cadastral surveys, land ownership 17. society 016 characteristics of society and cultures Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information 18. structure 017 man-made construction Examples: buildings, museums, churches, factories, housing, monuments, shops, towers 19. transportation 018 means and aids for conveying persons and/or goods Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways 20. utilitiescommunication 019 energy, water and waste systems and communications infrastructure and services Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks ISO 2003 All rights reserved 103

114 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL B.5.28 MD_TopologyLevelCode <<CodeList>> Name Domain code Definition 1. MD_TopologyLevelCode TopoLevCd degree of complexity of the spatial relationships 2. geometryonly 001 geometry s without any additional structure which describes topology 3. topology1d dimensional topological complex commonly called chain-node topology 4. planargraph dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in a plane in such a way that no two edges intersect except at a vertex.) 5. fullplanargraph dimensional topological complex that is planar. (A 2-dimensional topological complex is commonly called full topology in a cartographic 2D environment.) 6. surfacegraph dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimensional-and boundry-preserving correspondence to one another.) 7. fullsurfacegraph dimensional topological complex that is isomorphic to a subset of a surface 8. topology3d dimensional topological complex. (A topological complex is a collection of topological primitives that are closed under the boundary operations.) 9. fulltopology3d 008 complete coverage of a 3D Euclidean coordinate space 10. abstract 009 topological complex without any specified geometric realisation 104 ISO 2003 All rights reserved

115 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Annex C (normative) Metadata extensions and profiles C.1 Background Annexes A, B and Clause 6 of this International Standard provide standard metadata and an associated structure that will serve a wide variety of digital geographic data. The definitions and domain values are intended to be sufficiently generic to satisfy the metadata needs of various disciplines. However, the very diversity of data means that generic metadata may not accommodate all applications. This annex provides the rules for defining and applying additional metadata to better serve special user needs. C.2 Types of extensions The following types of extensions shall be allowed: 1) adding a new metadata section; 2) creating a new metadata codelist to replace the domain of an existing metadata element that has free text listed as its domain value; 3) creating new metadata codelist elements (expanding a codelist); 4) adding a new metadata element; 5) adding a new metadata entity; 6) imposing a more stringent obligation on an existing metadata element; 7) imposing a more restrictive domain on an existing metadata element. C.3 Creating an extension Prior to the creation of extended metadata a careful review of the existing metadata within this International Standard must be performed to confirm that suitable metadata does not already exist. For each extended metadata section, entity, and/or element, the name, short name, definition, obligation, condition, maximum, data type, and domain values shall be defined. Relationships as provided in Annex A shall be defined so a structure and schema can be determined. C.4 Rules for creating an extension 1) Extended metadata elements shall not be used to change the name, definition or data type of an existing element. 2) Extended metadata may be defined as entities and may include extended and existing metadata elements as components. ISO 2003 All rights reserved 105

116 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL 3) An extension is permitted to impose more stringent obligation on existing metadata elements than the standard requires. (Metadata elements that are optional in the standard may be mandatory in an extension.) 4) An extension is permitted to contain metadata elements with domains that are more restrictive than the standard. (Metadata elements whose domains have free text in the standard may have a closed list of appropriate values in the profile.) 5) An extension is permitted to restrict the use of domain values allowed by the standard. (If the standard contains five values in the domain of an existing metadata element, the extension may specify that its domain consists of three domain values. The extension shall require that the user select a value from the three domain values.) 6) An extension is permitted to expand the number of values in a codelist. 7) An extension shall not permit anything not allowed by the standard. C.5 Community profile If the information to be added is extensive, involving the creation of many metadata elements within a metadata entity, specific to a discipline or application, co-ordination of the proposed extension via user groups and creation of a community profile is recommended. This International Standard defines almost 300 metadata elements, with most of these being listed as "optional". They are explicitly defined in order to help users understand exactly what is being described. Individual communities, nations, or organizations may develop a "community profile" of this International Standard. They will make a select set of metadata elements mandatory. A given metadata element (e.g., the price of a dataset) may be established as "mandatory" for a certain community that will always want that metadata element reported. A community of users may want to establish additional metadata elements that are not in this International Standard. For example, a community may want to develop metadata elements for the status of datasets within their system to help manage production. However, these added elements will not be known outside the community unless they are published. A community profile should establish field sizes and domains for all metadata elements. If one system within a community uses thirty-two (32) characters for the title of a dataset and another system handles eight (8) characters, interoperability will not be achieved. Standardizing selected domains within a community is important to allow more efficient searches and better system control. See ISO for more information on community profiles. Figure C.1 illustrates the relationship between the Core Metadata components, the comprehensive metadata application profile and national, regional, domain specific or organizational profiles. 106 ISO 2003 All rights reserved

117 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Comprehensive metadata profile Community Profile 1 Core metadata components Extended metadata Figure C.1 Metadata community profile The inner circle contains the core metadata components. The comprehensive metadata includes the core metadata components. A community profile shall contain the core metadata components, but not necessarily all the other metadata components. Additionally it may contain metadata extensions (shaded area) which shall be defined following the metadata extension rules in this annex. C.6 Rules for creating a profile 1) Before creating a profile, the user shall check registered profiles. 2) A profile must adhere to the rules for defining an extension. 3) A profile shall not change the name, definition, or data type of a metadata element. 4) A profile shall include: the core metadata collected for a digital geographic dataset all mandatory metadata elements in all mandatory sections all conditional metadata elements in all mandatory sections, if the dataset meets the condition required by the metadata element all mandatory metadata elements in all conditional sections, if the dataset meets the condition required by the section all conditional metadata elements in all conditional sections, if the dataset meets the condition required by the metadata element and the section 5) Relationships, as provided in Annex A, shall be defined so that a structure and schema can be determined. 6) A profile shall be made available to anyone receiving metadata that was created according to that profile. ISO 2003 All rights reserved 107

118 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Annex D (normative) Abstract test suite D.1 Abstract test suite This abstract test suite applies to the comprehensive profile and any profile derived from this International Standard. Metadata shall be provided as specified in Clause 6 and Annexes A and B. r-defined metadata shall be defined and provided as specified in Annex C. r-defined metadata shall satisfy the requirements as stated in D.3. D.2 Metadata test suite D.2.1 Test case identifier: Completeness test a) Test Purpose: to determine conformance by the inclusion of all metadata sections, metadata entities, and metadata elements that are specified with an obligation of mandatory or mandatory under the conditions specified. NOTE Many elements designated as mandatory are contained within optional entities. These elements become mandatory only when their containing entity is used. b) Test Method: a comparison between this International Standard and a subject metadata set to be tested shall be performed to determine if all metadata defined as mandatory in annex B are present. A comparison test shall also be performed to determine if all metadata elements defined as conditional in Annex B are present if the conditions set out in this International Standard apply. c) Reference: Annex B. d) Test Type: Basic. The following test cases apply at all levels of obligation mandatory, conditional, and optional. D.2.2 Test case identifier: Maximum test a) Test Purpose: to ensure each metadata element occurs no more than the number of times specified in this International Standard. b) Test Method: examine a subject metadata set for the number of s of each metadata section, metadata entity, and metadata element provided. The number of s for each shall be compared with its Maximum Occurrences attribute specified in Annex B. c) Reference: Annex B. d) Test Type: Basic. D.2.3 Test case identifier: Short name test a) Test Purpose: to determine if short names used in a subject metadata set fall within the domain specified within this International Standard. 108 ISO 2003 All rights reserved

119 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) b) Test Method: the short name for each metadata element in a subject metadata set is examined to determine if it is defined in this International Standard. c) Reference: Annex B. d) Test Type: Basic. D.2.4 Test case identifier: Data type test a) Test Purpose: to determine if each metadata element within a subject metadata set uses the specified data type. b) Test Method: the value of each provided metadata element is tested to ensure its data type adheres to the data type specified. c) Reference: Annex B. d) Test Type: Basic. D.2.5 Test case identifier: Domain test a) Test Purpose: to determine if each provided metadata element within a subject metadata set falls within the specified domain. b) Test Method: the values of each metadata element are tested to ensure they fall within the specified domain. c) Reference: Annex B. d) Test Type: Basic. D.2.6 Test case identifier: Schema test a) Test Purpose: to determine if a subject metadata set follows the schema specified in this International Standard. b) Test Method: test each metadata element and ensure it is contained within the specified metadata entity. c) Reference: Annex B. d) Test Type: Basic. D.3 r-defined extension metadata test suite D.3.1 Test case identifier: Exclusiveness test a) Test Purpose: to verify that each user-defined metadata section, metadata entity, and metadata element is unique and not already defined in this International Standard. b) Test Method: each user-defined metadata entity and metadata element is tested to ensure it is unique and not previously used. c) Reference: Annex B. d) Test Type: Basic. ISO 2003 All rights reserved 109

120 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL D.3.2 Test case identifier: Definition test a) Test Purpose: to verify that user-defined metadata entities and metadata elements have been defined as specified in this International Standard. b) Test Method: each user-defined metadata entity and metadata element is tested to ensure that all attributes have been defined. c) Reference: Annex B. d) Test Type: Basic. D.3.3 Test case identifier: Standard metadata test a) Test Purpose: to verify that user-defined metadata within a subject metadata set fulfils the same requirements as ISO standard metadata. b) Test Method: all user-defined metadata in a subject metadata set is tested in accordance with D.2 of this International Standard. c) Reference: 2.3. d) Test Type: Basic. D.4 Metadata profiles D.4.1 Test case identifier: Metadata profiles a) Test Purpose: to verify that a profile follows the rules specified in this International Standard. b) Test Method: apply tests defined in Clauses D.2 and D.3 of this International Standard. c) Reference: 2.2. d) Test Type: Basic. 110 ISO 2003 All rights reserved

121 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Annex E (normative) Comprehensive dataset metadata application profile E.1 Comprehensive dataset metadata application schema The ISO series of geographic information standards define, in the abstract, the classes of information needed to: 1) model geographic phenomena; and 2) manipulate, manage and understand these models. In order to implement these standards, profiles must be developed. Typically, an information community with special requirements will develop profiles that use the appropriate parts provided by this series of standards. This comprehensive dataset metadata profile is a basic profile. It provides an international standardized profile applicable to a wide range of information communities. of this profile will promote interoperability between information communities. The comprehensive dataset metadata profile is a subset of packages, classes, attributes and relationships defined in Annexes A and B. Only the classes, attributes and relationships necessary to fulfill the requirements for general-purpose dataset metadata are present. The following are changes that were made to create the profile: Removed MD_ServiceIdentification class from the Identification information package Replaced simple conceptual types (Binary, Boolean, CharacterString, Date, DateTime, GenericName, Integer, and RecordType) with ISO/TS equivalent types Replaced simple conceptual type, CharacterString, with the newly-defined XML type, nonnullstring (based on the ISO/TS CharacterString type), in cases where the attribute is not optional Replaced simple conceptual type Real with newly-defined types (decimallatitude, decimallongitude, nonnegativedecimal, and positivedecimal), which are based on ISO/TS type, Decimal, in contextually appropriate cases, otherwise with the ISO/TS type, Decimal Replaced simple conceptual type TM_PeriodDuration with the XSD-equivalent type, duration Replaced complex conceptual types MemberName and Record with ISO/TS equivalent types Replaced complex conceptual types GF_AttributeType and GF_FeatureType with ISO equivalent types Replaced complex conceptual types (Angle, Distance, GM_Object, GM_Point, Measure, TM_Primitive and UomLength ) with newly-defined XML-equivalent types Removed the Metadata application package (which contained classes of geographic information to which metadata applies eg. DS_Aggregate, DS_Dataset, DS_Initiative, DS_OtherAggregate) Removed the aggregate relationship between MD_Distribution and MD_Format Constrained the implementation of the EX_BoundingPolygon s polygon attribute to be a Box (upper and lower corner Points) or Polygon (outer and inner bounding Rings) Changed all non-conforming class associations (e.g. two-way association, one-way ByReference or Unspecified aggregation) to be one-way ByValue aggregation relationships ISO 2003 All rights reserved 111

122 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL E.2 Comprehensive dataset metadata profile UML model The comprehensive dataset metadata profile is presented in a UML metadata application schema, Figure E.1. The attributes within each class and codelist have not been displayed in the model in order to simplify the diagram. Note that the diagram does not reference the relevant application schemas for the conceptual model since all conceptual types from these schemas have been replaced with other XML equivalent types. The models of these XML equivalent types are also not displayed in order to simplify the diagram. DQ_DataQuality (from Data quality information) +dataqualityinfo 0..* +metadataconstraints 0..* MD_Constraints (from Constraint information) <<Abstract>> MD_Identification (from Identification information) +identificationinfo 1..* MD_SecurityConstraints (from Constraint information) MD_LegalConstraints (from Constraint information) MD_DataIdentification (from Identification information) +referencesysteminfo 0..* MD_ReferenceSystem (from Reference system information) MD_CRS (from Reference system information) MD_PortrayalCatalogueReference (from Portrayal catalogue information) +portrayalcatalogueinfo 0..* MD_Metadata (from Metadata entity set information) +contentinfo 0..* <<Abstract>> MD_ContentInformatin (from Content information) MD_MaintenanceInformation (from Mantenance information) +metadatamaintenance spatialrepresentationinfo 0..* <<Abstract>> MD_SpatialRepresentation (from Spatial representation information) MD_CoverageDescription (from Content information) MD_ApplicationSchemaInformation (from Application schema information) +applicationschemainfo 0..* MD_FeatureCatalogueDescription (from Content information) MD_MetadataExtensionInformation (from Metadata extension information) +metadataextensioninfo 0..* MD_VectorSpatialRepresentation (from Spatial representation information) MD_GridSpatialRepresentation (from Spatial representation information) MD_Distribution (from Distribution information) +distributioninfo 0..1 Figure E.1 Comprehensive dataset metadata profile 112 ISO 2003 All rights reserved

123 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Annex F (informative) Metadata extension methodology F.1 Metadata extensions methodology The following nine-stage methodology should be followed in order to define additional metadata. F.2 Review of existing metadata elements (Stage 1) Stage 1 of the methodology is intended to ensure that only valid extensions are made to the standard set defined by ISO A full review of the standard set of metadata described in Annex B and any formally documented/published profiles should be conducted. This review should not only cover the metadata entity/element name, but also the definition, data type, obligation, domain, and the maximum number of s. It is possible that a new entity/element is not required as an existing entity/element meets the requirements. If a suitable entity/element can be identified, then the relationships of this entity/element should be reviewed with those in Annex A to ensure that the candidate entity/element is not precluded by excluded combinations with other entities/elements. METHOD: EITHER I) An existing metadata element or entity is identified as meeting the requirement. ACTION - Utilize the existing metadata entity/element, no metadata extensions are required. II) A new section of metadata entities is needed to meet the new requirement. ACTION - Go to Stage 2. III) An existing metadata element is identified whose domain could logically be restricted to meet the identified requirement by taking the action of limiting the existing free text domain. ACTION Go to Stage 3. IV) An existing metadata element is identified whose domain could logically be expanded to meet the identified requirement by taking the action of adding values to the existing codelist. ACTION Go to Stage 4. V) A new metadata element is needed to meet the requirement. Check that no existing metadata element could be modified to meet the requirement. ACTION - Go to Stage 5. VI) A new metadata entity is needed to meet the requirement. A metadata entity is a group of related elements, that in conjunction, meet the needs of the new requirement. Check that no existing metadata entity could be modified to meet the requirements by the addition of metadata elements. ACTION - Go to Stage 6. VII) An existing metadata element or entity or section meets the requirement, but the profile requires that a more stringent obligation is applied than that defined in this International Standard. The metadata obligations defined in the ISO cannot be relaxed in a profile. ACTION - Go to Stage 7. ISO 2003 All rights reserved 113

124 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL VIII) An existing metadata element meets the requirements, but the domain required by the profile is a subset of the ISO domain. ACTION - Go to Stage 8. F.3 Definition of a new metadata section (Stage 2) A new metadata section is to be defined, but no existing metadata section from ISO is suitable, nor can any existing section be expanded to meet the requirement. In this case, a new metadata section may be defined. The new metadata section should be defined in a style consistent with that of ISO (which is based on ISO/IEC ). METHOD: I) Go to Stage 5 to define the new metadata elements required to populate the section. II) Go to Stage 6 to define the new metadata entities required to populate the section. III) Go to Stage 9. F.4 Definition of a new metadata codelist (Stage 3) An existing metadata element is suitable, given that the free text domain of the identified element is restricted. No existing metadata codelist can be identified within the metadata standard that meets the requirements. In this circumstance a new metadata codelist may be defined to meet the specific requirements of the profile. The new metadata codelist should be defined in a style consistent with that of ISO (which is based on ISO/IEC ). METHOD: I) Define the new metadata codelist in terms of Definition (B.1.4), Name (B.1.2), and Short Name (B.1.3). The definition of the new codelist should be done so as to be consistent with the existing codelists which can be found in Clause B.5. II) Define the new metadata codelist elements in terms of Definition (B.1.4) and Domain code and Short Name (B.1.3). This definition should also be done so as to be consistent with the existing codelist elements found in Clause B.5. III) Got to Stage 9. F.5 Definition of a new metadata codelist element (Stage 4) An existing metadata element is suitable, given that the metadata codelist of the identified element is expanded. The new metadata codelist elements should be defined with reference to the existing set of elements. The expanded metadata codelist must be a logical expansion of the standard set of values. If the proposed new metadata domain element does not logically build upon the original domain then it may be that the identified element is not suitable for expansion, and the developer should return to Stage 1. To document the new metadata codelist element go to Stage ISO 2003 All rights reserved

125 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) F.6 Definition of a new metadata element (Stage 5) No existing metadata element can be identified within the metadata standard that meets the requirements. In this circumstance a new metadata element may be defined to meet the specific requirements of the profile. The new metadata element should be defined in a style consistent with that of ISO (which is based on ISO/IEC ). METHOD: I) Using the metadata schema described in Annex A and the data dictionary given in Annex B and any existing extensions to the metadata standard, identify the existing metadata entity to which the new element should be added. If no suitable grouping can be found then go to Stage 6. II) Define the new metadata element in terms of the extended element information as described in B : name, shortname, domaincode, definition, obligation, condition, datatype, domainvalue, maximumoccurence, parententity, rule, rationale and source. Identify any excluded metadata relationships with the newly defined element. See Annex A for the metadata UML model. III) Utilize the new metadata element to meet the requirement. IV) Go to Stage 9. F.7 Definition of a new metadata entity (Stage 6) No existing metadata element or entity can be identified within the metadata standard that meets the requirements, nor can an existing metadata entity be modified by the addition of simple metadata elements to meet the requirements. In this circumstance a new metadata entity may be defined to meet the specific requirements of the profile. The new metadata entity should be defined in a style consistent with that of ISO (which is based on ISO/IEC ). METHOD: I) Using the schema described in Annex A and the data dictionary given in Annex B and any existing extensions to the metadata standard, identify which grouping of metadata best describe the function of the new Metadata entity. Choose from: Metadata entity set Identification Constraints Data quality Maintenance Spatial representation Reference system Content ISO 2003 All rights reserved 115

126 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Portrayal catalogue Distribution Metadata extension Application schema Extent Citation and responsible party If no suitable grouping can be found then go to Stage 2. II) Define the new metadata entity in terms of the extended element information as described in B : name, shortname, domaincode, definition, obligation, condition, datatype, domainvalue, maximumoccurence, parententity, rule, rationale and source. Data type is Class for a metadata entity. III) Identify the elements that form the metadata entity, by following the steps outlined in Stage 5. IV) Identify any excluded metadata relationships with the newly defined entity. See Annex A for the UML metadata schema models. V) Utilize the new metadata entity to meet the requirement. VI) Go to Stage 9. F.8 Definition of a more stringent metadata obligation (Stage 7) An existing metadata element, entity or section meets the requirement, but the profile requires that the obligation category is more stringent than that defined in the ISO standard. (Where optional (O) is the least and mandatory (M) the most stringent obligation category). METHOD: I) Identify the new Obligation/Condition (B.1.5) value to be applied to the element, entity or section. If the chosen obligation is conditional, then the conditions under which the metadata is to be applied should be identified. The rules for creating conditions can be found in B II) Go to Stage 9. F.9 Definition of more restrictive metadata codelist (Stage 8) An existing metadata codelist meets the requirement, but the profile requires that the elements defined for the codelist be a restricted subset of the standard domain defined in the ISO standard. METHOD: I) Identify the restricted elements needed to meet the new requirement. II) Go to Stage ISO 2003 All rights reserved

127 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) F.10 Documentation of metadata extensions (Stage 9) Once new metadata entities/elements have been defined, it is essential that the changes from the base standard be recorded clearly. The modifications must be recorded in the profile document, in a standard format, which is derived from the ISO document itself and issued as a document along with the dataset and the metadata. Metadata issued according to the profile must also record the changes to the standard metadata set by completing the metadata extension fields defined in ISO (B ). Seven possible types of extensions may be documented: METHOD: Definition of a new metadata section. Definition of new metadata codelist to replace a free text domain. Definition of additional metadata codelist elements. Definition of a new metadata element. Definition of new metadata entity. Definition of a restricted metadata domain. Definition of more stringent metadata obligation. I) Update the metadata extension information field in the metadata for the product. This field should describe the extensions made to the metadata, including a definition of new elements. II) IF a new metadata section is defined: Create a UML schema for the new metadata section based on those from Annex A. III) IF new metadata entities defined: In accordance with ISO/IEC and using B as a template, record the new metadata entity description in terms of name, shortname, domaincode, definition, obligation, condition, datatype, domainvalue, maximumoccurence, parententity, rule, rationale and source. Update the appropriate UML schemas in Annex A with the new extension information. IV) IF new metadata elements defined: In accordance with ISO/IEC and using B as a template, record the new metadata elements description in terms of name, shortname, definition, obligation, condition, datatype, domainvalue, maximumoccurence, parententity, rule, rationale and source. Update the appropriate UML schemas in Annex A with the new extension information. V) IF an existing metadata codelist expanded: In accordance with ISO/IEC and using B and B.5 identify the metadata code list and record the new domain elements as described in B ISO 2003 All rights reserved 117

128 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL VI) IF new metadata codelist created: In accordance with ISO/IEC and using B and B.5 as a template, record the new metadata codelist in terms of name, shortname, definition and datatype. Record any new metadata codelist elements as described in B VII) IF an existing metadata element domain restricted: In accordance with ISO/IEC and using Clause B.1 identify the metadata element and record the modified domain set in terms of datatype and domainvalue. VIII) IF an existing metadata element or entity obligation made more stringent. In accordance with ISO/IEC and using Annex B identify the metadata entity/element and record the modified obligation characteristics in terms of Obligation/Condition (B.1.5). Update the appropriate UML schemas in Annex A with the new extension information. 118 ISO 2003 All rights reserved

129 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Annex G (informative) Metadata implementation G.1 Background G.1.1 Problem statement The body of this International Standard defines the content of a set of metadata elements, their definitions, data types, and inherent dependencies. The logical model of the metadata specifies the content and not the form of implementation or the form of presentation. A primary goal in the management of metadata for geographic data is the ability to access the metadata and the related spatial data it describes. This requires software implementations using common encoding methods to achieve operational use of the metadata for geographic data. Implementation methods are required to provide for the exchange of metadata between data management systems, the presentation of the metadata element tags in a variety of forms and languages, and to ensure means to assess the conformance of metadata produced and made available. G.1.2 Scope and ives This annex provides an overview of methods for the encoding of metadata element structure and content for the purposes of search and retrieval, metadata exchange, and presentation. The intent of this International Standard is to permit flexibility in the local management of the metadata while standardizing the understanding of metadata for geographic data. The intent of this implementation annex is to provide guidance on the creation of a metadata for geographic data service (Clearinghouse) on a local or wide-area network. G.1.3 Granularity of spatial data supported The notion of cataloguing a set of related documents together in a discoverable series is common in map catalogues. With digital spatial data, the definition of what constitutes a dataset is more problematic and reflects the institutional and software environments of the originating organization. Common metadata can be derived for a series of related spatial datasets, and such metadata is generally relevant or can be inherited by each of the dataset instances. Software to support this inheritance of metadata for geographic data within a cataloguing system can simplify data entry, update and reporting. There is a potential hierarchy of re-usable metadata that can be employed in implementing a metadata collection. By creating several levels of abstraction, a linked hierarchy can assist in filtering or targeting user queries to the requested level of detail. The hierarchy should not necessarily be interpreted to require multiple copies of metadata being managed on-line. Conversely, the definition of general metadata can be supplemented by spatially specific metadata that, when queried, either inherits or overrides the general case. Through use of pointers this method can reduce the redundancy of metadata managed at a site and provide for different views of the holdings by users. This hierarchy of metadata can be graphically represented as shown in Figure G.1. ISO 2003 All rights reserved 119

130 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Dataset series Dataset Dataset Feature type Attribute type Feature instance Attribute instance Figure G.1 Metadata hierarchy G.2 Metadata hierarchy levels G.2.1 Dataset series metadata (optional) A dataset series is a collection of spatial data that shares similar characteristics of theme, source date, resolution, and methodology. The exact definition of what constitutes a series entry will be determined by the data provider. Examples of dataset series metadata entries may include: A flight line of digital aerial photographs collected during a single flight with one camera and film type. A continuous scan swathe collected from a satellite using the same sensors on a single orbital pass. A collection of raster map data captured from a common series of paper maps. A collection of vector datasets depicting surface hydrography with associated attribution for multiple administrative areas within a country. The creation of a dataset series metadata level is an optional feature that allows users to consult higher-level characteristics for data search. The definition of this type of metadata may be adequate for the initial characterization of available spatial data, but may not be adequate for detailed assessment of data quality of specific datasets. G.2.2 Dataset metadata For the purposes of this International Standard, a dataset should be a consistent spatial data product instance that can be generated or made available by a spatial data distributor. A dataset may be a member of a data series, as defined in the previous subclause. A dataset may be composed of a set of identified feature types and instances, and attribute types and instances as described in the following four subclauses. On a demand basis, metadata from series and dataset information will be merged to present the user with a view of the metadata at the dataset level of abstraction. Metadata for which no hierarchy is listed are interpreted to be dataset metadata, by default. 120 ISO 2003 All rights reserved

131 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) G.2.3 Feature type metadata (optional) Constructs known as features are grouped with common characteristics. Spatial data services may elect to support feature type-level metadata where it is available and make such metadata available for query or retrieval. Feature Type -level metadata, together with feature instance-, attribute type- and attribute instancelevel metadata, will be grouped into datasets, as defined in the previous subclause. Examples of feature type metadata entries may include: All bridges within a dataset. G.2.4 Feature instance metadata (optional) Feature instances are spatial constructs (features) that have a direct correspondence with a real world. Spatial data services may elect to support feature instance-level metadata where it is available and make such metadata available for query or retrieval. Feature Instance-level metadata, together with feature type-, attribute type- and attribute instance-level metadata, will be grouped into datasets, as defined in G.2.2. Examples of feature instance metadata entries may include: The Sydney harbour bridge. The Golden Gate bridge, in San Francisco. G.2.5 Attribute type metadata (optional) Attribute types are the digital parameters that describe a common aspect of grouped spatial primitives (0-, 1-, 2-, and 3-dimensional geometric s). Spatial data services may elect to support attribute type-level metadata where it is available and make such metadata available for query or retrieval. Attribute type-level metadata, together with feature type-, feature instance-, and attribute instance-level metadata, will be grouped into datasets, as defined in G.2.2. Examples of attribute type metadata entries may include: Overhead clearance associated with a bridge. G.2.6 Attribute instance metadata (optional) Attribute instances are the digital parameters that describe an aspect of a feature instance. Spatial data services may elect to support attribute instance-level metadata where it is available and make such metadata available for query or retrieval. Attribute instance-level metadata, together with feature type-, feature instance-, and attribute type-level metadata, will be grouped into datasets, as defined in G.2.2. Examples of attribute instance metadata entries may include: The overhead clearance associated with a specific bridge across a road. ISO 2003 All rights reserved 121

132 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Annex H (informative) Hierarchical levels of metadata H.1 Levels of metadata At first sight, it can appear that there are many levels of metadata to be maintained. In the majority of cases, this is not so, as only metadata exceptions are defined at lower levels. If the metadata values are not changed, then the metadata is aggregated at a high level. It is anticipated that this situation would be the most common, with additional levels of metadata only being defined as the original data is maintained over a period of time. When the lower levels of the metadata hierarchy are populated, only the revised metadata values are recorded. So, if the distributor of the data remains the same, this need not be carried down the structure. In order to clarify this concept, the following example follows the life cycle of an example set of geographic data. H.2 Example 1) Consider a geographic data provider generating vector mapping data for three Administrative areas (A, B and C). Initially the vector mapping was generated using a common series of paper maps, which were processed in the same way into a vector format. The bulk of the metadata for this initial data could be carried at a single level, (Dataset series). This metadata would describe the quality, citation, source, processing, of the data for the three administrative areas. So, the metadata could be carried exclusively at Dataset Series level. Dataset series Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema 2) After some time alternate vector mapping of Administrative area A becomes available. The metadata would then be extended for Administrative area A, to describe the new quality date values. These values would supersede those given for the Dataset series, but only for Administrative area A. The metadata for B and C would remain unchanged. This new metadata would be recorded at Dataset level. So, additional metadata is required at Dataset level to describe the new Administrative area A data. The minimum level of metadata required to reflect this change would be: 122 ISO 2003 All rights reserved

133 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Dataset series Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent 3) Eventually further data becomes available for Administrative area A, with a complete re-survey of the road network. Again this implies new metadata for the affected feature types. This metadata would be carried at Feature type level for Administrative area A. All other metadata relating to other feature types remains unaffected. Only the metadata for roads in Administrative area A is modified. This road metadata is recorded at Feature type level. So, additional metadata is required at Feature type level to describe the new Administrative area A road data. The minimum level of metadata required to reflect this change would be: Dataset series Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party 4) An anomaly in the road survey is identified, in that all Overhead clearances for the Administrative area A have been surveyed to the nearest metre. These are re-surveyed to the nearest decimetre. This re-survey implies new metadata for the affected attribute type Overhead Clearance. All other ISO 2003 All rights reserved 123

134 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL metadata for Administrative area A remains unaffected. This Overhead Clearance metadata is recorded at Attribute Type level. So, additional metadata is required at Attribute type level to describe the new Administrative area A Overhead Clearance data. The minimum level of metadata required reflecting this change would be: Dataset series Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party Attribute type - Administrative area A - Overhead Clearance Dataset Identification Citation and Responsible Party Data quality 5) A new bridge is constructed in Administrative area A. This new data is reflected in the geographic data for Administrative area A, and new metadata is required to record this new feature. All other metadata for Administrative area A remains unaffected. This new feature metadata is recorded at Feature instance level. So, additional metadata is required at Feature instance level to describe the new Bridge. The minimum level of metadata required reflecting this change would be: Dataset series Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema 124 ISO 2003 All rights reserved

135 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party Attribute type - Administrative area A - Overhead Clearance Dataset Identification Citation and Responsible Party Data Quality Feature instance - Administrative area A - New bridge Dataset Identification Citation and Responsible Party Extent 6) The overhead clearance attribute of the new bridge was wrongly recorded, and is modified. Again this new attribute requires new metadata to describe the modification. All other metadata for Administrative area A remains unaffected. This new attribute metadata is recorded at Attribute instance level. So, additional metadata is required at Attribute Instance level to describe the new Overhead Clearance. The minimum level of metadata required reflecting this change would be: Dataset series Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party Attribute type - Administrative area A - Overhead Clearance Dataset Identification Citation and Responsible Party Data Quality Feature instance - Administrative area A - New bridge Dataset Identification Citation and Responsible Party Extent Attribute instance - Administrative area A - New bridge - Overhead clearance Dataset Identification Citation and Responsible Party Data Quality ISO 2003 All rights reserved 125

136 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Annex I (informative) Implementation examples I.1 Metadata examples Two examples are provided. One example is for a dataset titled Exploration Licences for Minerals. The other example illustrates an extension of the metadata standard. Examples are presented in English. However, countries and users are allowed to use their own natural language(s) in the implementation of this International Standard. I.2 Example 1 Exploration Licences for Minerals The example below is provided in a tabbed-outline format with element values underlined and role names denoted with a +. This example illustrates the hierarchical structure of ISO metadata and is based on an implementation schema that governs the ordering of the elements within the metadata instance document. MD_Metadata +identificationinfo MD_DataIdentification citation:. CI_Citation. title: Exploration Licences for Minerals. date:. CI_Date. datetype: 001. date: abstract: Location of all current mineral Exploration Licences issued under the Mining Act, Exploration Licences provide exclusive tenure rights to explore for mineral resources for up to a maximum of 5 years. Comment is sought on applications for Exploration Licences from numerous sources before granting. Exploration programs are subject to strict environmental and heritage conditions. Exploitation of identified resources must be made under separate mineral production leases. status: 004 pointofcontact:. CI_ResponsibleParty.. contactinfo:.. CI_Contact.. phone:... CI_Telephone... voice: facsimile: address:... CI_Address... deliverypoint: GPO Box city: Adelaide... administrativearea: South Australia... postalcode: country: Australia... electronicmailaddress: pirsa.spatial@saugov.sa.gov.au.. onlineresource: 126 ISO 2003 All rights reserved

137 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E)... CI_OnlineResource... linkage: role: organisationname: Department of Primary Industries and Resources SA.. positionname: GIS Coordinator +resourceconstraints.. MD_Constraints.. uselimitation: The data should not be used at a scale larger than 1: resourceformat.. MD_Format.. name: ArcInfo Export.. version: resourceformat.. MD_Format.. name: MapInfo.. version: 6.0 +resourceformat.. MD_Format.. name: DXF.. version: 14 +resourceformat.. MD_Format.. name: Plotted Maps.. version: Not applicable +resourcespecificusage. MD_Usage. specificusage: d to supply government, industry and the general public with an up-to-date status and extent of mineral exploration activities throughout the State.. usercontactinfo:. CI_ResponsibleParty. role: 007. positionname: GIS Coordinator +resourcemaintenance.. MD_MaintenanceInformation.. maintenanceandupdatefrequency: 002 +descriptivekeywords.. MD_Keywords.. keyword: BOUNDARIES Administrative.. keyword: INDUSTRY Mining Exploration.. keyword: MINERALS Exploration.. thesaurusname:.. CI_Citation.. title: ANZLIC Search Words.. date:... CI_Date... datetype: date: purpose: The dataset was developed to record information necessary for the administration of the Mining Act. spatialrepresentationtype: 001 spatialresolution:.. MD_Resolution.. equivalentscale:.. MD_RepresentativeFraction.. denominator: characterset: 001 topiccategory: 003 topiccategory: 008 extent:.. EX_Extent ISO 2003 All rights reserved 127

138 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL.. +geographicelement.. EX_GeographicBoundingBox... westboundlongitude: eastboundlongitude: southboundlatitude: northboundlatitude: description: South Australia language: en +dataqualityinformation DQ_DataQuality scope:. DQ_Scope. level: dataset +lineage. LI_Lineage. statement: Source Data History: Exploration Licence boundaries were sourced from the official Mining Register licence documents. Licence boundaries are legally defined to follow lines of latitude and longitude. The register has existed since Processing Steps: Coordinates entered by keyboard from licence documents. Linework cleaned to remove duplicate arcs. Data adjusted for accurate state border and coastline. Where appropriate, cadastral parcels removed from licence polygons. Associated attribute data also captured from licence documents. +report. DQ_CompletenessOmission. result:. DQ_QuantitativeResult. valueunit.. uomname: percent. value: Spatial data is 100% complete. Associated attribute data is 100% complete.. DQ_TopologicalConsistency. result:. DQ_QuantitativeResult. valueunit.. uomname: percent. value: The dataset contains no overshoots, undershoots or duplicate lines. All polygons representing licences contain only one label.. DQ_PositionalAccuracy. result:. DQ_ConformanceResult. specification:. CI_Citation.. title: Map Boundries.. date.. CI_Date.. datetype: date: explanation: Most boundary locations are constructed from lines of latitude and longitude, hence are scale independent. The accuracy of other boundaries is dependent upon the source, eg. state border, coastline, cadastre.. pass: 1. DQ_ThematicAccuracy. result:. DQ_QuantitativeResult. valueunit.. uomname: percent. value: Validation checks are performed periodically, resulting in an estimated 99% accuracy. These checks include comparisons between reports from the spatial dataset and the digital Mining Register. +referencesysteminfo MD_ReferenceSystem referencesystemidentifier: 128 ISO 2003 All rights reserved

139 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E). RS_Identifier. code: GDA 94. codespace: DIPR fileidentifier: ANZSA language: en characterset: 001 contact: CI_ResponsibleParty role: 002 organisationname: Department of Primary Industries and Resources SA datestamp: metadatastandardname: ISO metadatastandardversion: FDIS dataset: I.3 Example 2 Example of extended metadata This example illustrates the addition of new metadata entities and an extended codelist that can be used to document a hierarchical classification-based taxonomy. Figure I.1 presents a UML model of the extension information, Clause I.4 provides data dictionary entries for the extended entities and elements. MD_Identification (from ISO Metadata) +thetaxonomysystem descriptivekeywords 0..* MD_Keywords (from ISO Metadata) + keywords [1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusname [0..1] : CI_Citation TaxonomySystem + classificationsystemauthority : CI_Citation + classificationsystemmodifications [0..1] : CharacterString + generaltaxonomicscope [0..1] : CharacterString + identificationreference : CI_Citation + observer [0..*] : CI_ResponsibleParty + identificationtaxonomicprocedures : CharacterString + identificationtaxonomiccompleteness [0..1] : CharacterString MD_Keywords (modified) + discipline + placed + stratum + temporal + theme + taxon (new) Vouchers + specimen : CharacterString + repository : CI_ResponsibleParty +thevouchers +thetaxonomicclassification 0..* 1 TaxonomicClassification + commonname [0..*] : CharacterString + taxonrankname : CharacterString + taxonrankvalue : CharacterString + hiearchialclass [0..*] : TaxonomicClassification Figure I.1 Examples of extended metadata ISO 2003 All rights reserved 129

140 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL I.4 Data dictionary for the extended elements Name Short Name Domain Code Definition Obligation/ Condition Data Type Domain Max Occur Parent Entity Rule Rationale Source Role name: thetaxonomy System taxonomy information on the taxa (1 or more) included in the data set, including keywords, taxonomic system and coverage information, and taxonomic classification system. O Association 1 MD_Identification New Metadata section To provide for documentation of taxonomic information National Biological Information Infrastructure (NBII) Taxonomy System Taxonsys documentation of taxonomic sources, procedures, and treatments. O Class 1 MD_Identification New Metadata section as a class to MD_Identification The set of data elements contained within this class element represents an attempt to provide better documentation of taxonomic sources, procedures, and treatments. National Biological Information Infrastructure (NBII) Classification System Authority classsys information about the Classification system or authority used M Class CI_Citation N TaxonomySystem New Metadata class Together, the Classification system and any modifications made to it represent a significant piece of information concerning the data being documented. National Biological Information Infrastructure (NBII) Classification System Modifications classmod description of any modifications or exceptions made to the Classification system or authority used C / taxonomic classification system modified? Character String Free text 1 classificationsyste mauthority New Metadata attribute Many times a standard system is used, but exceptions are made to specific taxa or groups, this element allows for exceptions or modifications to be described. National Biological Information Infrastructure (NBII) 130 ISO 2003 All rights reserved

141 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name Short Name Domain Code Definition Obligation/ Condition Data Type Domain Max Occur Parent Entity Rule Rationale Source General Taxonomic Scope taxogen description of the range of taxa addressed in the data set or collection. For example, "all vascular plants were identified to family or species, mosses and lichens were identified as moss or lichen." O Character String Free text 1 TaxonomySystem New Metadata attribute To provide the capability to document the taxa addressed in the data set or collection via a free text description. This is especially important with data sets or collections which contain examples of a many taxonomic levels. National Biological Information Infrastructure (NBII) Identification Reference idref information on any non-authoritative materials (e.g. field guides) useful for reconstructing the actual process M Class N TaxonomySystem New Metadata class This information can be useful for someone who wishes to make use of a data set, and perhaps expand on it, following similar procedures National Biological Information Infrastructure (NBII) observer obs information about the individual(s) responsible for the identification(s) of the specimens or sightings, etc. O Class CI_Respo nsibleparty N TaxonomySystem New Metadata class If there are any questions on the identification of specimens or field sightings, this should provide some insight into the data creator. National Biological Information Infrastructure (NBII) Identification Taxonomic Procedures taxonpro description of the methods used for taxonomic identification. Could include specimen processing, comparison with museum materials, keys, and key characters, chemical or genetic analyses, etc. M Character String Free text 1 TaxonomySystem New Metadata attribute National Biological Information Infrastructure (NBII) ISO 2003 All rights reserved 131

142 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name Short Name Domain Code Definition Obligation/ Condition Data Type Domain Max Occur Parent Entity Rule Rationale Source Identification Taxonomic Completeness taxoncom information concerning the proportions and treatment of unidentified materials (i.e. materials sent to experts, and not yet determined); estimates of the importance, and identities of misidentifications, uncertain determinations, synonyms or other incorrect usages; taxa not well treated or requiring further work; and expertise of field workers. O Character String Free text 1 TaxonomySystem New Metadata attribute National Biological Information Infrastructure (NBII) Role name: thevouchers voucher information about the voucher Association Vouchers Vouchers information on the types of specimen, the repository, and the individuals who identified the vouchers. C / vouchers used? Class N TaxonomicSystem New Metadata class National Biological Information Infrastructure (NBII) 132 ISO 2003 All rights reserved

143 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name Short Name Domain Code Definition Obligation/ Condition Data Type Domain Max Occur Parent Entity Rule Rationale Source specimen specimen word or phrase describing the type of specimen collected (e.g. herbarium specimens, blood samples, photographs, individuals, or batches). M Character String free text 1 Vouchers New Metadata attribute National Biological Information Infrastructure (NBII) Example: "herbarium specimens" "blood samples" "photographs" "individuals" free text repository reposit information about the curator or contact person and/or agency responsible for the specimens. M Class CI_Respo nsibleparty 1 Vouchers New Metadata class If, for any reason, the specimens should need to be referred to, information about where they are being housed and who is responsible for them should be kept along with the documentation of the data set. If they have not been archived, this should be noted. National Biological Information Infrastructure (NBII) Role name: thetaxonomic Classification information about the taxonomic classification M 1 ISO 2003 All rights reserved 133

144 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Name Short Name Domain Code Definition Obligation/ Condition Data Type Domain Max Occur Parent Entity Rule Rationale Source Taxonomic Classification Taxoncl information about the range of taxa addressed in the data set or collection. It is recommended that one provide information starting from the taxonomic rank of kingdom, to a level which reflects the data set or collection being documented. The levels of Kingdom, Division/Phylum, Class, Order, Family, Genus, and Species should be included as ranks as appropriate. For example, if the data set deals with the species "red maple" or Acer rubrum var. rubrum, then the contents might look like the following: M Class 1 Taxonomic Classification New Metadata class To provide the capability to describe precisely the taxa addressed in the data set or collection. This can be accomplished using a hierarchical structure to specify from Kingdom down to the appropriate taxonomic level. National Biological Information Infrastructure (NBII) commonname common specification of applicable common names. These common names may be general descriptions of a group of organisms if appropriate (e.g. insects, vertebrate, grasses, waterfowl, vascular plants, etc.) O Character String free text N Taxonomic Classification New Metadata attribute To provide the capability to describe precisely the taxa addressed in the data set or collection. National Biological Information Infrastructure (NBII) 134 ISO 2003 All rights reserved

145 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Name Short Name Domain Code Definition Obligation/ Condition Data Type Domain Max Occur Parent Entity Rule Rationale Source taxonrank Name taxonrn name of the taxonomic rank for which the Taxon_Rank_Value is provided. See the example included in the definition of Taxonomic_Classifica tion M Character String free text 1 Taxonomic Classification New Metadata attribute To provide the capability to describe precisely the taxa addressed in the data set or collection. National Biological Information Infrastructure (NBII) Example: "Kingdom" "Division" "Phylum" "Subphylum" "SuperClass" "Class" "SubClass" "InfraClass" "Superorder" "Order" "Suborder" "Infraorder" "Superfamily" "Family" "Subfamily" "Tribe" "Subtribe" "Genus" "Species" taxonrank Value taxonry name representing the taxonomic rank of the taxon being described. See the example included in the definition of Taxonomic Classification. M Character String Free text 1 Taxonomic Classification New Metadata attribute To provide the capability to describe precisely the taxa addressed in the data set or collection. National Biological Information Infrastructure (NBII) Hierachical Class hiclass number of recursive sets of taxonomic classification systems O Character String Free text N Taxonomic Classification New Metadata attribute To provide the capability to declare the number of recursive taxonomic classification systems National Biological Information Infrastructure (NBII) ISO 2003 All rights reserved 135

146 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL I.5 MD_KeywordType (Modified) Name Domain code Definition MD_KeywordType Methods used to group similar keywords discipline 001 Keyword identifies a branch of instruction or specialized learning place 002 Keyword identifies a location stratum 003 Keyword identifies the layer(s) of any deposited subsurface temporal 004 Keyword identifies a time period related to the dataset theme 005 Keyword identifies a particular subject or topic taxon 006 Keyword identifies a taxonomy of the dataset 136 ISO 2003 All rights reserved

147 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) Annex J (informative) Multilingual support for free text metadata element J.1 Free text metadata elements In this International Standard a free text element may include multiple instances of information in different languages. Where the language is different from the language defined for the whole dataset, it may be identified, along with an optional attribute that specifies the variant of the language used in a particular country, and the character set used when that differs from the default for the whole dataset. Defined in Clause J.2 are metadata elements that allow for the specification of free text in multiple languages. Optionally, everywhere in this International Standard where free text is specified as the domain the class PT_FreeText can be used. An example of how the free text metadata elements may be used is described in J.3. The metadata element uselimitation is used in the example. It can be found in B.2.3 of this International Standard. ISO 2003 All rights reserved 137

148 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL J.2 Data structure for handling multi-languages support in free text metadata elements Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 1x PT_FreeText PtFreeText description of a multi-language free text metadata element obligation from referencing maximum from referencing Class Line 2x 2x Role name: textgroup textgroup information about the metadata elements required to support multilingual free text fields M N Association PT_Group 3x PT_Group PtGroup description of metadata elements required to support multilanguages in free text metadata elements obligation from referencing maximum from referencing Aggregated Class (PT_FreeText) Lines 2x and 4x-7x 4x languagecode PtLangCode language used for documenting a plain text O 1 Class LanguageCode <<CodeList>> (ISO 639, recommended 3-alphabetic digits code) 5x country PtCountry country of language used for documenting a plain text O 1 CharacterString Country <<CodeList>> (ISO 3166 recommended 3-numeric digits code) 6x charactersetcode PtCharCode full name of the ISO character coding standard used for documenting a plain text O 1 Class MD_CharacterSetCode <<CodeList>> (B 5.10) 7x plaintext PtText content of a free text metadata element M 1 CharacterString Free text 138 ISO 2003 All rights reserved

149 FINAL DRAFT / PROJET FINAL ISO 19115:2003(E) J.3 Example of multi-languages free text in a metadata element The metadata element uselimitation is used in the following example (B.2.3 line 68). Name Short Name Definition Obligation / Condition Maximum Data type Domain 68 uselimitation uselimit limitation affecting the fitness for use of the resource or metadata. Example, not to be used for navigation O N CharacterString Free text Example of multi-languages s on free text metadata element titled uselimitation Language code (Optional) Country code (Optional) Character set code (Optional) Plain text (Mandatory) eng (English) (see Note) 826 (United Kingdom) (see Note) 017 (ISO/IEC ) (see Note) Weight restriction on bridges Lorries exceeding five metric tonnes gross weight are not permitted on bridges fra (French) 017 (ISO/IEC ) Limitation de poids sur les ponts: Les camions dont le poids total excède 5 tonnes métriques ne sont pas autorisés à circuler sur les ponts. ara (Arabic) 011 (ISO/IEC ) zho (Chinese) 029 (GB2312) NOTE If English, United Kingdom and ISO/IEC would have been specified as default values for the entire metadata file, it would not have been necessary to specify them in this. ISO 2003 All rights reserved 139

150 ISO 19115:2003(E) FINAL DRAFT / PROJET FINAL Bibliography [1] ISO/IEC 646, Information technology ISO 7-bit coded character set for information interchange [2] ISO 690:1987, Documentation Bibliographic references Content, form and structure [3] ISO 8601:2000, Data elements and interchange formats Information interchange Representation of dates and times [4] ISO 11180, Postal addressing [5] ISO/TS 19103: 2), Geographic information Conceptual schema language [6] ISO 19104: 2), Geographic information Terminology [7] ISO 19116: 2), Geographic information Positioning services [8] ISO 19119: 2), Geographic information Services [9] ISO 19123: 2), Geographic information Schema for coverage geometry and functions [10] ISO 23950:1998, Information and documentation Information retrieval (Z39.50) Application service definition and protocol specification [11] ISO/TR 19121:2000, Geographic information Imagery and gridded data [12] IETF RFC 1738, Uniform Resource Locators (URL) [13] IETF RFC 2056, Uniform Resource Locators for Z ) To be published. 140 ISO 2003 All rights reserved

151

152 ISO/FDIS 19115:2003(E) ICS Price based on 140 pages ISO 2003 All rights reserved

153 REPORT OF VOTING ON ISO/DIS Closing date of voting Secretariat NSF ISO/TC 211 /SC A report shall be returned to ISO/CS no later than 3 months after the closing date of voting on the DIS, whether or not comments have been reviewed and/or a new text has been prepared. Preliminary report (submitted in those cases where comments are still to be considered and/or a decision has not yet been taken, or where it is decided that the nature of comments indicates a need for further consultation and/or reversion to a previous project development stage). To be followed by a 'Final report'. Any preliminary report is for ISO/CS for information, and is not circulated to member bodies) Final report (submitted either immediately, when all comments have been reviewed and a decision can be taken, or following a 'Preliminary report'. The final report is circulated by ISO/CS to member bodies, and is distributed with any associated DIS or FDIS text) 1 Result of the voting The above-mentioned document was circulated to member bodies with a request that the ISO Central Secretariat be informed whether or not member bodies were in favour of registration of the DIS as a Final Draft International Standard or for publication in the case of unanimous approval. The vote closed on the date indicated above. The replies listed in annex A have been received. 2 3 Comments received Observations of the secretariat See annex B 4 Decision of the Chairman Preliminary report (no annexes required) The comments are under review and/or a decision on further procedure has not yet been taken The project is to revert to the Preparatory Stage (a new working draft will be developed) The project is to revert to the Committee Stage (a new committee draft will be developed) Final report Having received 100% approval from the member bodies voting, the DIS is approved for direct publication without change other than editorial (no FDIS vote) (Option not applicable to projects progressing under the Vienna Agreement) A revised text is to be submitted to ISO/CS for the approval procedure (FDIS vote) A revised text is to be submitted to ISO/CS for a further enquiry (DIS) vote Remarks (e.g. observations on how comments were reviewed, date by which a decision is to be taken, date when a text is expected) There were two negative votes on the DIS. The comments have been resolved in cooperation with the editor Mr. Dave Danko and according to resolution 226 at the Bangkok plenary meeting in May A revised draft is enclosed. FORM 13 (ISO) Page 1 of 2 Version

154 Report of voting on ISO/DIS Enclosures Annex A Result of voting DIS Annex B Comments received with editor/secretariat observations Signature of the Secretary Signature of the Chairman Bjørnhild Sæterøy Date Olaf Østensen Date FORM 13 (ISO) Page 2 of 2

155 Title: Geographic information -- Metadata Document: ISO/DIS Committee: TC 211 Start date (CET): End date (CET): ISO/CS ballot closing date (CET): Voting phase: Enquiry Status: CLOSED Version: 1 Vienna Agreement: RESULT OF VOTING P-Members voting: 25 in favour out of 27 = % (requirement >= 66.66%) (P-members having abstained are not counted in the vote) Member bodies voting: 2 negative votes out of 28 = 7.14 % (requirement <= 25%) APPROVED Country Member Participation Voted Comments file Australia SAI P Approval with comments ISO/DIS_19115_SAI Austria ON P Approval Belgium IBN P Approval Canada SCC P Approval China SAC P Approval with ISO/DIS_19115_SACS comments Czech Republic CSNI P Approval with comments ISO/DIS_19115_CSNI Denmark DS P Approval Finland SFS P Approval France AFNOR O Abstention Germany DIN P Approval Hungary MSZT P Approval Italy UNI P Approval with comments ISO/DIS_19115_UNI Japan JISC P Disapproval ISO/DIS_19115_JISC Kenya KEBS Approval Korea, Republic of KATS P Approval Malaysia DSM P Approval Morocco SNIMA P Netherlands NEN O Abstention New Zealand SNZ P Approval Norway NSF S Approval with comments ISO/DIS_19115_NSF Portugal IPQ P Abstention Russian GOST Federation R P Approval Saudi Arabia SASO P Approval South Africa SABS P Approval

156 Spain AENOR P Approval Sweden SIS P Approval with comments ISO/DIS_19115_SIS Switzerland SNV P Approval with comments ISO/DIS_19115_SNV Thailand TISI P Approval Turkey TSE P Approval United Kingdom BSI P Disapproval ISO/DIS_19115_BSI USA ANSI P Approval with comments ISO/DIS_19115_ANSI Yugoslavia SZS P Approval

157 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 1 IT ge See annex Not accepted, in principle. Italian implementations shouldn t have have MD_Metadata as root. Instead, create profile that permits as many MD_Metadata s as there are number of tiles (where first one is at the parent level) However, to facilitate Italian implementations: 2 IT ge See annex 3 IT ge See annex 4 IT ge See annex add conditional statement that if the MD_Metadata.hieararchyLevel isn t dataset then MD_DataIdentification.topicCategor y is not mandatory (Fig A.2 and Line 41, Table B.2.2), and, add tile to end of MD_ScopeCode (Fig A.7 and Table B.5.25) Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 1 of 68

158 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 5 NO1 ge Normative parts of ISO/DIS have been translated into Norwegian. This work was difficult because many of the English definitions of metadata classes and elements were not good enough. There is a risk that mistranslation (in the process of translating to other languages or by wrong usage at the national level) will lead to different use of the same class or element in different countries, and prevent interoperability. It is unlikely that the definitions can be substantially improved for this version. Could this be a subject for the help desk on implementations under the advisory group on outreach? 6 SE-1 G Sweden appreciates the good work done to ISO The structure of this document regarding data quality is very different from the structure of ISO 19113, Quality principles (QP). This makes it difficult to implement quality in a rational manner. The UML diagrams does not reflect QP:s structure of elements, subelements and descriptors. QP may be difficult to model, which possibly indicates that it is QP that should be restructured. Restructure to harmonise with QP. (Or change QP!) No action for this present version. No action. In UML notation (which this stnd embodies), elements equate to classes and subelements equate to subclasses. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 2 of 68

159 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 7 UK GE The UK considers this draft to be unacceptable as an IS. There are several areas where DIS is inconsistent with other 191xx standards. Whereas it must be a high priority to get these standards published and allow market feedback to start as soon as possible so that they can evolve, it will undermine the fundamental ives of compatibility and inter-working to publish standards which are inconsistent with the other 191xx standards. Some examples to demonstrate this inconsistency are given in the attached detailed comments using But is not the only normative standard with which may conflict. Conflicts with the TC211 projects covering gridded data and imagery are also to be expected. The issue is not whether one of and is better than the other, but the fact that any inconsistency between them creates confusion for users of the 191xx suite of standards. These inconsistencies will potentially lead to conflicting implementations of the [non]standards. The problem will only be resolved by forcing to be consistent with other 191xx normative standards (such as 19111) by making direct reference to those standards. Unnecessary detail in that overlaps with those other standards should be removed. No action. The UK also believes that the core metadata set is still inadequately specified. 8 ANSI Genera l It is not clear how Code Lists are extended. A method for extending CodeLists needs to be given or explained better. Accepted, in principle. New registry work item is handling this. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 3 of 68

160 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 9 ANSI Techni cal 10 ANSI Techni cal 11 JP01 3 te Comment (justification for change) by the MB Proposed change by the MB Secretariat observations The distinctions between identificationinfo>resourceformat, identificationinfo>environmentdescription and identificationinfo>citation>presentationform are not clear.. The distinctions between distributioninfo>distributionformat vs distributioninfo>transferoptions>offline are not clear. ISO/IEC should be added as a normative reference since there are some UML concepts in ISO that are not provided in ISO/TS (e.g. derived classes) 12 SE-2 3 E As normative 5.5 package abbreviations includes references to ISO and ISO these standards should be added in Clause 3. Some guidance or illustration is needed of when each should be used, and the rationale for having this information in three different places explained Some guidance or illustration is needed of when each should be used.. Add ISO/IEC :, Information technology Unified Modeling Language (UML) Part 1: Specification as a normative reference Add normative references to ISO and ISO No Action. The definitions provided are adequate - these could be further explained in a user handbook. No Action. The definitions provided are adequate - these could be further explained in a user handbook. Accepted in principle. However, normative reference to ISO/TS is sufficient (since it refers to itself). Not accepted. ISO and are not needed to implement this standard. 13 JP02 4 ge According to ISO 19104, A.1.8, references to Accepted. standardized definitions shall be presented within square This should be handled by ISO19104 brackets after the definition. project team 14 CSNI and 3 ed Missing punctuation: and SG_Point e.g. Integer and SG Point. e.g. Integer. Accepted. 15 JP te This definition is not harmonized with ISO/TS 19103, Harmonize both definitions consistently Accepted. 16 JP ed There is no "SG_Point" defined in Spatial Schema. "SG_Point" should be replaced by "GM_Point". 17 SE E The definition is not harmonized with ISO But the example in the definition from ISO also includes SG_Point that could be changes to something else. (The package SG is not included in 5.5) Better use GM_Point that exists. the definition from ISO the note from but change SG_Point in the example to GM_Point Accepted (see above). Accepted (see above). 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 4 of 68

161 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 18 SE E The note differs from the one in ISO Harmonize Not accepted. The definition is the same. Notes and examples can be different. 19 JP te This definition is not harmonized with ISO 19123, Harmonize both definitions consistently Accepted. The definition for grid will be changed to: network composed of two or more sets of curves in which the member of each set intersect the members of the other sets in an algorithmic way 20 JP te The term metadata has already been defined in ISO/IEC standards for many years and is widely used. (See 8th comment of Canada on ISO/DIS in ISO/TC211 N 1141) Refer to the English and French existing ISO/IEC definitions for metadata" as stated in ISO/IEC 2382 IT Vocabulary: metadata: Data about data elements, including their data descriptions, and data about data ownership, access paths, access rights and data volatility.{private} métadonnée: Donnée au sujet d'élément de données, y compris leurs descriptions de données, ou donnée au sujet de la propriéte des données, des chemins d'accès, des droits d'accès et de la volatilité des données. Source: ISO/IEC :1999 ( ) Not accepted. The definition will remain as is. The ISO standard referenced is a use of metadata as it applies to data dictionaries. 21 SE E The definition is not harmonized with ISO Harmonize Accepted, in principle. The definition of 'metadata element' in will be harmonized to the 19115's, as per the Editing Committee. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 5 of 68

162 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 22 Se and 4.7 E As NOTE1 in 4.6 and NOTE2 in 4.7 both discusses UML, they should both be named NOTE2 Change order of NOTES for 4.6 Accepted. 23 JP te There is no note like 4.6 and 4.7. The note "Equivalent to a package in UML terminology." should be added. 24 SE E The definition is not harmonized with ISO Harmonize Accepted. Action: Replace model definition with s definition as follows: abstraction of some aspects of a universe of discourse 25 SE Figure 2 E This figure is not as instructive as the corresponding one in e.g. ISO Replace the figure with figure 1 from ISO DIS Accepted. 26 JP Figure 2 ed Mixed fonts in cardinalities Make fonts consistent Accepted. Accepted. Refer to Model Harmonization Team (MHT). 27 JP c) te The definition of datatype is different from UML 1.4. The definition should be; Accepted. "A descriptor of a set of values that lack Refer to Model Harmonization Team identity and whose operation do not (MHT). have side effects. Datatypes include primitive pre-defined types and userdefinable types. Pre-defined types include numbers, string and time. rdefinable types include enumerations." 28 JP g) ed Missing > : <<Metaclass> Change to << Metaclass>> Accepted. 29 ANSI 6.2 Figure 3 Editori al The part-whole relationships between datasets and aggregates are shown in Figure 3. However, the DS package is not fully documented in Annex A and Annex B. Add an attribute to MD-Metadata which supports describing the relationship beween datasets and aggregates. Add it to Annex A and B Accepted. Solution provided in OGC comments related to addition of MD_AggregateInformation. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 6 of 68

163 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 30 OGC 6.2 B.2.1 B.2.2 Figure 3 Figure A.1 Figure A.2 Editori al The part-whole relationships between datasets and aggregates are shown in Figure 3. However, the DS package is not fully documented in Annex A and Annex B. Add the attribute dataset to MD_Metadata to represent the dataset to which metadata applies. See Attachment A for a summary of changes to the associated figure(s) and data dictionary. Create/add a new class MD_AggregateInformation to the Identification information package to represent dataset aggregation information. See Attachment B a summary of changes to the associated figure(s) and data dictionary. Create an aggregate relationship between MD_AggregateInformation and MD_Identification with a role named aggregationinfo of cardinality of [0..*] (see Attachment B). Accepted in principle. The new attribute dataset will be added to MD_Metadata as an optional attribute. New class depicted in diagram provided in Attachment B is labelled MD_AggregationInformation. Class should be labelled MD_AggregateInformation, as recommended. The data dictionary table for the new class will be added as new clause, B Short name for class MD_AggregateInformation should be AggregateInfo vice aggregateinfo. Short name for attribute initiativetype should be inittype vice initiativetype. Short name for Role aggregationinfo should be aggrinfo. Also, modify by adding the following bullet to indicate that MD_AggregateInformation is an aggregate entity of MD_Identification: MD_AggregateInformation, information about datasets that are aggregate parts of the dataset that the metadata describes Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 7 of 68

164 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 31 AU , Annex A Annex B 32 JP The last sentence of the last paragraph and the first line of Table 2 Figure 3 T Errata: The part-whole relationships between datasets and aggregates are shown in Figure 3. However, although in section 5.5 it is indicated that the DS package is defined in ISO 19115, DS is not documented in Annex A and Annex B here. ed Subclause Name seems to be strange. (See the title of the second column in this template) Delete the specialised classes derived from DS_Aggregate from Figure 3. Move these to a new sub-clause of Annex A. Complete dictionary in Annex B to match. Annex A and Annex B require additional text to describe the DS package. Replace subclause Name by Subclause Number Disagree to delete the specialised classes derived from DS_Aggregate. These classes are present to demonstrate what metadata can apply to. Disagree to add additional text to describe the DS package. Action: However, because it is agreed that the part-whole relationships between datasets and their aggregates needs to be demonstrated, the following actions will be taken: Create a new class MD_AggregateInformation and aggregate it with MD_Identification in Fig. A.2 (as per the OGC recommendation) Move <<CodeList>> s DS_AssociationTypeCode and DS_InitiativeTypCode from Fig. 3 to Fig. A.2 (as per the OGC recommendation) Delete the initiativetype attribute from DS_Initiative in Fig. 3 Delete the associationtype attribute from DS_OtherAggregate in Fig. 3 Send to MHT. Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 8 of 68

165 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 33 SE last line E ISO is earlier referred to as ISO/IEC Write ISO/IEC Accepted. 34 JP th paragraph ed It is strange that single quotation marks are used in only this paragraph. 35 JP th paragraph ed Upside-down double quotation mark: statement and processstep 36 JP th paragraph ed Upside-down double quotation mark: statement and source 37 JP nd paragraph, 1st sentence 38 ANSI Techni cal te "geographicelement" should be "horizontalelement" as the word geographic means not only horizontal but also vertical and temporal. EX_Extent is not properly symmetrical between spatiotemporal dimensions, or between horizontal and vertical dimensions. double quotation marks Inverse the head side mark Inverse the head side mark Replace by "horizontalelement". And, all "geographic" in the term "geographic extent" in ISO/DIS should be changed by "horizontal". Maybe a more normalised solution would be better. Accepted. Accepted. Accepted. 39 CSNI ed Missing reference: Listed below are Listed below (see Table 3) are Accepted. 40 AU Table 3 T Table 3 core would be a good illustration of the profile concept if presented as UML. 41 JP Table 3 te Since core metadata elements are not documented in accordance with data dictionary, it is hard to follow and comprehend them intuitively. 42 JP Table 3 te It is difficult to understand the structure of the core metadata by this table. Show Table 3 core as UML. Rearrange each element in accordance with at least B.2.1 Add UML diagrams shown under the comments. Not accepted. EX_Extent can have vertical dimension. No action. Comment is vague and no specific solution is proposed. Not accepted. Format of table will remain as-is. Not accepted. Format of table will remain as-is. Not accepted. Format of table will remain as-is. 43 JP Table 3 te Since MD_Identification is an abstract class, it cannot be used to make an instance of a core metadata. MD_Identification in this table should be replaced by MD_DataIdentification. Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 9 of 68

166 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 44 JP Table 3 (Dataset reference date) 45 JP Table 3 (Geographic location of the dataset) te te date and datetype are attributes of CI.Date (its role name is date ). As the element geographicidentifier is an attribute of EX_GeographicDescription and it is referred by geographicdescripton as a role of association from MD_DataIdentification, it is necessary to insert geographicdescription between MD_DataIdentification and geographicidentifier. 46 NO2 6.5 Table 3 ed The reference within Geographic location of the dataset (by four coordinates or geographic identifier) (C)" is confusing. The path to MD_DataIdentification.geograhicIdentifier is not precise enough. Either it should be MD_DataIdentification.geographicDescription to be on the same level as MD_DataIdentification.geograhicBox or the reference should show the whole path such as MD_DataIdentification. geographicdescription. EX_GeographicDescription. geograhicidentifier.similar changes to geograhicbox 47 JP Table 3 te rs of this Standard cannot find Maximum s for each core metadata element. 48 JP Table 3 (Distribution format) CI_Citation should be replaced by CI_Citation.date. Put geographicdescription between MD_DataIdentification and geographicidentifier. Change to: (MD_Metadata > MD_DataIdentification.geographicBox or MD_DataIdentification.geographicDesc ription) Define maximum of each metadata element. For example, data set responsible party could be written more than one times. te MD_Distributor is unnecessary to refer format. > MD_Distributer should be removed. Accepted. Accepted in principle. See the response and action for this item in comment Editor 03. Accepted in principle. See the response and action for this item in comment Editor 03. Not accepted. Format of table will remain as-is. Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 10 of 68

167 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 49 JP Table 3 (Reference system) 50 JP Table 3 (Lineage statement) 51 CH1 6.5, A2.4 Table 3, Figure A.4 te Since elements defined in MD_ReferenceSystem do not have a capability to describe the vertical reference system and its datum, it is not necessary to define MD_CRS and RS_ReferenceSystem. It is possible to refer the horizontal and vertical reference systems by RS_Identifiers because it has identifier and authority to access the parameters. For describing spatial reference system, it is recommended to use RS_Identifier only. As the data type, RS_Identifier should have identifier and authority[0..1] for its attributes. te LI_Lineage is a data type of an attribute lineage. Change DQ_DataQuality to DQ_DataQuality.lineage. te The list of core metadata elements contains LI_Lineage.Statement which is part of the aggregate DQ_DataQuality. For datasets a condition implies that DQ_DataQuality.report is a mandatory class and therefore DQ_Element.result (which is a mandatory attribute in DQ_DataQuality.report) should be a core metadata element as well. Add DQ_DataQuality.report to the list of core metadata elements or drop the condition: "reprot" and "lineage" role are mandatory if scope.dq_scope.level = "dataset" Accepted, in principle (e.g. RS_Identifier should be used) However, RS_Identifier can be used to identify a vertical references system. Accepted. Accepted, in principle. The Obligation statement on line 80 in Table B.2.4 shall be changed to read C / lineage not provided? The Obligation statement on line 81 in Table B.2.4 shall be changed to read C / report not provided? Figure A.4 s conditional statement will be changed to read report or lineage role is mandatory if scope.dq_scope.level= dataset. Figure A.5 s lineage role is mandatory if DQ_DataQuality.scope.level = dataset (001) shall be removed. The related constraint in shall be changed to read Either the report or lineage roles of DQ_DataQuality must be present if.. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 11 of 68

168 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 52 UK1 6.5 Table 3 E The table is in a different format from the data dictionary given in Annex B, and it is very difficult to find the details of these elements. Restructure the table with headings: Core metadata element, Metadata element number, Metadata element name, Definition, Obligation/Condition 53 UK2 6.5 Table 3 E Dataset responsible party is a class not an element Replace with full set of elements ( ) 54 UK3 6.5 Table 3 E Geographic location of the dataset is a class not an element Replace with full set of elements ( & 349) 55 UK4 6.5 Table 3 E Spatial resolution of the dataset is a class not an element Replace with full set of elements (60, 61) 56 UK5 6.5 Table 3 E Distribution format is a class not an element Replace with full set of elements (285, 286) 57 UK6 6.5 Table 3 T Additional extent information for the dataset is a class not an element Replace with essential elements (351, 356) 58 UK7 6.5 Table 3 T Reference system is a class not an element Replace with reference system identifier (187) Not accepted. Format of table will remain as-is. The purpose of Table 3 is to provide a short list of core elements, not to repeat the data dictionary. Previous editing committees have voiced that the data dictionary should not be reproduced here. Not accepted. When a class or role is referenced, that implies that the class or role should be instantiated/present. Only the mandatory attributes of that class would then have to be present, along with any other optional attributes the user chooses to provide. It is not necessary to re-produce the full set of elements because UML model and data dictionary provide use constraints. Not accepted (see response to UK2). Not accepted (see response to UK2). Not accepted (see response to UK2). Not accepted (see response to UK2). Not accepted (see response to UK2). 59 UK8 6.5 Table 3 T Online resource is a class not an element Replace with essential element (275) Not accepted (see response to UK2). 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 12 of 68

169 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 60 UK9 6.5 Table 3 T Metadata about metadata is not essential metadata (except for date stamp an point of contact), as it is concerned with the metadataset and not specifically the dataset 61 UK Table 3 T The purpose of the dataset is important discovery metadata Delete Metadata file identifier, Metadata standard name, Metadata standard version, Metadata language, Metadata character set Add new core metadata element "Purpose" (26) 62 UK Table 3 T constraints are important discovery metadata Add new core metadata element " Constraints" (71) 63 CSNI ed Incorrect references: an XML document (J.1) is also provided (J.2). an XML document (J.3) is also provided (J.4). Not accepted. Over the 5 years of development, these are the recommended set of core elements that were arrived at. Not accepted (see response to UK9). Not accepted (see response to UK9). Accepted. 64 JP nd sentence ed Incorrect clause reference: J.1 Change to J.3 Accepted. 65 JP rd sentence ed Incorrect clause reference: J.2 Change to J.4 Accepted. 66 OGC Annex??? Editori al Create an additional informative annex containing the XML schema implementation of the conceptual model. Provide the content for the suggested annex during a future editing session. 67 JP27 A.1 Last sentence ed Missing punctuation Add period at the tail of the last sentence 68 CH2 A in general, e.g. A.2.1 and A.2.10 UML schemas in general, e.g. figures A.1 and A.12 ge According to the UML definition some part ( of the subclass) of an aggregation can be related to several wholes (s of the superclass). But e.g. in figures A.1 and A.12 an of the class MD_Distribution contains data as value of the attribute transfersize (in the associated class MD_DigitalTransferOptions), which can only be used by one of the class MD_Metadata. Check the aggregations in the UML diagrams of Annex A and replace by compositions if necessary 69 JP28 A.2.1 Last sentence ed Missing punctuation Add period at the tail of the last sentence Accepted in principle. The XML schema is presented in a Technical Specification that has been submitted as a TC211 New Work Item Proposal. Accepted. Not accepted. The aggregation relationships are valid. Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 13 of 68

170 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 70 JP29 A.2.1 Figure A.1 ed The characters of role name +distributioninfo are overlapping with the class MD_Metadata box. 71 CH3 A.2.1 Figure A.1 te The attribute MD_Metadata.parentIdentifier represents a recursive association and should therefore be modeled as such. 72 ANSI A.2.1 A.2.8 Figure A.1 Figure A AU 03 A.2.1, A.2.8 Figure A.1, Figure A AU 16 A Figure A.1 + NEW Table or diagram Techni cal T T Shift it to left a little bit Model the recursive association as such. Accepted. Action for MHT: clean up all figures so that all text (element names, notes, etc) are visible in all Figures. Not accepted. parentidentifier is the file identifier of the direct parent to which this set is a subset (e.g. not of all parents). MD_ContentInformation should be <<Abstract>> Change the stereotype to <<Abstract>>. Accepted in principle. Figures A.1 and A.10 will updated as proposed. In addition, B.2.8 line 232 (MD_ContentInformation) and B.2.1 line 16 (Role name: contentinfo) will be updated to indicate that this is an abstract stereotype. Send to MHT. Errata: MD_ContentInformation stereotype is not shown Need to provide a mechanism to record general relationships between a dataset and external resources: e.g. to MD_DataIdentification add +related[0..*]:md_identifier, or +related[0..*]:md_relatedentity, which has three attributes: an identifier (e.g. URI, SAP code), a role (e.g. ancestor dataset, associated project) a type (dataset, project) MD_ContentInformation should show <<Abstract>> Add +related[0..*]:md_relatedentity to MD_DataIdentification Accepted. Send to MHT. Accepted, in principle. Solution provided in OGC comments (#30) related to addition of MD_AggregateInformation. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 14 of 68

171 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 75 AU 02 A.2.1, B.2.1 Figure A.1 T Cardinality of MD_Metadata::contact[1] is too limited. This probably suits statutory data providers, but limits the application of ISO elsewhere. Adjust cardinality of MD_Metadata::contact to [1..*] Accepted. Send to MHT. 76 CSNI A.2.2 Fig. A.2, box MD_TopicCateg orycode ed Incorrect spelling: +climatologymeterology +climatologymeteorology Accepted. Send to MHT. 77 AU 04 A.2.4 Figure A.4 T Errata: DQ_Result stereotype is incorrect DQ_Result should show <<Abstract>> Accepted. Send to MHT. 78 ANSI A.2.4 Figure A.4 Techni cal DQ_Result should be <<Abstract>> Change the stereotype to <<Abstract>>. Accepted. Send to MHT. 79 AU 14 A.2.4 Figure A.4 T A DQ_QualitativeResult is required Add a DQ_QualitativeResult in parallel with DQ_ConformanceResult & DQ_QuantitativeResult 80 AU 05 A.2.5 Figure A.7 T Errata: Missing aggregation relationship from MD_Identification (role=resourcemaintenance) to MD_MaintenanceInformation, Missing aggregation relationship from MD_Metadata (role=identificationinfo) to MD_Identification 81 AU 15 A.2.5 Figure A.7 T MD_MaintenanceInformation : Add an attribute to allow recording of who has responsibility for maintaining the metadata Add the missing relationships Add +contact[0..*]:ci_responsibleparty to MD_MaintenanceInformation Not accepted. Additional class not required. Not accepted. These roles are already represented in Figure A.2. Accepted. Action: Add entry in B.2.5 for contact, using recommended definition (shortname of maintcont ), cardinality and type. Modify Fig. A.7 accordingly. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 15 of 68

172 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 82 ANSI A.2.5 Figure A.7 Techni cal Missing aggregation relationship from MD_Identification (role=resourcemaintenance) to MD_MaintenanceInformation 83 JP30 A.2.7 Figure A.9 te The cardinality of obliquelinepointparameter cannot be just one since at least two points are necessary to describe an oblique line. 84 UK12 A.2.7 B Figure A.9 T The detail given here is different from that given in Details of the coordinate system are missing from 19115, including axis information which gives the positive direction and order of coordinates. MD_CRS is subclassed as an aggregation of MD_ProjectionParameters and MD_EllipsoidParameters with MD_ProjectionParameters being an aggregate of MD_ObliqueLineAzimuth and MD_ObliqueLinePoint is inconsistent with In CRS is an aggregation of datum and coordinate system and conditionally also of projection. Projection is an aggregation of coordinate operation method and appropriate coordinate operation parameter values. Add the relationship. Replace 0..2 by 0,2 Not accepted. This role is already represented in Figure A.2. Accepted. Send to MHT. Not accepted. The ISO is expected to be different because while the defines an actual coordinate system, metadata is intended to simply identify the CRS used by the dataset (not to redefine the CRS used). Same comment applies to discussion of Projection. B B Lines Lines The ellipsoid parameter definition is identical in intent but differs in detail from the provisions of table 6. The conditions of applicability also differ. This information is a subset of projection parameters which are given in B Delete B Delete B Disagree. A simple reference to the applicable standards was attempted in earlier versions of this standard and it didn t work; the other standards didn t meet the requirements for metadata. B Lines This information is a subset of projection parameters which are given in B Delete B ( ditto ) 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 16 of 68

173 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 85 ANSI A.2.7 B B Lines The projection parameters listed are a subset of those possible. Figure A.9 Techni cal All that is required in is to refer to the provisions of 19108, and Additional attributes are required to provide an alternate way to identify a coordinate reference system 86 AU 06 A.2.8 Figure A.10 The class diagram for MD_Identifier is currently duplicated in both Figure A.9 and A.10 with references to both B.2.7 (where it is defined) and B.2.8 (where it isn t). 87 AU 07 A.2.10 ` T Errata: Missing aggregation relationship from MD_Identification (role=resourceformat) to MD_Format 88 ANSI A.2.10 Figure A.12 Techni cal Missing aggregation relationship from MD_Identification (role=resourceformat) to MD_Format 89 JP31 A.2.10 Figure A.12 ed Misspelling (duplicating the letter t ) in the upper conditional statement: distributorformatt Delete B Delete lines Lines then refer directly to 19108, and without conflict. Add two attributes to RS_Identifier codespace and version (See A Below) Remove MD_Identifier class diagram From Figure A.10. Add the missing relationship. Add the relationship. Change to distributorformat ( ditto ) The UK should provide a list of all possible projection parameters, but, since none was provided, no action taken. Disagree. See comment applicable to B2.7.1 B (above). Accepted in principle. The codespace attribute will be added as an optional attribute. The attribute version will be added as proposed. Send to MHT. Accepted. Send to MHT. Not accepted. This role is already represented in Figure A.2. Not accepted. This role is already represented in Figure A.2. Accepted. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 17 of 68

174 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 90 JP32 A.2.12 Figure A.14 te Figure A.14 illustrates the association between MD_ApplicationSchemaInformation and MD_SpatialAttributeSupplement to describe featurecataloguesupplement. However, MD_SpatialAttributeSupplement cannot be a feature catalogue. Classes under MD_ApplicationSchemaInformation should be eliminated if they do not illustrate feature catalogues. Define the entity for feature catalogue to allow the citation to feature catalogues from the application schema entity. Accepted. The entity for feature catalogue information is already defined as MD_FeatureCatalogueDescription (Fig. A.10) Action: Remove the classes under MD_ApplicationSchemaInformation from Fig. A.14 Modify by replacing the phrase which is an aggregate of MD_SpatialAttributeSupplement, which is an aggregate of MD_FeatureTypeList with a period, and, by replacing the phrase entities contain with entity contains. Send to MHT. 91 CH4 A2.12, A3.2 Figures A.14 and A16 ge CI_Citation is defined as a DataType in figure A.16 and used as aggregation (in attribute form) in figure A.14. This implies that the same citation data have to be copied to 17 different places if it is used 17 times. If it changes, it has to be changed at 17 different places too. This redundancy is not useful. 92 AU 08 A.3.1 Figure A.15 EX_Extent is very unsymmetrical between spatiotemporal dimensions, and in particular between horizontal and vertical dimensions. Define CI_Citation as class and associate it by aggregation (instead of composition) to the classes where it is used now as attribute A normalised solution would be better. Not accepted. The information in CI_Citation can differ in each instantiation. Accepted in principle. However, since no solution proposed, no action taken. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 18 of 68

175 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 93 AU 17 A.3.1 Figure A.15 T Duplicate functionality between EX_GeographicBoundingBox and GM_Envelope from AU 18 A.3.2 Figure A.16 T CI_ResponsibleParty: A date attribute would enable recording of when the party performed the role 95 AU 19 A.3.2 Figure A.16 T CI_ResponsibleParty: Add an attribute to enable recording of the details of the actions undertaken when the party performed the role 96 AU 20 A.3.2 Figure A.16 T A new identifier structure is introduced, even though MD_Identifier is already available. GM_Envelope (from 19107) in EX_Extent, and deprecate EX_GeographicBoundingBox, EX_VerticalExtent,?EX_TemporalExtent Add +actiondate[0..1]:date to CI_ResponsibleParty Add +actiondetails[0..1]:characterstring to CI_ResponsibleParty MD_Identifier in CI_Citation, instead of the identifier/identifiertype pair. Not accepted. EX_GeographicBoundingBox is a special case and should remain as-is to permit quick searches for extent (e.g. minlat, maxlat, maxlong, minlong). Not accepted. This information is not required; just a nice to have. May include in a profile, if desired. Not accepted. This information is not required; just a nice to have. May include in a profile, if desired. Accepted. Action: Replace the attributes identifier and identifiertype in CI_Citation with the attribute identifier [0..*]:MD_Identifier in Figure A.16 Delete line 366 (identifiertype) in B.3.2 Replace the definition of identifier in line 365, B.3.2, with the definition of MD_Identifier (line 205, B.2.7.2) Replace the Data type CharacterString in line 365, B.3.2, with MD_Identifier Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 19 of 68

176 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 97 ANSI A.3.2 B.5.5 Figure A.16 Techni cal 98 ANSI B Techni cal 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version There is no way to identify an author of a cited reference (From ISO comments) The tables in Annex B include many elements that are identified by role names from the UML model; the data types for these elements is identified as "Association." In fact, a role name is a reerence to a class at the end of the association, and it is the class that holds the pertinent data. 99 JP33 B.1.1 last sentence ed There is no difference between "geographic feature" and "feature" in ISO 191XX series. 100 ANSI B E "shall always be documented" Where? Not obvious in context. 101 JP34 B.1.7 NOTE te This description was valid in the 1st CD stage of ISO and there is no definition of data type in the latest version of ISO any longer. Now sub clause in ISO/TS seems to supersede it. 102 JP35 B.2.1 Line 7 te There is a discrepancy between condition in this line and conditional statements in Figure A JP36 B.2.1 Line 20 te matadataconstraints should provide restrictions about not data but metadata 104 JP37 B.2.2 Line 29 ed Duplicating plural expression in definition: organizations(s) Add author to CI-RoleCode Change data type from "Association" to "Class" for every element identified by a role name. Remove "geographic" to avoid miss understanding. Change to. "This is a descriptor always documented always be documented in the metadata. Change contains value(s) => contains values(the editing committee of said it would make these changes but they are not in the new text. Replace ISO 19118, by ISO/TS 19103, Harmonize both conditions consistently Replace data by metadata Change to organization(s) Accepted. Send to MHT. Not accepted (would be confusing). Accepted. Accepted (second recommendation). Accepted. Accepted, in principle. Will remove the constraints listed in Figure A.1 for hierarchylevel and hierarchylevelname, and, will remove the constraint on Line 6 in Table B.2.1 since it doesn t really apply. Send to MHT. Accepted. Accepted. page 20 of 68

177 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 105 JP38 B.2.2 Line 40 te Element "characterset" is allowed to occur only one Change the Maxmam 1 Accepted. time. But when plural "language" are described, the into N. Action: "characterset" should be allowed plural too. In Fig. A.2, change cardinality of MD_DataIdentification::characterSet from [0..1] to [0..*]. Send to MHT. In table B.2.2, change max. on line 40 from 1 to N 106 CSNI B ed Incorrect spelling: of the datset of the dataset Accepted. 107 JP39 B.2.2 Line 41 ed Misspelling: dataset Change to dataset Accepted. 108 JP40 B.2.3 B JP41 B.2.3 Line and 79 first row ed The title "name" should be "name/role name". Change the title. Accepted in principle. In addition to the referenced clauses, B.2.5, B.2.6, B.2.9, B.2.11, and B.2.12 will be changed as well for consitancy thoughout the data dictionary. te According to line 69, these elements should provide restrictions about not only resource but also metadata Replace resource by resource or metadata Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 21 of 68

178 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 110 SE-10 B.2.4 table and UMLdiagrams 111 SE-12 B.2.4 table 112 SE-11 B.2.4. table 113 SE-13 B table 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version T QP contains three data quality overview elements, purpose, usage and lineage. Purpose and usage is not to be found in the part of Metadata covering quality reporting. B.2.2 contains in line 26 a part named purpose. It is not clear if this is the same purpose as the one in QP as the descriptions differ. No reference is made to this in the UML model. It is furthermore not mandatory, as is purpose in QP. The descriptions and obligations should be the same, or a new term, QP_purpose, should be introduced. B deals with usage information. The description of this differs considerably from the one in QP. This is about current use while QP speaks about all usage that the producer is aware of. This calls for a change of the definition of usage in B or a new term QP_usage. line 79 T Maximum is set to 1. If the referencing is a data quality subelement, multiple scopes may be identified. Make the standard consistent regarding purpose and usage in ways indicated in comment. Change the definition in b and b2.2. Line 26 shall be mandatory. Change maximum to N if appropriate. line 79 T The name is written as scope. If this scope is the same as data quality scope mentioned in QP, the full name should be used. lines 83 to 85 T If the scope level is dataset or smaller is of no interest, lineage is always important. A part of a dataset is also a dataset per definition. According to the UML diagram, lineage is part of the scope and the definition of scope tells that it may be a smaller grouping of data located physically within the dataset. Remove DQ_scope.level = dataset or series. B.2.2: Not accepted. The metadata team wants to keep the number o f mandatory elements to a minimum; and the mandatory element abstract is considered to fulfil this requirement (e.g. suitable to define the purpose should the user desire to indicate the purpose in abstract ). B.2.2.5: Accepted. Change the ending of the sentence in Line 62 from.. is/are currently used to is/are currently or has been used. Not accepted. This requirement can be satisfied by instantiating DQ_DataQuality as many times as is required. Not accepted. The scope is the same as the QP s data quality scope element. However, the metadata team abided by the encoding standard to not repeat the class name (which is DA_DataQualityScope). Not accepted. In past discussions with the QP Team, it was determined to not make Lineage mandatory. page 22 of 68

179 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 114 SE-14 B table 115 SE-15 B table 116 SE-16 B table 117 OGC B Figure A.5 Editori al line 84 E Process steps describe what happens to the dataset after creation. Collection processes are source information. line 86 T Process steps have nothing to do with the creation of the dataset. It is history information that shall cover the life of the dataset after creation, including maintenance. line 88 T No such thing as rationale is mentioned in QP. If Metadata incorporates subjects not in QP, they should occur in that standard as well. Figure A.5 correctly depicts that the attribute statement (LI_Lineage), the role processstep (LI_ProcessStep) and the role source (LI_Source) can coexist. However, table B indicates otherwise (e.g. that statement should only be present if both the roles source and processstep are not provided, and, that either role can only be present if statement is not present and if the other role is not present). Change the definition. Information about events in the life of a dataset specified by the scope. Change the description to cover what is stated in QP. A record of events or transformations in the life of a dataset, including the process used to maintain the dataset whether continuos or periodic, and the lead-time. Harmonise with QP Make the following change to table B.2.4.1: Remove the and source and processstep not present? statement from the Obligation/Conditional entry for the attribute statement. Preface the Obligation/Conditional entry for processstep (Line 84) and source (Line 85) with mandatory if Accepted. Accepted. Not accepted. Metadata group determined that rationale is important for metadata. Accepted. 118 CSNI B ed Incorrect reference: Lines Lines Accepted. 119 SE-17 B table line 89 T It is highly essential, for a dataset that has undergone several processes, to know the order. For this reason, date is important. Transformation parameters may have changed at a certain date. Therefore the date of a transformation is essential to know. Make datetime mandatory. Not accepted. Metadata team wants to keep the number of mandatory elements to a minimum. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 23 of 68

180 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 120 SE-18 B table 121 SE-19 B table 122 SE-20 B table 123 SE-21 B table 124 SE-22 B table 125 SE-23 B table 126 SE-24 B table line 90 T No such thing as processor is mentioned in QP. If Metadata incorporates subjects not in QP, they should occur in that standard as well. line 92 to 98 T QP states that source information shall describe the parentage of a dataset. These lines do not cover this. The level is covered in the scope, the denominator is just one tiny bit of information regarding a map as is also the datum. Spatial information has nothing to do with parentage and should be covered by the scope. The most important thing, where the data does come from, is not even part of the list. Line 98 is obsolete as process steps report what happens to the dataset after creation. See comment about line 86 Heading T This is not information about data quality elements but about data quality subelements. The descriptors belong to them, not to the data quality elements. The data quality elements are just logical themes into which the subelements are grouped. line 99 T A data quality element or subelement is certainly not a type of test. line 100 T As QP states shall, if the name is known, the name can t be optional. line 101 T No such thing as measure identification is mentioned in QP. Metadata should not add components. Are there really registered standard procedures for percentage, standard deviation etc? Harmonise with QP. Add this in QP. Make a new list covering Responsible party for collection Method of collection Date of collection Reference datum Change the heading to data quality subelements. Change to Aspect of quantitative quality information Change to M Remove this entry from the table. Accepted. Action to QP Editor. Not accepted. All of this information can be specified, if desired, in the element description. Note that Reference system information allows you to specify datum. Note too that source citation describes responsible party. Source and process are used in conjunction with each other. Not accepted. Subelements are, in effect, elements. Furthermore, subelements is not a defined term in this standard. Accepted. line 102 E The words being determined seems out of place. Remove. Accepted. Not accepted (there is no standardized list of tests). Not accepted. The element has been added (and is optional) for metadata purposes. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 24 of 68

181 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 127 SE-25 B table 128 SE-26 B table 129 SE-27 B table 130 SE-28 B table 131 SE-29 B table 132 SE-30 B table 133 SE-31 B table 134 SE-32 B table line 102 T The description is mandatory according to ISO Change to M or C/.not. measid. Not accepted (response to SE-23 applies). line 103 T Evaluation method is only mentioned in the term list in QP and no demands for reporting is made. line 104 T No such thing as description of evaluation method is mentioned in QP. Metadata should not add components. Remove this entry from the table. Remove this entry from the table. line 105 T According to 19113, this is mandatory. Change to M or C/.not. measid. Not accepted. line 106 T According to 19113, this is mandatory. Change to M or C/.not. measid. Not accepted. line 106 T A data quality measure may well be applied on different dates for the same scope. Maybe the problem is caused by the fact that we do not have the full understanding of the word range. line 106 T The standard gives no indication on how to report time intervals. Change 1 to N if range only includes consecutive days Add description on this. line 107 E Outcome should be one word. Correct. Accepted. Not accepted (response to SE-23 applies). Not accepted (response to SE-23 applies). Accepted in principle. Modified cardinality should be [0..*], instead of recommended [1..N] since element is not mandatory. Action: In Fig. A.4, change cardinality of DQ_Element::dateTime from [0..1] to [0..*] Change Maximum on line 106 from 1 to N in Fig. A.4). Not accepted. This is covered in ISO (Temporal). 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 25 of 68

182 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 135 NO3 B Annex B, Line 124 ed Confusing definitions 1. DQ_ThematicAccuracy accuracy of quantitative attributes and the correctness of non-quantitative attributes and of the classifications of features and their relationships Clarify the difference between DQ_ThematicAccuracy and DQ_NonQuantitativeAttributeAccuracy by making the definition better. Accepted. Change DQ_NonQuantitativeAttributeAccuracy definition to what is recommended in NO4. 2. DQ_NonQuantitativeAttributeAccuracy correctness of non-quantitative attributes Both elements have correctness of non-quantitative attributes as the definitions (or part of the definition). Does this mean that the concept of DQ_ThematicAccuracy includes the concept of DQ_NonQuantitativeAttributeAccuracy? Unlikely. 136 NO4 B Annex B, Line 126 ed In the last DIS-version the classname DQ_NonQuantitativeAttributeAccuracy was changed from DQ_NonQuantitativeAttributeCorrectness. We do not have any problems with that, but the definition has not been changed accordingly. Change the definition from correctness of non-quantitative attributes to: Accepted. This resolves comment NO3. Accuracy of non-quantitative attributes Does this also resolve comment NO3? 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 26 of 68

183 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 137 SE-33 B table 138 SE-34 B table 139 SE-35 B table 140 SE-36 B table line 133 T This line and the UML diagram are not in agreement with QP. Here, the result has attributes (lines 136 to 139). In QP, all of them are descriptors of data quality subelements. It may work this way, but than we have lost the connection to QP. The result is not information about the value, it is the value. lines 134 and 135 T These are mandatory in Value (quanval) cannot stand on its own. line 137 T The value is the result or vice versa. The value is not an attribute to the result. line 138 T The definition is sort of circular and makes no sense (content describes the items specified by the content). There is a perfectly adequate definition in QP. 141 JP42 B Line140.(extent) te The word "spatial" in the definition should be "horizontal", as spatial means both horizontal and vertical. 142 ANSI B.2.6 Element 163 transformation parameter availability Editori al " whether parameters for transformation exists" Subject verb agreement Follow the structure in QP and redraw the UML diagrams. After that has been done, these tables can be reconstructed. Change to M. See comment to line 135. extent or characteristic(s) of the data for which quality information is reported. Replace "spatial" by "horizontal". "exists" => "exist" or "are available" (second alternative was in editing committee report. Accepted in principle. The model agrees with the QP s definition of data quality result ; therefore, no changes are required to the model. Action: Modify the definition of DQ_QuantitativeResult to be The value(s) and information about the value(s) Accepted for valueunit. Action: Make valueunit mandatory. Send to MHT. Not accepted for valuetype (will remain optional). Not accepted. No action. This model was worked with and previously approved by the QP and QEP teams. Accepted. Accepted. Accepted (if submitter intended to state Line 161 vice Line 163.) 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 27 of 68

184 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 143 ANSI B.2.6 Element 163 transformation parameter availability Editori al original comment was listed as accepted with modifications, but editing committee reply did not address question of what transformation parameters were for, either by including specifics in text or stating why it was not necessary to do so 144 JP44 B. 2.6 Line 174 ed Name parameters is not suitable for short name georefpars. Change to "whether parameters for transformation between image coordinates and geographic or map coordinates exist (are available)" Change the name into georeferencedparameters. 145 JP43 B.2.6 Line 169 te The definition is almost the same as that of line 168. Make the definition distinctive or remove this line Accepted (if submitter intended to state Line 161 vice Line 163.) Accepted. Send to MHT. Accepted. Action: 146 JP45 B Line 184 te Incorrect explanation in definition Change to name of point or vector s used to locate zero-, one-, twoor three- dimensional spatial locations in the dataset Change the definition on Line 168 (for transformationdimensiondescription ) to be "general description of the transformation." Change the definition on Line 169 (for transformationdimensionmapping ) to be "information about which grid axes are the spatial (map) axes." Accepted. 147 CSNI B ed Superfluous punctuation: the reference system. the reference system Accepted. 148 NO5 B.2.7 Annex B Line 187 ed The shortname does not follow the rules for making tagged names. Change refsysid to refsysid Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 28 of 68

185 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 149 NO6 B.2.7 Annex B Line 188 ed The definition of role name/ Reference System tells us something else than the UML-model in Figure A.9 We have learned that it is the UML-model that is correct if there are inconsistencies. In this case the definition in Annex B seems to be right, but the graphics in the model does not tell the same story. What is the reason of dealing with a derived role name which is Not applicable? Is TM_ReferenceSystem really a subtype of RS_ReferenceSystem? This is not stated in DIS 19111(Figure B1). Clarify what is right and correct the model in annex A or the definition in annex B in accordance to this. 150 CSNI B ed Incorrect capital letter: Identity identity Accepted. 151 JP46 B ed Unnecessary vertical space between Line 202 and Line Reduce this vertical space Accepted UK13 B T These provisions conflict with ISO as described through ISO section 6.6. Provision for identifier/citation information should be made in the normative references. Delete B Agreed in principle. Action: Remove the derived characteristic from all currently derived attributes in the Reference system information package. Send to MHT. Action: Remove the role ReferenceSystem and the subclasses of RS_ReferenceSystem (e.g. SC_CRS, TM_ReferenceSystem and SI_SpatialReferenceSystemUsingGe ogrpahicidentifiers). Modify by removing the last two sentences. Send to MHT. Not accepted. Previous discussions on this topic resulted in the agreement that two attributes would be added to RS_Identifier and that RS_Identifier would remain subclassed to MD_Identifier. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 29 of 68

186 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 153 NO7 B Annex B Line 208 ed A Norwegian comment (NO5) on a previous DIS version has not been accepted. We are not sure of if the comment was understood correctly. We can't see the need of dealing with the class RS_Identifier as long as it contains the same elements (authority and code) as MD_Metadata using the same domain (CI_Citation and free text). This procedure has not been used elsewhere, and it does not help us much. We don t see that the use of RS_Identifier is a narrowing of the term MD_Identifer. The fact that the domain reference for geographicidentifier (line 349) and others were changed from RS_Identifiers to MD_Identifiers also support this CSNI B ed Incorrect position of the space between words: scaling tot he actual Change RS_Identifier to MD_Identifier within the whole standard. scaling to the actual Agreed, in principle. However, since two new attributes have been proposed to be added by OGC to RS_Identifier, and have been accepted, RS_Identifier will not be changed to MD_Identifier in the standard. Accepted. 155 JP47 B Line 229 ed Misspelling: tot he Change to to the Accepted. 156 CH5 B2.8 Row 233 ed ISO/DIS recommends the use of a conceptual schema language to model feature catalogue information. We suggest reflecting this recommendation in the definition of MD_FeatureCatalogueDescription. 157 CSNI B ed Duplication of the word: count of the number the number of lossy Add to the definition the underlined text: Information identifying the feature catalogue or the conceptual schema count of the number of lossy Accepted. Accepted. 158 JP48 B.2.8 Line 250 ed Duplicate phrase: the number Remove this phrase Accepted. 159 JP49 B Line 300 te dataset in definition should be resource considering term coincidence with line 298 and line 299 Replace dataset by resource Accepted. 160 CSNI B ed Superfluous punctuation: metadata element. metadata element Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 30 of 68

187 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 161 NO8 B and B.5.21 Annex B Line 310 ed The domain reference does not follow the rules for naming Change <<enumeration>> to <<Enumeration>> Accepted. Action: make suggested change to the following: Title of table B.5.21 Domain entry on Line 311 Stereotype of MD_ObligationCode model in Figure A JP50 B.2.12 Line 325 te The data type of this file could be binary, as graphics files cannot be represented by using text format. 163 JP51 B.2.12, B and B JP52 B.3.1 Extent Information EX_Extent Replace CharacterString in data type and Free text in domain by Binary respectively Send to MHT. Accepted. Send to MHT. te See JP32 Accepted (as per response to JP32). Action: Remove Line 328 (Role featurecataloguesupplement ) from B.2.12 Remove table B (Featuretype list information) from the data dictionary Remove table B (Spatial attribute supplement information) te "spatial" should be "horizontal". See JP42. Replace by "horizontal". Accepted. 165 JP53 B.3.1 Line 336 te The title of this element should be renamed as Replace geographicelement by Not accepted. horizontalelement, because verticalelement also horizontalelement EX_BoundingPolygon can provide both describes the geographic extent. By the way, most vertical and horizontal extent (e.g. 2-dim geographic identifiers are horizontal. or 3-dim). 166 CSNI B ed Incorrect capital letter: Description description Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 31 of 68

188 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 167 JP54 B Geographic Extent information ed See JP15 Not accepted. Response to comment to JP15 applies. 168 JP55 B Line 343 te Note documented in definition should be eliminated because the extent is represented by longitude and latitude. Remove note statement Not accepted. Note has been proven to be very necessary. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 32 of 68

189 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 169 UK14 B Line 343 T The note in the definition uses terminology which is inconsistent with ISO Change 'coordinate system' to 'coordinate reference system' Agreed that coordinate system should be changed to coordinate reference system. B B B Line 343 Line 358 Lines The provisions for horizontal and vertical coordinates are inconsistent. Horizontal extent, according to 343, is approximate and does not require CRS to be identified. Vertical extent, in line 358, requires the CRS to be identified. The provision for user-defined height units is inconsistent with the requirement to give horizontal coordinates in degrees. For metadata purposes ISO standard units should be mandated. (i) Delete line 358. (ii) Add the note in the description in line 343 to line 341. (iii) Add the note in the description in line 343 to line 354. (i) delete line 357. (ii) in lines 355 and 356 replace extent contained with extent in metres contained Disagree to (i), (ii) and (iii). The vertical datum is required because a vertical coordinate system requires a datum as reference. The reason why CRS is not required for horizontal coordinates (e.g. EX_GeographicBoundingBox) is because the units and the unit range are specified for the attributes of EX_GeographicBoundingBox. However, CRS is required for vertical extent because the user must specify height units of measure and origin. It should be noted that EX_GeographicBoundingBox is a special purpose class to facilitate search for datasets. In both the EX_BoundingPolygon and EX_VerticalExtent, the user must specify the CRS and units. Disagree to (i) delete line 357. Disagree to (ii) in lines 355 and 356 replace extent contained with extent in metres contained. rs must be allowed to specify height units and origin. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 33 of 68

190 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 170 JP56 B Line 351 te TM_Primitive is difficult to implement the temporal extent. This element should be separated to two. The first is beggingvalue that is the begging instant represented by TM_CalDate. The second is endvalue that is the end instant represented by TM_CalDate. 171 CSNI B ed Missing quotation mark: of the World of the World Accepted. 172 JP57 B.3.2 Line 361 ed Missing double quotation mark in definition: Digital Change to Digital Chart of the World Accepted. Chart of the World 173 JP58 B.3.2 Line 365 te The example in definition should be specific identifier in contrast with that of line 366. Make the example specific Not accepted. TM_Primitive provides mechanism to specify end date.time and beginning date.time. Accepted in principle. OGC comments recommended two attributes be added to RS_Identifier which should satisfy this request. 174 JP59 B Line 381 ed This element not only is used for delivery but also other The element name should be changed Disagree. purposes. as address, and tag name should be This standard s Editor followed the ISO addrs , Annex A standard. Additionally, making this change would violate the naming convention (e.g. which states that class attributes can t be named same as class that contains them). 175 CSNI B ed Incorrect position of the slash: ISO TS/19103 ISO/TS Accepted. 176 JP60 B.4.3 7th paragraph ed Incorrect name: ISO TS/19103 Change to ISO/TS Accepted. 177 JP61 B.4.4 te The explanations of each metaclass should be reflected in ISO more exactly. Refer the explanation in ISO more strictly 178 JP62 B.4.4 3rd sentence ed Incomplete sentence Add textual information at the top of this sentence. 179 JP63 B.4.5 ed "primitive" is a generic term. Title of this section should be "PeriodDuration and temporal primitive information". Disagree. rs are instructed to refer to ISO for more exacting definitions, if desired. Accepted. Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 34 of 68

191 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 180 JP64 B.5.6 Title ed Insert a space in front of <<CodeList>> Accepted. 181 JP65 B.5.7 Title ed The letter l in <<Codelist>> should be capital letter. Change to <<CodeList>> Accepted. 182 JP66 B.5.8 Line 8 and 10 te nonimagesensor and platform do not seem to be suitable in an initiative point of view. Remove line 8 and 10 Not accepted, in principle. platform is a valid code value. However, "nonimagesensor" should be changed to "sensor." Action: change nonimagesensor to sensor in B.5.8 and Fig. A.2. Sent to MHT. 183 NO9 B.5.10 Annex B, CodeList ed The character set 8859part10 is widely used within Norwegian datasets. To be able to tell this in a metadata service we need to have this included in the CodeList. Include 8859part10 in the list, preferably with domain code 015. Accepted. Action: Modify B.5.10 to include 8859part10 with the following definition: ISO/IEC 8-bit singlebyte coded graphic character sets -- Part 10: Latin alphabet No. 6 Modify Fig. A.2 s MD_CharacterSetCode model to include 8859part10 Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 35 of 68

192 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 184 CN B.5.10 The table T simplified Chinese code set is widely used in China, Singapore and other areas. 185 CN B.5.10 The 4 th column T big5 is used in Taiwan, Hong Kong of China and other areas. 186 NO 10 B.5.13 Annex B CodeList, line 12 ed The MD_DatatypeCode is not named following the rules for making tagged names Add one line as the attached table 1 below. (See Annex) Traditional Chinese code set used in Taiwan, Hong Kong of China and other areas. Change metaclass to metaclass. Accepted, in principle. Action: Add code GB2312 with corresponding Definition provided to end of MD_CharacterSetCode in B.5.10 as recommended. However, the Domain Code assigned will be the next number generated after the insertion of other code values recommended via other accepted comments (e.g. NO9, Editor 12). Add GB2312 to Fig. A.2 Send to MHT. Accepted. Accepted. Send to MHT for correction in Fig. A.13 Metadata extension information. 187 JP67 B.5.15 Line 1 te Same as JP45. Accepted. Change the Definition of MD_GeometricObjectTypeCode in B.5.15 to be identical to what was proposed for JP JP68 B.5.15 Line 2 te The name complexes is not necessarily plural expression. Change to complex Accepted. Change code value as recommended in table and in Fig.A.8 for MD_GeometricObjectTypeCode. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 36 of 68

193 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 189 JP69 B.5.15 Line 3 te The name composites is not necessarily plural expression. Change to composite Accepted. Change code value as recommended in table and in Fig.A.8 for MD_GeometricObjectTypeCode. Send to MHT. 190 JP70 B.5.15 Line 7 ed Missing primitive in definition: geometric Change to geometric primitive Accepted. 191 NO11 B.5.18 Annex B CodeList, line 9,10,11,12 ed Codes 008 and 009 are used twice Make the necessary corrections. Accepted. 192 CSNI B ed Incorrect Domain code: Accepted. 193 JP71 B.5.18 Line ed Incorrect number in domain code: 008, 009 and 998 Change to 010, 011 and 012 respectively Accepted. Change all 3 domain codes, as suggested. 194 CSNI B ed Incorrect Domain code: Accepted. 195 JP72 B.5.21 Title ed The first letter e in <<enumeration>> should be capital letter. Change to <<Enumeration>> Accepted. 196 NO12 B.5.23 Annex B CodeList, line 8 ed The MD_ProgressCode is not named following the rules for making tagged names 197 AU 09 B.5.27 T The CodeList MD_TopicCategoryCode, which contains the values of the mandatory element identificationinfo::topiccategory, is a mixture of subject and functional classifications. It is not comprehensive, and thus precludes the use of ISO for subject areas not included in the list. Change underdevelopment to underdevelopment. An extension mechanism for CodeLists is required. A method for substituting an alternative CodeList is required.. Accepted. underdevelopment will be changed to underdevelopment in table B.5.23 Accepted, in principle. An extension method for codelists is being worked as a new registry work item. Not accepted WRT to extending MD_TopicCategoryCode, which is intended to be a limited codelist. Action: change the stereotype of MD_TopicCategoryCode from <<Codelist>> to <<enumeration>> so that it cannot be extended, except via a new work item. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 37 of 68

194 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 198 ANSI B.5.27 Techni cal 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version The CodeList MD_TopicCategoryCode, which contains the values of the mandatory element identificationinfo>topiccategory, is a mixture of subject and functional classifications. It is not comprehensive, and thus precludes the use of ISO for subject areas not included in the list. 199 JP73 B.5.28 ed Names and definitions of Topological level code are not corresponding with Spatial Schema (19107). 200 NO13 B.5.28 Annex B line 1-10 ed It s hard to understand the use of this MD_TopologyLevelCode because It s difficult to understand the meaning of the definitions. Some of this concepts are better described in DIS Spatial Schema: The porposed change is mostly based on DIS and theory books, and should eventually be checked by a expert if accepted. If possible, the definitions should be further elaborated and exemplified. Complete the list. The table should be changed to follow ISO For example, names can be, primitive aggregate complex composite. Rewrite the definitions or add some examples of use. geometry only - geometry s without any additional structure which describes topology. Commonly called spaghetti-data. topology1d - 1- dimensional topological complex - commonly called chain-node topology planar graph - 1-dimensional topological complex which is planar. A planar graph is a graph that can be drawn in the plane in such a way that no two edges intersects except at a vertex. fullplanargraph - 2-dimensional topological complex which is planar. A 2-dimensional topological complex is commonly called full topology in a cartographic 2D environment Not accepted. Response to AU 09 applies. Not accepted. The Editor confirmed that the values in MD_ToplogyLevelCode are valid. Accepted in principle. Definitions accepted as-is: topology1d topology3d abstract Slightly modified definitions (WRT to grammar and mathematical validity) that will replace existing definitions: geometryonly - geometry s without any additional structure which describes topology planargraph - 1-dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in the plane in such a way that no two edges intersects except at a vertex.) fullplanargraph - 2-dimensional topological complex that is planar. (A 2- page 38 of 68

195 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations cartographic 2D environment. surfacegraph - 1-dimensional topological complex which is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimension-and boundary-preserving correspondence to one another.) fullsurfacegraph - 2-dimensional topological complex which is isomorphic to a subset of a surface topology3d - 3-dimensional topological complex. A topological complex is collection of topological primitives that is closed under the boundary operations dimensional topological complex is commonly called full topology in a cartographic 2D environment.) surfacegraph - 1-dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimension-and boundary-preserving correspondence to one another.) fullsurfacegraph - 2-dimensional topological complex that is isomorphic to a subset of a surface. fulltopology3d - complete coverage of a 3D Euclidean coordinate space 201 JP74 C.5 Figure C.1 ed Area boundaries core metadata components and community profile 1 are barely overlapping each other. full Topology3D - complete coverage of a 3D coordinate space abstract - topological complex without any specified geometric realisation Detach both boundaries adequately 202 JP75 C.6 Page 90 ed This page is a blank paper. Reduce this page and decrement the succeeding page numbers Accepted. Accepted. 203 JP76 D.2.2 a) ed Missing punctuation Add a period at the tail of Standard Accepted. 204 JP77 D.3.2 d) ed Missing punctuation Add a period at the tail of Basic Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 39 of 68

196 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 205 CSNI D ed Incorrect reference: with of with 2.3 of Accepted in principle. However, the correct reference should be D JP78 D.3.3 2nd sentence ed The contents of are not for the test. It could be D.2. Accepted. Change the second sentence in D.3.3 to read in accordance with D.2.. vice in accordance with JP79 D.3.3 3rd sentence ed 2.3 is not appropriate for the test. It could be D.2. Disagree. 2.3 is the correct reference. 208 NO14 D.4 D4.1 b) ed We have noticed that we have got a new clause D4. that Include D3 in D.4.1 b) so its says: Test Accepted. Annex D, D.4 was not included in a previous DIS version. We don t Method: apply tests defined in clause disagree of having this clause, but we see the need of D.2 and D.3 of this standard. including the D3 tests (r-defined extension metadata test suite) on profiles also. 209 CSNI D ed Incorrect reference: in clause D.2 in clause 2.2 Disagreed. However, comment in NO14 applies to Test Method. 210 SE-37 E T Annex E includes a profile but we do not think that we Make Annex E informative. Disagree to making Annex E informative. can hide an international standardised profile within ISO Annex E ISO19106 will give directives on how to make a Relate text to ISO and change Agree to changing the text label of Figure profile. It must be possible to have a unique text to: E.1 as recommended. identification of the standardised profile. The text does not relate to ISO as we think it should. The profile in the annex is not a profile. It is only a view of the intended profile. This annex exemplifies what could be included in a comprehensive dataset metadata profile that could be a basic profile according to ISO Change text of figure 1 to View of comprehensive metadata profile. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 40 of 68

197 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) 211 NO15 E Annex E 212 OGC E Annex E 213 OGC F Annex F 214 CH6 F Annex F Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations E1 ed?? Some new text has been inserted in this DIS version saying: The following are changes that were made to create the profile: E.1 Figure E JP80 F.1 2nd sentence of 1st paragraph Techni cal Editori al ge The MD_ServiceIdentification class was removed, as well as the identificationinfo role (between MD_Metadata and MD_Identification). and more. We can not recognise any discussion or reason for removing the MD_ServiceIdentification class. The importance of services in connection with geographic information is increasing. The relations to services should therefore not be weakened. Annex E needs to be updated with all changes made todate to create the comprehensive dataset metadata profile. Annex F (DTD implementation) needs to be updated in accordance with the most recent profile. An XML-DTD is only useful, if it can fully automatically be derived from the conceptual schema. Otherwise differences between the conceptual schema and the transfer format description are inevitable and priority rules have to be given for their resolution. Insert the MD_ServiceIdentification class again, or explain why this has been removed. Replace the content of paragraph E.1 with the text that provided in Attachment C. Replace Figure E.1 with the figure provided in Attachment C. If Annex F is not removed from the standard, provide the revised/updated content for the DTD during a future editing session. Replace the long-names (automatically) by short names in the conceptual schema before the automatic calculation of the XML-DTD. Describe all encoding and transformation rules used so that the procedure can be reproduced. ed Incorrect file name: ISO DatasetMetadata.dtd Change to DatasetMetadata.dtd Disagree that MD_ServiceIdentification should be re-inserted. The reason MD_ServiceIdentification was removed is because this profile is a dataset metadata application schema (NOT a service metadata application schema). However, we realize the importance of a service metadata application schema and it is currently being worked in the OGC. Accepted. Agreed in principle. Per 14 th ISO/TC211 Resolution 226, Annex F will be removed from the Standard. Accepted in principle. However, this comment is obsolete since the 14 th TC/211 Resolution 226 states that Annex F shall be removed from the Standard. Accepted, in principle. Response to CH6 applies. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 41 of 68

198 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 216 ANSI F.2 Genera l Short names and code numbers in the DTD would better ensure language neutrality. Replace the DTD and example with the attached files [dtd-short-esri.dtd and xml-sample.xml]. Accepted, in principle. Response to CH6 applies. 217 JP82 F.2 Line 2 of XML DTD document 218 ANSI F.2 Part 1 Editori al te This comment line does not seem to be suitable for an international standard document because of appearing a specific company name. Typographical error. Remove this line "conversiontoisostandarunit" should be "conversiontoisostandardunit". (Define what is an ISO standard unit) Disagreed, in principle. However, this comment is obsolete since 14 th ISO/TC211 Resolution 226 states that Annex F will be removed from the Standard. Accepted, in principle. Response to CH6 applies. 219 JP83 F.2 Last line of page 98 and 35th line of page 101 ed Tag name status does not correspond with the short name described in B.2.2 line 28. Change to idstatus Accepted, in principle. Response to CH6 applies. 220 JP84 F.2 Line of page JP85 F.2 Line 1 of page JP86 F.2 Line 7 of page JP87 F.2 Line 7 of page ANSI F.2 Part 5 Editori al te te te te Expression of measresult+ does not reflect one or two cardinality rule in accordance with Figure A.4. Expression of transdimmap* does not reflect zero, one or two cardinality rule in accordance with Figure A.8. Expression of stanpara* does not reflect zero, one or two cardinality rule in accordance with Figure A.9. Expression of oblnptpars* does not reflect zero or two cardinality rule in accordance with Figure A.9 (cf. JP30). Incorrect element name in the entity DigTranOps under Distribution Entities. Change to measresult, measresult? Change to (transdimmap, transdimmap?)? Change to (stanpara, stanpara?)? Change to (oblnptpars, oblnptpars)? under Distribution Entities, the entity DigTranOps contains the element "onlinemed". That should be "offlinemed". Accepted, in principle. Response to CH6 applies. Accepted, in principle. Response to CH6 applies. Accepted, in principle. Response to CH6 applies. Accepted, in principle. Response to CH6 applies. Accepted, in principle. Response to CH6 applies. 225 ANSI F.2 Part 5 Editori ial Typographical error in the entity Distributor under Distribution Entities. "distrotran" should be "distortran". Accepted, in principle. Response to CH6 applies. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 42 of 68

199 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 226 ANSI F.2 Part 5 Techni cal The entity "GeoBndBox" in the Extent entities section is missing the element "extypecode?". It should be in there with the bounding coordinate elements to say whether the box represents an area of inclusion or exclusion. 227 JP81 F.2 and J.3 te There are some discrepancies about metadata entity documenting order between data dictionary and XML DTD as well as XML metadata sample based on it, although B.2.1 and J.2 are consistent with each other. Add the element "extypecode" to the entity "GeoBndBox." Rearrange metadata entity order consistently 228 JP88 G.2 METHOD VIII) ed Incorrect reference: Stage 7 Change to Stage 8 Accepted. 229 JP89 G.4 METHOD ed Missing final procedure Add III) Go to Stage 9. after METHOD II) Accepted, in principle. Response to CH6 applies. Accepted, in principle. Response to CH6 applies. Accepted. 230 JP90 G.7 METHOD I) ed Missing punctuation Add a period at the tail of Stage 2 Accepted. 231 JP91 G.7 METHOD III) ed The letter s in stage should be capital letter. Change to Stage Accepted. 232 CSNI G.8 2 ed Incorrect reference: be found in B be found in B Accepted. 233 JP92 G.9 1st sentence ed The concept of entity is more generic than codelist. In this case, entity should be replaced by codelist to clarify the intension of this sentence. 234 JP93 H.2.1 ed All "Data series" shown in this section could be "data set series". 235 JP94 H.2.1 1st sentence te The first sentence does not constitute the sentence. It does not have verb and. Replace "data series" by "dataset series". The sentence may be "A series or collection of spatial data which share characteristics of theme, source date, resolution, and methodology may have relation between a data set series metadata". Accepted. Accepted. Accepted in principle. Action: replace the first sentence in H.2.1 with A dataset series is a collection of spatial data that shares characteristics of theme, source date, resolution, and methodology. 236 JP95 H.2.3 1st sentence te The 1st sentence of this clause is miss-understanding the feature definition. Feature is defined as abstraction of real world phenomena and it may not have spatial attributes. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version The 1st sentence should be as follows. Constructs known as features are grouped with common characteristics. Accepted. page 43 of 68

200 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 237 JP96 H.2.5 1st sentence ed Geometric primitive may take 0 to 3 geometric dimension. 238 JP97 I.2 ed There are some discrepancies about assigning vertical space in front of Dataset Administrative area A and Attribute type Administrative area A and documenting indentations of Feature type Administrative area A and Attribute type Administrative area A among each stage. 239 JP98 I.2 At the bottom of page 120 and 121 ed It does not seem that the blank spaces at the bottom of these pages are necessary. Insert ",3" between 0,1,2 and dimension. Make assigning vertical space and documenting indentations consistent on the whole Accepted. Accepted. Accepted. 240 JP99 J.1 Title te Continuing two examples do not describe core metadata. Remove Core from the title Accepted. 241 JP100 J.1 2nd sentence of 1st paragraph ed Upside-down double quotation mark: Exploration Licences for Minerals Inverse the tail side mark Accepted. 242 JP101 J.2 Line 8 ed Miss-spelling of CI_ResonsibleParty. CI_ResponsibleParty Accepted. 243 JP102 J.3 Line 2 of XML document 244 JP103 J.3 Line 3 of XML DTD document Te Ed This comment line does not seem to be suitable for an international standard document because of appearing specific brand and human names. Incorrect DTD file name: DatasetMetadata- 1_0.dtd Remove this line Change to DatasetMetadata.dtd Accepted in principle (human name). However, this comment is obsolete since the 14 th TC/211 Resolution 226 states that clause J.3 shall be removed from the Standard. Accepted in principle. Response to JP102 applies. 245 JP104 J.3 <lineage><state ment> Ed "Antartica" is "Antarctica". Revise the spelling. Accepted in principle. Response to JP102 applies. 246 CSNI J.4 1 ed Incorrect references: clauses J.3 and J.4 provide clause J.5 provides Accepted. 247 CSNI J.4 Fig. J.1, box TaxonomySyste m ed Incorrect spelling: Characterstring CharacterString Accepted. 248 JP105 J.4 Last sentence Ed Incorrect clause reference: J.3 and J.4 Change to J.5 and J.6 Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 44 of 68

201 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 249 CSNI K.1 3 ed Incorrect reference: be found in B.2.2 of this be found in B.2.3 of this Accepted. 250 JP106 K.1 The last sentence of the last paragraph Ed Incorrect clause reference: B.2.2 Change to B.2.3 Accepted. 251 CSNI K.2 6x ed Incorrect reference: (B.6.16) (B.6.10) Accepted in principle. Change to B JP107 K.2 Line 6x Ed Incorrect clause reference in domain: B.6.16 Change to B.5.10 Accepted. 253 CSNI K.2 7x ed Incorrect capital letter: Content content Accepted. 254 CSNI K.3 1 ed Incorrect reference: example (B.2.2 line 70). example (B.2.2 line 68). Accepted to B.2.3 line JP108 K.3 1st sentence and 1st table Ed Incorrect line reference to (B.2.2 line 70) Change to (B.2.3 line 68) Accepted B.2.3 line CSNI K.3 70 ed Incorrect identification: Accepted B.2.3 line CN K. 3 The 3rd column of the 2nd table T The example has used simplified Chinese. The character set code should be changed into the new one as suggested. That is 025. Change the character set code from 004(utf8) to 025(GB2312) like the attached table 2 below. (See Annex) Accepted. 258 CSNI Bibliography ed ISO cited in subclause B.3.2.1/381 is missing Please add ISO Accepted. 259 CSNI Bibliography ed ISO 646 US cited in subclause B.5.10/22 is missing Please add ISO 646 US Accepted. 260 JP109 Bibliography Line 1-5 Ed There are useless spaces between item numbers and head of sentences. Cut down spaces Accepted. 261 JP110 Bibliography Line 8 Ed Incorrect name: ISO TR Change to ISO/TR Accepted. 262 AU 10 New T The distinctions between identificationinfo::resourceformat, identificationinfo::environmentdescription and identificationinfo::citation::presentationform are not clear. Some guidance or illustration is needed of when each should be used, and the rationale for having this information in three different places explained. Agreed. Response to ANSI comment on this same topic applies. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 45 of 68

202 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 263 AU 11 New T distributioninfo::distributionformat vs distributioninfo::transferoptions::offline is confusing. 264 AU 12 G The comments (AU 13 to AU 20) are proposed for the next edition if not appropriate for current version CN B Figure A CN B.3.2 Lines 365 and 366 Line 257 Te NOTE: This comment submitted in-writing by the Chinese delegation to Editor during the 14 th ISO/TC211 Plenary Fig. A.10, the data-type of MD_RangeDimension::sequenceIdentifier is MemberName (as per the data dictionary, Line 257). Should this data-type be AttributeName instead? Ed NOTE: This comment submitted in-writing by the Chinese delegation to Editor during the 14 th ISO/TC211 Plenary The examples cited in the Definition block for CI_Citation::identifier and CI_Citation::identifierType are the same. Add guidance or illustration for usage. Agreed. Response to ANSI comment on this same topic applies. -- Each comment is individually addressed. Determine what the appropriate datatype is for MD_RangeDimension::sequenceIdentif ier. Change the examples so that they are not identical. No action. MemberName is the appropriate datatype for MD_RangeDimension::sequenceIdentifier. Accepted in principle. However, since response to AU 20 specifies that identifiertype will be deleted and that the data-type for identifier will be changed to MD_Identifier, this comment does not apply. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 46 of 68

203 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 267 Editor Editor Editor 03 Figure A.2 T MD_RepresentativeFraction does not require to be aggregated/associated with Scale since the denominator attribute is sufficient. Figure A.2 ed There is a trailing = character at the end of the class named MD_ServiceIdentification Table 3 Figure A.2 B.2.2 Geographic location of the dataset (by four coordinates or by geographic identifier) ( C ) Line 42, 43 and 45 The constaint for including at least one instance of EX G hi B di B 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version Te The attribute MD_DataIdentification::geographicBox is of data-type 'EX_GeographicBoundingBox' The attribute MD_DataIdentification::geographicDescription is of data-type 'EX_GeographicDescription' The attribute MD_DataIdentification::extent is of datatype 'EX_Extent' Since EX_GeographicBoundingBox and EX_GeographicDescription are aggregate parts of EX_Extent (via EX_GeographicExtent), only the MD_DataIdentification::extent attribute needs to be present. Remove the aggregation relationship. Remove the trailing character =. Correct s sentence regarding geographicbox and geographicdescription to read: The extent element of MD_Identificaiton is conditional; either the EX_GeographicBoundingBox or the EX_GeographicDescription subclass of extent s geographicelement Role shall be included if the dataset is spatially referenced. Correct Table 3 by replacing MD_DataIdentification.geographicBox or MD_DataIdentification.geographicIden tifier with Accepted. Accepted since work to produce an actual vmap0 XML instance document development efforts proved that Scale need not be present to define the value for MD_RepresentativeFraction::denominator (only a simple Real number need be provided). Action: Remove class Scale, its aggregation relationship with MD_RepresentativeFraction, and the associated constraint from Fig. A.2 Remove line 58 from B (Role /Scale ) Accepted. Accepted. Send to MHT. page 47 of 68

204 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations EX_GeographicBoundingBox or EX_GeographicDescription when MD_Metadata.hierarchyLevel = dataset can be applied to the extent attribute. MD_DataIdentification.extent > geographicelement > EX_GeographicBoundingBox, or, MD_DataIdentification.extent > geographicelement > EX_GeographicDescription Correct Figure A.2 and table B.2.2 by removing the geographicbox (Line 42) and geographicdescription (Line 43) attributes/entries. Change the constraint attached to/associated with MD_DataIdentification in Figure A.2 and in the Obligation/Condition column on Line 45 for the attribute extent to read: if MD_Metadata.hierarchyLevel = dataset then (count (self.extent.geographicelement.ex_ge ographicboundingbox) + count (self.extent.geographicelement.ex_ge ographicdescription) >= 1) 270 Editor 04 Figure A.4 B T The cardinality of DQ_Scope.level in Figure A.4 [1..*] is inconsistent with that in table B2.4.4 (1). Harmonize correctly. Accepted. Change cardinality in Fig. A.4 of DQ_Scope.level to be mandatory, 1 max. Send to MHT. 271 Editor 05 Figure A.4 B Line 134 Line 137 Te DQ_QuantitativeResult.valueUnit s data type is Measure. Measure, as defined in ISO 19103, Conceptual Schema Language, has a mandatory element value. However, DQ_QuantitativeResult has its own mandatory element value. Recommend that the data type of DQ_QuantitativeResult.valueUnit be changed from Measure to ISO s UnitOfMeasure. Accepted. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 48 of 68

205 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 272 Editor 06 Figure A.8 ed In the spirit of the response to NO8 (e.g. accepted that MD_ObligationCode s stereotype should be changed to Enumeration from enumeration to follow the rules for naming, it is noted that the same change should be applied to the enumerated-type MD_PixelOrientationCode Change <<enumeration>> to <<Enumeration>> Accepted. Action: change the stereotype of MD_PixelOrientationCode in Figure A.8 Send to MHT. 273 Editor 07 Figure A.8 B.5.28 Te The codelist value nonplanargraph is present in the MD_TopologyLevelCode codelist in Figure A.8 but is absent from table B If nonplanargraph is a valid codelist value for MD_TopologyLevelCode, add it to B.5.28 with a descriptive definition. Else, remove this value from Figure A.8 Accepted. Action: remove nonplanargraph from Fig. A.8. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 49 of 68

206 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 274 Editor 08 B.2 (all tables) Ed The current line numbering system (e.g. automatically, sequentially numbered) applied to the data dictionary tables provides a useful look-up mechanism to quickly identify elements in the standard. Since new elements will be inserted (due to the addition of classes and attributes to the model) and some existing elements will be removed (due to the removal of existing Roles, etc, from the model), the data dictionary tables line numbers are expected to change. It has been commented that this change in line numbers will adversely affect implementations that are using these line numbers as the means of identifying the model s elements. A decision needs to be made on whether the current line numbering system should be retained, should be removed all together, or, should be modified so that all current elements retain their current line numbers. One of the following three choices needs to be selected and implemented: Remove line numbering all together Retain the current mode of automatic, sequential line numbering so that, as elements are inserted or deleted, the line numbering for pre-existing elements changes accordingly based on the order each element appears in the tables Do not use an automatic, sequential line numbering system. Instead, manually number each element in the table so that it always retains the line number it was originally assigned. For new elements, use a tiered line numbering system (such as 1.1, 342.1). If an element is deleted, keep a same-numbered, but empty row in the table. Accepted. Action: Implement the third solution 275 Editor 09 B Line 342 Ge The stated longitude domain for EX_BoundingPolygon::polygon is -180 to 180. To support the range of longitudes 0 to 360 used by many by many countries, this domain range should be changed. Change -180 to 180 longitude to read -180 to 360 longitude. Accepted. 276 Editor 10 B.5.7 B.5.10 B.5.11 Figure A.16 Figure A.2 Figure A.13 Ed There are several discrepancies between the codelist values documented in Annex B.5 and the values displayed in the UML models present in Annex A. The discrepancies are as follows: Harmonize codelist table values with values displayed in corresponding Figures as suggested. Accepted. Send to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 50 of 68

207 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations B.5.23 imagehardcopy is missing from CI_PresentationFormCode in Fig. A.16 stereomate should be stereomate for DS_AssociationTypeCode, in B.5.7 isolec8859oneto15 is an erroneous MD_CharacterSetCode code value and should be removed from MD_CharacterSetCode in Fig. A.2 The following code values are present in B.5.10 but are missing from (and should be added to) MD_CharacterSetCode in Fig. A.2: utf7, 8859part1, 8859part2, 8859part3, 8859part4, 8859part5, 8859part6, 8859part7, 8859part8, 8859part9, 8859part11, 8859part14, 8859part15, usascii, ebcdic, euckr and big5 topsecret should be topsecret for MD_ClassificationCode in B.5.11 aggregatedclass should be aggregateclass for MD_DatatypeCode in Fig.A.13 underdevelopment should be underdevelopment for MD_ProgressCode in B.5.23 TIN should be tin for MD_SpatialRepresentationTypeCode in Fig. A.2 utilitiescommunications should be utilitiescommunication for MD_TopicCategoryCode in Fig.A.2 The following code values are present in B.5.28 but are missing from (and should be added to) MD_TopologyLevelCode in Fig. A.8: topology1d and topology3d 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 51 of 68

208 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 277 Editor 11 B.5.10 Ed The Definitions for the ISO/IEC 8859 code values should be changed to reflect the actual ISO/IEC 8859 definitions for those code values. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version The definitions should be changed to read: 8859part1: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No part2: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 2: Latin alphabet No part3: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 3: Latin alphabet No part4: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 4: Latin alphabet No part5: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 5: Latin/Cyrillic alphabet 8859part6: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 6: Latin/Arabic alphabet 8859part7: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 7: Latin/Greek alphabet 8859part8: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 8: Latin/Hebrew alphabet 8859part9: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 9: Latin alphabet No part11: ISO/IEC 8-bit single-byte Accepted. page 52 of 68

209 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations coded graphic character sets -- Part 11: Latin/Thai alphabet 8859part14: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 14: Latin alphabet No. 8 (Celtic) 8859part15: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 15: Latin alphabet No Editor 12 B.5.10 Figure A.2 Te ISO/IEC 8859 character set codes 8859part10, 8859part13 and 8859part16 are missing from the MD_CharacterSetCode codelist. Additionally, it seems that 8859part12 should be added and reserved for future use (at one time it was designated for Latin/Devanagari ). Add 8859part10, 8859part13 and 8859part16 to Fig.A.2 with the following definitions to table B.5.10: 8859part10: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 10: Latin alphabet No part13: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 13: Latin alphabet No part16: ISO/IEC 8-bit single-byte coded graphic character sets -- Part 16: Latin alphabet No. 10 Insert a numbered row for a future 8859part12 with the value (reserved for future use) with the following definition: A future ISO/IEC 8-bit single-byte coded graphic character set (e.g. possibly 8859part12) Accepted. Sent to MHT. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 53 of 68

210 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 279 Editor 13 Table 3 Additional extent information for the dataset (vertical and temporal) (O) Ed Currently, this optional element is written as (MD_Metadata > MD_DataIdentification.extent > EX_Extent) As written, the path to vertical and temporal extent information is not necessarily achieved since geographic extent is also an aggregate of EX_Extent. To properly convey the path to vertical or temporal extent, the optional element should be written as: (MD_Metadata > MD_DataIdentification.extent > verticalelement, or MD_Metadata > MD_DataIdentification.extent > temporalelement) Accepted. 280 Editor 14 Table 3 Dataset language (M) Ed Language is misspelled in MD_DataIdentification.lauguage. Correct the spelling. Accepted. 281 Editor Fig. A.10 Te According to Figure A.10, MD_RangeDimension is an aggregate of MD_CoverageDescription. However, states the opposite (e.g. that MD_CoverageDescription is an aggregate of MD_RangeDimension). Correct to state the proper relationship between MD_CoverageDescription and MD_RangeDimension. Accepted. Action: Change the phrase.. and is an aggregate of MD_RangeDimension to be.. and has an aggregate of MD_RangeDimension. 282 Editor Fig. A.12 Te Paragraph has several errors. The phrase which contain mandatory and optional elements is grammatically incorrect. Correct as follows: Replace which contain with which contains. Accepted also erroneously states that MD_DigitalTransferOptions is an aggregate of MD_DigitialTransferOptions. According to Fig. A.12, MD_DigitalTransferOptions is an aggregate of MD_Distributor. Replace the phrase, and is an aggregate of MD_DigitialTransferOoptins with, and is an aggregate of MD_Distributor. Finally, according to Figure A.12, MD_StandardOrderProcess is an aggregate of MD_Distributor. However, states the opposite (e.g. that MD_Distributor is an aggregate of MD_StandardOrderProcess). Replace MD_Distributor is an aggregate of the.. with MD_Distributor s other aggregate is... 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 54 of 68

211 Template for comments and secretariat observations Date: Document: ISO/DIS # 1 2 (3) 4 5 (6) (7) MB 1 Clause No./ Subclause No./ Annex (e.g. 3.1) Paragraph/ Figure/Table/No te (e.g. Table 1) Type of comment 2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 283 Editor 17 throughout document ed in reviewing the document, several instances of spelling, punction, and formatting errors have been found correct the errors Accepted. 284 Editor 18 throughout document ed in reviewing the document, several instances of erronous or stale cross references have been found correct the cross references Accepted. 285 Editor 19 A.2.7 B Fig. A.9 line 204 ed missing constraint note for MD_EllipsoidParameters:: denominatorofflatteningratio add a note to the figure for the constraint statement that is documented in the data dictionary Accepted 286 Editor 20 A.2.10 Fig. A.12 ed missing link between contstraint note attached to MD_Distributor and MD_Distribution add dashed line between the constraint note and MD_Distribution Accepted. 287 Editor 21 A.2.8 B B.4.8 Fig. A.10 line 257 ed MD_RangeDimension::sequenceIdentifier has a datatype of MemberName in the UML diagram and the data dictionary. The data dictionary indicates that the definition for MemberName is in B.4.8, but it is missing add definition of MemberName to B.4.8 Accepted. 288 Editor 22 B line 397 ed CI_OnlineResources::linkage is of type URL. the definition cites two documents, but they are not in the normative reference nor the bibliography add bibliography entries for IETF RFC 1738 and IETF RFC 2056 to the bibliography Accepted. 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory. ISO electronic balloting commenting template/version page 55 of 68

212 Template for comments and secretariat observations Date: Document: ISO/DIS ANNEXES China (CN) Attached Table 1: 25 big5 024 traditional Chinese code set used in Taiwan, Hong Kong of China and other areas. 26 GB simplified Chinese code set Attached Table 2: Zho (Chines e) 025 (GB2312) Memb er body Clause/ subclau se Paragra ph/ Figure/ Table Type of comme nt (ge/te/e d) 1 CN B.5.10 T big5 CN B.5.10 T CN K. 3 T 025 Comment Proposed change Observations of the secretariat on each comment submitted 1 004(utf8) 025(GB2312) 2 Attached Table 1: 25 big GB page 56 of 68

213 Template for comments and secretariat observations Date: Document: ISO/DIS Attached Table 2: Zho (Chines e) 025 (GB2312) page 57 of 68

214 Template for comments and secretariat observations Date: Document: ISO/DIS Italy 1. Comment Objectives The Centro Interregionale is in charge for the implementation of a National Cartographic Catalogue in the framework of the Agreement on GIS among Central, Regional and Local Institutions. Such a Catalogue must provide all interested users with complete information concerning the whole cartographic production available in Italy: it is a Metadata Catalogue, where no maps are actually contained, unless they are needed for example purposes, but with data concerning the technical characteristics and the information content of the available cartography, along with pointers to the actual location of the real maps and the way to get them. The definition of the metadata structure for the Catalogue has been derived from the works (although not yet completed) of ISO/TC211 and in particular the reference document has been ISO/DIS Geographic Information Metadata in its different versions, the last of which is dated August 20, A complete description of the System Architecture, and of the methods for searching and updating the Catalogue is reported in the Reference Documents (cfr. [1], [2], [3]), where a full analysis of these aspects can be found; the purpose of this document instead, is to highlight the observation concerning the Draft International Standard 19115, emerged during the work the Centro Interregionale has done for the implementation of the National Cartographic Catalogue; in fact during the last year a considerable amount of metadata has been collected, and a significant effort has been done by the project team to organise these materials according to the standard: from this work, some ideas are emerged, that are worth to be considered in the process of approving the standard. 2. Comment The ISO/DIS in the project of the National Cartographic Catalogue The adoption of the ISO standard is due to different very important aspects: The first reason is to agree on a common data structure (at level of logical model), among different institutions participating to the National Catalogue The second is to force all the participants to a common data format (XML) in order to achieve a certain degree of systems interoperability It is worth noting in fact, that the National Cartographic Catalogue has not been implemented as a collection of information (with a concentration operation), but on the contrary as a sort of search engine that, behind a common user interface, interact with a great number of local institutions by those organisms that are in charge for the management of their own (from a geographical as well as thematic point of view) cartographic data. In such a system the central problem is to standardize not the tools (because each participant could have its own software) but the logical model, the data structures are based on, and the communication protocols: the adoption of ISO DIS19115 has been of great importance exactly in this direction. The way of system interoperability is deeply pursued by the most recent developments of information technology: in particular, languages such as XML with its extension to specific application areas (e.g. GML for geographic information), would make it possible not only exchanging data, but accessing different systems and finally sharing the information. As far as the application of ISO DIS is concerned, the implementation of the Catalogue followed two main directions: 1. To organise the metadata according to the logical model proposed by the DIS To develop the software components needed for production and interpretation of XML files according to the DTD contained in DIS19115 The considerations illustrated in this document derives from this work, performed in over 1 year in a strict cooperation with a lot of regional institutions participating to the National Cartographic Catalogue: in [3] it is possible to evaluate the dimension of this work. 3. Comment Two proposals The experience gathered in this work indicates two major areas in which the ISO/DIS could be extended: the first one concerns the introduction of some hierarchy and inheritance mechanisms, while the second one concerns page 58 of 68

215 Template for comments and secretariat observations Date: Document: ISO/DIS the link toward the standard ISO Feature Catalogue, that is needed to fulfil the requirements of the users of a National Cartographic Catalogue, in particular those related to the completeness of information. Prior to the definition of these proposals, it is worth noting that they do not imply any formal extension to the standard, but are limited to suggestions about the interpretation of the standard within the present logical model. In the first case in fact, the proposal is to use entities and elements already defined in the schema to implement inheritance properties whose needs is someway mentioned in DIS 19115, but not fully defined, and that appear to be very important to provide a more efficient system; in the second case the proposal is to formally define a DTD for the standard (as it is for 19115), for a better implementation of the logical model involved by the standard; this way the Feature Catalogue standard would evolve in the same direction of Metadata, building up the structures needed for a better link among the two data set. Hierarchies The most important criticism to advance towards the ISO/DIS 19115, concerns the observations that the proposed model is suited for the description of independent maps, but seems to be weak for the description of a unique maps, that is divided in tiles with different characteristics upon a basis of common information; this is the case in particular, for a certain number 1 of Regional Technical Maps (CTR), that are among the most important sources of basic geographic data in Italy: they are divided in tiles according to a specific layout, and some attributes must be specified for each tile (e.g. reference date), while the great majority are valid for the whole map (e.g. reference system). The ISO/DIS actually introduce the idea of hierarchical structures, where in the MD_METADATA entity the following elements are defined: 2. fileidentifier 5. parentidentifier 6. hyerarchylevel Moreover two specific annexes (H and I, but they are only informational) are provided with some definition that could be useful in this direction, but they are not complete and the example are insufficient. Finally the schema expressed by the DTD (Annex F), that is the fundamental reference for the validation of exchange XML files, does not permit the use of this possibility, because it enforces the complete description of each dataset, with no way to point to other hierarchically superior elements (series). The approach we have implemented in the National Cartographic Catalogue is suited for an inheritance mechanism, that allows the description of a tiled map, with a root-element where all common elements are reported, and many child-elements where only the specific attributes are defined because all the others are inherited by the parent-element. The logical model of the National Cartographic Catalogue has a three level hierarchy (with levels named Theme, Edition and Dataset, cfr. [1]), so the problem is how to implement an efficient derivation of the XML files (compliant with the DIS19115) needed by the search engine and the consultation interface. The proposal is to apply the opportunity given by the DTD to provide more identificationinfo sections within the same MD_Metadata. In particular, when the XML files are produced, the first identificationinfo section is filled with the information relevant for the entire map ( Edition level), while the following (if any) are filled with the Dataset level; each section must have its own unique identifier in the Metadata file. The identificationinfo sections following the first one, must have at least the following attributes (cfr. the example file in Annex 1): title: DataSet name (e.g. the name and the code identifying each tile in a CTR) date (creation): the production date of the DataSet citedresponsibleparty: data concerning the author of the dataset, as defined in DIS 19115, with rolecode = Originator abstract: free text credit: list of contributors; free text resourceformat: as defined in DIS language: as defined in DIS The problem is particularly significant for the older, paper based CTR, while the more recent production of information layer is more suited for a description through the Feature Catalogue page 59 of 68

216 Template for comments and secretariat observations Date: Document: ISO/DIS topiccategory: repeating those reported at Edition level 2 geographicbox: extension of the DataSet (typically smaller than the whole Edition ) environmentdescription: as defined in DIS EX_TemporalExtent: acquisition date for the realization of the dataset (typically different from on dataset to another in the same Edition ) This way of applying the ISO/DIS to implement the inheritance among elements, include all involved elements in the same XML file, so the following attributes are not used: 2. fileidentifier 5. parentidentifier 6. hyerarchylevel 7. hyerarchylevelname Relation with the Feature Catalogue The description of the information content of each map is managed in the DIS through the entity continfotypes, who provides for 3 different sub-entity: Feature Catalogue Description, for the description of vector data, or even for paper maps. Coverage Description, for the description of raster (or better for gridded) data. Image Description, for the description of images (in particular in a remote sensing context) The National Cartographic Catalogue at present does not consider remotely sensed data, so the most interesting entity is the Feature Catalogue; for this entity the ISO/DIS point to another ISO standard, that is the ISO/DIS Feature Cataloguing Methodology (last edition dated june12, In coherence to this approach the logical model of the National Cartographic Catalogue provide for the definition (cfr. [1]) of one or more Entities for each Edition: each entity carry on its own information content, and geometric/topologic properties: these entities correspond exactly to the FeatureTypes in the ISO standard. So the logical model adopted for the Feature Catalogue is well suited to describe the information content of the maps managed by the National Cartographic Catalogue, and the present proposal does not involve an extension of the standard, but only the definition of the corresponding DTD in order to allow the validation of XML files compliant with the standard: in fact the DTD file attached to the ISO/DIS does not comprehend a DTD for the feature catalogue (only a pointer to), while the ISO (older) does not have an Annex with the DTD. In the present document a FeatureCatalogue.dtd is proposed, compliant with the logical model of the standard, to be used in conjunction with the DatasetMetadata for the publication of XML files providing a complete description of the cartography (general description and information content). This proposed DTD does not completely implement the standard, but only the main aspects, in particular those involved in the description of the information content of data in the National Cartographic Catalogue. Completing the DTD with the whole logical model of standard would be straightforward once the needed consensus would be established on methodological aspects. In Annex 2 it is enclosed the proposed FeatureCatalogue.dtd for the validation of XML files of a Feature Catalogue and the link to the corresponding Metadata XML files. In particular the following files are presented: FeatureCatalogue.dtd FC1352.XML (as an example XML Feature Catalogue) ED1352.XML (as an example XML Metadata with a pointer to the corresponding Feature Catalogue) The link is driven by the Metadata file by means of the continfotypes attribute where the pointer to the Feature Catalogue is stored. Two different files, referring to distinct standard seems to be the most flexible choice: this way the publication of a Feature Catalogue is not mandatory with the Metadata, and it is possible to manage a Feature Catalogue with no reference to any Metadata. 4. Comment Reference Documents [1]. Convenzione Regione Basilicata - Centro Interregionale per il Sistema Cartografico di Riferimento, Architettura del Repertorio Cartografico. Versione 3.2. Roma, 20/12/ This is a duplicatoin of the same information; it would be better to declare this attribute as optional, as it appear to be logical, but this would imply a modification in the DTD that does not seem to be justified for this only reason. page 60 of 68

217 Template for comments and secretariat observations Date: Document: ISO/DIS [2]. Convenzione Regione Basilicata - Centro Interregionale per il Sistema Cartografico di Riferimento, Manuale di consultazione del Repertorio Cartografico Nazionale. Roma, 31/12/2001 [3]. Convenzione Regione Basilicata - Centro Interregionale per il Sistema Cartografico di Riferimento, Sintesi dei dati caricati nel Repertorio Cartografico Nazionale al [4]. ISO/TC 211 Geographic Information/Geomatics ISO/DIS Geographic Information, Metadata 20/08/2001 [5]. ISO/TC 211 Geographic Information/Geomatics ISO/DIS Geographic Information, Methodology for feature cataloguing 12/06/ FeatureCatalogue.dtd DatasetMetadata-1_0.dtd DCW2.xml ED1352.xml FC1352.xml page 61 of 68

218 Template for comments and secretariat observations Date: Document: ISO/DIS USA RS_Identifier Issue B Name Short Name Definition Obligation Maximum Data Type Occurrence authority identauth Authority citation O 1 CI_Citation code identcode Alphanumeric value identifying an instance in the namespace O 1 CharacterString codespace identcodespce Name or identifier of the person or organization responsible for O 1 CharacterString namespace version identvrsn Version identifier for the namespace O 1 CharacterString A.2.7 <<DataType>> MD_Identifier (from Reference System) authority [0..1] : CI_Citation code : CharacterString <<DataType>> RS_Identifier (from Reference System) codespace : CharacterString version(0..1) : CharacterString page 62 of 68

219 Template for comments and secretariat observations Date: Document: ISO/DIS OGC Attachment A This attachment describes the changes to the ISO standard resulting from the addition of the dataset attribute to MD_Metadata. Figure A.1 changes The modified MD_Metadata class will be represented in Figure A.1 as follows: B.2.1 changes The data dictionary of MD_Metadata (B.2.1 Metadata entity set information) will change as follows. Note that the dataset attribute will be inserted as Item 12 and that the remaining items (Items 12 22) will be renumbered as items page 63 of 68

220 Template for comments and secretariat observations Date: Document: ISO/DIS Name / Role name Short Name Definition Obligation / Condition Maximum Data type 12. dataset dataset Identifies the location M 1 CharacterString Free text (URL) of the dataset to which the metadata applies Attachment B Domain This attachment describes the changes to the ISO standard resulting from the addition of the class MD_AggregateInformation to the Identification information package. Figure A.2 changes The MD_AggregateInformation class will be represented in Figure A.2 as follows: B.2.1 changes The role aggregationinfo will be added to the end of the data dictionary for MD_Metadata (B.2.1 Metadata entity set information) as Item 24 as follows: Name / Role name Short Name Definition Obligation / Condition Maximum Data type Domain 24. Role name: aggregationinfo aggregationinfo Provides aggregate dataset information O N Association MD_AggregateInformation (B.2.2) page 64 of 68

221 Template for comments and secretariat observations Date: Document: ISO/DIS B.2.2 changes Attachment B - continued Note that with the addition of the 2 items to B.2.1 (attribute dataset and role aggregationinfo ), the starting number of items appearing in B.2.2 will be 25. The description of the class MD_AggregateInformation will be added to the end of B.2.2 as Items as follows: Name / Role name Short Name Definition Obligation / Condition Maximum Data type 50. MD_AggregateInformation aggregateinfo Aggregate dataset O N Aggregated Class information (MD_Identification) 51. aggregatedatasetname aggrdsname Citation information C / either this or about the aggregate aggregatedatasetidentifier dataset must be present 52. aggregatedatasetidentifier aggrdsident Identification information about the aggregate dataset 53. associationtype assoctype Association type of the aggregate dataset 54. initiativetype initiativetype The type of initiative under which the aggregate dataset was produced C / either this or aggregatedatasetname must be present Lines Class CI_Citation (B.3.2) <<DataType>> Domain 1 Class MD_Identifier (B.2.8) <<Data Type>> M 1 Class DS_AssociationTypeCode (B.5.7) <<CodeList>> O 1 Class DS_InitiativeTypeCode (B.5.8) <<CodeList>> page 65 of 68

222 Template for comments and secretariat observations Date: Document: ISO/DIS Attachment C This attachment describes the changes to Annex E of the ISO standard based on changes made to-date to create the comprehensive dataset metadata profile. E.1 changes The contents of paragraph E.1 Comprehensive dataset metadata application schema will be replaced with the text below: The ISO series of geographic information standards define, in the abstract, the classes of information needed to: 1) model geographic phenomena; and 2) manipulate, manage and understand these models. In order to implement these standards, profiles must be developed. Typically, an information community with special requirements will develop profiles that use the appropriate parts provided by this series of standards. This comprehensive dataset metadata profile is a basic profile. It provides an international standardized profile applicable to a wide range of information communities. of this profile will promote interoperability between information communities. The comprehensive dataset metadata profile is a subset of packages, classes, attributes and relationships defined in Annexes A and B. Only the classes, attributes and relationships necessary to fulfill the requirements for general-purpose dataset metadata are present. The following are changes that were made to create the profile: Removed MD_ServiceIdentification class from the Identification information package Replaced simple conceptual types (Binary, Boolean, CharacterString, Date, DateTime, GenericName, Integer, Real, RecordType and TM_PeriodDuration ) with XSD-equivalent types Replaced complex conceptual types (Angle, Distance, GF_AttributeType, GF_FeatureType, GM_Object, GM_Point, Measure, MemberName, Record, TM_Primitive and UomLength ) with newly-defined XML-equivalent types Removed the Metadata application package (which contained classes of geographic information to which metadata applies eg. DS_Aggregate, DS_Dataset, DS_Initiative, DS_OtherAggregate) Added attribute dataset (type xsd:anyuri) to MD_Metadata for XML implementation purposes To compensate for the loss of the Metadata application package, created/added the new class MD_AggregateInformation to the Identification information package with following attributes: aggregatedatasetname (type CI_Citation), aggregatedatasetidentifier (type MD_Identifier), associationtype (type DS_AssociationTypeCode) and initiativetype (type DS_InitiativeTypeCode) Removed the aggregate relationship between MD_Distribution and MD_Format Removed RS_ReferenceSystem and all of its derived classes Added the following attributes to RS_Identifier: codespace (xsd:string) and version[0..1] (xsd:string) Constrained the implementation of the EX_BoundingPolygon s polygon attribute to be a Box (upper and lower corner Points) or Polygon (outer and inner bounding Rings) Changed all non-conforming class associations (e.g. two-way association, one-way ByReference or Unspecified aggregation) to be one-way ByValue aggregation relationships E.2 changes The contents of paragraph E.2 Comprehensive dataset metadata profile UML model will be replaced with the text below: page 66 of 68

223 Template for comments and secretariat observations Date: Document: ISO/DIS The comprehensive dataset metadata profile is presented in a UML metadata application schema, Figure E.1. The attributes within each class and codelist have not been displayed in the model in order to simplify the diagram. Note that the relevant application schemas for the conceptual model are not referenced by the diagram since all conceptual types from these schemas have been replaced with other XML equivalent types. The models of these XML equivalent types are also not displayed in order to simplify the diagram. Attachment C - continued Figure E.1 changes Figure E.1 Comprehensive dataset metadata profile will be replaced with the following diagram: page 67 of 68