Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) SDSFIE Metadata (SDSFIE-M): Conceptual Schema

Transcription

1 Spatial Data Standards f Facilities, Infrastructure, and Environment (SDSFIE) SDSFIE Metadata (SDSFIE-M): Conceptual Schema Version (28 AUGUST 2014) Prepared By: The Defense Installation Spatial Data Infrastructure (DISDI) Group Chair: Office of the Deputy Under Secretary of Defense (Installations & Environment), Business Enterprise Integration Directate 2014

2 THIS PAGE IS INTENTIONALLY BLANK i

3 Executive Summary Metadata, data about data, is imptant and valuable because it enables discovery of infmation. It I also an aid to data and system interoperability. Metadata describes the source, methods, content and the appropriate use of a data service. As archived data and imagery grow to enmous volumes, metadata is becoming even me critical. Without good metadata, a consumer cannot search and retrieve data containing the characteristics and content necessary to suppt their mission. Metadata instills data accountability and limits data liability. The timely capture of metadata is also fundamental to the quality of the data resource as a whole. F geospatial datasets, accurate, complete and descriptive geospatial metadata is a key component of that dataset and is needed by a rapidly growing geospatial data market to locate available geospatial data and services and assess their quality and lineage, allowing the appropriate understanding, use and exploitation of that geospatial data. Certain geospatial metadata is also used in the DoD Installations and Environment (I&E) community to specify the structure and characteristics of I&E data. In general, geospatial metadata describes the geospatial data elements used to specify infmation about features, events, coverages (including, images and elevation surfaces), datasets (collections of such infmation) and services (capabilities to create, access, display, and/ manipulate such infmation). Geospatial metadata also specifies characteristics of the values of data items (e.g., the accuracy of a measured height value the analytic confidence that a type-assignment is crect) and characteristics of datasets (the producer, release date, content summary and the like). In der f a geospatial data resource to be discovered, assessed f its fitness of use, retrieved, and then exchanged, it must comply with certain DoD and international standards that mandate the structure and content of metadata f geospatial infmation. All the diverse metadata requirements within these various standards that are appropriate f compliance in I&E systems have been brought together under a single umbrella reference standard f ease of use in the I&E community. Spatial Data Standards f Facilities, Infrastructure, and Environment (SDSFIE) Metadata (SDSFIE- M) is a standard which defines the conceptual schema profile f specifying geospatial metadata in and f the I&E community. It is the policy of the Deputy Under Secretary of Defense f Installations and Environment that all I&E geospatial data have accompanying metadata, confming to DoD standards. SDSFIE-M is that standard f the I&E community. This document defines the mandaty and common elements of the SDSFIE-M conceptual schema. This document does not contain the implementation schema f SDSFIE-M. The XML schema implementation of SDSFIE-M, called the SDSFIE Metadata Implementation Schema (SMIS), is defined and provided separately. This document does not contain implementation guidance. Implementation guidance is defined in a separate SDSFIE-M Implementation Guidance document. i

4 Revision Histy Description Date Version Initial DISDIG Approved Version June 12, Revision to include modifications as follows: Changed the name SMF to SDSFIE-M. Fixed one typographical err. Add PresentationFmCode code list that was inadvertently left out of 1.0 specification Remove ResourceAssociationType code list that was duplicative of the AssociationType code list and unused in the remainder of the specification Remove the UnclassHandlingCode code list as it duplicates many of the entries in the IC ISM. Add a free text handlingdescription element to allow f additional infmation about the restrictions on handling the resource metadata Updated the SMF_Feature data type to allow f alias name, model name, description, and note SDSFIE. Reintroduced BrowseGraphic element after discussions with the Metadata Wking Group. Revision to include modifications as follows: Aligned code lists (Table 3) to SMIS document. Set hierarchylevel and heirarchyname to multiplicity N to align with NMF 2.2 (Table 7). changed SMF_RoleCode reference to RoleCode (Table 7). removed the default value on metadatastandardversion (Table 7). Changed the reference to the MetadataStandardNameCode value sdsfiemetadatafoundation to sdsfiemetadata and the URL ode/sdsfiemetadatafoundation to Code/sdsfieMetadata (Table 7 and footnote). Changed MD_Keywds/Type element to MD_Keywds/type (Table 11). May 16, August 28, ii

5 Table of Contents Executive Summary... i Fward... xi Introduction... xiii 1 Scope General Relation to other Standards References Nmative References Infmative References Definitions Abbreviations Confmance and Compliance Introduction Profiles and Confmance Confmance Ce Confmance Profile Confmance Requirements Implementation Specification Confmance Requirements Compliance Requirements General Resource Model Metadata Requirement f Geographic Data SDSFIE-M Conceptual Schema Profile Introduction Value Domains Datatypes Codelists Enumerations Element Table Structure Introduction Name Definition Obligation/Condition Maximum Datatype / Domain Business Rule iii

6 7.4 Resource Metadata Sections Metadata Entity Set Identification Constraints Data Quality Maintenance Infmation Spatial Representation Infmation Reference System Identifier Content Infmation Application Schema Acquisition Infmation Extent Citation Annex A Profiles (Nmative) A.1 Extending the SDSFIE-M Conceptual Schema Profile A.1.1 Introduction A.1.2 Extension Methodology A.1.3 Existing Element A.1.4 New Element Entity A.2 Profiling the SDSFIE-M Conceptual Schema Profile A.2.1 Introduction A.2.2 Profile Structure A.2.3 Business Rules Annex B Data Types (Nmative) Annex C Abstract Test Suite (ATS) (Nmative) C.1 Abstract test suite C.2 Introduction C.3 Test Purpose C.4 Test Methods C.5 Test case SDSFIE-M -derived Profiles C.5.1 Test Purpose C.5.2 Test Method C.5.3 Test Criteria C.6 Test Case Extensions to the SDSFIE-M Conceptual Schema Profile C.6.1 Test Purpose C.6.2 Test Method C.6.3 Test Criteria C.7 Test Case Confmance with Established SDSFIE-M -Based Profiles iv

7 C.7.1 Test Purpose C.7.2 Test Method C.7.3 Test Criteria Annex D UML Primer (Infmative) D.1 UML notations D.2 UML model relationships D.2.1 Associations D.2.2 Generalization D.2.3 Instantiation / Dependency D.2.4 Roles D.3 UML model stereotypes D.4 Package abbreviations Bibliography v

8 Table of Figures Figure 1 : General Resource Model Figure 2 : SDSFIE-M Metadata Packages Figure 3 : Metadata Entity Set Figure 4 : Metadata Entity Set, Extended f Imagery and Gridded Data Figure 5 : Identification Figure 6 : Service Identification Context Figure 7 : Constraints Figure 8 : Data Quality Figure 9 : LI_Lineage Metadata Figure 10 : LE_Lineage Metadata Figure 11 : Quality Element Context Figure 12 : Data Quality Result Figure 13 : Data quality result with coverage quality extension Figure 14 : Transfer Files Figure 15 : Maintenance Infmation Figure 16 : Spatial Representation Figure 17 : Spatial representation extension f imagery Figure 18 : Reference System Figure 19 : Identifier Figure 20 : Content Infmation Figure 21 : Content Infmation with imagery extensions Figure 22 : Application Schema Figure 23 : Acquisition Overview Figure 24 : Acquisition Detail Figure 25 : Extent Figure 26 : Citation and Responsible Party Figure 27 : UML Notation Figure 28 : UML Roles vi

9 Table of Tables Table 1 : SDSFIE-M metadata packages and their cresponding obligations Table 2 : SDSFIE-M Conceptual Schema Profile Datatypes Table 3 : SDSFIE-M Conceptual Schema Codelists Table 4 : Enumeration MD_TopicCategy Domain Values Table 5 : Enumeration MD_PixelOrientationCode Domain Values Table 6 : Multiplicity and Implied Obligation Table 7 : Metadata Entity Set Table 8 : Metadata Entity Set, Extension f Imagery and Gridded Data Table 9 : Locale Table 10 : Identification Table 11 : Keywds Table 12 : Fmat Table 13 : Resolution Table 14 : Representative Fraction Table 15 : Aggregate Infmation Table 16 : Operation Infmation Table 17 : Operation Chain Infmation Table 18 : Parameter Infmation Table 19 : Coupled Resource Infmation Table 20 : Standard Order Process Infmation Table 21 : Constraints Table 22 : SDSFIE-M Security Constraints Table 23 : ISM Security Attributes Group Table 24 : Need To Know Table 25 : ISM Notices Table 26 : Data Quality Table 27 : Data Quality Scope Table 28 : Using LI_Lineage Table 29 : LI_Lineage Table 30 : LI_ProcessStep Table 31 : LI_Source Table 32 : LE_Source Table 33 : LE_ NominalResolution Table 34 : LE_ ProcessStep Table 35 : LE_ ProcessStepRept Table 36 : LE_Processing Table 37 : LE_Algithm Table 38 : DQ_Element vii

10 Table 39 : DQ_Result Table 40 : MX_File, MX_DataFile, and MX_SupptFile Table 41 : Maintenance Infmation Table 42 : Scope Description Table 43 : Spatial Representation Infmation Table 44 : MD_Dimension Table 45 : MI_Geectified Table 46 : MI_Geeferenceable Table 47 : MI_GeolocationInfmation Table 48 : MI_GCP Table 49 : Geometric Objects Table 50 : Reference System Table 51 : Identifier Table 52 : Resolvable Resource Identifiers Table 53 : Non-Resolvable Resource Identifiers Table 54 : General Purpose Identifiers f Imagery and Gridded Data Table 55 : Imagery and Gridded Data Identifiers Table 56 : RS_Identifier Table 57 : Content Infmation Table 58 : SMF_FeatureTypes Table 59 : SMF_Features Table 60 : MD_RangeDimension Table 61 : MI_Band Table 62 : MI_CoverageDescription Table 63 : MI_ImageDescription Table 64 : MI_RangeElementDescription Table 65 : Application Schema Infmation Table 66 : MI_AcquisitionInfmation Table 67 : MI_EnvironmentalRecd Table 68 : MI_Plan Table 69 : MI_Requirement Table 70 : MI_RequestedDate Table 71 : MI_Instrument Table 72 : MI_Objective Table 73 : MI_Operation Table 74 : MI_Platfm Table 75 : MI_PlatfmPass Table 76 : MI_Event Table 77 : Extent viii

11 Table 78 : Geographic Extent Table 79 : Tempal Extent Table 80 : Vertical Extent Table 81 : Citation Table 82 : Responsible Party Table 83 : Address Table 84 : Contact Table 85 : Date Table 86 : Online Resource Table 87 : Series Table 88 : Telephone ix

12 THIS PAGE IS INTENTIONALLY BLANK x

13 Fward The Spatial Data Standards f Facilities, Infrastructure, and Environment (SDSFIE) Metadata Foundation, SMF is a community standard f geospatial metadata and is a profile of the National System f Geospatial-Intelligence (NSG) Metadata Foundation, NMF. NMF is, in turn, a profile of ISO 19115:2003/C 1:2006 (Geographic Infmation Metadata). SMF is specifically applicable to the Defense Installation Spatial Data Infrastructure Community of Interest (DISDI COI) as listed in the United States Department of Defense (DoD) Metadata Registry, and having a cresponding DISDI namespace. The SDSFIE suppts the ability of the DISDI COI, also known as the Installation Geospatial Infmation and Services (IGI&S) user community, to describe its spatial data holdings (e.g. those structured accding to the Spatial Data Standard f Facilities, Infrastructure, and Environment). Complete and current geospatial metadata is also essential to meet the goals of DoD Directive summarized as making data and services me visible (discoverable), accessible, understandable, trusted, and interoperable. The DISDI COI is led by the Defense Installation Spatial Data Infrastructure (DISDI) Group, DISDIG. A subgroup of the DISDIG called the Metadata Wking Group (DMWG) serves as the I&E communitywide fum to conduct and codinate pertinent metadata standardization effts like the SDSFIE-M. The SDSFIE-M (previously known as the Defense Installation Spatial Data Infrastructure (DISDI) Geospatial Metadata Profile DGMP) specification was established via consensus input of the DISDIG, the officially designated I&E governance body f spatial data standards, including metadata standards. In 2009 the DUSD(I&E), as the chair of the RPILM Investment Review Board, required the Components to implement the DGMP as the enterprise standard f IGI&S metadata that is primarily used to suppt RPILM ce business missions (DUSD(I&E) memandum, 14 April, 2009). The DISDI Group exercises tiered governance of the SDSFIE-M, ensuring implementation of the standard suppts the Department s business transfmation goals, the Business Enterprise Architecture, and RPILM initiatives. The DISDI Group is also responsible f ensuring all concepts in SDSFIE-M are harmonized to the greatest extent practicable with the NMF, and integrated with the NMF where beneficial. The DISDI COI has long known the value of metadata. Pri to developing DGMP 1.0, the community used the Federal Geographic Data Committee s (FGDC) Content Standard f Digital Geospatial Metadata (CSDGM), established in 1998 and required under the provisions of Office of Management and Budget Circular A-16. Although the CSDGM is widely used, it has been implemented inconsistently due to inherent flaws in the standard itself as well as a general lack of detailed implementation guidance throughout the DISDI COI. Without a unifm implementation of the CSDGM standard, the goal of authitative net-centric data sharing is defeated. The growing challenges in implementing CSDGM have converged with the new policybased requirements to implement International Organization f Standardization (ISO) 19115:2003 Geographic Infmation Metadata. In 2010, the GEOINT Standards Wking Group (GWG) developed a profile of ISO known as the National System f GEOINT (NSG) Metadata Foundation, NMF. In accdance with DoDD , xi

14 the DISDI Community is required to implement this standard. Meanwhile, the FGDC recently developed a success standard to CSDGM in conjunction with the Canadian Geospatial governance body. This Nth American Profile (NAP) is a profile of the ISO just as the SDSFIE-M 1.0 and NMF. The SDSFIE-M Version 1.0 is intended to serve as a bridge standard f the DISDI community, allowing easy translation of metadata to the NMF profile as well as the NAP, both of which are required by federal DoD policy but which, on their own, do not meet all the needs of the I&E business mission area. xii

15 Introduction The term Geospatial refers to either an implicit explicit reference to a location relative to the earth. Metadata is infmation which captures the underlying characteristics of an resource. It represents the who, what, when, where, why and how of the resource. The term Geospatial Infmation & Services GI&S encompasses the concept f collection, infmation extraction, stage, dissemination, and exploitation of geodetic, geomagnetic, imagery, gravimetric, aeronautical, topographic, hydrographic, littal, cultural, and toponymic data accurately referenced to a precise location on the earth s surface 1. These data are used in the battlespace f military planning, training, and operations, including navigation, mission planning, mission rehearsal, modeling, simulation, and precise targeting, as well as in the basing space to provide situational awareness f fce protection and management of the built and natural infrastructure. F the purposes of this specification, Installation GI&S (IGI&S) refers to the subset of GI&S activities that enhance the DoD I&E business mission area and suppt I&E business enterprise priities as defined in the DoD Business Enterprise Architecture. IGI&S are considered complimentary to but different GEOINT, and are managed as DoD infmation resources and infmation technology as defined in EO 12906, DoD Directives and Geospatial infmation provides the basic framewk f IGI&S business mission suppt. It is infmation that can be produced by one me sources to common interoperable data standards. It may be utilized in the fm of printed maps, charts, and publications; in digital simulation and modeling databases; in photographic fm; in the fm of digitized maps and charts attributed centerline data. Geospatial services include tools that enable users to access and manipulate data and also include instruction, training, labaty suppt, and guidance f its use. SDSFIE-M defines an NMF Profile (and thus an ISO 19115:2003/C 1:2006 Profile) f specifying geospatial metadata in the I&E business mission area. The purposes of the SDSFIE-M are to promote the following: Common understanding of Geospatial metadata within and across I&E business mission area; Conceptual specification standard f Geospatial metadata; Foundation standard defining business rules f specifying Geospatial metadata; Logical specification standard f Geospatial metadata; Re-use and standardization of Geospatial metadata in the I&E business mission area; 1 Joint Publication (JP) 2-03, 31 Oct xiii

16 Harmonization of Geospatial metadata creation within and across I&E business mission area, suppting varying business requirements and practices; Physical specification(s) standard f Geospatial metadata with multiple COTS technologies, including standards-based exchange; and Geospatial metadata publication standard using externally-specified specifications and mechanisms. A note on terminology SDSFIE-M uses the Unified Markup Language (UML) to model a conceptual schema. This mixture of techniques may lead to some confusion of terms. A conceptual schema consists of metadata entities composed of elements. A UML model is composed of classes containing attributes. An efft has been made to use the terminology appropriate f the context. However, it is best to remember that: 1) Entities are concepts modeled by classes 2) Classes are models representing concepts 3) Elements are concepts modeled by attributes 4) Attributes are models representing elements. xiv

17 SDSFIE Metadata 1 Scope 1.1 General Geospatial metadata is used in the IGI&S community to describe the characteristics and structure of IGI&S data and services. Geospatial metadata describes the geospatial data elements used to specify infmation about features, events, coverages (including images and elevation surfaces), datasets (collections of such infmation), measurements, observations and services (capabilities to create, access, display, and/ manipulate such infmation). SDSFIE Metadata (SDSFIE-M) is a profile of the National System f Geospatial- Intelligence (NSG) Metadata Foundation, NMF. NMF is, in turn, a profile of ISO 19115:2003/C 1:2006 (Geographic Infmation Metadata) that specifies the minimum and recommended sets of metadata elements required f the discovery and exchange of geospatial datasets in the IGI&S community. This Conceptual Schema Profile shall be used to document geospatial datasets f cataloguing, discovery and retrieval. It may be used as a basis f populating DoD Discovery Metadata Standard (DDMS) confmant metacards f use in the Global Infmation Grid (GIG) Enterprise Discovery Service. 1.2 Relation to other Standards SDSFIE-M is a profile of the conceptual schema f metadata defined by Geospatial- Intelligence Standards Wking Group (GWG) 2. This specification profiles NMF Parts 1, 2, and 3 and is thus also a profile of ISO 19115:2003/C 1:2006 and ISO :2009 and is intended to specify the minimum and recommended set of metadata elements required f the discovery and exchange of geospatial datasets in the IGI&S community. 2 The GWG is an NSG fum that serves the Direct, National Geospatial-Intelligence Agency and the NGA Chief Infmation Officer who is the delegated functional manager f GEOINT architecture and standards, in executing the functional management responsibilities authized in NSG Directive ST 8100, 1 March The GWG provides the fum f the codination of GEOINT standard activities. The GWG is led and chaired by the NGA's National Center f Geospatial Intelligence Standards (NCGIS). In addition to its designation as an NSG Functional Management fum, the GWG is a Joint Technical Wking Group that participates in both the DoD and IC standards governance processes. In the DoD, the GWG votes and manages GEOINT standards lifecycle recommendations repted to the Infmation Technology Standards Committee (ITSC), the governing group responsible f developing and promoting standards interoperability in suppt of net-centricity within the Department of Defense (DoD). GWG recommendations f mandating standards f the DoD are approved by the DoD Architecture and Standards Review Group (ASRG). Approved GEOINT standards are then cited in the DoD Infmation Technology (IT) Standards Registry (DISR). In the Intelligence Community (IC), the GWG provides the same GEOINT standards lifecycle management recommendations brought into the DoD process and these voted upon recommendations are approved f the IC by the IC Enterprise Standards Committee (IC ESC) and the IC CIO s Architecture, Standards and Engineering Committee (ASEC). Approved GEOINT standards are then cited in the IC Standards Registry (ICSR). 15

18 As a profile of GEOINT and ISO standards, SDSFIE-M is only nmative in those areas where the GEOINT and ISO standards have been profiled to address IGI&S requirements. The iginating ISO standards continue to provide the nmative definition of all elements not restricted extended by SDSFIE-M. Infmation those standards has been included solely to provide context. This standard is a specification of the SDSFIE-M conceptual schema. A conceptual schema is agnostic to implementing technology. Implementation specifications address how this conceptual schema should be realized f a specific technology. The SDSFIE Metadata Implementation Specification (SMIS) provides that guidance f XML schema. Additional implementation specifications may be developed as requirements f those specifications are identified. One near-term example of this is the SDSFIE-M Feature Level Metadata (SDSFIE-M-FLM) profile (a strict subset of SDSFIE-M intended to be used at define metadata at the feature level). The SDSFIE-M-FLM implementation specification will most likely be expressed as Structured Query Language (SQL) Data Definition Language (DDL). 16

19 2 References 2.1 Nmative References The following referenced documents provide the basis f SDSFIE-M. F dated references, only the edition cited applies. F undated references, the latest edition of the referenced document (including amendments) applies. Department of Defense Discovery Metadata Specification (DDMS), August 10, 2007, Deputy Assistant Secretary of Defense/Deputy Chief Infmation Officer. ISO 639-2:1998, Codes f the representation of names of languages Part 2: Alpha-3 code ISO 3166 (all parts), Codes f the representation of names of countries and their subdivisions ISO 8859 (parts 1 to 16), Infmation technology 8-bit single-byte coded graphic character sets ISO 8879, Infmation processing Text and office systems Standard Generalized Markup Language (SGML) ISO/IEC , Infmation technology Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture and Basic Multilingual Plane ISO/IEC (all parts), Infmation technology Specification and standardization of data elements ISO 19106: 1, Geographic infmation Profiles ISO 19107:2003, Geographic infmation Spatial schema ISO 19108:2002, Geographic infmation Tempal schema ISO 19109: 1, Geographic infmation Rules f application schema ISO 19110: 1, Geographic infmation Methodology f feature cataloguing ISO 19111:2003, Geographic infmation Spatial by codinates ISO 19112: 1, Geographic infmation Spatial by geographic identifiers ISO 19115:2003: 1, Geographic infmation Metadata ISO 19115:2006: 1, Geographic infmation Metadata, Technical Crigendum 1 ISO/DIS , Geographic infmation Metadata Part 1: Fundamentals, Nov 2011 (NOTE: This is a DRAFT International Standard) ISO :2009, Geographic infmation - Metadata - Part 2: Extensions f imagery and gridded data ISO 19118: 1, Geographic infmation Encoding 17

