Tiêu chuẩn iso 19115 1 2014

There are 13 packages that are used to define and provide the metadata that is defined in this part of ISO 19115: Metadata information, Identification information, Constraint information

Conformance requirements

Any metadata claiming conformance with this part of ISO 19115 shall pass the requirements described in the abstract test suite presented in Annex A.

Metadata shall be provided as specified in Clause 6 and Annex B.

If a discrepancy exists between the UML models provided in Clause 6 and Annex B, the UML models shall be considered authoritative.

User-defined metadata shall be defined and provided as specified in Annex C.

Any profile conforming to this part of ISO 19115 shall conform to the rules in C.6.

ISO 19115 outlines the metadata standards for data description, allowing datasets compliant with this version to coexist with those from earlier iterations of the standard Additionally, domain-specific or regional profiles play a crucial role in implementing these guidelines.

Copyright International Organization for Standardization

Provided by IHS under license with ISO Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs

Backward compatibility in services utilizing metadata defined by ISO 19115 requires clear conformance clauses These clauses must be specified in the relevant profiles or service specifications to ensure compatibility within their domain.

Abstract test suite

In conformance testing with the abstract test suite outlined in Annex A, it is essential to classify metadata classes and elements as mandatory, conditional, or optional according to the relevant profile specifications.

This document references essential documents that are crucial for its application For references with specific dates, only the cited edition is applicable In the case of undated references, the most recent edition of the referenced document, including any amendments, is relevant.

ISO 639 (all parts), Codes for the representation of names of languages

ISO 3166 (all parts), Codes for the representation of names of countries and their subdivisions

ISO 4217:2008, Codes for the representation of currencies and funds

ISO 8601:2004, Data elements and interchange formats — Information interchange — Representation of dates and times

ISO/TS 19103:2005, Geographic information — Conceptual schema language

ISO 19107:2003, Geographic information — Spatial schema

ISO 19108:2002, Geographic information — Temporal schema

ISO 19109:2005, Geographic information — Rules for application schema

ISO 19110:2005, Geographic information — Methodology for feature cataloguing

ISO 19111:2007, Geographic information — Spatial referencing by coordinates

ISO 19111-2:2009, Geographic information — Spatial referencing by coordinates — Part 2: Extension for parametric values

ISO 19112:2003, Geographic information — Spatial referencing by geographic identifiers

ISO 19157:2013, Geographic information ― Data Quality

IETF RFC 3986:2005, Uniform Resource Identifier (URI): Generic Syntax

For the purposes of this document, the terms and definitions given in ISO/TS 19103:2005 and the following apply.

4.1citation information object containing information that directs a reader’s or user’s attention from one resource

4.2data type specification of a value domain with operations (4.15) allowed on values in this domain

EXAMPLE Integer, Real, Boolean, String, Date, and GM_Point.

Note 1 to entry: A data type is identified by a term, e.g Integer.

4.3dataset identifiable collection of data

A dataset refers to a smaller collection of data that is constrained by factors like spatial extent or feature type, yet exists within a larger dataset It can range in size from a single feature or feature attribute to a more extensive collection Additionally, hardcopy maps or charts qualify as datasets.

4.4dataset series collection of datasets (4.3) sharing common characteristics

4.5feature abstraction of real world phenomena

4.6free text textual information that can be expressed in one or many languages

4.7grid network composed of two or more sets of curves in which the members of each set intersect the members of the other sets in an algorithmic way

4.8interface named set of operations (4.15) that characterize the behaviour of an entity

4.9lineage provenance, (4.16) source(s) and production process(es) used in producing a resource (4.17)

4.11metadata element discrete unit of metadata (4.10)

Note 1 to entry: Metadata elements are unique within a metadata class.

Note 2 to entry: Equivalent to an attribute and/or an association in UML terminology.

Note 3 to entry: Class attributes and relationships are referred to collectively as metadata elements.

4.12metadata entity set of metadata elements (4.11) describing the same aspect of data

Note 1 to entry: Can contain one or more metadata entities.

Note 2 to entry: Equivalent to a class in UML terminology.

4.13metadata section subset of metadata (4.10) which consists of a collection of related metadata entities (4.12) and metadata elements (4.11)

Note 1 to entry: Equivalent to a package in UML terminology.

4.14model abstraction of some aspects of reality

4.15operation specification of a transformation or query that an object may be called to execute

Note 1 to entry: An operation has a name and a list of parameters.

4.16provenance organization or individual that created, accumulated, maintained and used records

4.17resource identifiable asset or means that fulfils a requirement

EXAMPLE Dataset (4.3), datasetseries (4.4), service (4.18), document, initiative, software, person or organization.

4.18service distinct part of the functionality that is provided by an entity through interfaces (4.8)

Abbreviated terms

Abbreviated terms — Package

Abbreviated two-letter terms are used to identify the package containing a class, with these terms preceding class names and separated by an underscore The corresponding International Standard for these classes is specified in parentheses Below is a list of these abbreviated terms.

PT Polylinguistic Text (ISO/TS 19103)

SV Metadata for Services (ISO 19115-1)

