NorwegianProfile of ISO 19115 Metadata – Experience and – Experience andimplementation Metadata Norsk profil av ISO 19115 Metadata versjon 1.0 ISO TC 211/

Presentasjon om: "NorwegianProfile of ISO 19115 Metadata – Experience and – Experience andimplementation Metadata Norsk profil av ISO 19115 Metadata versjon 1.0 ISO TC 211/"— Utskrift av presentasjonen:

1 NorwegianProfile of ISO 19115 Metadata – Experience and – Experience andimplementation Metadata Norsk profil av ISO 19115 Metadata versjon 1.0 ISO TC 211/ Date: 2000-12-12 ISO/DIS 19115 ISO TC 211/WG 3 Secretariat: NSF Geographic information — Metadata Document type: International Standard Document subtype: Document stage: (40) Enquiry Document language: E C:\WINDOWS\Desktop\1911 5\ISO 19115 (E).doc STD Version 1.0 Information géographique — Métadonnées Warning This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. ISO

2 The content of this presentation   The Evolution of Metadata in the Norwegian standard   The Norwegian Metadata project   Procedure of making the profile   Table of content   Some challenges   Conclusions To give you our experiences concerning a translation of 19115 metadata standard and producing a profile.

3 SOSI (early 90th) The SOSI standard Feature 1Feature n Metadata Dataset 1 In the dataset Feature 2 The Evolution og Metadata in the Norwegian standard

4 Dataset Objekt 2-1 Objekt 2-2Objekt 2-n Metadata Subset 2 Objekt 1-1 Objekt 1-2Objekt -1-n Metadata Subset 1 more metadata elements in versjon 2.1 (1996).GEOSYS..GEO-DATUM..GEO-PROJ..GEO-SONE..GEOKOORD.VERT-INT..H-REF-INT H2..D-REF-INT H2.VERT-DELTA *...V-DELTA-MIN H2...V-DELTA-MAX H2 with extensions from..ADM_OPPL...ORG_NAVN...ORG_KORTNAVN...ORG_ADR...KONTAKTPERSON...KONTAKTROLLE...KONTAKTADRESSE...UNDERLEVERANDØR...RESTRIKSJONER...OPPHAVSRETT...PRISPOLITIKK...UTTAKSDATO.DATASET_IDENT..DATASET_NAVN..DATASET_ID.DATASET_OVERSIKT..SAMMENDRAG..FORMÅL..BRUK..INKL_DATASET..SUPPL_DATASET..AVLEDET_DATASET..PROD_DATO..OPPDATERT..TILLATELSES_NR..TILLATELSES_INNEH..METADATAKILDE...METADATA_DATO...METADATA_REF..OVERORD_KVALITET...PROSESS_HISTORIE...SAML_TEMA_NØY...SAML_FULLST...SAML_LOG_KONS...ELDSTE_DATASET...YNGSTE_DATASET ISO Metadata elements in versjon 3.0 (1998) The Evolution og Metadata in the Norwegian standard

5 0 50 100 150 200 250 300 350 400 450 SOSI 1.4 SOSI 2.0SOSI 2.1SOSI 2.2 SOSI 2.21 SOSI 3.0 CEN 12657 ISO 19115 No. of elements No. of Metadata elements - Implemented in SOSI The Evolution og Metadata in the Norwegian standard - SOSI 1999 SOSI 3.2 1996 1997 1994 2000 2001 SOSI 3.1 1998 SOSI 3.3 Almost no implementation after 1998 due to the evolution of the ISO standard 2002?

6 The work on a Norwegian metadata profile started in 2. febr. 2001 and the first version was delivered 1. June 2001 5 two-days Workshops, and a lot of homework did the job! The progress could be followed on the web

7 Organisations attending the work on a Norwegian Metadata Profile Norwegian geological survey - projectmanager Norwegian mapping authority Norwegian polar institute Norwegian military survey Directorate for cultural heritage Directorate of Nature Management Coastal directorate Local Road Authority Oslo municipality Ski municipality Norconsult Inf. AS GEODATA AS Sysdeco MapMill AS Sintef. Telcommunication SINTEF ( 10 – 17 participants on each meeting)

8 It was decided that most of the 19115 Metadata document should be translated into Norwegian The Norwegian profile of ISO 19115 - Metadata standard All the Comprehensive dataset metadata profile from ISO 19115 Instantiation of rules for extension No extended Metadata so far Whole of the Core metadata