20 ISO 19139:2007 1, Geographic infmation Metadata XML schema implementation NGA.STND.0012_2.1, National System f Geospatial-Intelligence (NSG) Metadata Framewk (NMF) Part 1: Conceptual Schema Profile, Version 2.1 NGA.STND _1.0.0, National System f Geospatial-Intelligence (NSG) Metadata Framewk (NMF) Part 2: Quality Metadata, Version 1.0 NGA.STND _1.0.0, National System f Geospatial-Intelligence (NSG) Metadata Framewk (NMF) Part 3: Metadata f Imagery and Gridded Data, Version Infmative References The following publications were referenced to suppt the development of this Profile. Content Standard f Digital Geospatial Metadata Wkbook, Version 2.0, May 1, 2000, Federal Geographic Data Committee Defence Imagery and Geospatial Organisation, Data Management Profile of ISO 19115:2003 Geographic Infmation Metadata, Draft Version 1.15, Australian Government Department of Defence, Intelligence & Security. Department of Defense Manual Vol. 1, DoD Infmation Security Program: Overview, Classification, and Declassification, February 24, 2012, Under Secretary f Intelligence. Department of Defense Manual Vol. 2, DoD Infmation Security Program: Marking of Classified Infmation, February 24, 2012, Under Secretary f Intelligence. Department of Defense Manual Vol. 4, DoD Infmation Security Program: Controlled Unclassified Infmation (CUI), February 24, 2012, Under Secretary f Intelligence. Department of Defense Instruction Sharing Data, Infmation, and Infmation Technology (IT) Services in the Department of Defense, August 5, 2013, Department of Defense Chief Infmation Officer. Department of Defense Infmation Technology Standards Registry (DISR) Baseline, Release , October 25, 2006, Deputy Chief Infmation Officer. Department of Defense Installation Visualization Tool Quality Assurance Plan (IVT QAP), Version 1.1, December 31, 2003, IVT Program Office, Headquarters Air Fce Geo Integration Office. Content Standard f Digital Geospatial Metadata(CSDGM), Version 2.0, 1998, Federal Geographic Digital Committee (FGDC). Federal Geographic Digital Committee (FGDC) International Standardization Organization (ISO) Crosswalk, Version 4.0, April 17, 2003, Intergraph Cpation. 18

21 National System f Geospatial-Intelligence (NSG) Metadata Framewk (NMF) Part 1: Conceptual Schema Profile, Version 2.1, February 2012, National Geospatial-Intelligence Agency (NGA). White Paper: A Common DoD Business Mission Area Metadata Profile, October 12, 2006, Defense Installation Spatial Data Infrastructure (DISDI). 19

22 3 Definitions This section provides definitions f terms used in this document. The standard specification indicated in brackets is the authitative source of the definition. abstract test case (ATS) generalized test f a particular requirement [ISO 19105] NOTE An abstract test case is a fmal basis f deriving executable test cases. One me test purposes are encapsulated in the abstract test case. An abstract test case is independent of both the implementation and the values. It should be complete in the sense that it is sufficient to enable a test verdict to be assigned unambiguously to each potentially observable test outcome (i.e. sequence of test events). abstract test method method f testing implementation independent of any particular test procedure [ISO 19105] abstract test module a set of related abstract test cases [ISO 19105] NOTE Abstract test modules may be nested in a hierarchical way. abstract test suite an abstract test module specifying all the requirements to be satisfied f confmance [ISO 19105] application schema conceptual schema f data required by one me applications [ISO 19101] attribute see feature attribute base standard ISO geographic infmation standard other infmation technology standard that is used as a source which a profile may be constructed [ISO 19106] basic test initial capability test intended to identify clear cases of non-confmance [ISO 19105] business rule guidance and documentation to describe and standardize the use of metadata elements that best suppt a community s needs [DCMI] business mission area A defined area of responsibility with function and processes contributing to mission accomplishment. capability test 20

23 test designed to determine whether an IUT confms to a particular characteristic of an International Standard as described in the test purpose [ISO 19105] class description of a set of s that share the same attributes, operations, methods, relationships, and semantics [adapted ISO/IEC 19501] codelist a code list is a list of coded values that can be used to describe an open enumeration and shall be used if only the likely an initial set of allowed values are known. This means that it may need to be represented and implemented in such a way that it can be extended during system runtime. [adapted 19103] component The Office of the Secretary of Defense, the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, and the Defense Agencies. conceptual model model that defines the concepts of a universe of discourse [ISO 19101] conceptual schema fmal description of a conceptual model [ISO 19101] confmance fulfillment of specified requirements [ISO 19105] NOTE F the NMF, the concept of confmance pertains to the confmance of specifications, including any profile functional standard, with the series of ISO geographic infmation standards as a whole, plus NMF-authized extensions to those geographic infmation standards. content metadata schema that defines data (including metadata) structures, including the types of elements, sub-elements, and values they can contain [Getty Library - Introduction to Metadata] codinate reference system codinate system that is related to an by a datum [ISO 19111] NOTE 1 A codinate system is a set of mathematical rules f specifying how codinates are to be assigned to points. [ISO 19111] NOTE 2 A datum is a parameter set of parameters that define the position of the igin, the scale, and the ientation of a codinate system. [ISO 19111] 21

24 coverage NOTE 3 A codinate is one of a sequence of n numbers designating the position of a point in n-dimensional space. 3 [ISO 19111] feature that acts as a function to return values its range f any direct position within its spatiotempal domain [ISO 19123] dataset EXAMPLES A raster image, a polygon overlay, and a digital elevation matrix. [ISO 19123, 5.1.1] NOTE In other wds, a coverage is a feature that has multiple values f each attribute type, where each direct position within the geometric representation of the feature has a single value f each attribute type; it associates positions within a bounded space (its domain) to feature attribute values (its range). It is both a feature and a function. [ISO 19123, 5.1.1] identifiable collection of data [ISO 19115] data type specification of a value domain with operations allowed on values in this domain [ISO 19103] entity EXAMPLES An Integer, a Real, a Boolean, a CharacterString, and a Date. NOTE Data types include primitive predefined types and user-definable types. set of metadata elements describing the same aspect of data [ISO 19115] event action which occurs at an instant [ISO 19108] extension the addition of infmation not included in the content being extended [adapted 19106] externally-specified specification a specification referenced by the NSG Metadata Foundation (NMF) document feature abstraction of real wld phenomena [ISO 19101] feature attribute characteristic of a feature [ISO 19101] 3 In a codinate reference system, the n numbers shall be qualified by units. 22

25 geospatial refers to either an implicit explicit reference to a location relative to the earth. geographic dataset a dataset that represents physical geospatial features. Not to be confused with vendspecific implementations (f example, ESRI dataset). geospatial infmation infmation that identifies the geographic location and characteristics of natural constructed features and boundaries on the earth, including statistical data; infmation derived, among other things, remote sensing, mapping, and surveying technologies; and mapping, charting, and geodetic data, including geodetic products. [Title 10 US Code 467] geospatial infmation & services The concept f collection, infmation extraction, stage, dissemination, and exploitation of geodetic, geomagnetic, imagery, gravimetric, aeronautical, topographic, hydrographic, littal, cultural, and toponymic data accurately referenced to a precise location on the earth s surface. These data are used in the battlespace f military planning, training, and operations, including navigation, mission planning, mission rehearsal, modeling, simulation, and precise targeting, as well as in the basing space to provide situational awareness f fce protection and management of the built and natural infrastructure. F the purposes of this specification, Installation GI&S (IGI&S) refers to the subset of GI&S activities that enhance the DoD I&E business mission area and suppt I&E business enterprise priities as defined in the DoD Business Enterprise Architecture. IGI&S are considered complimentary to but different GEOINT, and are managed as DoD infmation resources and infmation technology as defined in EO 12906, DoD Directives and Geospatial infmation provides the basic framewk f IGI&S. It is infmation produced by multiple sources to common interoperable data standards. It may be presented in the fm of printed maps, charts, and publications; in digital simulation and modeling databases; in photographic fm; in the fm of digitized maps and charts attributed centerline data. Geospatial services include tools that enable users to access and manipulate data and also include instruction, training, labaty suppt, and guidance f the use of geospatial data. geospatial intelligence (GEOINT) the exploitation and analysis of imagery and geospatial infmation to describe, assess, and visually depict physical features and geographically referenced activities on the Earth. [Title 10 U.S. Code 467] NOTE Consists of imagery, imagery intelligence, and geospatial infmation geospatial intelligence standard documented agreement containing technical specifications other precise criteria to be used consistently as rules, guidelines, definitions of characteristics to ensure that 23

26 materials, products, processes, services are fit f the analysis and visual representation of physical features and geographically referenced activities. geospatial metadata infmation which captures the basic characteristics of a data resource; represents the who, what, when, where, why and how of the resource. image gridded coverage whose attribute values are a numerical representation of a physical parameter [ISO ] imagery NOTE The physical parameters are the result of measurement by a sens a prediction a model. representation of phenomena as images produced by electronic and/ optical techniques [ISO/TS ] NOTE1 It is assumed that the s and phenomena have been sensed detected by camera, infrared and multispectral scanners, radar and photometers, similar devices. NOTE2 A likeness presentation of any natural manmade feature related of activity and the positional data acquired at the same time that the likeness representation was acquired. implementation realization of a specification. In the context of the ISO geographic infmation standards, this includes specifications of geographic infmation services and datasets [ISO 19105] infmation knowledge concerning s, such as facts, events, things, processes, ideas, including concepts, that within a certain context has a particular meaning [ISO 19118] measure value described using a numeric amount with a scale using a scalar reference system [ISO 19136] NOTE 1 metadata When used as a noun, measure is a synonym f physical quantity. NOTE 2 A physical quantity is a quantity used f the quantitative description of physical phenomena. 4 data about data [ISO 19115] 4 In GML a physical quantity is always a value described using a numeric amount with a scale using a scalar reference system. 24

27 metadata element discrete unit of metadata [ISO 19115] NOTE 1 NOTE 2 metadata entity Metadata elements are unique within a metadata entity. Equivalent to an attribute in UML terminology. set of metadata elements describing the same aspect of data [ISO 19115] NOTE 1 NOTE 2 metadata mapping May contain one me metadata entities. Equivalent to a class in UML terminology. table that maps the relationships and equivalencies between two me metadata schemes. Crosswalks metadata mapping suppt the ability of search engines to search effectively across heterogeneous databases. [DCMI] metadata package metadata is presented in UML packages, called metadata packages. Each package contains one me entities (UML Classes), which can be specified (subclassed) generalized (superclassed). [ISO 19115] metadata section subset of metadata which consists of a collection of related metadata entities and metadata elements [ISO 19115] model NOTE Equivalent to a package in UML terminology. abstraction of some aspects of reality [ISO 19109] national system f geospatial intelligence the combination of technology, policies, capabilities, doctrine, activities, people, data, and communities necessary to produce geospatial intelligence in an integrated multiintelligence, multi-security domain environment profile set of one me base standards subsets of base standards, and, where applicable, the identification of chosen clauses, classes, options and parameters of those base standards, that are necessary f accomplishing a particular function [ISO/IEC TR ] quality NOTE A profile is derived base standards so that by definition, confmance to a profile is confmance to the base standards which it is derived. totality of characteristics of a product that bear on its ability to satisfy stated and implied needs [ISO 19101] 25

28 raster usually rectangular pattern of parallel scanning lines fming cresponding to the display on a cathode ray tube [ISO 19123] registry infmation system on which a register is maintained [adapted :1994] remote sensing collection and interpretation of infmation about an without being in physical contact with the [ISO/TS ] resource asset means that fulfills a requirement [ISO 19115] specification declarative description of what something is does [adapted ISO/IEC 19501] unit of measure reference quantity adopted as a standard of measurement f other quantities of the same kind. [adapted ISO 19103] EXAMPLE value domain The unit of measure metre the categy length. set of accepted values [ISO/IEC 19103:2005] EXAMPLE The range 3-28, all integers, any ASCII character, enumeration of all accepted values (green, blue, white). 26

29 4 Abbreviations CRS Codinate Reference System CSDGM Content Standard f Digital Geospatial Metadata DDMS Department of Defense Discovery Metadata Specification DISDI Defense Installation Spatial Data Infrastructure DISDIG DISDI Group DISR Department of Defense Infmation Technology Standards Registry DMWG DISDI Metadata Wking Group DoD Department of Defense DSN Defense Switched Netwk FGDC Federal Geographic Data Committee IGI&S Installation Geospatial Infmation & Services GI&S Geospatial Infmation & Services I&E Installations & Environment ISO International Organization f Standardization NSG National System f Geospatial-Intelligence POC Point of Contact SDSFIE Spatial Data Standards f Facilities, Infrastructure, and Environment SME Subject Matter Expert UML Unified Modeling Language XML Extensible Markup Language 27

30 5 Confmance and Compliance 5.1 Introduction SDSFIE-M is a conceptual schema. The purpose of a conceptual schema is to capture the concepts and relationships of a domain model in a fm which is agnostic to the eventual choice of an implementing technology. Due to this level of abstraction, compliance with SDSFIE-M cannot be tested directly. Therefe, developers seeking to implement an SDSFIE-M compliant system shall first locate develop a confmant implementation specification 5. SDSFIE-M-confmant implementation specifications provide a validated specification f implementing the SDSFIE-M when employing a specific technology. The implementation specification then serves as a requirements specification that guides system development. Demonstration of compliance of the system with the implementation specification and then confmance of the implementation specification with SDSFIE-M shall constitute demonstration of compliance of the system with SDSFIE-M. SDSFIE-M is a profile of NMF and several International Standards. Except where modified in SDSFIE-M, those International Standards are the nmative authity f SDSFIE-M elements and entities. 5.2 Profiles and Confmance ISO 19106:2004 Geographic infmation - Profiles details two classes of confmance, which may be generally thought of as profile types. Confmant Class 1 profiles are a pure subset of the ISO geographic infmation standards. Confmance class 2 allows profiles to include extensions within the context permitted in the base standard and permits the profiling of non-iso geographic infmation standards as parts of profiles. When such a profile adds any infmation that is not covered in a base ISO geographic infmation standard other ISO standard, then the profile will not be processed as an ISO geographic infmation standard but may be established under the authity of the standards ganization, member body liaison ganization making the profile. Specifications that profile the SDSFIE-M Conceptual Schema may extend the SDSFIE- M Conceptual Schema to meet the metadata requirements of individual ganizations and systems. These include, e.g., I&E datasets, products, systems and services, profiles of the SDSFIE-M Conceptual Schema, application schemas, implementation specifications and any other documentation that is required to confm to this standard. Demonstration of the compliance of a specification with SDSFIE-M requires both the determination that metadata elements and entities that are included in the SDSFIE-M Conceptual Schema (Class 1 profile confmance) are crectly implemented, and the 5 The DISDI Program Office will provide both an XML Schema-based SDSFIE Metadata Implementation Specification (SMIS) and template instance documents f vect datasets, imagery, and services that confm to SMIS. The DISDI Program Office will also issue an SMF Implementation Guidance document that provides implementation guidance details. 28

31 determination that metadata elements and entities that are valid extensions to the SDSFIE-M Conceptual Schema (Class 2 profile confmance) are crectly implemented. The validity of metadata extensions shall be tested using the 19115:2003/C 1:2006 rules f metadata extensions. 5.3 Confmance Ce Confmance Confmance with this standard shall be a requirement f any specification claiming to be an SDSFIE-M profile (confmance class 1 2). The minimum and recommended sets of metadata elements, their content, rules, relationships and representations, as described conceptually in this standard can be tested through the use of a defined set of confmance criteria. Any implementation claiming confmance to SDSFIE-M shall satisfy the criteria found in the Abstract Test Suite (ATS) in Annex C of this standard. That test suite includes criteria f confmance with the content, rules, and encoding requirements of the SDSFIE-M Conceptual Schema, its profiles, and all nmatively-cited ISO, IC, and DoD documentation Profile Confmance Requirements Confmance with the provisions of the SDSFIE-M Conceptual Schema is addressed in two related, yet distinct, categies of SDSFIE-M profile confmance. Confming profiles: SDSFIE-M allows f the documentation of applicationspecific profiles of the SDSFIE-M Conceptual Schema. Profiles of the SDSFIE-M Conceptual Schema shall confm to the requirements and provisions of Section B.2, Profiling the SDSFIE-M Conceptual Schema. Approved profiles: SDSFIE-M has provisions f establishing additional profiles of the SDSFIE-M Conceptual Schema. Application implementation of approved SDSFIE-M profiles shall confm to the obligations and business rule constraints established by that specific profile Implementation Specification Confmance Requirements An implementation specification realizes a conceptual schema in a fm that can be directly implemented using a specific technology. Development of an implementation specification shall follow the rules f an ISO Class 2 profile where the community requirements are the rules, structures and conventions of the implementation environment. As a profile of the SDSFIE-M Conceptual Schema, any Implementation Specification of the SDSFIE-M Conceptual Schema shall demonstrate confmance with SDSFIE-M as described in Section Compliance Compliance with the SDSFIE-M Conceptual Schema is defined in terms of confmance of derivative specifications (implementation specifications and profiles) to the conceptual schema. Ultimately SDSFIE-M must be implemented in software, data 29

32 structures and logic; the compliance of an implementation with SDSFIE-M must be testable. Therefe, developers seeking to implement SDSFIE-M shall perfm the following actions to demonstrate compliance: Locate develop an SDSFIE-M implementation specification f the target implementation environment. Demonstrate confmance of the implementation specification to the SDSFIE-M Conceptual Schema. that implementation specification as a requirements specification to guide system development. Demonstrate compliance of the system with that implementation specification. These steps fm a chain of verification that the system has crectly implemented the SDSFIE-M Conceptual Schema. Compliance with the conceptual schema is not enough to guarantee interoperability. To that end, the following requirements shall apply to any system that implements an SDSFIE-M -based implementation specification, profile, the conceptual schema itself. These requirements help to assure that SDSFIE-M implementations successfully interoperate. Any specification claiming compliance with this standard shall meet the following requirements: A compliant implementation shall populate all mandaty elements with valid values. A compliant implementation when populating conditional optional elements must do so with valid values. A compliant implementation shall ingest and properly process all mandaty elements any compliant metadata set. A compliant implementation shall ingest any compliant metadata set containing valid conditional optional elements but is not required to process them in any meaningful manner (e.g., their values may be igned). 30

33 THIS PAGE IS INTENTIONALLY BLANK 31

34 6 Requirements 6.1 General Resource Model The SDSFIE-M Conceptual Schema Profile is intended to be applied in many I&E community resource contexts. An imptant use case f the SDSFIE-M Conceptual Schema Profile is the publication of metadata documenting the content of geospatial intelligence resources. Figure 1 presents a general-case model of a geospatial intelligence resource whose content shall be documented using metadata intended to suppt its discovery and content exchange. Resource Dataset Series Entity {abstract} Metadata Subclasses Event Feature Coverage Infmation (e.g., pirate attack) (e.g., building, road) (e.g., image, grid) (e.g., place-name, sens) Figure 1 : General Resource Model The fundamental building-block of the resource content is the abstract Entity class, which has identity and whose subclasses are used to model different types of geospatial phenomena (e.g., events, features, coverages and other types of geospatial infmation). Entities may be ganized into sets (the Dataset class) accding to some rationale (e.g., common production publication process). Entities may simultaneously be members of multiple datasets, e.g., a lighthouse may participate in an air obstruction product, a maritime navigation product, and a map product. Furtherme, datasets may be grouped (by the Series class) accding to some strategy (e.g., a repeated process that is sequentially applied to different spatial and/ tempal extents). A series might consist of an atlas of the primary and secondary highways of each of the 48 contiguous states of the US, where each state-specific highway dataset is prepared and/ updated as local data sources become available, but all adhere to a common specification (feature catalog, application schema, and production processes). 32

35 Metadata is used to describe the abstract Entity class; therefe, metadata can be used to describe any of the subclasses of the abstract Entity class. 6.2 Metadata Requirement f Geographic Data This section focuses on the metadata packages specified in SDSFIE-M (section 7.4). These metadata packages are used to describe DoD Installation and Environment (I&E) geospatial assets to suppt their discovery and end use. The requirement to have these metadata applies to all I&E geospatial feature types and their aggregations. Figure 2 depicts all the SDSFIE-M metadata packages (the boxes in the figure) and the hierarchical relationships between the packages (the arrows). Figure 2 : SDSFIE-M Metadata Packages SDSFIE-M metadata packages are also listed in Table 1. This table provides a description of the metadata package and an indication as to whether it is mandaty f all data sets (Mandaty) its inclusion in a metadata set is elective (Optional). Any Optional SDSFIE-M metadata package can be mandated as required by policy at the Component installation level f some all geospatial data resources in their jurisdiction. 33