Metadata for resources

ISO 19115 outlines the essential metadata needed to describe various resource types, including collections, datasets, software, hardware, services, and non-geographic datasets While metadata is mandatory for geographic datasets, it is optional for other resource types.

Metadata application information

Figure 1 presents a UML class diagram that outlines the classes of information relevant to metadata It indicates that resources (DS_Resource) and their aggregations must be associated with one or more Metadata sets (MD_Metadata) Metadata can also be linked to various features, including Feature Attributes, Feature Types, and Feature Property Types, as defined by ISO 19109 Specializations of resources include datasets (DS_Dataset), aggregates (DS_Aggregate), and services (SV_Service) Resource aggregations can be categorized as general associations (DS_OtherAggregate), dataset series (DS_Series), or specific activities (DS_Initiative) Notably, aggregates classified as series (DS_Series) share a common origin, such as datasets derived from the same sensor (DS_Sensor) or platform (DS_Platform) MD_Metadata is applicable to a diverse range of resources and services, as detailed in MD_ScopeCode (B.3.28), with the data dictionary for this model found in Table B.1.

Metadata Information::MD_Metadata ôabstractằ

Metadata fundamentals package and dependencies

The ISO geographic information standards are structured through integrated UML models, incorporating concepts from various related standards This section of ISO 19115 relies on multiple ISO/TC 211 packages, as depicted in Figure 2 Additionally, the fundamentals of metadata are established and supplied by these standards.

The ISO 19115 standard defines 13 essential packages for metadata information, including Identification, Constraint, Lineage, Content, Distribution, Reference system, Spatial representation, Portrayal catalogue, Metadata application, Application Schema, Metadata extension, and Service metadata information Additionally, there are four supporting packages: Citation, Responsible party, Language-character set localization, and Extent information While individual packages can be utilized independently to fulfill specific metadata requirements, it is mandatory to include both the Metadata and Identification information packages to create a complete metadata set, with supplementary packages added as needed.

ISO 19110 Methodology for feature cataloguing ISO 19112 Spatial referencing by geographic identiiers

ISO 19111 Spatial referencing by coordinates

ISO 19111-2 Spatial referencing by coordinates - Part 2: Extensions for parametric values

Figure 2 — Metadata fundamentals package and dependencies

Citation and responsible party, Metadata application information, Language-characterset

The four essential packages utilized for metadata provision include Citation and responsible party information, Language-characterset localisation information, Extent information, and Metadata application information, as illustrated in Figure 3.

Citation and responsible party information

Lineage information Portrayal catalogue information

Application schema information Metadata extension information

Service metadata information Metadata application information

Figure 3 — Citation and responsible party information, Language-characterset localisation information, Metadata application information, and Extent information package relationships

Resource metadata class diagrams by package

Metadata consists of multiple packages, each containing various classes and attributes The relationships among these packages and classes are illustrated through composition and aggregation symbols Collectively, class attributes and relationships are known as metadata elements Diagrams 6.5.2 to 6.6.3 present "views" of the overall abstract model for metadata, defining UML packages that include related classes, elements, data types, and code lists Related classes are depicted with suppressed attributes, and their complete specifications can be found in the corresponding package identified by a double colon (::) The comprehensive details of the metadata are outlined in the UML model diagrams and a corresponding data dictionary for each package in Annex B Abstract classes, which serve organizational purposes and are not directly implemented, are indicated by italicized names.

NOTE In some cases, optional classes can have mandatory elements; those elements become mandatory only if the optional element is used.

The MD_Metadata package outlines the schema for detailing comprehensive metadata regarding a resource, as well as the metadata pertaining to the metadata itself For further reference, the data dictionary corresponding to this diagram can be found in Table B.2.

Full metadata is provided by MD_Metadata and an aggregate of 12 additional metadata classes as specified in Figure 4 The DQ_DataQuality class is defined in ISO 19157.

Identiication information::MD_Identiication responsibilities Caution should be taken with regard to the use of m ultiple instances of

Reference system information:: MD_ReferenceSystem ôA bstractằ

Metadata extension information:: MD_MetadataExtensionInformation

+m etadataM aintenance 0 1 +applicationS chem aInfo 0 *

The MD_Metadata class contains attributes providing information about the metadata as specified in Figure 5 The data dictionary for this diagram is located in Table B.2. © ISO 2014 – All rights reserved 9

+ m etadataLinkage: CI_OnlineResource [0 *] constraints {defaultLocale docum ented if not deined by the encoding}

{defaultLocale.P T_Locale.characterE ncoding default value is UTF-8}

{count (M D_M etadata.parentM etadata) > 0 when there is an higher level object}

{count (M D_M etadata.m etadataS cope) > 0 if M D_M etadata.m etadataS cope.M D_M etadataS cope.resourceS cope not equal to "dataset"}

{count (M D_M etadata.dateInfo.CI_Date.dateType.CI_DateTypeCode="creation") > 0}

+ nam e: CharacterS tring [0 1] constraints {nam e is m andatory if resourceS cope not equal to "dataset"}

Figure 5 — Metadata on metadata classes