9 Table of content - Norwegian profile 1Foreword 2History 3Change log 4Introduction 5Scope 6Conformance 7References 8Definitions 9Graphic notation 10Metadata requirement 11Metadata UML-models (annex A) 12 Metadata components (annex B) 12 Metadata package data dictionaries 12 Metadata entity set information 12 Data type information 12 Code Lists and enumeration 13Implementation 14Extensions (methods) 15Hierarchic levels 16Examples

10 • Technical decisions: • Long names must be translated and used in UML • Long names will be made unique and used as SOSI-tags • English short names and data types will not be translated • English short names will be used in XML • Keep the English text for comparison Annex B

11 Example from Annex B B.2.1Informasjon om Metadataobjekttypene - (Metadata entity set information) Name / Role name Navn Short Name Kortna vn (engelsk, lik ISO- standarden ) Definition Definisjon Oblig ation / Condi tion Påkr evet/o psjon Maxim um occurr ence Maks antall foreko mster Data type Datatype Domain Domene MD_Metadata MD_MetadataInfo Metadat a root entity which defines metadata about a resource or resources Informasjon om metadata som beskriver datasett, datatjenester og lignende. M P M P 1Class Lines 2-22 Kent bruker linjenummerene ved overføring til UML-modellene fileIdentifier metadataIdentifika tor mdFileI D unique identifier for this metadata file Unik identifikator på en metadata-fil som bl.a. beskriver datasett/tjenester og instanser av objekttyper. O 1Character String Free text Fri tekst language metadataSpråk mdLanglanguage used for documenting metadata Språket metadataene er beskrevet i. C / not define d by encod ing? 1Character String ISO 639-2, other parts may be used ISO 639-2, andre deler kan også benyttes.

12 Table 3 — Core metadata for geographic datasets Dataset title (M) (MD_Metadata > MD_Identification.citation > CI_Citation.title) Spatial representation type (O) (MD_Metadata > MD_DataIdentification.spatialRepresentationType) Dataset reference date (M) (MD_Metadata > MD_Identification.citation > CI_Citation > CI_Date.date and CI_dateType) Reference system (O) (MD_Metadata > MD_ReferenceSystem) Dataset responsible party (O) (MD_Metadata > MD_Identification.pointOfContact > CI_ResponsibleParty) Lineage statement (O) (MD_Metadata > DQ_DataQuality > LI_Lineage.statement) Geographic location of the dataset (by four coordinates or by geographic identifier) (C) (MD_Metadata > MD_DataIdentification.geographicBox or MD_DataIdentification.geogrphicIdentifier) On-line resource (O) (MD_Metadata > MD_Distribution > MD_DigitalTransferOption.onLine > CI_OnlineResource)

13 Table 3 — Core metadata for geographic datasets - improved Dataset reference date (M) (MD_Metadata > MD_Identification.citation > CI_Citation > CI_Date.date and CI_dateType) 362 /394 dataReferanseDato/ referanseDato resRef Date/r efdate Dato som refererer deg til det refererte datasett eller tjeneste. Muliggjør bruk av flere ulike datoer. P NrNavnKort navn DefinisjonPåkrev d /opsjon

14 Geographic location of the dataset (by four coordinates or by geographic identifier) (C) (MD_Metadata > MD_DataIdentification.geographicBox or MD_DataIdentification.geogrphicIdentifier) 42 geografiskOmrådeBok s geoBoxMinimum rektangel som avgenser datasettet geografisk. Utløser egenskapene 343-346 fra objektklassen EX_GeografiskAvrensingBok s B / metadataNi vå er lik "datasett" og geografiskO mrådeBeskr ivelse ikke dokumentert ? 344 vestligsteKoordinat westBLVestligste koordinat som avgrenser datasettet. Uttrykt i lengdegrad med 1 desimal (positiv mot øst). P 345 østligsteKoordinat eastBLØstligste koordinat som avgrenser datasettet. Uttrykt i lengdegrad med 1 desimal (positiv mot øst). P 346 sørligsteKoordinat southBLSydligste koordinat som avgrenser datasettet. Uttrykt i breddegrad med 1 desimal (positiv mot nord). P 347 nordligsteKoordinat northBLNordligste koordinat som avgrenser datasettet. Uttrykt i breddegrad med 1 desimal (positiv mot nord). NrNavnKort navn Definisjonobligat ion Table 3 — Core metadata for geographic datasets