36 Section Name Obligation Description Metadata Entity Set Infmation (MD_Metadata) Identification Infmation (MD_Identification) Constraints Infmation (MD_Constraint) Data Quality Infmation (DQ_DataQuality) Maintenance Infmation (MD_Maintenance) Spatial Representation Infmation (MD_SpatialRepresentation) Reference System Infmation (MD_ReferenceSystem) Content Infmation (MD_ContentInfmation) Application Schema Infmation (MD_ApplicationSchema) Imagery Acquisition Infmation (MI_Imagery) Mandaty Mandaty Mandaty Optional Mandaty Optional Mandaty Optional Optional Conditional The Metadata Entity Set Infmation provides the overview descriptions necessary to establish understanding and use of the metadata entity. Identification infmation is used to specifically identify the data being described by the metadata. Constraint infmation is used to describe legal and security constraints placed on the resource to suppt access and use requirements. Data quality infmation. Maintenance infmation provides a clear understanding of how the resource is managed. Spatial representation infmation repts the spatial mechanisms of vect and gridded resources. Reference system infmation provides the necessary data to identify how a spatial resource is positioned relative to the earth. Content infmation captures details relevant to a feature catalog and the description of the coverage. Application schema infmation provides the means to rept details regarding an application s use of the metadata. Designations f the measuring instruments, the platfm carrying them, and the mission to which the data contributes Extent (EX_Extent) Mandaty Extent provides f various descriptions of the geographic, tempal, and vertical extent of the resource Citation (CI_Citation) Mandaty Citation provides f description of authitative reference infmation, including responsible party and contact infmation. Table 1 : SDSFIE-M metadata packages and their cresponding obligations. 34

37 THIS PAGE IS INTENTIONALLY BLANK 35

38 7 SDSFIE-M Conceptual Schema Profile 7.1 Introduction The SDSFIE-M Conceptual Schema Profile defines what we all must understand (as a set of metadata concepts) in the I&E community regarding geospatial metadata in suppt of (e.g.) data discovery, determining data fitness f use, data access, data transfer, and mission-specific use of IGI&S infmation. The SDSFIE-M Conceptual Schema Profile draws abstract metadata concepts a broad community of International, National, DoD, and IC standards. These are used as the basis f establishing a coherent set of metadata concepts that meet I&E community requirements f geospatial metadata. ISO 19115:2003/C 1:2006 serves as the primary source, specifically the ce metadata f geographic datasets that is defined in that International Standard. The Dublin Ce Metadata Set, DDMS and IC.ADD are then used to expand upon that Ce, by adding other concepts that are defined in 19115:2003/C 1:2006. The IC.ADD also defines additional security fields that are not present in the International Standard, so those concepts are presented as extensions to the 19115:2003/C 1:2006 Security package. The ISO 19115:2003/C 1:2006 standard is defined using Unified Modeling Language (UML) diagrams 6. As the SDSFIE-M Conceptual Schema Profiles is a profile of NMF and, therefe, 19115:2003/C 1:2006, it is also defined using UML diagrams. F an introduction on understanding UML notation, see Annex D of this document. The SDSFIE-M Conceptual Schema Profile is specified as follows: Section 7.2 specifies the basic value domains (data types, code lists, and enumerations) used by the Conceptual Schema Profile; Section 7.3 specifies the structure of the tables used to specify the Conceptual Schema data dictionary; Section 7.4 specifies the resource metadata sections Section specifies the metadata entity set metadata elements; Section specifies the identification metadata elements; Section specifies the constraints metadata elements; Section specifies the data quality metadata elements; Section specifies the maintenance metadata elements; Section specifies the spatial representation system metadata elements; Section specifies the reference system metadata elements; Section specifies the identifier metadata elements; 6 In fact, all ISO standards in the 1900 series are defined using UML. 36

39 Section specifies the content infmation metadata elements; Section specifies the application schema metadata elements; Section specifies the acquisition infmation metadata elements; Section specifies the extent metadata elements; Section specifies the citation and responsible party metadata elements; 7.2 Value Domains In this SDSFIE-M Conceptual Schema Profile the specification of value domains provides a nmalization of metadata values in der to ensure that two community members exchanging infmation speak the same conceptual encoding language. The SDSFIE-M Conceptual Schema Profile draws on ISO/TS f its abstract types when specifying value domains; Section Annex B specifies the definitions f these datatypes. The SDSFIE-M Conceptual Schema Profile, however, requires additional types in der to unambiguously specify value domains. These fall into four categies: Datatypes expressing complex content directly indirectly in a CharacterString these are specified in Table 2; Codelists expressing a resource-managed value in a CharacterString these are specified in Table 3; Enumerations expressing fixed values in a CharacterString these are specified in Table 4; and Complex datatypes consisting of multiple elements whose value domains are either abstract types, datatypes, Codelist, Enumeration values Datatypes The SDSFIE-M Conceptual Schema Profile specifies unique datatypes; each expresses complex content as a CharacterString who s allowed values are constrained to follow specific semantics (and syntax). These datatypes are specified in Table 2. Name/Definition TelephoneNumber An internationalized telephone number as specified in ITU-T Recommendation E.123 Clause 2. NOTE1: The international prefix symbol is a + (plus) and should precede the country code in the international number. It serves to remind the subscriber to dial the international prefix which differs country to country and also serves to identify the number following as the international telephone number. NOTE2: Spacing symbols are symbols that are used solely to separate parts of a telephone number each other. They cannot be dial-able, procedural infmation symbols. Grouping of digits in a telephone number should be accomplished only through the use of spaces in an international number. In the international number, spacing shall occur between the country code and the trunk code and between the trunk code and the subscriber number. NOTE3: A slash (/) may not be used to indicate alternate numbers; instead separate element(s) shall be populated. Example(s)

40 Name/Definition CrsIdentifier An identification of a spatial (codinate) reference system. NOTE1: Represented as a single URL with two distinguishable components separated by a fward-slash ( / ) character. NOTE2: The first component is a well-fmed RestrictedURI expressing an authitative namespace within which codinate reference systems are designated; it may be treated as optional if its value can be determined the context of use. NOTE3: The second component is an unambiguous identifier of a codinate reference system in the authitative namespace; it consists of a character string of length at least one, and restricted such that it must not contain any of the following characters: : (colon), (space), / (fward slash), (new line), (carriage return), and (tab). 7 NOTE4: Using the fully-qualified CharacterString as a URL it shall be possible to unambiguously identify and access (e.g., via a catalog register) the parametric specification of the codinate reference system being referenced. Example(s) dse/ns/gsip/crs/ WGS84E_2D where the final substring designates the codinate reference system. WGS84E_2D where the authitative namespace URL can be determined in context. Table 2 : SDSFIE-M Conceptual Schema Profile Datatypes Codelists Data Agility The SDSFIE-M Conceptual Schema Profile uses the Codelist type (literally, a list of codes ) to specify the value domains f many metadata elements. The use of Codelists instead of free text a fixed enumeration has three principal advantages: They ensure that the lexical content of a metadata element is encoded in a consistent manner f a given concept. Even though the code may be a human-readable wd phrase, code lists eliminate variations in spelling, character case, spacing and other presentation facts to reduce the concept to a single unambiguous representation. They are independent of the conceptual schema and the metadata content. This allows Codelists to be profiled to meet evolving user needs without requiring changes to the conceptual schema. They provide a mechanism f encoding data f use in a multilingual environment. Because the codes provide a consistent representation f a given concept, suppting dictionaries containing definitions and human-readable labels in one me languages can be developed f presentation of Codelist infmation in multiple languages. Within a metadata instance document, the content of a metadata element that is specified as a Codelist value requires two pieces of infmation. In addition to the value itself, identification of the Codelist (value domain) is required in der f consumers of the metadata to interpret the value. One means to identify a value domain is publication and access of the values through a named register on common-access registry such as the DoD Metadata Registry (MDR). The Codelists used to specify value domains in the SDSFIE-M Conceptual Schema shall be specified in the MDR; accdingly their domains are not specified in this document, although example values are provided. 7 This restriction is efficiently specified by the XML Schema pattern "[^: /\n\r\t]+". 38

41 Codelist Value A Codelist value is an unambiguous identifier of a concept within a set of related concepts (e.g., country codes geometry types). A Codelist value may be designated through the use of a URL, allowing f the identification of the Codelist value to be tied to a resource where the semantic of the value may be maintained. F each Codelist the following rules apply: A domain value is represented as a CharacterString with two distinguishable components separated by a fward-slash ( / ) character. The first component is a RestrictedURI expressing an authitative namespace within which the Codelist value is designated; this first component may be treated as optional if its value can be determined the context of use. The second component is an unambiguous identifier of a value in the authitative Codelist namespace; it follows the XML schema pattern "[^: /\n\r\t]+" which ensures that the Codelist value excludes specific characters and is at least one character in length. Using the fully-qualified CharacterString as a URL it shall be possible to unambiguously identify and access (e.g., via a catalog register) the full specification of the Codelist value being referenced Conceptual Schema Profile Codelists The Codelists used by the SDSFIE-M Conceptual Schema Profile are specified in Table 3. The examples provided in Table 3 are not all-inclusive. All URLs containing DISDI may not be in-place at the time this document is published. Initial codelist values will be posted with SMIS when it is released. Name / Authitative Namespace(s) AssociationTypeCode justification f the crelation of two datasets NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile): DISDI: BandDefinitionCode designation of criterion f defining and minimum wavelengths f a spectral band NOTE: The allowed authitative namespaces are : ISO :2009 (profiled): DISDI: CellGeometryCode code indicating whether grid data is point, area, volume NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile): DISDI: Example(s) (not all-inclusive) "crossreference" "largerwkcitation" "partofseamlessdatabase" etc. 3dB halfmaximum fiftypercent oneovere equivalentwidth point area voxel 39

42 Name / Authitative Namespace(s) CharacterSetCode character coding standard used by the text of a resource NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (profiled): DISDI: ClassifiedCode a code indicating whether a resource is classified not. NOTE: The allowed authitative namespaces are: DISDI: ClassificationCode level of classification applicable to a resource, ption of a resource. NOTE: The allowed authitative namespaces are: DISDI: ContextCode designation of criterion f defining the context of the scanning process event NOTE: The allowed authitative namespaces are : ISO :2009: DISDI: CountryCode recognized geographic identifier that is a member of the list of countries maintained in the GENC standard. NOTE: The allowed authitative namespace is: DISDI: CouplingTypeCode type of coupling between service and associated data. NOTE: The allowed authitative namespaces are: ISO/DIS : DISDI: CoverageContentTypeCode specific type of infmation represented in the cell. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006: DISDI: Example(s) (not all-inclusive) utf8 etc. unclassified classified U (Unclassified) C (Confidential) S (Secret) TS (Top Secret) R (Restricted) acquisition pass waypoint US USA GB GBR etc. loose mixed tight "image" "thematicclassification" "physicalmeasurement" 40

43 Name / Authitative Namespace(s) DateTypeCode context with respect to which a date is specified. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile): DISDI: DCPList type of distributed computing platfm environment. NOTE: The allowed authitative namespaces are: ISO/DIS : DISDI: DimensionNameTypeCode name of the dimension. NOTE: The allowed authitative namespaces are: ISO :2009: DISDI: EvaluationMethodTypeCode type of method f evaluating an identified data quality measure. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile) DISDI: GeometricObjectTypeCode name of point vect s used to locate zero-, one-, two-, three-dimensional spatial locations in the dataset. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006: DISDI: GeometryTypeCode geometric description of the collection NOTE: The allowed authitative namespaces are : ISO :2009: DISDI ImagingConditionCode code which indicates conditions which may affect the image. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006: DISDI: Example(s) (not all-inclusive) creation publication revision etc. XML CORBA JAVA etc. "row" "column" "vertical" etc. directinternal directexternal indirect "complex" "composite" "curve" etc. point linear areal etc. "blurredimage" "cloud" "degradingobliquity" etc. 41

44 Name / Authitative Namespace(s) KeywdTypeCode method used to group a set of similar keywds. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile) DISDI: MaintenanceFrequencyCode frequency with which modifications and deletions are made to the data after it is first produced. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile): DISDI: MetadataStandardNameCode name of the metadata standard used. NOTE: The allowed authitative namespaces are: DISDI: NoticeTypeCode set of currently authized Notice values NOTE: The allowed authitative namespacs are:: ISM: urn:us:gov:ic:ism-cvenum Found in the schema file:./ic/ism/version/cvegenerated/cvenumismnotice.xml Where version is the version of IC-ISM used (currently this is ). DISDI (f the currently mandated version of ISM): ObjectiveTypeCode tempal persistence of collection ive NOTE: The allowed authitative namespaces are : ISO :2009: DISDI: OnlineFunctionCode function perfmed by the resource. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile): DISDI: ParameterDirection indication if the parameter is an input to the service, an output both. NOTE: The allowed authitative namespaces are: ISO/DIS : DISDI: Example(s) (not all-inclusive) discipline place stratum etc. continual daily weekly etc. sdsfiemetadata RD IMCON FRD etc. instantaneouscollection persistentview survey "download" "infmation" "offlineaccess" etc. in out inout 42

45 Name / Authitative Namespace(s) PolarisationOrientationCode polarisation of the antenna relative to the wavefm NOTE: The allowed authitative namespaces are : ISO :2009 (profiled): DISDI PriityCode dered list of priities NOTE: The allowed authitative namespaces are : ISO :2009 (profiled): DISDI: PresentationFmCode mode in which the data is represented NOTE: The allowed authitative namespaces are : ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile) DISDI: ProgressCode status of the dataset progress of a review NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile) DISDI: RestrictionCode limitation placed upon the access to, use of, a resource. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (profiled) DISDI: RoleCode function perfmed by a responsible party f a resource. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile) DISDI: ScopeCode class of infmation to which the entity applies. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (profiled): DISDI: Example(s) (not all-inclusive) hizontal vertical leftcircular etc. critical highimptance mediumimptance etc. documentdigital" "documenthardcopy" "imagedigital" etc. "completed" "histicalarchive" "obsolete" etc. copyright intellectualpropertyrights restricted etc. resourceprovider custodian owner etc. dataset series feature etc. 43

46 Name / Authitative Namespace(s) ScopeAmplificationCode A set of scope amplifications individually identifying an augmentation of an identified grouping of infmation within a resource. NOTE: The allowed authitative namespaces are : DISDI: SequenceCode tempal relation of activation NOTE: The allowed authitative namespaces are : ISO :2009: DISDI SpatialRepresentationTypeCode method used to represent geospatial infmation in a resource. NOTE: The allowed authitative namespaces are: ISO 19115:2003/C. 1:2006 (as extended by the Nth American Profile) DISDI: TopologyLevelCode code which identifies the degree of complexity of the spatial relationships NOTE: The allowed authitative namespaces are : DISDI: TransferFunctionTypeCode transfm function to be used when scaling a physical value f a given element NOTE: The allowed authitative namespaces are : ISO :2009: DISDI TriggerCode Mechanism of activation NOTE: The allowed authitative namespaces are : ISO :2009: DISDI Example(s) (not all-inclusive) cell theme notapplicable etc. start end instantaneous vect grid texttable etc. geometryonly topology1d planargraph etc. linear logarithmic exponential automatic manual preprogrammed Table 3 : SDSFIE-M Conceptual Schema Codelists Enumerations An Enumeration value is an unambiguous identifier of a concept within a fixed, finite set of related concepts. Unlike a Codelist this set may not be extended without a schema modification. The following subsections specify the Enumerations used in the SDSFIE- M Conceptual Schema Profile TopicCategy The Enumeration TopicCategy is defined as follows: 44

47 TopicCategy A high-level geographic data thematic classification that assists in the grouping and search of available geospatial data sets. NOTE1 NOTE2 May be used to group keywds as well. The listed example topic members are not exhaustive. It is understood there are overlaps between general categies and the user is encouraged to select the one most appropriate. Its domain members (enumerants) are specified in Table 4; f each the following infmation is specified: domain Code a 3-digit numeric code that may be used where compactness in denotation is desirable; concept Topic a human-interpretable camel-case designation f the topic; concept Definition; and Example Topic Members concepts that fall within the scope of the topic categy. Code Topic Definition Example Topic Members 001 farming The rearing of animals and/ the cultivation of plants. 002 biota Fla and/ fauna in the natural environment. Agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock. Wildlife, vegetation, biological sciences, ecology, wilderness, sea life, wetlands, and habitat. 003 boundaries Legal land descriptions. Political and administrative boundaries. 004 climatologymeteology Atmosphere 8 Processes and phenomena of the atmosphere. 005 economy Economic activities, conditions and employment. Cloud cover, weather, climate, atmospheric conditions, climate change, and precipitation. Production, lab, revenue, commerce, industry, tourism and ecotourism, festry, fisheries, commercial subsistence hunting, explation and exploitation of resources such as minerals, oil and gas. 006 elevation Height above below sea level. Altitude, bathymetry, digital elevation models, slope, and derived products. 007 environment environmental resources, protection and conservation 008 geoscientificinfmation Infmation pertaining to earth sciences. 009 health Health, health services, human ecology, and safety. 010 imagerybasemaps EarthCover8 Base maps. 011 intelligencemilitary Military bases, structures, and activities. Environmental pollution, waste stage and treatment, environmental impact assessment, moniting environmental risk, nature reserves, and landscapes. Geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and igin of the earth s rocks, risks of earthquakes, volcanic activity, landslides, gravity infmation, soils, permafrost, hydrogeology, and erosion. Disease and illness, facts affecting health, hygiene, substance abuse, mental and physical health, and health services. Land cover, topographic maps, imagery, unclassified images, and annotations. Barracks, training grounds, military transptation, and infmation collection. 8 Although split over two lines f presentation purposes this is a single string with no breaks. 45

48 Code Topic Definition Example Topic Members 012 inlandwaters Inland water features, drainage systems and their characteristics. 013 location Positional infmation and services. 014 oceans Features and characteristics of salt water bodies (excluding inland waters). 015 planningcadastre Infmation used f appropriate actions f future use of the land. 016 society Characteristics of society and cultures. Rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, and hydrographic charts. Addresses, geodetic netwks, control points, postal zones and services, and place names. Tides, tidal waves, coastal infmation, and reefs. Land use maps, zoning maps, cadastral surveys, and land ownership. Settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, and census infmation. 017 structure Man-made constructions. Buildings, museums, churches, facties, housing, monuments, shops, and towers. 018 transptation Means and aids f conveying persons and/ goods. 019 utilitiescommunication Energy, water and waste systems and communications infrastructure and services. Table 4 : Enumeration MD_TopicCategy Domain Values PixelOrientationCode The Enumeration PixelOrientation is defined as follows: PixelOrientationCode Point in a pixel cresponding to the Earth location of the pixel Roads, airpts/airstrips, shipping routes, tunnels, nautical charts, vehicle vessel location, aeronautical charts, and railways. Hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, and communication netwks. Its domain members (enumerants) are specified in Table 5; f each the following infmation is specified: domain Code a 3-digit numeric code indicating the maturity rating; concept Maturity a human-interpretable camel-case designation f the rating; concept Description - a description of the criteria f each rating; and Code Orientation Description 000 center point halfway between the lower left and the upper right of the pixel 001 lowerleft the cner in the pixel closest to the igin of the SRS; if two are at the same distance the igin, the one with the smallest x-value 002 lowerright next cner counterclockwise the lower left 003 upperright next cner counterclockwise the lower right 004 upperleft next cner counterclockwise the upper right 005 center point halfway between the lower left and the upper right of the pixel 46

49 Table 5 : Enumeration MD_PixelOrientationCode Domain Values 47

50 7.3 Element Table Structure Introduction Each subsection in Section 7.4 contains a UML diagram and a data dictionary table. The data dictionary tables provide definitions and explanations to go along with the UML diagram in der to fully define the metadata. The dictionary is specified in a hierarchy to establish relationships and an ganization f the infmation. The UML diagrams contained in Section 7.4 are profiled versions of the UML diagrams contained in ISO 19115:2003/C 1:2006, ISO :2009, ISO/DIS , NMF Parts 1-3. Some classes, attributes and association roles have been hidden and some have been extended because they do not apply to SDSFIE-M. F the full diagrams, consult the relevant ISO document. F the data dictionary tables in Section 7.4, 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 six attributes (as listed below). The term dataset, when used as part of a definition, is synonymous with all the types of aggregated geographic data attributes (all members the NMF_ScopeCode codelist) Name A label assigned to a metadata entity to a metadata element. Metadata entity names start with an upper case letter. Spaces do not appear in a metadata entity name. Instead, multiple wds are concatenated, with each new subwd starting with a capital letter (example: XnnnYmmm). Metadata entity names are unique within the entire data dictionary of this document. Metadata element names are unique within a metadata entity, not the entire data dictionary of this document. 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 other metadata elements Definition The metadata entity/element description Obligation/Condition General This is a descript indicating whether a metadata entity metadata element shall always be documented in the metadata sometimes be documented (i.e. contains value(s)). This descript may have the following values: M (mandaty), C (conditional), O (optional) Mandaty The metadata entity metadata element shall be documented. 48