Identification information is essential for uniquely identifying a resource and can be categorized as either MD_DataIdentification or SV_ServiceIdentification This encompasses seven classes of metadata that facilitate resource identification, as illustrated in Figure 6, with the corresponding data dictionary available in Table B.3.

MD_Resolution + equivalentS cale: M D_RepresentativeFraction + distance: Distance

+ vertical: Distance + angularDistance: A ngle + levelOfDetail: CharacterS tring ôDataTypeằ

MD_RepresentativeFraction + denom inator: Integer

+ speci icUsage: CharacterS tring + usageDateTim e: TM _P rim itive [0 *]

+ userDeterm inedLim itations: CharacterS tring [0 1]

Common classes::MD_BrowseGraphic + ileNam e: CharacterS tring

MD_AssociatedResource + nam e: CI_Citation [0 1]

+ associationType: DS _A ssociationTypeCode + initiativeType: DS _InitiativeTypeCode [0 1] + m etadataReference: CI_Citation [0 1] constraints {count of (nam e + m etadataReference) > 0}

MD_Keywords + keyword: CharacterS tring [1 *]

+ thesaurusNam e: CI_Citation [0 1] constraints {W hen the resource described is a service, one instance of M D_K eyword shall refer to the service taxonom y de ined in IS O 19119}

+ citation: CI_Citation + abstract: CharacterS tring + purpose: CharacterS tring [0 1]

MD_DataIdenti ication + defaultLocale: P T_Locale [0 1]

+ supplem entalInform ation: CharacterS tring [0 1] constraints {defaultLocale docum ented if resource includes textual inform ation}

{defaultLocale.P T_Locale.characterE ncoding default value is UTF-8} Service metadata information::SV_ServiceIdenti ication

MD_KeywordClass + classNam e: CharacterS tring + conceptIdenti ier: URI [0 1] + ontology: CI_Citation

{(M D_M etadata.m etadataS cope.M D_M etadataS cope.resourceS cope)=’dataset’ im plies count (extent.geographicE lem ent.E X_GeographicB oundingB ox + extent.geographicE lem ent.E X_GeographicDescription) >= 1}

{(M D_M etadata.m etadataS cope.M D_S cope.resourceS cope) = (’dataset’ or ‘series’) im plies topicCategory is m andatory}

The article discusses various topics related to farming, biota, and environmental factors, including climatology, meteorology, and atmospheric conditions It emphasizes the importance of geoscientific information in understanding health, imagery, and base maps Additionally, it covers aspects of earth cover, military applications, inland waters, and the significance of location in planning and cadastre The content also touches on societal structures, transportation, utilities, communication, and the implications of extraterrestrial disasters.

+ grid + textTable + tin + stereoM odel + video ôCodeListằ

MD_ProgressCode + com pleted + historicalA rchive + obsolete + onGoing + planned + required + underDevelopm ent + inal

+ pending + retired + superseded + tentative + valid + accepted + notA ccepted + withdrawn + proposed + deprecated ôCodeListằ

+ place + stratum + tem poral + them e + dataCentre + featureType + instrum ent + platform + process + project + service + product + subTopicCategory + taxon ôCodeListằ

+ collection + exercise + experim ent + investigation + m ission + sensor + operation + platform + process + program + project + study + task + trial ôCodeListằ

+ largerW orkCitation + partOfS eam lessDatabase + stereoM ate

+ isCom posedOf + collectiveTitle + series + dependency + revisionOf

This package facilitates the provision of metadata related to the legal and security constraints on resources, including details about the resources themselves It encompasses MD_Constraints, which can be categorized as MD_LegalConstraints and/or MD_SecurityConstraints For a comprehensive overview, refer to Figure 8, with the corresponding data dictionary available in Table B.4.

+ patent + patentP ending + tradem ark + licence + intellectualP ropertyRights + restricted

+ otherRestrictions + unrestricted + licenceUnrestricted + licenceE ndUser + licenceDistributor + private

+ statutory + conidential + sensitiveB utUnclassiied + in-conidence

MD_Constraints + useLim itation: CharacterS tring [0 *]