15 Main challenges geoscientificInformation geovitenskapligInfo information pertaining to earth sciences Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structurel and origin of the earth’s rocks, risks of earthquakes volcanic activity, landslides, gravity information, soils, permafrost, hydrogelogy, erosion Vitenskaper som omhandler sammensetning struktur og opphav av jordens berggrunn, og dens kjemiske og geofysiske egenskaper. Eksempler: Geologiske, geofysiske og geokjemiske data generelt, bergarter, mineraler, løsmasser, strukturgeologi, hydrogeologi, permafrost, vulkanisk aktivitet, jordskjelv, skred og erosjon. GFYS GKJEM LØSM BERG MD_TematiskHovedKategori - MD_TopicCategoryCode > Example: GFYSGeophysical mapping GKJEMGeochemical mapping LOSMSurficial deposits BERGBedrock geology Makiing links to Norwegian Thematic themes: SOSI Chapters: Organizing our commen Norwegian datasets inside ISO Topic Categories

16 Main challenges Understanding the different metadata elements Example: MD_TopologiNivaaKode - MD_TopologyLevelCode >

17 Main challenges How to produce the UML models most effectively?

18 The tables was transferred to a MS Access database ISO 19115 Norwegian profile

19 The generation of a mapping file SELECT ModelLevel, Name, C.Min, C.Max, Navn, Definition FROM ISO19115dict AS A, NoMetadataProfil AS B, Multiplicity AS C WHERE A.ShortName = B.ShortName AND A.ModelLevel = B.ModellNivå AND Left(A.Obligation,1) = C.Obligation AND Left(A.MAxOccurrence,1) = C.MaxOccurrence ORDER BY LineNbr; SQL call in Access "C","MD_Metadata",,,"MD_MetadataInformasjon","Informasjon om metadataene som beskriver datasett, datatjenester og lignende" "M","fileIdentifier","0","1","metadataIdentifikator","Unik identifikator på en metadata-fil som bl.a. beskriver datasett/tjenester og instanser av objekttyper." "M","language","0","1","metadataSpråk","Språket metadataene er beskrevet i." "L","characterSet","0","1","metadataTegnsett","Denne egenskapen angir hvilken tegnrepresentasjon som er benyttet på metadata-fila. (Dvs. hvilke 8(7)-bits koder tegnene har). Dette kommer spesielt til anvendelse ved tolkning av ÆØÅ, samt valg av "M","parentIdentifier","0","1","metdataOpphav","Dersom metadataene er et uttdrag fra en annen overordnet (mer omfattende) metadata-fil, identifiseres opphavsfilen her" "L","hierarchyLevel","0","*","metadataOmfang","Navn på ett eller flere av de nivåene metadata er gitt på (f.eks. ""datasett, objekttype og egenskaper"")." A report file A Rational Rose script was made to make the changes

20 All ISO object classes...

21 … was translated semiautomatically

22 Example from the UML-models Annex A Data types was not translated.

23 A simple informative UML example was put in (in Norwegian)

24 Main challenges Example from MD_ReferansesystemInfo - Informasjon om referansesystemer) Correct translation? A few missing translations missing translation

25 The overall diagram showing all translated metadata classes (suitable for large scale printing only) Classes pointing to other (not translated)ISO standards generates problems

26 The Norwegian metadata profile are being used in ongoing projects on: -Web Map Services -Catalogue services and based on: -high speed network -WMS interface

27 Geodata Catalogue must work in all browsers on Internet The Norwegian geographic infrastructure - catalogue Arc Catalog + others..and in other catalogue services A 1 st version already implemented

28 ISO 191XX familien ISO 19114 Quality ISO 19115 Metadata NSxx - Official Norwegian Profiles of ISO 19100 - standards Product spesifications Digital products with metadata And in the end…. translation of all relevant parts of all ISO standards

29 Some conclusions: Some conclusions: • Some of the English definitions are not good enough and therefore difficult to translate into Norwegians (strong on structure / low on definitions) • There are still some errors in the standard • We must have extensions to the profile to cover all what’s inn SOSI to day • Copyright problems during project work • The official profile has to wait for the IS (february 2002)?

30 • • ISO 19115 Metadata is comprehensive. Most of what you need is there. • • However, it may be difficult to find what you need. There is a risk that extension mechanisms can be used to define new metadata element even if there are standard mechanisms that fulfill your requirements. • • Needs some ‘core’ metadata experts to assist in the usage of Metadata, or a national profile. More conclusions:

31 Finaly …. Thank you for your attention !