51 Conditional Specifies an electronically manageable condition under which at least one metadata entity a metadata element is mandaty. Conditional is used f one of the three following possibilities: Expressing a choice between two me options. At least one option is mandaty and must be documented. Documenting a metadata entity a metadata element if another element has been documented. Documenting a metadata element if a specific value f another metadata element has been documented. To facilitate reading by humans, the specific value is used in plain text (ex. "C/not defined by encoding? ). If the answer to the condition is positive, then the metadata entity the metadata element shall be mandaty. The conditions are typically supplied as footnotes to make the table me legible Optional A metadata recd may may not include a metadata entity the SDSFIE-M, and may may not specify a value of a metadata element in SDSFIE-M. Optional metadata entities and optional metadata elements provide a guide to those looking to fully document their data when preparing a metadata recd. ( of this common set of defined elements will help promote interoperability among geographic data users and producers in the I&E community.) If an optional metadata entity is not included in a metadata recd, then the metadata elements contained within that entity (including mandaty elements) shall have no specified values. If an optional metadata entity is included in a metadata recd, then the mandaty metadata elements contained within that entity shall have specified values. If a metadata entity (optional otherwise) is included in a metadata recd and there are no mandaty metadata elements contained within that entity, then at least one conditional optional element contained within that entity shall have a specified value. The choice of which metadata element shall become mandaty is determined by a conditional expression in the context in which the metadata entity is referenced (the UML class whose association role references the metadata entity UML class) Maximum Specifies the number of instances the metadata entity 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 cresponding number (i.e. 2, 3 etc.). 49

52 Multiplicity should always be understood to apply to the specified metadata element as a whole regardless of the nature (e.g., complex) of its value domain. Conversely, multiplicity should always be understood to be only applicable (meaningful) within the scope of the table within which the element is specified. F example, while a point of contact shall have exactly one postal address, that postal address may have multiple delivery point element values (e.g., a street address as well as a suite number). The multiplicity of the Contact (in whatever table it appears) would then be exactly one with a value domain of ContactPostalAddress, however the table specifying the Contact Postal Address would contain a line (element) specifying a Delivery Point with a multiplicity of one me (with a value domain perhaps of CharacterString). The types of possible multiplicity statements are listed in Table 6. Multiplicity Definition Implied Obligation Exactly one Example: 1 At least one Example: 1..* Exact number Example: 3 Exact range Example: 2..4 Zero one Example: 0..1 Zero me Example: 0..* Exact range (possibly empty) Example: 0..3 Exactly one value is permitted. At least one value is required, and multiple value s are permitted. Exactly the specified number of value s must be present. At least the number of value s specified in the lower range limit must be present; no me value s than the specified upper range limit may be present. Possibly one; zero one value is permitted. A possibly empty range; zero me value s are permitted. No s are permitted; no me s than the specified upper range limit may be present. Table 6 : Multiplicity and Implied Obligation Minimum Minimum Minimum Minimum Additional Additional Additional Datatype / Domain Specifies a set of distinct values f representing the metadata elements; f example, integer, real, string, DateTime, and Boolean. The data type attribute is also used to define metadata entities, stereotypes, and metadata associations. In cases where the value domain is complex, a reference is provided to the section that specifies its complex content requirement. When this occurs no example is specified, that table cell grey-filled, and the example is instead specified in the referenced section. The domain specifies the values allowed the use of free text. indicates that no restrictions are placed on the content of the field. Integer-based codes shall be used to represent values f domains containing codelists Business Rule Business rules describe the operation of an enterprise and can relate to something as high-level as privacy security, as low-level as the derivation of a particular 50

53 metadata element value. It is generally not appropriate to build such constraints routinely into implementation database structures even interfaces. However, such rules are still imptant and must be discerned, documented and accommodated in such a way that implementers will not overlook their imptance, requirements builders will fully understand their impact, and acquisition personnel will recognize their necessity. Details on business rules can be found in Section A

54 7.4 Resource Metadata Sections Metadata Entity Set Metadata Entity Set UML This UML diagram presented in this section is a SDSFIE-M -specific version of the cresponding Metadata Entity Set Package UML diagrams found in ISO 19115:2003/C 1:2006 (Figure A.1) and NMF Part 1 (Figure 2). The diagram has been profiled, so some classes, attributes and association roles have been hidden. F the full diagram, consult ISO 19115:2003/C 1:2006. This diagram shows containment relationships with the other metadata classes which, in aggregate, define metadata f geographic data Metadata Entity Set Figure 3 : Metadata Entity Set The data dictionary (Table 9) presented in this section is an SDSFIE-M -specific version of the cresponding Metadata Entity Set data dictionary table found in NMF Part 1 (Table 7). The table has been extended, so some classes, attributes and association roles have been added and some domains have been modified. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule 52

55 MD_Metadata root entity which defines metadata about a resource resources M 1 Class fileidentifier unique identifier f this metadata file M 1 CharacterString / language language used f documenting metadata M 1 CharacterString / ISO 639-2, other parts may be used Default value: en characterset full name of the character coding standard used f the metadata set M 1 Class / CharacterSetCode <<CodeList>> ( ) See Table 3 (CharacterSetCode) Default value: utf8 parentidentifier file identifier of the metadata to which this metadata is a subset (child) C 1 CharacterString / Obligation: Required if there is an upper hierarchy level. hierarchylevel scope to which the metadata applies (see ISO 19115, Annex H f me infmation about metadata hierarchy levels) M N Class / ScopeCode <<CodeList>> ( ) See Table 3 (ScopeCode) Note: this element is optional in hierarchylevelname name of the hierarchy levels f which the metadata is provided M N CharacterString / ScopeAmplification Code <<CodeList>> ( ) See Table 3 (ScopeAmplification) Note: this element is optional in contact party responsible f the metadata infmation M N Class / CI_ResponsibleParty <<DataType>> ( ) In the case of me than a single contact element then the first of the set shall use the RoleCode pointofcontact. datestamp date that the metadata was created M 1 Class / Date (Annex B) metadatastandardname name of the metadata standard (including profile name) used M 1 CharacterString / MetadataStandardName <<CodeList>> ( ) See Table 3 (Metadata StandardNameCode) Default Value: SDSFIE-M Identifier 9 Note: This element is optional in metadatastandardversion version of the metadata standard (version of the profile) used M 1 CharacterString / It is recommended Best Practice that the version number follow the fmat. Note: This element is optional in dataseturi Unifmed Resource Identifier (URI) of the dataset to which the metadata applies O 1 CharacterString /

56 locale provides infmation about an alternatively used localized character string f linguistic extension O 1 Class / PT_Locale ( ) Obligation: Required when not defined by encoding. Note: This element has a of N in role name: spatialrepresentationinfo digital representation of spatial infmation in the dataset O N Association / MD_SpatialRepresentation <<Abstract>> ( ) role name: referencesysteminfo description of the spatial and tempal reference systems used in the dataset C N Association / MD_ReferenceSystem ( ) Obligation: Required if the resource includes codinates. 10 role name: identificationinfo basic infmation about the resource(s) to which the metadata applies M N Association / MD_Identification <<Abstract>> ( ) role name: contentinfo provides infmation about the feature catalogue and describes the coverage and image data characteristics O N Association / MD_ContentInfmation <<Abstract>> ( ) role name: dataqualityinfo provides overall assessment of quality of a resource(s) O N Association / DQ_DataQuality ( ) role name: metadataconstraints provides restrictions on the access and use of metadata M 2..N Association / MD_Constraints ( ) It is a Recommended Best Practice that there shall be two instances of MD_Constraints, one f MD_SecurityConstraint s and at least one f MD_LegalConstraints. role name: applicationschemainfo provides infmation about the conceptual schema of a dataset O N Association / MD_ApplicationSchemaInf mation ( ) role name: metadatamaintenance provides infmation about the frequency of metadata updates, and the scope of those updates O 1 Association / MD_MaintenanceInfmati on (7.4.5) Table 7 : Metadata Entity Set The MI_Metadata class is a specialization of MD_Metadata defined in ISO (Figure A.1) and retained in NMF Part 3 (Section , Figure 1). This class is used when documenting imagery gridded data. No additional profiling of this class has been perfmed to address I&E community requirements. 10 if spatialrepresentationtype in MD_DataIdentification is "vect", "grid", "tin" 54

57 Figure 4 : Metadata Entity Set, Extended f Imagery and Gridded Data The data dictionary table in this section is NMF Part 3 (Section , Table 6). No additional profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_Metadata root entity that defines infmation about imagery gridded data (MD_Metadata extended) condition Specified Class (MD_Metadata) role name: acquisitioninfmation provides infmation about the acquisition of the data C 11 N Association / MI_AcquisitionInfmation ( ) Obligation: Required when documenting imagery gridded data Locale Table 8 : Metadata Entity Set, Extension f Imagery and Gridded Data The data dictionary table presented in this section is an profile of the cresponding NMF Part 1 PT_Locale datatype (Section , Table 8). Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule 11 if spatialrepresentationtype in MD_DataIdentification is "grid" 55

58 PT_Locale identification of the human language(s), language country(ies), and character set(s) used in the resource condition Class <<DataType>> language identification of the human language that is used in the text M 1 Class / LanguageCode <<CodeList>> See Table 3 (LanguageCode) Default value: en country national localization of the language that is used in the text M 1 Class / CountryCode <<CodeList>> See Table 3 (CountryCode) Default value: US characterencoding identification of the character set that is used in the text M 1 Class / CharacterSet <<CodeList>> See Table 3 (CharacterSetCode) Default value: utf8 Table 9 : Locale 56

59 7.4.2 Identification Identification UML This UML diagram is an SDSFIE-M -specific version of the cresponding Identification Package UML diagram (Figure A.2) found in ISO 19115:2003/C 1:2006 and NMF Part 1 (Figure 3). The diagram has been profiled NMF Part 1. The NMF_DataIdentification class has been removed, some attributes and association roles ISO 19115:2003/C 1:2006 have been rested. This diagram defines the metadata classes required to identify a resource. Figure 5 : Identification This UML diagram in Figure 6 is provided to show the relationships between SV_ServiceIdentification and its associated classes. 57

60 Identification Figure 6 : Service Identification Context The data dictionary table presented in this section is a SDSFIE-M -specific version of the cresponding Identification data dictionary table (Section B.2.2) found in ISO 19115:2003/C 1:2006 and NMF Part 1 (Table 9). The SV_ServiceIdentification ption of the table is ISO/DIS (Section B ). The table has been profiled that table, so some classes, attributes and association roles have been hidden. F the full table, consult ISO 19115:2003/C 1:2006 and NMF Part 1. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_Identification basic infmation required to uniquely identify a resource resources condition Aggregated Class (MD_Metadata) <<Abstract>> citation citation data f the resource(s) M 1 Class / CI_Citation <<DataType>> ( ) 58

61 abstract brief narrative summary of the content of the resource(s) M 1 CharacterString / Abstract narrative should include infmation on general content, thematic features (e.g., geology; climatology; etc.), and features; dataset application: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date single date; and special data characteristics limitations purpose summary of the intentions with which the resource(s) was developed. O 1 CharacterString / status status of the resource(s) M N Class / ProgressCode <<CodeList>> ( ) See Table 3 (ProgressCode) pointofcontact identification of, and means of communication with, person(s) and ganization(s) associated with the resource(s) M N Class / CI_ResponsibleParty <<DataType>> ( ) In the case of me than a single pointofcontact element then the members of the set shall be dered in descending priity of their recommended use, however not all implementations will necessarily hon the dering. Note: this element is optional in role name: resourcemaintenance provides infmation about the frequency of resource updates, and the scope of those updates O N Association / MD_MaintenanceInfmatio n (7.4.5) role name: graphicoverview provides a graphic that illustrates the resource(s) (should include a legend f the graphic) O N Association / MD_BrowseGraphic role name: resourcefmat provides a description of the fmat of the resource(s) O N Association / MD_Fmat ( ) 59

62 role name: descriptivekeywds provides categy keywds, their type, and reference source M N Association / MD_Keywds ( ) role name: resourceconstraints provides infmation about constraints which apply to the resource(s) M 2..N Association / MD_Constraints (7.4.3) It is a Recommended Best Practice that there shall be two me instances of MD_Constraints, one f security constraints and at least one f legal constraints. role name: aggregationinfo provides aggregate dataset infmation O N Association / MD_AggregateInfmation ( ) MD_DataIdentification infmation required to identify a dataset condition Specified Class (MD_Identification) spatialrepresentationtype method used to spatially represent geographic infmation O N Class / SpatialRepresentation TypeCode <<CodeList>> ( ) See Table 3 (SpatialRepresentationType Code) spatialresolution fact which provides a general understanding of the density of spatial data in the dataset O N Class / MD_Resolution <<Union>> ( ) language language(s) used within the dataset M N CharacterString / ISO 639-2, other parts may be used Default: en characterset full name of the character coding standard used f the dataset M N Class / CharacterSetCode <<CodeList>> ( ) See Table 3 (CharacterSetCode) Default: utf8 topiccategy main theme(s) of the dataset C / if hierarchylevel equals dataset? N Class / MD_TopicCategyCode <<Enumeration>> ( ) environmentdescription 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 / 60

63 extent extent infmation including the bounding box, bounding polygon, vertical, and tempal extent of the dataset C / if hierarchylevel equals dataset? either extent.geogra phicelement.e X_Geographic BoundingBox extent.geogra phicelement.e X_Geographic Description is required N Class / EX_Extent <<DataType>> ( ) If the hierarchylevel element value is dataset then at least either the bounding box point shall be populated. If the hierarchylevel element value is series then at least either the bounding box polygon shall be populated. At least one of MinimumBoundin grectangle, BoundingPolygon, BoundingPoint is required. Note that this may not necessarily be the full extent of the content of the resource as multiple instances of this class may be specified. supplementalinfmation SV_ServiceIdentification servicetype servicetypeversion any other descriptive infmation about the dataset identification of capabilities which a service provider makes available to a service user through a set of interfaces that define a behaviour - See ISO Services f further infmation a service type name a registry of services. F example, the values of the namespace and name attributes of GeneralName may be "OGC" and "catalogue". provides f searching based on the version of servicetype. F example, we may only be interested in OGC Catalogue V1.1 services. If version is maintained as a separate attribute, users can easily search f all services of a type regardless of the version. O 1 CharacterString / condition Specified Class (MD_Identification) M 1 GenericName (Annex B) O N CharacterString 61

64 accessproperties infmation about the availability of the service, including, - fees - planned available date and time - dering instructions - turnaround O 1 Class / MD_StandardOrderProcess ( ) couplingtype qualitative infmation on the tightness with which the service and the associated data are coupled M 1 Class / CouplingType <<CodeList>> ( ) See Table 3 (CouplingType) coupledresource further description of the coupling between the service and the data when they are tightly coupled O N Class / SV_CoupledResource ( ) operateddataset role name: containsoperations role name: operateson role name: containschain provides a reference to the dataset on which the service operates provides infmation about the operations that comprise the service provides infmation on the datasets that the service operates on provide infmation about the chain applied by the service O N Class / CI_Citation <<DataType>> ( ) M N Association / SV_OperationMetadata ( ) O N Association / MD_DataIdentification ( ) O N Class / SV_OperationChainMetadat a ( ) Keywds Table 10 : Identification The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Keywds data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.2.3) and NMF Part 1 (Table 10). Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_Keywds keywds, their type and reference source condition Aggregated Class (MD_Identification) keywd commonly used wd(s) fmalised wd(s) phrase(s) used to describe the subject M N CharacterString / type subject matter used to group similar keywds O 1 Class / KeywdTypeCode <<CodeList>> ( ) See Table 3 (KeywdTypeCode) See Table 3 (KeywdTypeCode) 62

65 thesaurusname name of the fmally registered thesaurus a similar authitative source of keywds M 1 Class / CI_Citation <<DataType>> ( ) Note: this element is optional in BrowseGraphic Table 11 : Keywds The data dictionary table presented in this section is an SDSFIE-M-specific version of the cresponding Browse Graphic data dictionary table found in ISO 19115:2003 (Section B.2.2.2). Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_BrowseGraphic graphic that provides an illustration of the dataset (should include a legend f the graphic) condition Aggregated Class (MD_Identification) filename name of the file that contains a graphic that provides an illustration of the dataset M 1 CharacterString / filedescription text description of the illustration O 1 CharacterString / filetype fmat in which the illustration is encoded Examples: CGM, EPS, GIF, JPEG, PBM, PS, TIFF, XWD O 1 CharacterString / Fmat The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Keywds data dictionary table found in ISO 19115:2003/C 1:2006 (Section B ) and NMF Part 1 (Section , Table 31). Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_Fmat description of the computer language construct that specifies the representation of data s in a recd, file, message, stage device transmission channel condition Aggregated Class (MD_Identification) name name of the data transfer fmat(s) M 1 CharacterString / version version of the fmat (date, number, etc.) M 1 CharacterString / Table 12 : Fmat 63

66 Resolution The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Resolution data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.2.5). The table has been profiled, so some classes, attributes and association roles have been hidden. F the full table, consult ISO 19115:2003/C 1:2006. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_Resolution level of detail expressed as a scale fact a ground distance condition Class <<Union>> UNION one and only one attribute should be populated equivalentscale level of detail expressed as the scale of a comparable hardcopy map chart C / if distance not documented if spatialrepresentation Type in MD_DataIdentification is "vect" "tin"? 1 Class / MD_RepresentativeFraction <<DataType>> ( ) distance ground sample distance C / if equivalentscale not documented if spatialrepresentation Type in MD_DataIdentification is "grid"? Table 13 : Resolution 1 Class / Distance (Annex B) Distance is used as a type f returning the length between two points. (defined in ISO/TS 19103) Representative Fraction The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Representative Fraction data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.2.4). The table has been profiled, so some classes, attributes and association roles have been hidden. F the full table, consult ISO 19115:2003/C 1:2006. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_RepresentativeFraction derived ISO Scale where MD_RepresentativeFraction. denominat = 1 / Scale.measure And Scale.targetUnits = Scale.sourceUnits condition Class <<DataType>> denominat the number below the line in a vulgar fraction M 1 Integer / Integer > 0 Table 14 : Representative Fraction 64

67 Aggregate Infmation The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Aggregate data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.2.7). The table has been profiled, so some classes, attributes and association roles have been hidden. F the full table, consult ISO 19115:2003/C 1:2006. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_AggregateInfmation aggregate dataset infmation condition Aggregated Class (MD_Identification) aggregatedatasetname citation infmation about the aggregate dataset C / if aggregatedata SetIdentifier not documented? 1 Class / CI_Citation <<DataType>> ( ) aggregatedatasetidentifier identification infmation about aggregate dataset C / if aggregatedata SetName not documented? 1 Class / MD_Identifier <<DataType>> ( ) associationtype association type of the aggregate dataset M 1 Class / AssociationTypeCode <<CodeList>> ( ) See Table 3 (AssociationTypeCode) Operation Infmation Table 15 : Aggregate Infmation The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Operation Metadata data dictionary table found in ISO/DIS (Section B ). Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule SV_OperationMetadata describes the signature of one and only one method provided by the service. condition Aggregated Class (SV_ServiceIdentification) operationname distributedcomputingplatfm operationdescription an identifier that uniquely designates the operation distributed computing platfms on which the operation has been implemented free text description of the intent of the operation and the results of the operation M 1 CharacterString / M N Class / DCPList <<CodeList>> ( ) See Table 3 (DCPList) O 1 CharacterString / 65

68 invocationname connectpoint role name: dependson role name: parameters role name: thesv_serviceidentification the name used to invoke this interface within the context of the DCP. The name is identical f all DCPs. handle f accessing the service interface list of operations that must be completed immediately befe current operation is invoked, structured as a list f capturing alternate predecess paths and sets f capturing parallel predecess paths the parameters that are required f this interface capabilities which a service provider makes available to a service O 1 CharacterString / M N Class / CI_OnlineResource <<DataType>> ( ) O N Sequence / CharacterString set{sequence{operationname} set(operationname} M 1 Sequence (B.4.7) / SV_Parameter ( ) O N Association / SV_ServiceIdentification ( ) Operation Chain Infmation Table 16 : Operation Infmation The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Operation Chain Infmation data dictionary table found in ISO/DIS (Section B ). Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule SV_OperationChainMetadata Operation Chain Infmation condition Aggregated Class (SV_ServiceIdentification) name description role name: operation the name, as used by the service f this chain a narrative explanation of the services in the chain and resulting output (dered) infmation about the operations applied by the chain M 1 CharacterString / FreeText O 1 CharacterString / FreeText M N Class / SV_OperationMetadata ( ) Parameter Infmation Table 17 : Operation Chain Infmation The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Parameter Infmation data dictionary table found in ISO/DIS (Section B ). 66

69 Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule SV_Parameter describes a parameter of a service condition Aggregated Class (SV_ServiceIdentification) name direction description optionality repeatability role name: valuetype the name, as used by the service f this parameter indication if the parameter is an input to the service, an output both description a narrative explanation of the role of the parameter indication if the parameter is required indication if me than one value of the parameter may be provided the class used f thevalue type M 1 Class / MemberName (Annex B) O 1 Class / ParameterDirection <<CodeList>> ( ) See Table 3 (ParameterDirection) O 1 CharacterString M 1 CharacterString M 1 Boolean O N TypeName (Annex B) Coupled Resource Infmation Table 18 : Parameter Infmation The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Coupled Resource Infmation data dictionary table found in ISO/DIS (Section B ). Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule SV_CoupledResource infmation describing the linkage between a service operation and a tightly coupled dataset condition Aggregated Class (SV_ServiceIdentification) scopedname resourcereference scoped identifier of the resource in the context of the given service instance NOTE: name of the resources (i.e. dataset) as it is used by a service instance (e.g. layer name featuretypename). reference to the dataset on which the service operates O 1 Class / ScopedName (Annex B) O N Class / CI_Citation <<DataType>> ( ) 67

70 role name: resource role name: operation the tightly coupled dataset. This attribute should be implemented by reference The service operation. This attribute should be implemented by reference O N Class / MD_DataIdentification ( ) O 1 Class / SV_OperationMetadata ( ) Table 19 : Coupled Resource Infmation Standard Order Process Infmation The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Standard Order Process Infmation data dictionary table found in ISO/DIS (Section B ). MD_StandardOrderProcess common ways in which the resource may be obtained received, and related instructions and fee infmation condition Aggregated Class (SV_ServiceIdentification) fees fees and terms f retrieving the resource. Include monetary units (as specified in ISO 4217) C 1 CharacterString / Obligation: At least one of the conditional attributes in this class must be used plannedavailabledatetime date and time when the resource will be available C 1 Class / DateTime (Annex B) Obligation: At least one of the conditional attributes in this class must be used deringinstructions general instructions, terms and services provided by the distribut C 1 CharacterString / Obligation: At least one of the conditional attributes in this class must be used turnaround typical turnaround time f the filling of an der C 1 CharacterString / Obligation: At least one of the conditional attributes in this class must be used deroptionstype description of the der options recd O 1 Class / RecdType (Annex B) deroptions request/purchase choices C 1 Class / Recd (Annex B) Obligation: At least one of the conditional attributes in this class must be used Table 20 : Standard Order Process Infmation 68

71 7.4.3 Constraints Constraints UML This UML diagram is an SDSFIE-M -specific version of the cresponding Constraint Package UML diagram found in ISO 19115:2003/C 1:2006 (Figure A.3) and as extended by NMF Part 1 (Section , Figure 4). Classes, attributes and associations that have not been included in this SDSFIE-M profile have been hidden. Likewise, classes, attributes and associations which extend the base standard have been added. F the iginal diagram consult ISO 19115:2003/C 1:2006. The NMF and SDSFIE-M modifies the ISO model of MD_SecurityConstraints as follows: MD_SecurityConstraints has been subclassed by NMF (and thus SDSFIE-M) to create the NMF_SecurityConstraints class. This class serves as the root f U.S. Intelligence and Defense related security marking metadata. 69

72 Constraints Figure 7 : Constraints The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Constraints data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.3) and NMF Part 1 ( , Table 15). F the iginal data dictionary consult ISO 19115:2003/C 1:2006. The SDSFIE-M modifies the ISO and NMF data dictionary f Constraints as follows: The elements accessconstraints, useconstraints, and classification have been restricted to SDSFIE-M /NMF CodeLists 70