+ responsibleP arty: CI_Responsibility [0 * ôabstractằ

Identiication information::MD_Identiication ôCodeListằ

+ restricted + conidential + secret + topS ecret + sensitiveB utUnclassiied + forOficialUseOnly + protected + lim itedDistribution

+ classiication: M D_ClassiicationCode + userNote: CharacterS tring [0 1]

+ classiicationS ystem : CharacterS tring [0 1] + handlingDescription: CharacterS tring [0 1]

MD_Releasability + addressee: CI_Responsibility [0 *]

+ dissem inationConstraints: M D_RestrictionCode [0 *] constraints {count (addressee + statem ent) > 0}

{If M D_LegalConstraints used then count of (accessConstraints + useConstraints + otherConstraints + useLim itation + releasability) > 0}

{otherConstraints: only docum ented if accessConstraints or useConstraints = “otherRestrictions”}

The package facilitates the provision of metadata related to the sources and production processes involved in resource creation LI_Lineage comprises two classes: LI_Source and LI_ProcessStep, as illustrated in Figure 9 The classes with the "LE" suffix are defined in ISO 19115-2, included here for reference to offer a comprehensive understanding of the lineage model For detailed information, the data dictionary corresponding to this diagram can be found in Table B.5.

LI_Source + description: CharacterS tring [0 1]

+ scope: M D_S cope [0 1] constraints {"description" is m andatory if "scope" is not docum ented}

{"scope" is m andatory if "description" is not docum ented}

LI_ProcessStep + description: CharacterS tring + rationale: CharacterS tring [0 1]

LI_Lineage + statem ent: CharacterS tring [0 1]

+ additionalDocum entation: CI_Citation [0 *] constraints MD_Metadata

LE_Processing + identiier: M D_Identiier + softwareReference: CI_Citation [0 1]

+ runTim eP aram eters: CharacterS tring [0 1]

LE_ProcessStepReport + nam e: CharacterS tring + description: CharacterS tring [0 1]

LE_Algorithm + citation: CI_Citation + description: CharacterS tring ôUnionằ

From IS O 19115-2 shown for inform ative purposes only

{”source” role is m andatory if LI_Lineage.statem ent and

“processS tep” role are not docum ented}

{”processS tep” role is m andatory if LI_Lineage.statem ent and “source” role are not docum ented}

This package facilitates the provision of metadata concerning the maintenance scope and frequency for a resource, encapsulated within the MD_MaintenanceInformation class The complete package is illustrated in Figure 10, with the corresponding data dictionary available in Table B.6.

MD_MaintenanceInformation + m aintenanceA ndUpdateFrequency: M D_M aintenanceFrequencyCode [0 1]

+ contact: CI_Responsibility [0 *] constraints {count (m aintenanceA ndUpdateFrequency + userDeinedM aintenanceFrequency) >0} ôabstractằ

Metadata Information::MD_Metadata ôCodeListằ

+ continual + daily + weekly + fortnightly + m onthly + quarterly + biannually + annually + asNeeded + irregular + notP lanned + unknown + periodic + sem im onthly + biennially

6.5.7 Spatial representation information (MD_SpatialRepresentation)

This package provides metadata that identifies the spatial primitives utilized by a resource and the methods for modeling real-world phenomena within a digital information system It includes the MD_SpatialRepresentation, which can be defined as either MD_VectorSpatialRepresentation or MD_GridSpatialRepresentation The MD_GridSpatialRepresentation can be further categorized into MD_Georectified or MD_Georeferencable For a comprehensive overview, refer to Figure 11, with the corresponding data dictionary available in Table B.7.

MD_GeometricObjects + geom etricObjectType: M D_Geom etricObjectTypeCode + geom etricObjectCount: Integer [0 1]

+ area + voxel + stratum ôenum erationằ

MD_PixelOrientationCode centre lowerLeft lowerRight upperRight upperLeft ôCodeListằ

+ row + colum n + vertical + track + crossTrack + line + sam ple + tim e

MD_Dimension + dim ensionNam e: M D_Dim ensionNam eTypeCode + dim ensionS ize: Integer

MD_Georeferenceable + controlP ointA vailability: B oolean + orientationP aram eterA vailability: B oolean + orientationP aram eterDescription: CharacterS tring [0 1] + georeferencedP aram eters: Record

+ param eterCitation: CI_Citation [0 *] ôA bstractằ

Metadata Information::MD_Metadata ôCodeListằ

+ com posite + curve + point + solid + surface

MD_GridSpatialRepresentation + num berOfDim ensions: Integer + axisDim ensionP roperties: M D_Dim ension [0 *]

+ cellGeom etry: M D_CellGeom etryCode + transform ationP aram eterA vailability: B oolean

+ transform ationDim ensionDescription: CharacterS tring [0 1]

+ transform ationDim ensionM apping: CharacterS tring [0 2]

Figure 11 — Spatial representation information classes

6.5.8 Reference system information (MD_ReferenceSystem)

This package supports the metadata identifying the spatial, temporal and parametric reference system(s) used by a resource in one class, MD_ReferenceSystem The full package is specified in Figure

12 The data dictionary for this diagram is located in Table B.8.

MD_ReferenceSystem + referenceS ystem Identi ier: M D_Identi ier [0 1]

+ referenceS ystem Type: M D_ReferenceS ystem TypeCode [0 1] responsibilities Refer to IS O 19111 and IS O 19111-2 when coordinate reference system inform ation is not given through referenceS ystem Identi ier ôCodeListằ

MD_ReferenceSystemTypeCode + com poundE ngineeringP aram etric + com poundE ngineeringP aram etricTem poral + com poundE ngineeringTem poral

+ com poundE ngineeringV ertical + com poundE ngineeringV erticalTem poral + com poundGeographic2DP aram etric + com poundGeographic2DP aram etricTem poral + com poundGeographic2DTem poral

The article discusses various compound geographic models, including Compound Geographic 2D Vertical, Compound Geographic 2D Vertical Temporal, and Compound Geographic 3D Temporal It also covers Compound Projected 2D Parametric, Compound Projected 2D Parametric Temporal, and Compound Projected Temporal These models are essential for understanding spatial data and temporal changes in geographic information systems.

+ com poundP rojectedV ertical + com poundP rojectedV erticalTem poral + engineering

+ engineeringDesign + engineeringIm age + geodeticGeocentric + geodeticGeographic2D + geodeticGeographic3D + geographicIdenti ier + linear

+ param etric + projected + tem poral + vertical

Figure 12 — Reference system information classes

This package enables the identification of resource content through metadata by citing the feature catalogue (MD_FeatureCatalogueDescription), incorporating the feature catalogue as defined in ISO 19110 (MD_FeatureCatalogue), or describing coverage resources (MD_CoverageDescription), which can also be specified as MD_ImageDescription The complete package is illustrated in Figure 13, with the corresponding data dictionary available in Table B.9.

+ illum inationE levationA ngle: Real [0 1]

+ illum inationA zim uthA ngle: Real [0 1]

+ cam eraCalibrationInform ationA vailability: B oolean [0 1]

+ film DistortionInform ationA vailability: B oolean [0 1]

MD_RangeDimension + sequenceIdentifier: M em berNam e [0 1]

+ toneGradation: Integer [0 1] constraints {if count (boundMax + boundMin) >0 then boundUnits is mandatory} ôCodeListằ

+ rain + sem iDarkness + shadow + snow + terrainM asking ôCodeListằ

+ featureCatalogueCitation: CI_Citation [0 *] constraints {if Feature Catalogue not included with resource and

M D_FeatureCatalogue not provided then featureCatalogueCitation > 0}

MD_SampleDimension + m axV alue: Real [0 1]

+ bitsP erV alue: Integer [0 1] constraints {if count (m axV alue + m inV alue + m eanV alue) > 0 then units is m andatory}

MD_FeatureCatalogue + featureCatalogue: FC_FeatureCatalogue [1 *]

MD_FeatureTypeInfo + featureTypeNam e: GenericNam e + featureInstanceCount: Integer [0 1]

+ attributeGroup 0 * responsibilities {minValue, maxValue and units must have units of length}

6.5.10 Portrayal catalogue information (MD_PortrayalCatalogueReference)

This package includes metadata that identifies the portrayal catalogue utilized, which outlines how the resource is visually represented for human viewing The complete package is detailed in Figure 14, with the corresponding data dictionary available in Table B.10.

Figure 14 — Portrayal catalogue information classes

The MD_Distribution package provides essential metadata regarding the distributor and options for acquiring a resource It consists of three additional classes, as illustrated in Figure 15, with the corresponding data dictionary available in Table B.11.

MD_Format + form atS peciicationCitation: CI_Citation + am endm entNum ber: CharacterS tring [0 1]

MD_Distributor + distributorContact: CI_Responsibility

MD_Distribution + description: CharacterS tring [0 1]

MD_DigitalTransferOptions + unitsOfDistribution: CharacterS tring [0 1]

+ distributionForm at: M D_Form at [0 *] responsibilities units of distribution applies to both onLine and offLine distributions

MD_StandardOrderProcess + fees: CharacterS tring [0 1]

+ tar + highS ierra + iso9660 + iso9660RockRidge + iso9660A ppleHFS + udf ôDataTypeằ

MD_Medium + nam e: CI_Citation [0 1]

+ m edium Form at: M D_M edium Form atCode [0 *]

+ identiier: M D_Identiier [0 1] constraints {if density used then count (densityUnits) > 0}

6.5.12 Metadata extension information (MD_MetadataExtensionInformation)

This package supports the provision of information about user specified metadata extensions MD_ MetadataExtensionInformation is an aggregate of one other class The full package is specified in Figure

16 The data dictionary for this diagram is located in Table B.12.

+ codelist + enum eration + codelistE lem ent + abstractClass + aggregateClass + speciiedClass + datatypeClass + interfaceClass + unionClass + m etaClass + typeClass + characterS tring + integer + association ôenum erationằ

MD_ObligationCode m andatory optional conditional

MD_MetadataExtensionInformation + extensionOnLineResource: CI_OnlineResource [0 *]

MD_ExtendedElementInformation constraints {if dataType notE qual codelist, enum eration, or codelistE lem ent, then obligation, m axim um Occurence and dom ainV alue are m andatory}

{if obligation = conditional then condition is m andatory}

{if dataType = codelistE lem ent, enum eration, or codelist then code is m andatory}

{if dataType = codelistE lem ent, enum eration, or codelist then conceptNam e is m andatory}

{if dataType = codelist, enum eration, or codelistE lem ent then nam e is not used}

+ nam e: CharacterS tring + deinition: CharacterS tring + obligation: M D_ObligationCode [0 1]

+ dataType: M D_DatatypeCode + m axim um Occurrence: CharacterS tring [0 1]

+ dom ainV alue: CharacterS tring [0 1]

+ rule: CharacterS tring + rationale: CharacterS tring [0 1]

Figure 16 — Metadata extension information classes

6.5.13 Application schema information (MD_ApplicationSchemaInformation)

This package facilitates the provision of metadata that outlines the application schema, which defines and reveals the structure of a resource The application schema serves as the model or data dictionary representing the resource, as illustrated in Figure 17 For detailed information, refer to the data dictionary in Table B.13.

MD_ApplicationSchemaInformation + nam e: CI_Citation

+ schem aLanguage: CharacterS tring + constraintLanguage: CharacterS tring + schem aA scii: CharacterS tring [0 1]

+ softwareDevelopm entFileForm at: CharacterS tring [0 1]

Figure 17 — Application schema information class

This package facilitates the delivery of service metadata, which is organized into three primary categories The first category, the SV_ServiceIdentification class, offers a general overview of the service's functionality The other two categories detail the operations available through the service (SV_OperationMetadata) and the data it provides (MD_DataIdentification).

SV_ServiceIdentification is associated with several instances of SV_OperationMetadata through an aggregation relationship Although the service structure could be more complex than this simple aggregation, further details about services that aggregate other services are unnecessary in a service metadata record.

A service instance may be either tightly coupled with a dataset instance, loosely coupled (i.e non associated with specific dataset instances), or it may be “mixed coupled.”

Extent, Citation and Common information packages

The datatype in this package aggregates metadata elements that describe the spatial and temporal extent of various resources, objects, events, or phenomena The EX_Extent class provides details on geographic (EX_GeographicExtent), temporal (EX_TemporalExtent), and vertical (EX_VerticalExtent) extents Additionally, EX_GeographicExtent can be further subclassed into EX_BoundingPolygon, EX_GeographicBoundingBox, and EX_GeographicDescription.

(EX_SpatialTemporalExtent) is an aggregate of EX_GeographicExtent EX_SpatialTemporalExtent is a subclass of EX_TemporalExtent The full package is specified in Figure 19.

The EX_Extent class has three optional roles named “geographicElement”, “temporalElement”, and

“verticalElement” and an element called “description” At least one of the four shall be used The data dictionary for this diagram is located in Table B.15.

EX_VerticalExtent + m inim um V alue: Real + m axim um V alue: Real constraints {count(verticalCRS + verticalCRS Id) >0)} ôDataTypeằ

EX_Extent + description: CharacterS tring [0 1] constraints {count (description + geographicE lem ent + tem poralE lem ent + verticalE lem ent) >0} ôA bstractằ

EX_TemporalExtent + extent: TM _P rim itive

EX_SpatialTemporalExtent + verticalE xtent: E X_V erticalE xtent [0 1]

EX_GeographicBoundingBox + westB oundLongitude: Decim al + eastB oundLongitude: Decim al + southB oundLatitude: Decim al + northB oundLatitude: Decim al

Reference system information::MD_ReferenceSystem ôtypeằ

Coordinate Reference Systems:: SC_VerticalCRS

+spatialE xtent 1 * +tem poralE lem ent 0 *

6.6.2 Citation, responsibility and party information (CI_Citation, CI_Responsibility, and CI_Par- ty) classes

This package offers a standardized approach for resource citation and identifies the responsible party Citations are made using CI_Citation, while the responsible party is denoted by CI_Responsibility, which can be utilized independently of CI_Citation CI_Responsibility encompasses one or more parties, represented as CI_Party, which can include either CI_Individual or CI_Organisation For a complete overview, refer to Figure 20, with the corresponding data dictionary available in Table B.16.

CI_Contact + phone: CI_Telephone [0 *]

CI_Citation + title: CharacterS tring + alternateTitle: CharacterS tring [0 *]