73 Constraints are mandaty f MD_Metadata and MD_Identification instances. One instance of NMF_SecurityConstraints is required. One instance of MD_LegalConstraints is required with additional instances being optional. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_Constraints restrictions on the access and use of a resource metadata condition Aggregated Class (MD_Metadata and MD_Identification) uselimitation limitation affecting the fitness f use of the resource metadata. Example, not to be used f navigation O N CharacterString / MD_LegalConstraints restrictions and legal prerequisites f accessing and using the resource metadata condition N Specified Class (MD_Constraints) accessconstraints access constraints applied to assure the protection of privacy intellectual property, and any special restrictions limitations on obtaining the resource metadata O N Class / RestrictionCode <<CodeList>> ( ) See Table 3 (RestrictionCode) See Table 3 useconstraints constraints applied to assure the protection of privacy intellectual property, and any special restrictions limitations warnings on using the resource metadata O N Class / RestrictionCode <<CodeList>> ( ) See Table 3 (RestrictionCode) See Table 3 SMF_LegalConstraints Extended class to hold additional legal infmation condition N Specified Class (MD_LegalConstraints) furtherexplanation further explanation of the legal restrictions O N CharacterString / MD_SecurityConstraints handling restrictions imposed on the resource metadata f national security similar security concerns condition 1 Specified Class (MD_Constraints) classification name of the handling restrictions on the resource metadata M 1 Class / ClassificationCode <<CodeList>> ( ) See Table 3 (ClassificationCode) See Table 3 usernote explanation of the application of the legal constraints other restrictions and legal prerequisites f obtaining and using the resource metadata O 1 CharacterString / classificationsystem name of the classification system M 1 CharacterString Always has to be "US CAPCO" 71

74 handlingdescription additional infmation about the restrictions on handling the resource metadata O 1 CharacterString / Table 21 : Constraints SDSFIE-M Security Constraints Extension ISO 19115:2003/C 1:2006 contains a bare minimum of security-related metadata elements. That bare minimum is not sufficient f use in the NSG ( in the I&E community). The MD_SecurityConstraints class has been extended to accommodate the additional security requirements. The extension follows DoD/IC directives f the use of IC.ADD.V2 (Chapter 3, Infmation Security Marking) as defined in the table below. The XML Data Encoding specification f Need-To-Know Metadata, version 5 (NTK.XML.V5) is an ODNI standard f encoding metadata necessary to facilitate automated systems making a need-to-know determination in der allow to address a resource. Suppt f this standard has been included in Table 24. MD_SecurityConstraints entity has been extended by the SDSFIE-M to include an attribute describing handling restrictions f unclassified data.it is mandaty f all users of the SDSFIE-M to document security metadata using the SMF_SecurityConstraints class. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule SMF_SecurityConstraints Extended class to hold additional security infmation. condition 1 Specified Class (MD_SecurityConstraints) (Table 16) capcomarking needtoknow provides Intelligence Community Infmation Security Markings (IC.ADD) security elements. r, group profile identifying infmation to be used to make a need-to-know access determination. M 1 Class / ISM_SecurityAttributesGr oup (Table 23) O 1 Class / NTK_Access (Table 24) handlingdescription additional infmation about the restrictions on handling the resource metadata C / NMFSecurity Constraints.c apcomarking.classification = "U" and the handling restriction defined in the associated code list exists? 1 CharacterString / UnclassHandlingCode <<CodeList>> ( ) See Table 3 (UnclassHandlingCode) 72

75 role name: notices Infmation concerning welldefined security notices including those defined in the CAPCO register and the ISM.XML standard O N Class / ISM_Notices (Table 25) Table 22 : SDSFIE-M Security Constraints Capco Marking The Controlled Access Program Codination Office (CAPCO) is responsible f establishing the unifm list of security control markings authized f dissemination of classified infmation by components of the U.S. Intelligence Community and the authized abbreviated fms of such markings. This list is maintained and disseminated through the Authized Classification and Control Markings Register (known as the CAPCO Register). The authitative list of CAPCO markings f use in the NSG are documented in IC.ADD.V2 (Chapter 3, Infmation Security Marking).XML encodings of the CAPCO markings is specified is the ISM.XML standard. The data dictionary table presented in this section is not found in ISO 19115:2003/C 1:2006. This metadata represents the CAPCO markings as specified in IC.ADD version 2 and is specific to NSG implementations. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule ISM_SecurityAttributesG roup condition Class atomicenergymarkings One me indicats identifying infmation controlled under the Atomic Energy Act. O 1 Character String / Free Text classification A single indicat of the highest level of classification applicable to an infmation resource ption within the domain of classified national security infmation. M 1 Character String / Free Text The Classification element is always used in conjunction with the Owner Producer element. Taken together, the two elements specify the classification categy and the type of classification (US, non-us, Joint). classificationreason The basis f an iginal classification decision O 1 Character String / Free Text This element is used only in conjunction with the classifiedby element. classifiedby The identity, by name personal identifier, and position title of the iginal classification authity f a resource O 1 Character String / Free Text This element is used only when the value f the classification element is not unclassified and the derivedfrom element is not used. 73

76 dateofexemptedsource declassdate declassevent declassexception derivativelyclassifiedby derivedfrom compilationreason A specific year, month, and day of publication release of a source document, the most recent source document, that was itself marked with a declassification constraint. A specific year, month, and day upon which the infmation shall be automatically declassified if not properly exempted automatic declassification A description of an event upon which the infmation shall be automatically declassified if not properly exempted automatic declassification. A single indicat describing an exemption to the nominal 25-year point f automatic declassification. The identity, by name personal identifier, of the derivative classification authity A citation of the authitative source reference to multiple sources of the classification markings used in a classified resource The reason that a ption resource is marked with a higher and/ me restrictive mark than its components would indicate. F example this would document why 3 Unclassified bullet items fm a Secret List. Without this reason being noted the above-described document would be considered to be mismarked and overclassified. O 1 Date /YYYY-MM-DD Deprecated. Not valid in ISM Version 7 O 1 Date /YYYY-MM-DD O 1 Character String / Free Text O 1 CharacterString / FreeText (Code) O 1 Character String / Free Text O 1 Character String / Free Text O 1 Character String / Free Text This element is used in conjunction with the Declassification Date Declassification Event This element is used in conjunction with the derivedfrom element. This element is used only when the value f the classification element is not unclassified and the classifiedby element is not used. 74

77 displayonlyto One me indicats identifying the country countries and/ international ganization(s) to which classified infmation may be displayed based on the determination of an iginat in accdance with established feign disclosure procedures. This element is used in conjunction with the Dissemination Controls element. O 1 Character String / Free Text Country and ganization names disseminationcontrols One me indicats identifying the expansion limitation on the distribution of infmation O N Character String / Free Text This element is used only when the value f the classification element is not unclassified fgisourceopen One me indicats identifying infmation which qualifies as feign government infmation f which the source(s) of the infmation is not concealed O N CharacterString / FreeText (Code) fgisourceprotected A single indicat that infmation qualifies as feign government infmation f which the source(s) of the infmation must be concealed O 1 CharacterString / FreeText (Code) Within protected internal ganizational spaces this element may be used to maintain a recd of the one me indicats identifying infmation which qualifies as feign government infmation f which the source(s) of the infmation must be concealed. Measures must be taken pri to dissemination of the infmation to conceal the source(s) of the feign government infmation nonicmarkings One me indicats of the expansion limitation on the distribution of an infmation resource ption within the domain of infmation iginating non-intelligence components O N CharacterString / FreeText (Code) This element is used only when the value f the classification element is not unclassified nonuscontrols One me indicats of the expansion limitation on the distribution of an infmation resource ption within the domain of infmation iginating non-us components. Currently just includes a few NATO marks. O N CharacterString / FreeText (Code) 75

78 ownerproducer One me indicats identifying the national government international ganization that have purview over the classification marking of an infmation resource ption therein. M 1 CharacterString / Free Text This element is always used in conjunction with the Classification element. Taken together, the two elements specify the classification categy and the type of classification (US, non-us, Joint). Within protected internal ganizational spaces this element may include one me indicats identifying infmation, which qualifies as feign government infmation, f which the source(s) of the infmation must be concealed. Measures must be taken pri to dissemination of the infmation to conceal the source(s) of the feign government infmation. releasableto One me indicats identifying the country countries and/ international ganization(s) to which classified infmation may be released based on the determination of an iginat in accdance with established feign disclosure procedures. C N Class / CountryCode <<CodeList>> ( ) See Table 3 (CountryCode) This element is used in conjunction with the disseminationcontrols element. saridentifier One me indicats identifying the defense intelligence programs f which special access is required O N CharacterString / FreeText (Code) This element is used only when the value f the classification element is not unclassified scicontrols One me indicats identifying sensitive compartmented infmation control system(s). O N CharacterString / FreeText (Code) This element is used only when the value f the classification element is not unclassified Table 23 : ISM Security Attributes Group Need to Know Infmation sharing within the U.S. national intelligence enterprise frequently relies on being able to determine an individual s need-to-know as one component in determining whether to allow access to data. This need to know metadata are used to represent the system-specific properties assigned to an infmation resource that will be used, in conjunction with infmation about the user, and possibly other infmation, to determine the user s access to the data. The data dictionary table presented in this section is not found in ISO 19115:2003/C 1:2006. This metadata represents the Need to Know metadata defined in NTK.XML version 5 and is specific to NSG implementations. 76

79 Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule NTK_Access A statement description of a group of people who should be granted access to an infmation resource. condition Class individual group profile A statement, as defined by an access system, of a mechanism that identifies an individual who has access to the resource. A statement, as defined by an access system, of a group that should refer ultimately to one me individuals. A statement of the traits that an access system will use in determining if a particular individual making a request f access to an infmation resource is granted access. O N Class / MD_Identifier <<DataType>> ( ) O N Class / MD_Identifier <<DataType>> ( ) O N Class / MD_Identifier <<DataType>> ( ) Table 24 : Need To Know Notices In some cases restrictions on the distribution and use of a resource cannot be adequately captured in the CAPCO markings. Notices provide that additional security related infmation in a textual fmat. Most notices are standardized through registration in the CAPCO register. Registered notices can be identified by their notice type. of the notice type avoids the need to distribute the full text of the notice. The data dictionary table presented in this section is not found in ISO 19115:2003/C 1:2006. This metadata represents the Notices metadata defined in ISM.XML version 7 and is specific to NSG implementations. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule ISM_Notices Infmation concerning welldefined security notices including those defined in the CAPCO register and the ISM.XML standard. condition Class noticetext The actual text of a notice M N CharacterString / Free Text noticetype noticedate noticereason Specifies which categy of notice is included in this entity. Specifies the date the notice was issued Specifies the reason the notice was issued O 1 Class / NoticeTypeCode <<CodeList>> ( ) See Table 3 (NoticeTypeCode) O 1 Class / Date (Annex B) O 1 CharacterString / Free Text 77

80 unregisterednoticetype d to represent notices that are not registered in the CAPCO register and are not defined in the ISM. O 1 CharacterString / Free Text Table 25 : ISM Notices Data Quality The DQ_DataQuality class is the root of the SDSFIE-M Quality metadata. This class defines the scope of the quality assessment and aggregates the histy (LI_Lineage) and quality measurements (DQ_Element) f the referenced resource Data Quality UML This UML diagram is an SDSFIE-M -specific version of the cresponding Data Quality Package UML diagram found in 19115:2003/C 1:2006 (Figure A.4) and NMF Part 2 ( , Figure 1). No profiling of this diagram was needed to address I&E Community requirements. This diagram defines the metadata required to give a general assessment of the quality of a resource Data Quality Figure 8 : Data Quality The data dictionary table presented in this section is the same cresponding Data Quality data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.4.1). No 78

81 profiling was required to address I&E community requirements. Additional text to clarify business rules has been added to assist users in the use of these elements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule DQ_DataQuality quality infmation f the data specified by a data quality scope condition Aggregated Class (MD_Metadata) scope the specific data to which the data quality infmation applies M 1 Class / DQ_Scope <<DataType>> ( ) "rept" "lineage" role is mandaty if scope. DQ_Scope. level = 'dataset' series role name: rept quantitative quality infmation f the data specified by the scope C / lineage not provided and (DQ_DataQuality. scope. DQ_Scope.level = dataset series )? N Association / DQ_CompletenessCommission and/ DQ_CompletenessOmission and/ DQ_ConceptualConsistency and/ DQ_DomainConsistency and/ DQ_FmatConsistency and/ DQ_TopologicalConsistency and/ DQ_AbsoluteExternalPositionalAccuracy and/ DQ_GriddedDataPositionalAccuracy and/ DQ_RelativeInternalPositionalAccuracy and/ DQ_ThematicClassificationCrectness and/ DQ_NonQuantitativeAttributeAccuracy and/ DQ_QuantitativeAttributeAccuracy and/ DQ_AccuracyOfATimeMeasurement and/ DQ_TempalValidity and/ DQ_TempalConsistency ( ) role name: lineage non-quantitative quality infmation about the lineage of the data specified by the scope C / rept not provided and (DQ_DataQuality. scope. DQ_Scope.level = dataset series )? 1 Association / LI_Lineage (B 2.4.1) Table 26 : Data Quality 79

82 Scope DQ_Scope specifies the extent of the resources that are described by the repted quality metadata. Extent can be described in terms of spatial, tempal, hierarchy level and resource type properties. The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Scope data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.4.5). The table has been profiled, as follows: The leveldescription attribute has been restricted a Union of references (MD_ScopeDescription) to a code list. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule DQ_Scope extent of characteristic(s) of the data f which quality infmation is repted condition Class <<DataType>> level hierarchical level of the data specified by the scope M 1 Class / ScopeCode <<CodeList>> ( ) See Table 3 (ScopeCode) See Table 3 (NMF_ScopeCode) extent infmation about the hizontal, vertical and tempal extent of the data specified by the scope O 1 Class / EX_Extent <<DataType>> ( ) leveldescription detailed description about the level of the data specified by the scope M 1 Class / ScopeAmplificationC ode <<CodeList>> ( ) See Table 3 (ScopeAmplification Code) See Table 3 (NMF_ScopeAmplificationC ode ) Note: this element is optional in 19115, and the domain class has been constrained to a code list Lineage Table 27 : Data Quality Scope When assessing the quality of a data resource, it is imptant to know how that resource was created; what source material was used, and what processing was applied to that source. Lineage metadata entities provide that infmation. Lineage is described in terms of Sources and Process Steps. Sources and Process Steps, in turn are associated with each other. This structure allows discovery of the lineage of a resource both the processing and source perspective. Examples of how this structure can be used are provided in Table 28. r Question Class Path What sources were used to create this resource? LI_LineageLI_Source 80

83 What processing was applied to those sources to create this resource? Were all of the required process steps executed in the production of this resource? Was appropriate source used in each process step? Is the lineage metadata complete? LI_LineageLI_SourceLI_ProcessStep LI_LineageLI_ProcessStep LI_LineageLI_ProcessStepLI_Source LI_LineageLI_ProcessStepLI_Source == LI_Lineage-LI_Source and LI_LineageLI_SourceLI_ProcessStep == LI_LineageLI_ProcessStep Table 28 : Using LI_Lineage The examples above reflect a rather simple lineage, where sources are processed directly ( at least without persistent intermediate products) into a product. That model is suppted by the LI_Lineage entity. The LE_Lineage model extends LI_Lineage to address me complex cases. In these cases, sources may go through several stages of processing befe being used on the final product. Capturing this lineage requires me robust metadata, including details about intermediate sources (process step outputs), processing parameters and algithms. In sht; LI_Lineage provides a flat lineage model, typical of cartographic production and LE_Lineage provides a deep lineage model, typical of image processing wkflows. LI_Lineage and LE_Lineage are profiled ISO and respectively LI_Lineage LI_Lineage is the base lineage class defined in ISO It associates the sources used to produce a data resource with the process steps perfmed on those sources. This model assumes a compilation environment typical of cartographic production. Under this model a number of sources are compiled into the final product (the data resource). Each source may be processed in some manner pri to being applied to the product. Any intermediate data created by this processing was discarded. As such, output that processing is considered the data resource itself LI_Lineage UML This UML diagram is based on the Lineage Package UML diagram (Figure A.5) found in ISO 19115:2003/C 1:2006. The diagram has not been profiled f SDSFIE-M. 81

84 Figure 9 : LI_Lineage Metadata LI_Lineage Data Dictionary LI_Lineage provides infmation on the sources and processing that was perfmed to create the described resource. The data dictionary in table 31is based on the cresponding data dictionary found in ISO 19115:2003/C 1:2006 (Section B ). No profiling of this table was required to address I&E community requirements. LI_Lineage is included in SDSFIE-M NMF Part 1 and is extended by NMF Part 2 as follows: The source association has been rested ISO The processstep association has been rested ISO Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LI_Lineage infmation about the events source data used in constructing the data specified by the scope lack of knowledge about lineage condition Aggregated Class (DQ_DataQuality) 82

85 statement general explanation of the data producer s knowledge about the lineage of a dataset C / If(count(source) + count(processst ep) =0) and (DQ_DataQuality.scope.level = 'dataset' 'series') then statement is mandaty 1 CharacterString / The statement element of LI_Lineage is mandaty if DQ_DataQuality.scope. DQ_Scope.level has a value of dataset series and the LI_Lineage roles of source and processstep are not documented. role name: processstep infmation about events in the life of a dataset specified by the scope C / mandaty if LI_Lineage.state ment and "source" role are not documented N Association / LI_ProcessStep ( ) The processstep role of LI_Lineage is mandaty if the statement element and the source role of LI_Lineage are not documented. role name: source infmation about the source data used in creating the data specified by the scope C / mandaty if LI_Lineage.state ment and "processstep" role are not documented N Association / LI_Source ( ) The source role of LI_Lineage is mandaty if the statement element and the processstep role of LI_Lineage Table 29 : LI_Lineage LI_ProcessStep Data Dictionary LI_ProcessStep describes an instance of the processing that was perfmed on a source sources to create the described resource. Sources and process steps that wked together are linked by the metadata to provide a histy of how the resource was created. The data dictionary presented in this table is based on the cresponding data dictionary found in ISO 19115:2003/C 1:2006 (Section B ). No profiling of this table was required to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LI_ProcessStep infmation about an event transfmation in the life of a dataset including the process used to maintain the dataset condition Aggregated Class (LI_Lineage and LI_Source) description description of the event, including related parameters tolerances M 1 CharacterString / Free Text rationale requirement purpose f the process step O 1 CharacterString / Free Text datetime date and time range of date and time on over which the process step occurred O 1 Class / DateTime (Annex B) process identification of, and means of communication with, person(s) and ganization(s) associated with the process step O N Class / CI_ResponsibleParty <<DataType>> ( ) 83

86 role name: source infmation about the source data used in creating the data specified by the scope O N Association / LI_Source ( ) Table 30 : LI_ProcessStep LI_Source Data Dictionary LI_Source describes a source that was used to create the described resource. Sources and process steps that wked together are linked by the metadata to provide a histy of how the resource was created. The data dictionary presented in this table is based on the cresponding data dictionary found in ISO 19115:2003/C 1:2006 (Section B ). No profiling of this table was required to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LI_Source infmation about the source data used in creating the data specified by the scope condition Aggregated Class (LI_Lineage and LI_ProcessStep) description detailed description of the level of the source data C / sourceextent not provided? 1 CharacterString / Free Text Either the description sourceextent element of LI_Source must be documented. scaledenominat sourcereferencesystem sourcecitation denominat of the representative fraction on a source map spatial reference system used by the source data recommended reference to be used f the source data O 1 Class / MD_RepresentativeFraction <<DataType>> ( ) O 1 Class / MD_ReferenceSystem ( ) O 1 Class / CI_Citation <<DataType>> ( ) sourceextent infmation about the spatial, vertical and tempal extent of the source data C / description not provided? N Class / EX_Extent <<DataType>> ( ) Either the description sourceextent element of LI_Source must be documented. role name: sourcestep infmation about an event in the creation process f the source data O N Association / LI_ProcessStep ( ) Table 31 : LI_Source LE_Lineage The lineage entities defined in Section model a histy which is wide but shallow. Many data resources, however, are the result of a long chain of processing applied to a small number of raw sources. ISO addresses this case by extending the lineage entities defined in ISO A key change is the addition of an output association to the process step class. Distinguishing between input (source) 84

87 and output data allows process steps to be assembled into long processing chains. These chains describe the iginal source, every processing step applied and all intermediate products. Since these process chains are by necessity automated, this model expands the process step class to describe the automated resources used and to capture repts on the wk done at each process step LE_Lineage UML Figure 10 defines the extended metadata classes required to specify the lineage of imagery and gridded data. This diagram is based on Figure A.3 in ISO :2009. No profiling of this diagram was required to address I&E community requirements. 85

88 Figure 10 : LE_Lineage Metadata 86