CI_Address + deliveryP oint: CharacterS tring [0 *]

+ adm inistrativeA rea: CharacterS tring [0 1]

+ electronicM ailA ddress: CharacterS tring [0 *] ôabstractằ

+ role: CI_RoleCode + extent: E X_E xtent [0 *]

CI_Individual + positionNam e: CharacterS tring [0 1] constraints {count (nam e + positionNam e) > 0}

CI_Organisation + logo: M D_B rowseGraphic [0 *] constraints {count (nam e + logo) > 0}

Figure 20 — Citation and responsible party information classes

6.6.3 Citation, responsibility and party information (CI_Citation, CI_Responsibility, and CI_Par- ty) and codelists

The classes and codelists used by Citation and responsible party information are specified in Figure 21 The data dictionary for this diagram is located in Table B.16. © ISO 2014 – All rights reserved 25

CI_Date + date: DateTim e + dateType: CI_DateTypeCode ôCodeListằ

CI_DateTypeCode + creation + publication + revision + expiry + lastUpdate + lastRevision + nextUpdate + unavailable + inForce + adopted + deprecated + superseded + validityB egins + validityE xpires + released + distribution ôCodeListằ

+ inform ation + of lineA ccess + order + search + com pleteM etadata + browseGraphic + upload + em ailS ervice + browsing + ileA ccess ôDataTypeằ

CI_OnlineResource + linkage: CharacterS tring + protocol: CharacterS tring [0 1]

+ applicationP ro ile: CharacterS tring [0 1]

The CI_PresentationFormCode encompasses various formats for presenting information, including both digital and hardcopy options These formats include documents, images, maps, models, profiles, tables, videos, audio, and multimedia, as well as physical objects and diagrams Each category is available in both digital and hardcopy forms, ensuring versatility in how content is delivered and accessed.

CI_RoleCode + resourceP rovider + custodian + owner + user + distributor + originator + pointOfContact + principalInvestigator + processor

+ publisher + author + sponsor + coA uthor + collaborator + editor + m ediator + rightsHolder + contributor + funder + stakeholder ôDataTypeằ

CI_Telephone + num ber: CharacterS tring + num berType: CI_TelephoneTypeCode [0 1] ôDataTypeằ

CI_Series + nam e: CharacterS tring [0 1]

Figure 21 — Citation and responsible party information codelists

This package contains classes that are commonly used by the other packages in all parts of ISO 19115

It provides the MD_Identifier, URI, MD_Scope, MD_BrowseGraphic and related classes The package is specified in Figure 22 The data dictionary for this diagram is located in Table B.17.

MD_Identiier + authority: CI_Citation [0 1]

+ code: CharacterS tring + codeS pace: CharacterS tring [0 1]

MD_Scope + level: M D_S copeCode + extent: E X_E xtent [0 *]

MD_ScopeCode + attribute + attributeType + collectionHardware + collectionS ession + dataset

+ series + nonGeographicDataset + dim ensionGroup + feature

+ featureType + propertyType + ieldS ession + software + service + m odel + tile + m etadata + initiative + sam ple + docum ent + repository + aggregate + product + collection + coverage + application ôUnionằ

MD_ScopeDescription + attributes: S et

+ dataset: CharacterS tring + other: CharacterS tring ôtypeằ

MD_BrowseGraphic + ileNam e: CharacterS tring + ileDescription: CharacterS tring [0 1]

Multilingual support for free text fields

ISO 19115 allows for a free text element to contain multiple instances of information in various languages If the language differs from the dataset's defined language, it can be identified, along with an optional attribute for the language variant used in a specific country and the character set if it differs from the default The PT_FreeText class can be utilized wherever "free text" is specified, while a locale (PT_Locale) combines language, country, and character encoding for localized character strings LocalisedCharacterString is a subtype of CharacterString, expressed in a single locale A Free Text instance is a CharacterString with a value in a default language and character set, as defined in MD_Metadata For a multi-lingual example, refer to Annex D, and the PT_Locale schema is illustrated in Figure 23, with the data dictionary available in Table B.18.2.

PT_Locale + language: LanguageCode + country: CountryCode [0 1]

+ characterE ncoding: M D_CharacterS etCode ôtypeằ

LanguageCode responsibilities Use IS O 639-2 Codes for the representation of nam es of languages ôCodeListằ

MD_CharacterSetCode responsibilities use IA NA Character S et register: http://www.iana.org/assignm ents/character-sets ôCodeListằ

CountryCode responsibilities use IS O 3166 Codes for the representation of nam es of countries and their subdivisions P art 1: Country codes or equivalent

Free text instances consist of default character strings and their translations in various locales through localized strings, which are distributed across multilingual metadata sets A more effective approach to managing multilingual information is to group localized strings by their respective locales To facilitate this management, ISO 19115 introduces the concept of a locale container (PT_LocaleContainer), which aggregates localized strings associated with a specific locale While there is no direct relationship between a locale container and a metadata set, a locale container can encompass localized strings from a metadata set.

The translation container concept is essential for the XML implementation of ISO 19115 and other related components, but it is also relevant for various other implementations An XML file is limited to supporting data in a single character set, typically specified in the XML File Header.

Having all the localised strings stored in a single XML File would limit the use of a single character set such as UTF-8 In order to avoid this:

— The LocalisedCharacterString class is implemented specifically to allow a by reference containment of the PT_FreeText.textGroup property.

— The PT_LocaleContainer is the recommended root element to be instantiated in a dedicated XML File.

Localized strings for a specific locale can be stored in an XML file, known as a locale container, and accessed through the PT_FreeText.textGroup property instances The Translation container is illustrated in Figure 24, with the corresponding data dictionary available in section B.2.

PT_LocaleContainer + description: CharacterS tring + locale: P T_Locale

Figure 24 — Translation containerMetadata extensions and profiles

Annex C provides guidance on extending metadata and rules for creating profiles to better serve special user needs.

Implementation examples

Annex D illustrates the application of ISO 19115 for geographic datasets, showcasing an example of extended metadata elements tailored by a specific information community.

Metadata implementation

Annex E provides an overview of methods and ideas for the implementation and management of metadata for the purposes of search and retrieval, metadata exchange, and presentation.

Discovery metadata

Annex F provides a list of metadata elements that facilitate the discovery of geospatial resources.

Revisions

Metadata outlined in Clause 6 and Annex B must adhere to the criteria set forth in this abstract test suite, which is applicable to any profile derived from ISO 19115 Additionally, user-defined metadata should be established and supplied according to Annex C, ensuring compliance with the requirements detailed in section A.3.

The completeness test aims to verify compliance by ensuring that all mandatory metadata packages, classes, and elements are included as specified under the defined conditions.