89 LE_Source Data Dictionary The LE_Source data dictionary table presented in this section is an extension of the LI_Source dictionary found in Table 31 of this document. The extensions are described in ISO :2009 section B This data dictionary includes additional SDSFIE-M -specific profiling of the parent LI_Source class: Obligation of scaledemoninat element has been changed to conditional. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LE_Source infmation on data sets input to output by the processing step (LI_Source extended) condition SpecifiedClass (LI_Source) Inherited LI_Source description detailed description of the level of the source data C / sourceextent not provided? 1 CharacterString / Free Text Either the description sourceextent element of LI_Source must be documented. scaledenominat denominat of the representative fraction on a source map C / if LE_Source. resolution. scanningresolution is specified, then LE_Source. scaledenominat (inherited LI_Source) is required. 1 Class / MD_RepresentativeFraction <<DataType>> ( ) sourcereferencesystem sourcecitation spatial reference system used by the source data recommended reference to be used f the source data O 1 Class / MD_ReferenceSystem ( ) O 1 Class / CI_Citation <<DataType>> ( ) sourceextent infmation about the spatial, vertical and tempal extent of the source data C / description not provided? N Class / EX_Extent <<DataType>> ( ) Either the description sourceextent element of LI_Source must be documented. role name: sourcestep processedlevel infmation about an event in the creation process f the source data processing level of the source data O N Association / LI_ProcessStep ( ) LE_Source-specific attributes O 1 Class / MD_Identifier <<DataType>> ( ) 87

90 resolution distance between consistent parts (centre, left side, right side) of two adjacent pixels O 1 Class / LE_NominalResolution <<Union>> ( ) Table 32 : LE_Source LE_NominalResolution Data Dictionary LE_NominalResolution provides a means to capture the resolution of an image. Since resolution can be in terms of ground resolution scanning resolution, this class serves to combine those two mutually exclusive measures into a single element. The LE_NominalResolution data dictionary presented in this table is based on the cresponding data dictionary found in ISO :2009 section B No profiling of this table was required to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LE_NominalResolution distance between consistent parts of (centre, left side, right side) adjacent pixels condition Class <<Union>> UNION one and only one attribute should be populated scanningresolution distance between consistent parts of (centre, left side, right side) adjacent pixels in the scan plane M 1 Class / <<Type>> Distance Defined in ISO groundresolution distance between consistent parts of (centre, left side, right side) adjacent pixels in the space M 1 Class / <<Type>> Distance Defined in ISO Table 33 : LE_ NominalResolution LE_ProcessStep Data Dictionary The LE_ProcessStep data dictionary table presented in this section is an extension of the LI_ProcessStep dictionary found in Table 30 of this document. The extensions are described in ISO :2009 section B Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LE_ProcessStep infmation about an event transfmation in the life of the dataset including details of the algithm and software used f processing (LI_ProcessStep extended) condition Aggregated Class (LI_Lineage) Inherited LI_ProcessStep description description of the event, including related parameters tolerances M 1 CharacterString / Free Text rationale requirement purpose f the process step O 1 CharacterString / Free Text 88

91 datetime date and time range of date and time on over which the process step occurred O 1 Class / DateTime (Annex B) process identification of, and means of communication with, person(s) and ganization(s) associated with the process step O N Class / CI_ResponsibleParty <<DataType>> ( ) role name: source infmation about the source data used in creating the data specified by the scope O N Association / LI_Source ( ) LE_ProcessStep-specific attributes role name: output description of the product generated as a result of the process step O N Association / LE_Source ( ) role name: processinginfmation comprehensive infmation about the procedure by which the algithm was applied to derive geographic data the raw instrument measurements, such as datasets, software used, and the processing environment O 1 Association / LE_Processing ( ) role name: rept rept generated by the process step O N Association / LE_ProcessStepRept ( ) Table 34 : LE_ ProcessStep Image Process Step Rept Processing systems often generate a rept on what was done, issues encountered and the level of quality achieved. LE_ProcessStepRept provides a way to capture that rept f latter reference. The LE_ProcessStepRept data dictionary presented in this table is based on the cresponding data dictionary found in ISO :2009 section B No profiling of this table was required to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LE_ProcessStepRept rept of what occurred during the process step condition Aggregated Class (LE_ProcessStep) name name of the processing rept M 1 Character String / Free Text description filetype textual description of what occurred during the process step type of file that contains the processing rept O 1 Character String / Free Text O 1 Character String / Free Text LE_Processing Table 35 : LE_ ProcessStepRept 89

92 LE_Processing provides infmation about how an output product was derived source data. This entity is useful to describe automated processing where established algithms, software and procedures are used. The LE_Processing data dictionary presented in this table is based on the cresponding data dictionary found in ISO :2009 section B No profiling of this table was required to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LE_Processing comprehensive infmation about the procedure(s), process(es) and algithm(s) applied in the process step condition Aggregated Class (LE_ProcessStep) identifier softwarereference proceduredescription documentation runtimeparameters role name: algithm infmation to identify the processing package that produced the data reference to document describing processing software additional details about the processing procedures reference to documentation describing the processing parameters to control the processing operations, entered at run time details of the methodology by which geographic infmation was derived the instrument readings M 1 Class / MD_Identifier <<DataType>> ( ) O N Class / CI_Citation <<DataType>> ( ) O 1 CharacterString / O N Class / CI_Citation <<DataType>> ( ) O 1 CharacterString / O N Association / LE_Algithm ( ) Table 36 : LE_Processing LE_Algithm LE_Algithm describes an algithm used f automated processing of source data. The LE_Algithm data dictionary presented in this table is based on the cresponding data dictionary found in ISO :2009 section B No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule LE_Algithm details of the methodology by which geographic infmation was derived the instrument readings condition Aggregated Class (LE_Processing) 90

93 citation infmation identifying the algithm and version date M 1 Class / CI_Citation <<DataType>> ( ) description infmation describing the algithm used to generate the data M 1 CharacterString / Quality Element Table 37 : LE_Algithm DQ_Element is the root class f all quantifiable measures of quality. When a quality measurement is perfmed, this class captures the quality measurement technique used and the resulting measurement values. ISO and define the semantics of this infmation by subclassing the DQ_Element class. In effect, the inheritance tree DQ_Element fms a taxonomy of quality measurement types. A register of quality measurement techniques has been established on the NSG Standards Registry to help capture this infmation in a standard repeatable fm. Detailed descriptions of a measurement technique can be retrieved the register using the measureidentification element of DQ_Element Quality Element UML This UML diagram is an SDSFIE-M -specific version of the cresponding Data Quality Classes and Subclasses UML diagram (Figure A.6) found in ISO 19115:2003/C 1:2006. The diagram has been extended to include additional classes beyond those defined in ISO The NMF Part 2 Quality Extension modifies the ISO of DQ_Element as follows: Added QE_Usability subclass ISO This entity provides an expression of how suitable this resource would be f its intended use. Added the NMF_QualityMeasure subclass. This subclass extends the quality measure taxonomy to include measures related to codinate transfmations, statistical measures and signal quality. 91

94 Figure 11 : Quality Element Context Quality Element Data Dictionary DQ_Element is the root class f all measurements of quantifiable quality. When a quality measurement is perfmed, this class identifies the quality measurement process used and the resulting measurement values. ISO and have constructed a taxonomy of quality measurement types by subclassing DQ_Element. Since it is unlikely that this taxonomy will suppt all possible quality measures, the NMF_QualityMeasure sub-class has been added to provide an alternate to the taxonomy. 92

95 The data dictionary presented in this table includes SDSFIE-M-specific extensions to the Quality Element Data Dictionary table found in ISO 19115:2003/C 1:2006 (Section B.2.4.3). Modifications to the DQ_Element class in ISO are: Added QE_Usability subclass ISO This entity provides an expression of how suitable this resource would be f its intended use. Added the NMF_QualityMeasure subclass. This subclass extends the quality measure taxonomy to include measurements related to codinate transfmations, statistical measures and signal quality. Added business logic identifying the measureidentification element of DQ_Element as being the preferred way to reference the quality measurement technique used. DQ_Element provides six elements that describe the measurement and how it was perfmed. A register of quality measurement techniques has been established on the NSG Standards Registry to capture this infmation in a standard repeatable fm. Implementations of the NMF Part 2 shall reference the appropriate register entry f a measurement technique using the measureidentification element. of the other five elements should be avoided except as allowed under the business rules. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule DQ_Element aspect of quantitative quality infmation condition Aggregated Class (DQ_DataQuality) <<Abstract>> nameofmeasure name of the test applied to the data O N CharacterString / should be avoided measureidentification code identifying a registered standard procedure O 1 Class / MD_Identifier <<DataType>> ( ) I&E community preferred method to identify the measure measuredescription description of the measure O 1 CharacterString / should be avoided evaluationmethodtype type of method used to evaluate quality of the dataset O 1 Class / EvaluationMethodTypeCo de <<CodeList>> ( ) See Table 3 (EvaluationMethodTypeC ode) should be avoided 93

96 Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule evaluationmethoddescription description of the evaluation method O 1 CharacterString / Shall only be used to convey essential infmation not supplied by measureide ntification evaluationp rocedure evaluationprocedure reference to the procedure infmation O 1 Class / CI_Citation <<DataType>> ( ) Shall only be used when there are alternative procedures f calculating a measure datetime date range of dates on which a data quality measure was applied O N Class / DateTime (Annex B) result value ( set of values) obtained applying a data quality measure the outcome of evaluating the obtained value ( set of values) against a specified acceptable confmance quality level M 2 Class / DQ_Result <<Abstract>> ( ) No me than one instance of each DQ_Result subclass shall be provided Generalization of DQ_Element f completeness with no additional attributes operations DQ_Completeness presence and absence of features, their attributes and their relationships condition Specified Class (DQ_Element) <<Abstract>> Generalization: DQ_CompletenessCommission excess data present in the dataset, as described by the scope condition Specified Class (DQ_Completeness) Generalization: DQ_CompletenessOmission data absent the dataset, as described by the scope condition Specified Class (DQ_Completeness) Generalization of DQ_Element f consistency with no additional attributes operations 94

97 Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule DQ_LogicalConsistency degree of adherence to logical rules of data structure, attribution and relationships (data structure can be conceptual, logical physical) condition Specified Class (DQ_Element) <<Abstract>> Generalization: DQ_ConceptualConsistency adherence to rules of the conceptual schema condition Specified Class (DQ_LogicalConsistency) Generalization: DQ_DomainConsistency adherence of values to the value domains condition Specified Class (DQ_LogicalConsistency) Generalization: DQ_FmatConsistency degree to which data is sted in accdance with the physical structure of the dataset, as described by the scope condition Specified Class (DQ_LogicalConsistency) Generalization: DQ_TopologicalConsistency crectness of the explicitly encoded topological characteristics of the dataset as described by the scope condition Specified Class (DQ_LogicalConsistency) Generalization of DQ_Element positional quality with no additional attributes operations DQ_PositionalAccuracy accuracy of the position of features condition Specified Class (DQ_Element) <<Abstract>> Generalization: DQ_AbsoluteExternalPositionalAccuracy closeness of repted codinate values to values accepted as being true condition Specified Class (DQ_PositionalAccuracy) Generalization: DQ_GriddedDataPositionalAccuracy closeness of gridded data position values to values accepted as being true condition Specified Class (DQ_PositionalAccuracy) Generalization: DQ_RelativeInternalPositionalAccuracy closeness of the relative positions of features in the scope to their respective relative positions accepted as being true condition Specified Class (DQ_PositionalAccuracy) Generalization of DQ_Element f tempal quality with no additional attributes operations 95

98 Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule DQ_TempalAccuracy accuracy of the tempal attributes and tempal relationships of features condition Specified Class (DQ_Element) <<Abstract>> Generalization: DQ_AccuracyOfATimeMeasurement crectness of the tempal references of an item (repting of err in time measurement) condition Specified Class (DQ_TempalAccuracy) Generalization: DQ_TempalConsistency crectness of dered events sequences, if repted condition Specified Class (DQ_TempalAccuracy) Generalization: DQ_TempalValidity validity of data specified by the scope with respect to time condition Specified Class (DQ_TempalAccuracy) Generalization of DQ_Element thematic quality with no additional attributes operations DQ_ThematicAccuracy accuracy of quantitative attributes and the crectness of non-quantitative attributes and of the classifications of features and their relationships condition Specified Class (DQ_Element) <<Abstract>> Generalization: DQ_ThematicClassificationCrectness comparison of the classes assigned to features their attributes to a universe of discourse condition Specified Class (DQ_ThematicAccuracy) Generalization: DQ_NonQuantitativeAttributeAccuracy accuracy of nonquantitative attributes condition Specified Class (DQ_ThematicAccuracy) Generalization: DQ_QuantitativeAttributeAccuracy accuracy of quantitative attributes condition Specified Class (DQ_ThematicAccuracy) Generalization of DQ_Element f usability with no additional attributes operations QE_Usability degree of adherence of a dataset to a specific set of user requirements (DQ_Element extended) condition Specified class (DQ_Element) From

99 Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule Generalization of DQ_Element f unclassified measures with one additional attribute to address the case of multi-part results NMF_QualityMeasure Quality measures that do not fall under the other categies including codinate transfmations, statistics and signal quality. condition Specialized Class (DQ_Element) role name: derivedelement In the case of aggregation derivation, indicates the iginal element O N Association / DQ_Element Table 38 : DQ_Element DQ_Result Figure 12 defines the metadata classes required to capture the value ( set of values) obtained applying a quality measure technique. This diagram is based on Figure A.4 in ISO 19115:2003/C 1:2006. This diagram has not been profiled to address I&E community requirements. Figure 12 : Data Quality Result DQ_Result Data Dictionary DQ_Result is used by DQ_Element to capture the value ( set of values) obtained applying a quality measure technique the outcome of evaluating the obtained value ( set of values) against a specified acceptable confmance quality level. The data dictionary table presented in this section is based on the cresponding Quality Result data dictionary table (Section B.2.4.4) found in ISO 19115:2003/C 1:2006. Modifications to the DQ_Element class in ISO are: Added business logic discouraging use of the errstatistic element. 97

100 Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule DQ_Result generalization of me specific result classes condition Class <<Abstract>> DQ_ConfmanceResult Infmation about the outcome of evaluating the obtained value ( set of values) against a specified acceptable confmance quality level condition Specified Class (DQ_Result) specification explanation pass citation of product specification user requirement against which data is being evaluated explanation of the meaning of confmance f this result indication of the confmance result where 0 = fail and 1 = pass M 1 Class / CI_Citation <<DataType>> ( ) M 1 CharacterString / M 1 Boolean / 1 = yes, 0 = no DQ_QuantitativeResult the values infmation about the value(s) ( set of values) obtained applying a data quality measure condition Specified Class (DQ_Result) valuetype value type f repting a data quality result O 1 Class / RecdType <<Metaclass>> (Annex B) valueunit value unit f repting a data quality result M 1 Class / UnitOfMeasure (Annex B) Defined in ISO/TS 19103:2005 value quantitative value values, content determined by the evaluation procedure used M N Class / Recd (Annex B) Table 39 : DQ_Result Extension to data quality result to suppt coverage quality Figure 13 defines an extension required to specify the repted quality f coverage data. The additional elements provide infmation about the representation of the quality result documenting the data in the dataset. 98

101 Figure 13 : Data quality result with coverage quality extension The specification of QE_CoverageResult is simply based on existing concepts ISO and ISO/TS 19139: the coverage result has a spatial representation which, in some cases, can be exactly the same as the resource spatial representation may differ (e.g., coverage result computed on a vect database coverage result using a sample of the resource). The construct used to describe the spatial representation of the coverage result is the MD_SpatialRepresentation class. The resultspatialrepresentation property is mandaty but can be implemented as a reference to the instance of MD_SpatialRepresentation related to the resource. the coverage result has a content description. The construct used to describe the content of the result coverage is MD_CoverageDescription. The resulting coverage will often be defined by the distribution of a single attribute over the result coverage domain, but it is anticipated that the range type of the result coverage can comprise many attributes. the coverage result has a fmat which is expressed through the MD_Fmat class. the coverage result is associated to a data file containing the coverage result data. The construct used to describe the result coverage data file is MX_DataFile ( ISO/TS 19139). 99

102 The data dictionary presented in this table includes SDSFIE-M -specific extensions to the QE_CoverageResult Data Dictionary table found in ISO :2009 (Section B.2.2.1). No profiling of this table was required to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule QE_CoverageResult result of a data quality measure ganising the measured values as a coverage (DQ_Result extended) condition Specified class (DQ_Result) spatialrepresentationtype method used to spatially represent the coverage result M 1 Class / SpatialRepresentationTypeCode <<CodeList>> ( ) See Table 3 (SpatialRepresentationTypeCode) Role name: resultspatialrepresentation provides the digital representation of data quality measures composing the coverage result M 1 Association / MD_SpatialRepresentation <<Abstract>> ( ) Role name: resultcontentdescription provides the description of the content of the result coverage, i.e. semantic definition of the data quality measures M 1 Association / MD_CoverageDescription ( ) Role name: resultfmat provides infmation about the fmat of the result coverage data M 1 Association / MD_Fmat ( ) Role name: resultfile provides infmation about the data file containing the result coverage data M 1 Association / MX_DataFile ( ) Transfer files Figure 14 describes the suppt and data files concept and is based on the cresponding figure ISO/TS 19139:2005 (Figure 9). The data files are potentially related to one many feature types. Each data file has its own fmat which is generally described within the metadata of the dataset. 100

103 Figure 14 : Transfer Files The MX_File data dictionary presented in this table is based on the cresponding data dictionary found in ISO/TS 19139:2005 section B No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MX_File Description of a transfer file condition Class <<Abstract>> filename filedescription filetype Name of the transfer data file. This name is associated with a path to the physical file General description of the transfer data file Type of the transfer data file. The textual description of the file type is associated with an indication of the MIME Type. M 1 FileName (Annex B) M 1 CharacterString / M 1 MimeFileType (Annex B) MX_DataFile Description of a transfer data file condition Specified Class (MX_File) 101

104 featuretype Role name: filefmat Provides the list of Feature Types concerned by the transfer data file. Depending on the transfer choices, a data file may contain data related to one many feature types. This attribute may be omitted when the dataset is composed of a single file and/ the data does not relate to a feature catalogue Defines the fmat of the transfer data file MX_SupptFile Description of a transfer suppt file condition O N GenericName (Annex B) M 1 Class / MD_Fmat ( ) Table 40 : MX_File, MX_DataFile, and MX_SupptFile Specified Class (MX_File) Maintenance Infmation Maintenance infmation is used to describe the maintenance and update practices (scope and frequency) f the documented resource Maintenance Infmation UML Figure 15 is based on the cresponding Maintenance Infmation Package UML diagram (Figure A.7) found in 19115:2003/C 1:2006. No profiling of this diagram was required to address I&E requirements. 102

105 Maintenance Infmation Figure 15 : Maintenance Infmation The data dictionary table presented in this section is based on the cresponding Maintenance Infmation data dictionary table (Section B.2.5.1) found in ISO 19115:2003/C 1:2006. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_MaintenanceInfmation infmation about the scope and frequency of updating condition Aggregated Class (MD_Metadata and MD_Identification) 103

106 maintenanceandupdatefrequency dateofnextupdate userdefinedmaintenancefrequency updatescope updatescopedescription maintenancenote Contact frequency with which changes and additions are made to the resource after the initial resource is completed scheduled revision date f resource maintenance period other than those defined scope of data to which maintenance is applied additional infmation about the range extent of the resource infmation regarding specific requirements f maintaining the resource identification of, and means of communicating with, person(s) and ganization(s) with responsibility f maintaining the metadata M 1 Class / MaintenanceFrequencyCode <<CodeList>> ( ) See Table 3 (MaintenanceFrequencyCode) O 1 Class / Date (Annex B) O 1 Class / TM_PeriodDuration (Annex B) O N Class / NMF_ScopeCode <<CodeList>> ( ) O N Class / MD_ScopeDescription <<Union>> ( ) O N CharacterString / O N Class / CI_ResponsibleParty <<DataType>> ( ) Scope Description Table 41 : Maintenance Infmation The data dictionary table presented in this section is based on the cresponding Scope Description data dictionary table (Section B.2.5.2) found in ISO 19115:2003/C 1:2006. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_ScopeDescription description of the class of infmation covered by the infmation condition Class <<Union>> UNION one and only one attribute should be populated attributes instances of attribute types to which the infmation applies C / features, featureinstances, attributeinstances, dataset and other not documented? 1 Set (B.4.7) / GF_AttributeType (Annex B) features instances of feature types to which the infmation applies C / attributes, featureinstances, attributeinstances, dataset and other not documented? 1 Set (B.4.7) / GF_FeatureType (Annex B) featureinstances feature instances to which the infmation applies C / attributes, features, attributeinstances, dataset and other not documented? 1 Set (B.4.7) / GF_FeatureType (Annex B) 104

107 attributeinstances attribute instances to which the infmation applies C / attributes, features, featureinstances, dataset and other not documented? 1 Set (B.4.7) / GF_AttributeType (Annex B) dataset dataset to which the infmation applies C / attributes, features, featureinstances, attributeinstances, and other not documented? 1 CharacterString / other class of infmation that does not fall into the other categies to which the infmation applies C / attributes, features, featureinstances, attributeinstances, and dataset not documented? 1 CharacterString / Table 42 : Scope Description Spatial Representation Infmation The MD_SpatialRepresentation entity captures infmation about the mechanisms used to represent spatial infmation in a data set Spatial Representation UML The data dictionary table presented in this section is based on the cresponding Scope Description data dictionary table (Section B.2.5.2) found in ISO 19115:2003/C 1:2006 and ISO :2009. No profiling of this diagram was required to address I&E requirements. 105

108 Figure 16 : Spatial Representation Figure 17 depicts extensions made by ISO :2009 f imagery. 106