Many elements classified as mandatory are found within optional classes, becoming mandatory only when their containing class is utilized A comparison test must be conducted between this section of ISO 19115 and the subject metadata set to verify the presence of all mandatory metadata defined in Clause 6 and Annex B Additionally, a comparison test is required to check for the presence of all conditional metadata elements in Clause 6 and Annex B, provided the relevant conditions apply For reference, see Clause 6 and Annex B, with the test type being basic.

NOTE 2 The test cases in A.2.2 to A.2.5, A.3 and A.4 apply at all levels of obligation – mandatory, conditional, and optional.

The Maximum Occurrence Test aims to verify that each metadata element does not exceed the specified number of occurrences outlined in ISO 19115 This is achieved by analyzing a subject metadata set to count the occurrences of each metadata package, class, and element, and comparing these counts with the "Maximum Occurrences" attribute defined in Clause 6 and Annex B This test is categorized as a Basic Test.

A.2.3 Test case identifier: Data type test a) Test Purpose: to determine if each metadata element within a subject metadata set uses the specified data type.

`,`,`,,,`,``,`,,,,,,``,,````,-`-`,,`,,`,`,,` - b) Test Method: the value of each provided metadata element is tested to ensure its data type adheres to the data type specified. c) Reference: Clause 6 and Annex B. d) Test Type: Basic.

The test case identifier A.2.4 focuses on domain testing, aiming to verify that each metadata element in a subject metadata set adheres to the defined domain specifications The testing method involves evaluating the values of each metadata element to confirm their compliance with the specified domain This test is categorized as basic and is referenced in Clause 6 and Annex B.

The test case identifier for the schema test aims to verify if a subject metadata set adheres to the schema outlined in ISO 19115 The testing method involves examining each metadata element to confirm its inclusion within the designated metadata class This test is referenced in Clause 6 and Annex B, and it is classified as a basic test type.

A.3 User-defined extension metadata test suite

The Exclusiveness Test aims to ensure that every user-defined metadata package, class, and element is unique and not previously defined in ISO 19115 This is achieved by testing each user-defined metadata class and element for uniqueness The test is referenced in Clause 6 and Annex B, and it is categorized as a Basic test type.

The test case identifier aims to verify that user-defined metadata classes and elements are defined according to ISO 19115 standards The testing method involves checking each user-defined metadata class and element to confirm that all attributes are properly defined This test is categorized as a basic type, with references available in section C.3.

The test case identifier A.3.3 focuses on standard metadata testing, aiming to ensure that user-defined metadata within a metadata set meets the same requirements as specified in ISO 19115.

`,`,`,,,`,``,`,,,,,,``,,````,-`-`,,`,,`,`,,` - b) Test Method: all user-defined metadata in a subject metadata set is tested in accordance with A.2 of this part of ISO 19115. c) Reference: 2.3. d) Test Type: Basic.

The test case identifier for metadata profiles aims to ensure compliance with the rules outlined in ISO 19115 The testing method involves applying the procedures specified in sections A.2 and A.3 of the same standard This test is categorized as a basic type and references section 2.2 for further details.

Data dictionary for geographic metadata

This data dictionary outlines the metadata characteristics defined in sections 6.2 to 6.7, organized hierarchically to illustrate relationships among the information It is divided into sections that correspond to the UML model package diagrams, with expanded table titles reflecting class specifications Each model diagram from sections 6.2, 6.5, 6.6, and 6.7 includes a set of tables in the data dictionary, where each UML model class and its subclasses correspond to a table The classes and metadata elements are defined by six attributes, detailed in sections B.1.2 to B.1.7.

Metadata class names begin with an uppercase letter and do not contain spaces; instead, they concatenate multiple words with each new subword starting with a capital letter (e.g., XnnnYmmm) These names are unique within the data dictionary of ISO 19115 In contrast, metadata element names are unique only within their respective metadata class, and their uniqueness within an application is achieved through the combination of the metadata class and element names (e.g., MD_Metadata.characterSet) Additionally, role names identify metadata abstract model associations and are prefixed with "Role name:" to differentiate them from other metadata elements.

The metadata class/element description.

This descriptor indicates the documentation requirements for a metadata class or element, specifying whether it must always be documented (M for mandatory), may be documented under certain conditions (C for conditional), or is documented at the discretion of the user (O for optional).

The metadata class or metadata element shall be documented.

A condition is defined for machine processing, requiring at least one mandatory metadata class or element The term 'conditional' refers to one of three possible scenarios.

— Expressing a choice between two or more options At least one option is mandatory and must be documented.

When documenting a metadata element, it is essential to include a specific value for another metadata element in plain text for human readability, such as "C / not defined by encoding and UTF-8 not used?" in Table B.2, row 17 If this condition is met, the corresponding metadata class or element becomes mandatory.

Tiêu đề	Geographic Information — Metadata — Part 1: Fundamentals
Trường học	University of Alberta
Thể loại	tiêu chuẩn
Năm xuất bản	2014
Thành phố	Switzerland

Định dạng
Số trang	176
Dung lượng	3,4 MB