109 Figure 17 : Spatial representation extension f imagery Spatial Representation Infmation The data dictionary table presented in this section is based on the cresponding Spatial Representation Infmation data dictionary table (Section B.2.6.1) found in ISO 19115:2003/C 1:2006. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule 107

110 MD_SpatialRepresentation digital mechanism used to represent spatial infmation condition Aggregated Class (MD_Metadata) <<Abstract>> MD_GridSpatial Representation infmation about grid spatial s in the dataset condition Specified Class (MD_SpatialRepresentation) numberofdimensions axisdimensionsproperties cellgeometry transfmationparameter Availability number of independent spatial-tempal axes infmation about spatialtempal axis properties identification of grid data as point cell indication of whether not parameters f transfmation between image codinates and geographic map codinates exist (are available) M 1 Integer M 1 Sequence (Annex B) / MD_Dimension <<DataType>> ( ) M 1 Class / CellGeometryCode <<CodeList>> ( ) M 1 Boolean / 1 = yes, 0 = no See Table 3 (CellGeometryCode) MD_Geectified grid whose cells are regularly spaced in a geographic (i.e., lat / long) map codinate system defined in the Spatial Referencing System (SRS) so that any cell in the grid can be geolocated given its grid codinate and the grid igin, cell spacing, and ientation condition Specified (MD_GridSpatialRepresentation) checkpointavailability indication of whether not geographic position points are available to test the accuracy of the geeferenced grid data M 1 Boolean / 1 = yes, 0 = no checkpointdescription description of geographic position points used to test the accuracy of the geeferenced grid data C / checkpoint Availability equals yes? 1 CharacterString / 108

111 cnerpoints centerpoint pointinpixel transfmationdimension Description transfmationdimension Mapping MD_Geeferenceable controlpointavailability ientationparameter Availability ientationparameter Description geeferencedparameters parametercitation MD_VectSpatial Representation earth location in the codinate system defined by the Spatial Reference System and the grid codinate of the cells at opposite ends of grid coverage along two diagonals in the grid spatial dimensions. There are four cner points in a geectified grid; at least two cner points along one diagonal are required. The first cner point cresponds to the igin of the grid. earth location in the codinate system defined by the Spatial Reference System and the grid codinate of the cell halfway between opposite ends of the grid in the spatial dimensions point in a pixel cresponding to the Earth location of the pixel general description of the transfmation infmation about which grid axes are the spatial (map) axes grid with cells irregularly spaced in any given geographic/map projection codinate system, whose individual cells can be geolocated using geolocation infmation supplied with the data but cannot be geolocated the grid properties alone indication of whether not control point(s) exists indication of whether not ientation parameters are available description of parameters used to describe sens ientation terms which suppt grid data geo reference providing description of the parameters infmation about the vect spatial s in the dataset M 1 Sequence (Annex B) GM_Point <<Type>> (Annex B) O 1 Class / GM_Point <<Type>> (Annex B) M 1 Class / MD_PixelOrientationCode <<Enumeration>> ( ) O 1 CharacterString / O 2 CharacterString / condition M 1 Boolean / 1 = yes, 0 = no M 1 Boolean / 1 = yes, 0 = no Specified Class (MD_GridSpatialRepresentation) O 1 CharacterString / M 1 Class / Recd (Annex B) O N Class / CI_Citation <<DataType>> ( ) condition Specified Class (MD_SpatialRepresentation) 109

112 topologylevel geometricobjects code which identifies the degree of complexity of the spatial relationships infmation about the geometric s used in the dataset O 1 Class / TopologyLevelCode <<CodeList>> ( ) See Table 3 (TopologyLevelCode) O N Class / MD_GeometricObjects <<DataType>> ( ) Table 43 : Spatial Representation Infmation Dimension The data dictionary table presented in this section is based on the cresponding MD_DImension data dictionary table (Section B.2.6.2) found in ISO 19115:2003/C 1:2006. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_Dimension axis properties condition Class <<DataType>> dimensionname name of the axis M 1 Class / DimensionNameTypeCode <<CodeList>> ( ) See Table 3 (DimensionNameTypeCode) dimensionsize resolution number of elements along the axis degree of detail in the grid dataset M 1 Integer / Integer O 1 Class / Measure (Annex B) Table 44 : MD_Dimension Geectified - Extensions The data dictionary table presented in this section is based on the cresponding Geectified - Extensions data dictionary table (Section B.2.3.2) found in ISO :2009. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_Geectified extends geectified grid description to include associated checkpoints (MD_Geectified extended) condition Specified Class (MD_Geectified) role name: checkpoint geographic references used to validate geectification of the data O N Association / MI_GCP ( ) Table 45 : MI_Geectified 110

113 Geeferenceable- Extensions The data dictionary table presented in this section is based on the cresponding Geeferenceable- Extensions data dictionary table (Section B.2.3.3) found in ISO :2009. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_Geeferenceable description of infmation provided in metadata that allows the geographic map location of the raster points to be located (MD_Geeferencable extended) condition Specified Class (MD_Geeferenceable) role name: geolocationinfmation infmation that can be used to geolocate the data M N Association / MI_GeolocationInfmation ( ) Table 46 : MI_Geeferenceable Ground Control Point Collection The data dictionary table presented in this section is based on the cresponding Ground Control Point Collection data dictionary table (Section B.2.3.4) found in ISO :2009. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_GeolocationInfmation infmation used to determine geographic location cresponding to image location condition Aggregated Class (MI_Geeferenceable) role name: qualityinfo provides an overall assessment of quality of geolocation infmation O * Association / DQ_DataQuality ( ) MI_GCPCollection infmation on ground control point collections used f geolocation condition Specified Class (MI_GeolocationInfmation) collectionidentification identifier of the GCP collection M 1 Integer / Integer collectionname name of the GCP collection M 1 CharacterString / codinatereferencesystem role name: gcp codinate system in which the ground control points are defined ground control point(s) used in the collection M 1 Class / MD_ReferenceSystem ( ) M * Association / MI_GCP ( ) Table 47 : MI_GeolocationInfmation 111

114 Ground Control Points The data dictionary table presented in this section is based on the cresponding Ground Control Points data dictionary table (Section B.2.3.5) found in ISO :2009. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_GCP infmation on ground control points used f geolocation condition Aggregated Class (MI_GCPCollection) geographiccodinates role name: accuracyrept geographic map position of the control point, in either two three dimensions accuracy of a ground control point M 1 Class / Direct Position (ISO/TS 19103) O * Class / DQ_Element ( ) Table 48 : MI_GCP Geometric Objects The data dictionary table presented in this section is based on the cresponding Geometric Objects data dictionary table (Section B.2.6.3) found in ISO 19115:2003/C 1:2006. No profiling of this table was required to address I&E requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_GeometricObjects number of s, listed by geometric type, used in the dataset condition Class <<DataType>> geometricobjecttype geometricobjectcount name of point vect s used to locate zero-, one-, two-, three-dimensional spatial locations in the dataset total number of the point vect type occurring in the dataset M 1 Class / GeometricObjectTypeCode <<CodeList>> ( ) O 1 Integer / > 0 See Table 3 (GeometricObjectTypeCode) Table 49 : Geometric Objects Reference System Reference System UML This UML diagram is an SDSFIE-M -specific version of the cresponding Reference System Package UML diagram (Figure A.9) found in ISO 19115:2003/C 1:2006. The diagram has been profiled, so some classes, attributes and association roles have been hidden. F the full diagram, consult ISO 19115:2003/C 1:2006. This diagram defines metadata required to describe the spatial reference system used in the resource. 112

115 Reference System Figure 18 : Reference System The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Reference System data dictionary table (Section B.2.7.1) found in ISO 19115:2003/C 1:2006. The table has been profiled, so some classes, attributes and association roles have been hidden. F the full table, consult ISO 19115:2003/C 1:2006. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MD_ReferenceSystem infmation about the reference system condition Aggregated Class (MD_Metadata) referencesystemidentifier name of reference system M 1 Class / RS_Identifier ( ) See Table 2 (CrsIdentifier) CrsIdentifier is a realization of the abstract functionality described by RS_Identifier, and is the preferred realization. It is a Recommended Best Practice that when a Geodetic 2D CRS is used that it be in accdance with Wld Geodetic System Geographic, 2- Dimensional, as specified in NIMA TR (3rd Edition, Amendment 1) and identified by the URI: ns/gsip/crs/wgs84e_2d Note: this element is optional in ISO 19115:2003/C. 1:2006. Table 50 : Reference System 113

116 7.4.8 Identifier Identifier UML This UML diagram is an SDSFIE-M -specific diagram that is not found in ISO 19115:2003/C 1:2006. The classes defined here are present in ISO 19115:2003/C 1:2006, but they have been moved to a separate diagram f ease of understanding. This diagram defines the metadata required to unambiguously identify a resource Identifier Figure 19 : Identifier The MD_Identifier entity serves to unambiguously identify a resource. The structure of this entity consists of a namespace authity and a code value. The code value uniquely identifies a resource within the specified namespace. The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Identifier Infmation data dictionary table (Section B.2.7.3) found in ISO 19115:2003/C 1:2006. It differs the ISO version in that the obligation on authity is mandaty in this profile and that the RS_Identifier subclass is documented in a separate table. Name / role name Definition Obligation / Condition Max Occur Data type Domain Busi ness Rule MD_Identifier value uniquely identifying an within a namespace condition Class <<DataType>> authity person party responsible f maintenance of the namespace M 1 Class / CI_Citation <<DataType>> ( ) code alphanumeric value identifying an instance in the namespace M 1 CharacterString / Table 51 : Identifier 114

117 MD_Identifier is flexible construct suppting many different fms of identification. Flexibility, however, is often the enemy of interoperability. This standard addresses that issue by specifying the content of the MD_Identifier elements f each metadata element in this standard which is of type MD_Identifier. Table 52 addresses the case where the identifier can be resolved to the referenced entity through automated means. Element Authity (CI_Citation) Code (CharacterString) NMF_RevisionRecall. revisionlink MD_AggregateInfmation. aggregatedatasetidentifier NTK_Access. Individual and NMF_rInput.user NTK_Access. group NTK_Access. profile EX_GeographicDescription. geographicidentifier CI_Citation. identifier Title: ITU-T REC. X.667 Date: 08/2008 Title: IETF RFC 3986 Date: 2005 Title: ITU-T REC. X.667 Date: 08/2008 Title: IETF RFC 3986 Date: 2005 Title: URN f the LDAP server Date: date and time when the identification was last validated Title: URN f the LDAP server Date: date and time when the identification was last validated Title: URN f the LDAP server Date: date and time when the definition was last validated Title: ITU-T REC. X.667 Date: 08/2008 Title: IETF RFC 3986 Date: 2005 Title: ITU-T REC. X.667 Date: 08/2008 Title: IETF RFC 3986 Date: 2005 Hexadecimal UUID value per ITU-T REC. X.667 URI per IETF RFC 3986 Hexadecimal UUID value per ITU-T REC. X.667 URI per IETF RFC 3986 LDAP Distinguished Name f the user per IETF RFC 4514 LDAP Distinguished Name f the group per IETF RFC 4514 LDAP Distinguished Name f the profile per IETF RFC 4514 Hexadecimal UUID value per ITU-T REC. X.667 URI per IETF RFC 3986 Hexadecimal UUID value per ITU-T REC. X.667 URI per IETF RFC 3986 NOTE: Implementation Specifications may specify another X.667 compliant encoding of the UUID as long as it conveys equivalent infmation to the specified hexadecimal encoding. Table 52 : Resolvable Resource Identifiers Not all identifiers will be suitable f automated resolution. In those cases, it may be sufficient that the authity / code pair is unique, human intervention may be required to perfm the resolution. Table 53 addresses these case where the identifier cannot be resolved through automated means. Element Authity (CI_Citation) Code (CharacterString) 115

118 NMF_RevisionRecall. revisionlink MD_AggregateInfmation. aggregatedatasetidentifier NTK_Access. Individual and NMF_rInput.user NTK_Access. group NTK_Access. profile EX_GeographicDescription. geographicidentifier CI_Citation. identifier NA notice content should be provided in revisiondetails NA aggregatedatasetname provides dataset name Title: name of the system Date: date and time when the identification was last validated Title: name of the system Date: date and time when the identification was last validated Title: name of the system Date: date and time when the definition was last validated Title: title of the document where the identifier is described Date: date of the describing document Title: title of the governing specification Date: date of the governing specification NA NA r name Group name Profile name Textual identification of the geographic extent Identifier (ex. card catalog number) Table 53 : Non-Resolvable Resource Identifiers F imagery and gridded data, many of the identifier metadata elements may be captured using one of the general purpose identifiers described in Table 31. Element Authity (CI_Citation) Code (CharacterString) UUID Title: ITU-T REC. X.667 Date: 08/2008 Hexadecimal UUID value per ITU-T REC. X.667 UUID URN encoding Title: IETF RFC 4122 Date: 2005 URI Title: IETF RFC 3986 Date: 2005 URN per IETF RFC 4122 URI per IETF RFC 3986 NOTE: Implementation Specifications may specify another X.667 compliant encoding of the UUID as long as it conveys equivalent Table 54 : General Purpose Identifiers f Imagery and Gridded Data F imagery and gridded data, many of the identifier metadata elements may be captured using one of the general purpose identifiers described in Table 55. Element Authity (CI_Citation) Code (CharacterString) MD_ImageDescription. imagequalitycode MD_ImageDescription. processinglevelcode MI_Requirement.identifier Title: Name of the quality measurement specification Date: Date of the version used Title: Name of the processing specification Date: Date of the version used Title: Name of community standard Date: Date of the version used A general purpose identifier Image quality code value Processing level value Community identifier value 116

119 MI_Instrument.identifier MI_Objective.identifier MI_Operation.identifier MI_Platfm.identifier MI_PlatfmPass.identifier MI_Event.identifier Title: Name of community standard Date: Date of the version used A general purpose identifier Title: Name of community standard Date: Date of the version used A general purpose identifier Title: Name of community standard Date: Date of the version used A general purpose identifier Title: Name of community standard Date: Date of the version used A general purpose identifier Title: Name of community standard Date: Date of the version used A general purpose identifier Title: Name of community standard Date: Date of the version used A general purpose identifier Community identifier value Community identifier value Community identifier value Community identifier value Community identifier value Community identifier value Reference System Identifier Table 55 : Imagery and Gridded Data Identifiers The RS_Identifier entity extends MD_Identifier to identify a reference system. The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Identifier Infmation data dictionary table (Section B.2.7.3) found in ISO 19115:2003/C 1:2006. It differs the ISO version in its obligations and in that the MD_Identifier and RS_Identifier classes are documented in separate tables. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule RS_Identifier identifier used f reference systems condition Specified Class (MD_Identifier) codespace name identifier of the person ganization responsible f namespace M 1 CharacterString / version version identifier f the namespace O 1 CharacterString / Table 56 : RS_Identifier 117

120 7.4.9 Content Infmation Content Infmation UML This UML diagram is an SDSFIE-M -specific version of the cresponding Content Infmation Package UML diagram (Figure A.10) found in ISO 19115:2003/C 1:2006. The diagram has been profiled, so some classes, attributes and association roles have been hidden. F the full diagram, consult ISO 19115:2003/C 1:2006 class Content infmation MD_Metadata +contentinfo 0..* MD_ContentInfmation «union» SMF_FeatureTypes + featuretypes :GenericName + sdsfiefeaturetypes :SMF_Feature «<<DataType>>» SMF_Feature + name :CharacterString + aliasname :CharacterString + modelname :CharacterString + definition :CharacterString + description :CharacterString + note :CharacterString + justification :CharacterString MD_Cov eragedescription + attributedescription :RecdType + contenttype :MD_CoverageContentTypeCode +dimension 0..* 0..* MD_FeatureCatalogueDescription + compliancecode :Boolean [0..1] + language :CharacterString [0..*] + includedwithdataset :Boolean + featuretypes :SMF_FeatureTypes [1..*] + featurecataloguecitation :CI_Citation [1..*] MD_RangeDimension + sequenceidentifier :MemberName [0..1] + descript :CharacterString [0..1] MD_Band + maxvalue :Real [0..1] + minvalue :Real [0..1] + units :UomLength [0..1] + peakresponse :Real [0..1] + bitspervalue :Integer [0..1] + tonegradation :Integer [0..1] + scalefact :Real [0..1] + offset :Real [0..1] "units" is mandaty if "maxvalue" "minvalue" are provided MD_ImageDescription + illuminationelevationangle :Real [0..1] + illuminationazimuthangle :Real [0..1] + imagingcondition :MD_ImagingConditionCode [0..1] + imagequalitycode :MD_Identifier [0..1] + cloudcoverpercentage :Real [0..1] + processinglevelcode :MD_Identifier [0..1] + compressiongenerationquantity :Integer [0..1] + triangulationindicat :Boolean [0..1] + radiometriccalibrationdataavailability :Boolean [0..1] + cameracalibrationinfmationavailability :Boolean [0..1] + filmdisttioninfmationavailability :Boolean [0..1] + lensdisttioninfmationavailability :Boolean [0..1] «CodeList» MD_Cov eragecontenttypecode {root,leaf} + image + thematicclassification + physicalmeasurement «CodeList» MD_ImagingConditionCode {root,leaf} + blurredimage + cloud + degradingobliquity + fog + heavysmokeordust + night + rain + semidarkness + shadow + snow + terrainmasking Figure 20 : Content Infmation 118

121 This UML diagram is the cresponding Content Infmation Package UML diagram (Figure A.7) found in ISO :2009. No profiling of this diagram has been perfmed to address I&E community requirements. Figure 21 : Content Infmation with imagery extensions Content Infmation The data dictionary table presented in this section is an SDSFIE-M -specific version of the cresponding Content Infmation data dictionary table (Section B.2.8) found in ISO 19115:2003/C 1:2006. The table has been modified by updating the featuretypes DataType to allow f a me detailed description of SDSFIE feature types while still leaving the possibility f the description of non-sdsfie feature types. F the full table, consult ISO 19115:2003/C 1:2006. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule 119

122 MD_ContentInfmation description of the content of a dataset condition Aggregated Class (MD_Metadata) <<Abstract>> MD_FeatureCatalogueDescription infmation identifying the feature catalogue the conceptual schema condition Specified Class (MD_ContentInfmation) includedwithdataset featuretypes featurecataloguecitation indication of whether not the feature catalogue is included with the dataset subset of feature types cited feature catalogue occurring in dataset complete bibliographic reference to one me external feature catalogues M 1 Boolean / 0=no, 1=yes M N Class / SMF_FeatureTypes <<Union>> ( ) M N Class / CI_Citation <<DataType>> ( ) MD_CoverageDescription infmation about the content of a grid data cell condition Specified Class (MD_ContentInfmation) attributedescription contenttype role name: dimension description of the attribute described by the measurement value type of infmation represented by the cell value infmation on the dimensions of the cell measurement value M 1 Class / RecdType <<Metaclass>> (Annex B) M 1 Class / CoverageContentTypeCode <<CodeList>> ( ) See Table 3 (CoverageContentTypeCode) O N Class / MD_RangeDimension ( ) MD_ImageDescription infmation about an image s suitability f use condition Specified Class (MD_CoverageDescription) illuminationelevationangle illumination elevation measured in degrees clockwise the target plane at intersection of the optical line of sight with the Earth s surface. F images a scanning device, refer to the centre pixel of the image O 1 Real /

123 illuminationazimuthangle imagingcondition imagequalitycode cloudcoverpercentage processinglevelcode compressiongenerationquantity triangulationindicat radiometriccalibrationdata Availability cameracalibrationinfmation Availability filmdisttioninfmation Availability lensdisttioninfmation Availability illumination azimuth measured in degrees clockwise true nth at the time the image is taken. F images a scanning device, refer to the centre pixel of the image conditions affected the image specifies the image quality area of the dataset obscured by clouds, expressed as a percentage of the spatial extent image distribut s code that identifies the level of radiometric and geometric processing that has been applied count of the number of lossy compression cycles perfmed on the image indication of whether not triangulation has been perfmed upon the image indication of whether not the radiometric calibration infmation f generating the radiometrically calibrated standard data product is available indication of whether not constants are available which allow f camera calibration crections indication of whether not Calibration Reseau infmation is available indication of whether not lens aberration crection infmation is available O 1 Real / O 1 Class / ImagingConditionCode <<CodeList>> ( ) See Table 3 (ImagingConditionCode) O 1 Class / MD_Identifier <<DataType>> ( ) O 1 Real / O 1 Class / MD_Identifier <<DataType>> ( ) O 1 Integer O 1 Boolean / 0=no, 1=yes O 1 Boolean / 0=no, 1=yes O 1 Boolean / 0=no, 1=yes O 1 Boolean / 0=no, 1=yes O 1 Boolean / 0=no, 1=yes Table 57 : Content Infmation 121

124 FeatureTypes SMF_FeaturesTypes is an entirely new element meant to provide f documentation of the feature types contained within a dataset, either by name (using the featuretypes element), f SDSIFE-based feature types by name, alias name, model name, definition, description, note, and justification (using the sdsfiefeaturetypes element). Name / role name Definition Obligation / Condition SMF_FeatureTypes description of feature types condition featuretypes sdsfiefeaturetypes feature types contained within the dataset SDSFIE (Gold Adaptation) feature types contained with the dataset C / sdsfiefeature Types is not set? C / featuretypes is not set? Max Occur Data type / Domain Class <<Union>> N Class / GenericName (Annex B) N Class / SMF_Feature <<DataType>> ( ) Business Rule UNION one and only one attribute should be populated Table 58 : SMF_FeatureTypes Features The SMF_Features DataType is an entirely new element intended to group the elements of an SDSFIE-based feature type description in to a single entity. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule SMF_Feature SDSFIE-M specific infmation required to describe feature classes that are defined by some Adaptation of SDSFIE condition Class <<DataType>> name the name of the SDSFIE feature class M 1 CharacterString / aliasname the alias name of the SDSFIE feature class O 1 CharacterString / modelname the model name of the SDSFIE feature class O 1 CharacterString / definition the definition of the SDSFIE feature class M 1 CharacterString / description the description of the SDSFIE feature class O 1 CharacterString / note the note f the SDSFIE feature class O 1 CharacterString / justification infmation regarding the business justification and/ purpose f collection of this feature class O 1 CharacterString / Table 59 : SMF_Features 122

125 Range Dimension The data dictionary table presented in this section is based on the cresponding Range Dimension data dictionary table found in ISO 19115:2003/C. 1:2006 (Section B.2.8.2). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MD_RangeDimension infmation on the range of each dimension of a cell measurement value condition Aggregated Class (MD_CoverageDescription) sequenceidentifier descript number that uniquely identifies instances of bands of wavelengths on which a sens operates description of the range of a cell measurement value O 1 Class / MemberName (Annex B) O 1 CharacterString / MD_Band range of wavelengths in the electromagnetic spectrum condition Specified Class (MD_RangeDimension) maxvalue minvalue longest wavelength that the sens is capable of collecting within a designated band shtest wavelength that the sens is capable of collecting within a designated band O 1 Real O 1 Real units units in which sens wavelengths are expressed C / minvalue maxvalue provided? 1 Class / UomLength (Annex B) peakresponse bitspervalue tonegradation scalefact offset wavelength at which the response is the highest number of significant bits in the uncompressed representation f the value in each band of each pixel number of discrete numerical values in the grid data scale fact which has been applied to the cell value the physical value cresponding to a cell value of zero O 1 Real O 1 Integer O 1 Integer O 1 Real O 1 Real 123

126 Table 60 : MD_RangeDimension Wavelength Band Infmation The data dictionary table presented in this section is based on the cresponding Wavelength Band data dictionary table found in ISO :2009 (Section B.2.4.2). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_Band extensions to electromagnetic spectrum wavelength description (MD_Band extended) condition Specified Class (MD_Band) bandboundarydefinition nominalspatialresolution transferfunctiontype transmittedpolarisation detectedpolarisation designation of criterion f defining and minimum wavelengths f a spectral band smallest distance between which separate points can be distinguished, as specified in instrument design type of transfm function to be used when scaling a physical value f a given element polarisation of the radiation transmitted polarisation of the radiation detected O 1 Class / BandDefinition <<CodeList>> ( ) See Table 3 (BandDefinition) O 1 Class / Distance <<DataType>> O 1 Class / TransferFunctionTypeCode <<CodeList>> ( ) See Table 3 (TransferFunctionTypeCode) O 1 Class / PolarisationOrientationCode <<CodeList>> ( ) See Table 3 (PolarisationOrientationCode) O 1 Class / PolarisationOrientationCode <<CodeList>> ( ) See Table 3 (PolarisationOrientationCode) Table 61 : MI_Band Coverage and Image Description Extensions The data dictionary table presented in this section is based on the cresponding section of the Coverage and Image Description Extensions data dictionary table found in ISO :2009 (Section B.2.4.3). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_CoverageDescription infmation about the content of a coverage, including the description of specific range elements (MD_CoverageDescription extended) condition Specified class (MD_CoverageDescription) 124

127 role name: rangeelementdescription provides the description of the specific range elements of a coverage O N Association / MI_RangeElementDescription ( ) Table 62 : MI_CoverageDescription The data dictionary table presented in this section is based on the cresponding section of the Coverage and Image Description Extensions data dictionary table found in ISO :2009 (Section B.2.4.3). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_ImageDescription infmation about the content of an image, including the description of specific range elements (MD_ImageDescription extended) condition Specified class (MD_ImageDescription) role name: rangeelementdescription provides the description of the specific range elements of an image O N Association / MI_RangeElementDescription ( ) Table 63 : MI_ImageDescription The data dictionary table presented in this section is based on the cresponding section of the Coverage and Image Description Extensions data dictionary table found in ISO :2009 (Section B.2.4.3). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type Domain Business Rule MI_RangeElementDescription description of specific range elements condition Class name definition rangeelement designation associated with a set of range elements description of a set of specific range elements specific range elements, i.e. range elements associated with a name and their definition M 1 CharacterString / M 1 CharacterString / M N Class / Recd (Annex B) Application Schema Table 64 : MI_RangeElementDescription Application Schema UML This UML diagram is an SDSFIE-M -specific version of the cresponding Application Schema Package UML diagram (Figure A.14) found in ISO 19115:2003/C 1:2006. The MD_ApplicationSchema class was specialized to provide a place f the version of 125

128 the application schema to be included. F the full diagram, consult ISO 19115:2003/C 1:2006 This diagram defines the application schema used. Figure 22 : Application Schema Application Schema The data dictionary table presented in this section is based on the cresponding section of the Application Schema data dictionary table (Section B.2.12) found in ISO 19115:2003/C 1:2006. The definition of the name element to indicate that the name of the application schema is equivalent to the SDSFIE Adaptation name if that is the application schema used. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MD_ApplicationSchema Infmation name schemalanguage constraintlanguage schemaascii infmation about the application schema used to build the dataset The name of the application schema used. If the resource being documented is SDSFIE data, then this element is the name of the applicable SDSFIE Adaptation. identification of the schema language used fmal language used in Application Schema full application schema given as an ASCII file condition Aggregated Class (MD_Metadata) M 1 Class / CI_Citation <<DataType>> ( ) M 1 CharacterString / M 1 CharacterString / O 1 CharacterString / 126

129 graphicsfile softwaredevelopmentfile softwaredevelopmentfile Fmat SMF_ApplicationSchema Infmation sdsfieadaptationversion full application schema given as a graphics file full application schema given as a software development file software dependent fmat used f the application schema software dependent file SDSFIE-M specific infmation required to describe an application schema f feature classes that are defined by some Adaptation of SDSFIE the version of the SDSFIE Adaptation that contains this feature class O 1 Binary O 1 Binary O 1 CharacterString / condition C / is an SDSFIE (Gold adaptation) feature class? Specified Class (MD_ApplicationSchema Infmation) 1 CharacterString / Table 65 : Application Schema Infmation Acquisition Infmation The MI_AcquisitionIfmation entity captures infmation about the measuring instruments and their bands, the platfm carrying them, and the mission to which the data contributes. This infmation is added to SDSFIE-M through this entity Acquisition Infmation UML Two UML diagrams have been presented in this section. The first diagram (Figure 23) is based on the Acquisition Overview UML diagram (Figure A.7) found in ISO :2009. The second diagram (Figure 24) provides a detailed view of the Acquisition Infmation classes. It is based on the Acquisition Details UML diagram (Figure A.8) also found in ISO :2009. Neither diagram has been modified f SDSFIE-M. 127

130 Figure 23 : Acquisition Overview 128

131 Figure 24 : Acquisition Detail Acquisition Infmation Data Dictionary The data dictionary table presented in this section is based on the cresponding Acquisition Infmation data dictionary table found in ISO :2009 (Section B.2.5.1). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_AcquisitionInfmation role name: acquisitionplan designations f the measuring instruments, the platfm carrying them, and the mission to which the data contributes Identifies the plan as implemented by the acquisition condition Aggregated Class (MI_Metadata) O N Association / MI_Plan ( ) 129

132 role name: acquisitionrequirement role name: instrument role name: ive role name: operation role name: platfm Identifies the requirement the data acquisition intends to satisfy general infmation about the instrument used in data acquisition identification of the area to be sensed general infmation about an identifiable activity which provided the data general infmation about the platfm which the data were taken O N Association / MI_Requirement ( ) O N Association / MI_Instrument (7.4,11.7) O N Association / MI_Objective ( ) O N Association / MI_Operation ( ) O N Association / MI_Platfm ( ) Table 66 : MI_AcquisitionInfmation Environmental Infmation The data dictionary table presented in this section is based on the cresponding Environmental Recd data dictionary table found in ISO :2009 (Section B.2.5.2). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_EnvironmentalRecd averageairtemperature maxrelativehumidity maxaltitude meteologicalconditions Infmation about the environmental conditions during the acquisition average air temperature along the flight pass during the photo flight relative humidity along the flight pass during the photo flight altitude during the photo flight meteological conditions in the photo flight area, in particular clouds, snow and wind condition M 1 Real M 1 Real M 1 Real Aggregated Class (MI_Operation) M 1 CharacterString / Free Text Table 67 : MI_EnvironmentalRecd Plan Infmation The data dictionary table presented in this section is based on the cresponding Plan Infmation data dictionary table found in ISO :2009 (Section B.2.5.7). No profiling of this table has been perfmed to address I&E community requirements. 130

133 Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_Plan designations f the planning infmation related to meeting the data acquisition requirements condition Aggregated Class (MI_Acquisition Infmation) type status citation role name: operation role name: satisfiedrequirement manner of sampling geometry that the planner expects f collection of ive data current status of the plan (pending, completed, etc.) identification of authity requesting target collection identification of the activity activities that satisfy a plan requirement satisfied by the plan O 1 Class / GeometryTypeCode <<CodeList>> ( ) See Table 3 (GeometryTypeCode) M 1 Class / ProgressCode <<CodeList>> ( ) See Table 3 (ProgressCode) M 1 Class / CI_Citation <<DataType>> ( ) O N Association / MI_Operation ( ) O N Association / MI_Requirement ( ) Table 68 : MI_Plan Requirement Infmation The data dictionary table presented in this section is based on the cresponding Requirement Infmation data dictionary table found in ISO :2009 (Section B ). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_Requirement requirement to be satisfied by the planned data acquisition condition Aggregated Class (MI_Acquisition Infmation) citation identifier identification of reference guidance material f the requirement unique name, code, f the requirement O 1 Class / CI_Citation <<DataType>> ( ) M 1 Class / MD_Identifier <<DataType>> ( ) request igin of requirement M N Class / CI_ResponsibleParty <<DataType>> ( ) recipient person(s), body(ies), to receive results of requirement M N Class / CI_ResponsibleParty <<DataType>> ( ) 131

134 priity requesteddate expirydate role name: satisfiedplan relative dered imptance, urgency, of the requirement required preferred acquisition date and time date and time after which collection is no longer valid plan that identifies solution to satisfy the requirement M 1 Class / PriityCode <<CodeList>> ( ) See Table 3 (PriityCode) M 1 Class / MI_RequestedDate <<DataType>> ( ) M 1 Class / DateTime (Annex B) O N Association / MI_Plan ( ) Table 69 : MI_Requirement Request Date Range The data dictionary table presented in this section is based on the cresponding Request Date Range data dictionary table found in ISO :2009 (Section B ). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_RequestedDate range of date validity condition Class <<DataType>> requesteddateof Collection latestacceptabledate preferred date and time of collection latest date and time collection must be completed M 1 Class / DateTime (Annex B) M 1 Class / DateTime (Annex B) Table 70 : MI_RequestedDate Instrument Identification The data dictionary table presented in this section is based on the cresponding Instrument Identification data dictionary table found in ISO :2009 (Section B.2.5.4). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_Instrument designations f the measuring instruments condition Aggregated Class (MI_Acquisition Infmation) citation complete citation of the instrument O * Class / CI_Citation <<DataType>> ( ) 132

135 identifier type description role name: mountedon unique identification of the instrument name of the type of instrument textual description of the instrument platfm the instrument is mounted on M 1 Class / MD_Identifier <<DataType>> ( ) M 1 CharacterString / O 1 CharacterString / O 1 Association / MI_Platfm ( ) Table 71 : MI_Instrument Objective Identification The data dictionary table presented in this section is based on the cresponding Objective Infmation data dictionary table found in ISO :2009 (Section B.2.5.5). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_Objective describes the characteristics, spatial and tempal extent of the intended to be observed condition Aggregated Class (MI_Acquisition Infmation, MI_Operation) identifier code used to identify the ive M * Class / MD_Identifier <<DataType>> ( ) priity priity applied to the target O 1 CharacterString / type function extent role name: iveoccurence role name: pass role name: sensinginstrument collection technique f the ive role purpose perfmed by activity perfmed at the ive extent infmation including the bounding box, bounding polygon, vertical and tempal extent of the ive event events associated with ive completion. pass of the platfm over the ive instrument which sensed the ive data O N Class / ObjectiveTypeCode <<CodeList>> ( ) See Table 3 (ObjectiveTypeCode) O N CharacterString / O N Class / EX_Extent <<DataType>> ( ) M N Association / MI_Event ( ) O N Association / MI_PlatfmPass ( ) O N Association / MI_Instrument (7.4,11.7) Table 72 : MI_Objective 133

136 Operation Infmation The data dictionary table presented in this section is based on the cresponding Operation Infmation data dictionary table found in ISO :2009 (Section B.2.5.6). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_Operation designations f the operation used to acquire the dataset condition Aggregated Class (MI_Acquisition Infmation, MI_Operation) description description of the mission on which the platfm observations are made and the ives of that mission O 1 CharacterString / citation identification of the mission O 1 Class / CI_Citation <<DataType>> ( ) identifier unique identification of the operation M 1 Class / MD_Identifier <<DataType>> ( ) status status of the data acquisition M 1 Class / ProgressCode <<CodeList>> ( ) See Table 3 (ProgressCode) role name: childoperation role name: ive sub-missions that make up part of a larger mission (s) area(s) of interest to be sensed O N Association / MI_Operation ( ) O N Association / MI_Objective ( ) role name: parentoperation heritage of the operation M 1 Association / MI_Operation ( ) role name: plan role name: platfm role name: significantevent plan satisfied by the operation platfm ( platfms) used in the operation recd of an event occurring during an operation O 1 Association / MI_Plan ( ) O N Association / MI_Platfm ( ) O N Association / MI_Event ( ) Table 73 : MI_Operation Platfm Infmation The data dictionary table presented in this section is based on the cresponding Platfm Infmation data dictionary table found in ISO :2009 (Section B.2.5.8). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule 134

137 MI_Platfm citation identifier description spons role name: instrument designation of the platfm used to acquire the dataset source where infmation about the platfm is described unique identification of the platfm. narrative description of the platfm suppting the instrument ganization responsible f building, launch, operation of the platfm instrument(s) mounted on a platfm condition Aggregated Class (MI_Acquisition Infmation, MI_Operation) O 1 Class / CI_Citation <<DataType>> ( ) M 1 Class / MD_Identifier <<DataType>> ( ) M 1 CharacterString / O N Class / CI_ResponsibleParty <<DataType>> ( ) M N Association / MI_Instrument (7.4,11.7) Table 74 : MI_Platfm Platfm Pass Identification The data dictionary table presented in this section is based on the cresponding Platfm Pass Infmation data dictionary table found in ISO :2009 (Section B.2.5.9). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule MI_PlatfmPass identification of collection coverage condition Aggregated Class (MI_Objective) identifier unique name of the pass M 1 Class / MD_Identifier <<DataType>> ( ) extent area covered by the pass O 1 Class / GM_Object (ISO 19107) <<Type>> role name: relatedevent of one me events f a pass Table 75 : MI_PlatfmPass O N Association / MI_Event ( ) Event Identification The data dictionary table presented in this section is based on the cresponding Event Identification data dictionary table found in ISO :2009 (Section B.2.5.3). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule 135

138 MI_Event identification of a significant collection point within an operation condition Aggregated Class (MI_Operation) identifier event name number M 1 Class / MD_Identifier <<DataType>> ( ) trigger initiat of the event M 1 Class / TriggerCode <<CodeList>> ( ) See Table 3 (TriggerCode) context meaning of the event M 1 Class / ContextCode <<CodeList>> ( ) See Table 3 (ContextCode) sequence relative time dering of the event M 1 Class / SequenceCode <<CodeList>> ( ) See Table 3 (SequenceCode) time time the event occurred M 1 Class / DateTime (Annex B) role name: expectedobjective role name: relatedpass role name: relatedsens ive ives satisfied by an event pass during which an event occurs instrument instruments f which the event is meaningful O N Association / MI_Objective ( ) O 1 Association / MI_PlatfmPass ( ) O N Association / MI_Instrument (7.4,11.7) Table 76 : MI_Event Extent Extent UML This UML diagram is an SDSFIE-M -specific version of the cresponding Extent Package UML diagram (Figure A.15) found in ISO 19115:2003/C 1:2006. Classes, attributes and associations which extend the base standard have been added. F the iginal diagram consult ISO 19115:2003/C 1:2006. SDSFIE-M modifies the ISO model of EX_Extent as follows: Extended EX_GeographicExtent through the NMF_BoundingPoint subclass. This addresses the I&E community requirement f zero-dimension extents. 136

139 Extent Figure 25 : Extent The data dictionary table presented in this section is based on the cresponding Extent data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.3.1.1). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule EX_Extent infmation about hizontal, vertical, and tempal extent condition Class <<DataType>> description spatial and tempal extent f the referring C / geographicelement and tempalelement and verticalelement not documented? 1 CharacterString / 137

140 role name: geographicelement provides geographic component of the extent of the referring C / description and tempalelement and verticalelement not documented? N Association / EX_GeographicExtent <<Abstract>> ( ) role name: tempalelement provides tempal component of the extent of the referring C / description and geographicelement and verticalelement not documented? N Association / EX_TempalExtent ( ) role name: verticalelement provides vertical component of the extent of the referring C / description and geographicelement and tempalelement not documented? N Association / EX_VerticalExtent ( ) Table 77 : Extent Geographic Extent The data dictionary table presented in this section cresponds to the Geographic Extent data dictionary table (Section B.3.1.2) found in ISO 19115:2003/C 1:2006. The SDSFIE-M modifies the ISO data dictionary f EX_GeographicExtent by extending EX_GeographicExtent through the NMF_BoundingPoint subclass. This addresses the I&E community requirement f zero-dimension extents. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule EX_GeographicExtent extenttypecode EX_BoundingPolygon polygon EX_GeographicBoundingBox geographic area of the dataset indication of whether the bounding polygon encompasses an area covered by the data an area where data is not present boundary enclosing the dataset, expressed as the closed set of (x,y) codinates of the polygon (last point replicates first point) sets of points defining the bounding polygon geographic position of the dataset. NOTE This is only an approximate reference so specifying the codinate reference system is unnecessary condition Aggregated Class (EX_Extent and EX_SpatialTempalExtent) <<Abstract>> O 1 Boolean / 0 exclusion, 1 inclusion condition Specified Class (EX_GeographicExtent) M N Class / GM_Object (Annex B) condition Specified Class (EX_GeographicExtent) 138

141 westboundlongitude eastboundlongitude southboundlatitude nthboundlatitude EX_GeographicDescription geographicidentifier NMF_BoundingPoint point western-most codinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east) eastern-most codinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east) southern-most codinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive nth) nthern-most, codinate of the limit of the dataset extent expressed in latitude in decimal degrees (positive nth) description of the geographic area using identifiers identifier used to represent a geographic area point position of the resource point defining the location of the resource M 1 Decimal / -180,0 <= West Bounding Longitude Value <= 180,0 M 1 Decimal / -180,0 <= East Bounding Longitude Value <= 180,0 M 1 Decimal / -90,0 <= South Bounding Latitude Value <= 90,0; South Bounding Latitude Value <= Nth bounding Latitude Value M 1 Decimal / -90,0 <= Nth Bounding Latitude Value <= 90,0; Nth Bounding Latitude Value >= South Bounding Latitude Value condition Specified Class (EX_GeographicExtent) M 1 Class / MD_Identifier <<DataType>> ( ) condition Specified Class (EX_GeographicExtent) M N Class / GM_Point (Annex B) Tempal Extent Table 78 : Geographic Extent The data dictionary table presented in this section is based on the cresponding Tempal Extent data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.3.1.3). No profiling of this table has been perfmed to address I&E community requirements. 139

142 Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule EX_TempalExtent extent EX_SpatialTempalExtent role name: spatialextent time period covered by the content of the dataset date and time f the content of the dataset extent with respect to date/time and spatial boundaries spatial extent component of composite spatial and tempal extent con dition Aggregated Class (EX_Extent) M 1 Class / TM_Primitive (Annex B) con dition Specified Class (EX_TempalExtent) M N Association / EX_GeographicExtent <<Abstract>> ( ) Vertical Extent Table 79 : Tempal Extent The data dictionary table presented in this section is based on the cresponding Vertical Extent data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.3.1.4). No profiling of this table has been perfmed to address I&E community requirements. Name / role name Definition Obligation / Condition Max Occur Data type / Domain Business Rule EX_VerticalExtent vertical domain of dataset condition minimumvalue Value lowest vertical extent contained in the dataset highest vertical extent contained in the dataset M 1 Real M 1 Real Aggregated Class (EX_Extent) 140

143 role name: verticalcrs provides infmation about the vertical codinate reference system to which the and minimum elevation values are measured. The CRS identification includes unit of measure. M 1 Association / SC_CRS (ISO 19111) See Table 2 (CrsIdentifier) CrsIdentifier is a realization of the abstract functionality described by SC_CRS, and is the preferred realization. It is a Recommended Best Practice that when a Vertical CRS is used that it be in accdance with the Earth Gravity Model 1996 (EGM96), as specified in NIMA TR (3rd Edition, Amendment 1). This Vertical CRS is identified by one of two URIs depending on whether the codinate is a height depth value: e/ns/gsip/crs/egm96_h e/ns/gsip/crs/egm96_d Table 80 : Vertical Extent Citation Citation UML This UML diagram is an SDSFIE-M -specific version of the cresponding Citation Package UML diagram (Figure A.16) found in ISO 19115:2003/C 1:2006. The diagram has been modified by replacing some of the CodeLists. Figure This diagram defines metadata describing authitative reference infmation, including responsible party and contact infmation. 141

144 Citation Figure 26 : Citation and Responsible Party The data dictionary table presented in this section is based on the cresponding Citation data dictionary table found in ISO 19115:2003/C 1:2006 (Section B.3.2.1). The ). The data type of the presentationfm element has been modified to align with 142