energy industry metadata standards workshopthe vision realize metadata standards and guidelines...
TRANSCRIPT
Energy Industry MetadataStandards Workshop
An Informational WorkshopSeptember 30. 2009
Chevron OfficesHouston Texas
Energistics Meeting Policies
• Intellectual Property
– Participation indicates
agreement to abide
– Do not disclose confidential
• Disclosures are deemed
public
• Competitive Information
– Do not disclose pricing,
costs, sales, plans, schedules, etc.
• Or your participation
may be terminated
– If you are uncomfortable public
– Contributions are made
with grant of rights to use,
modify, etc.
– If you are uncomfortable
regarding such legal matters, leave the
meeting and report your
concerns.
Workshop Objectives
• Continue growing awareness of the initiative
• Initiate formal compilation of requirements
• Identify participants interested in • Identify participants interested in contributing as WG Active Participants
• Position Active Participants to engage their organizations in development activities
3
Agenda
8:00am Welcome & logistics
8:15 Initiative Overview- Vision, scope, use cases
8:45 GIN Architecture Example- NGDS Pilot Project
9:15 Review of ISO 19115 Standard- Organization of base standard; Profile purpose & characteristics
9:45 Break9:45 Break
10:00 Preliminary Requirements- Focus on key attributes
10:30 Breakout Exercise- Identify obligation levels of key attributes, and those requiring reference lists
11:30 Next-steps
11:40 Q&A
12:00pm Adjourn
Energistics Role in the Industry
• Energistics
– serves as a custodian,
– facilitates the development, and
– encourages and supports adoption
• of open data, information and process standards standards
• in the upstream oil and gas industry
5
Energy Industry Metadata Standards:
Initiative Overview
Scott Hills, Chevron and Alan Doniger, Energistics
Outline
• Introduction to Energistics
• Musings about Metadata
• The Opportunity
• The Vision
• Initiative Scope
• Use Cases
7
Energistics
Board of Directors Management & Staff
Advisory Council
Membership, Standards and SIGs
PRODML SIG
SIGs are standards
user communities
Advisory CouncilMembership
Other SIGs
RESQML SIG
WITSML SIG
Participants
Energistics Standards
8
Energistics Subject Areas
Reservoir
Engineering
Expl Petrophysics Petroleum
Production
Geology
AssetManagement
Reservoir
Engineering
Expl Petrophysics Petroleum
Production
Geology SIGGeologySIG
Asset/DataMgt SIG
• Global Unique Well Id
• Industry Metadata
eRegulatorySIG
Industry Services SIG• Technical Architecture• Energy Identity Trust
Expl
Geology
Petrophysics Petroleum
Engineering
Drilling
Engineering
Production
Engineering
Facilities
Engineering
Production
OperationsGeophysics
Drilling
Operations
Completion &
Workover
Expl
Geology
Petrophysics Petroleum
Engineering
Drilling
Engineering
Production
Engineering
Facilities
Engineering
Production
OperationsGeophysicsDrilling
Operations
Completion &
Workover
Geophysics SIG SIG SIG
<<EnergyMLEnergyML/>/> ™™
9
What is Metadata?
• The US FGDC explains that Metadata for a ‘thing’ what a news reporter would report about the ‘thing’:
– WHO created it?
– WHAT is it about? What is its form & size?
WHEN
10
– WHEN was it created? When is it useful?
– WHERE is it geographical relevance?
– HOW did it come to be as it is?
– WHY did it come to be as it is?
Why have and use Metadata?
• Searching for ‘things’ to learn about
• Researching subjects involving ‘things’
• Qualifying ‘things’ as relevant to a task at hand
11
task at hand
Metaphors for Metadata?
• Context – versus content
• Catalog entries
• Directory entries
• Tags
12
• Tags
• Indexes
Challenges for using Metadata effectively?
• Metadata models
• Metadata formats
• Metadata vocabulary
13
• Scope of ‘things’
• Scope of searchers, users
• Understandability among catalogers, between catalogers and users, and among users
Surprise, Surprise !!
• Success requires
– Good planning
• Well defined purpose and scope
– Good requirements
• Avoid purpose and scope creep
14
– Effective (automated) cataloging
• Diligent management and controls
– Full-scale data management
• Versioning
• Aliases
• Translations
• etc.
Best Practice Guidelines
• Generate nominal metadata asa by-product of ‘thing’ creation
– Whether the ‘thing’ is itself data or even if it is a physical resource
• Purposefully adapt nominalmetadata in directories / catalogs
15
metadata in directories / catalogs/ etc.
• Include metadata in data exchange messages
• Treat quality validation actively
• Expect change; manage change
The Opportunity
>40% of staff time devoted to finding, retrieving, and verifying information, and data growing at 60-80%/yr
= Assembling information relevant to a question becoming more problematic, impacting balance of cost and decision quality
Use cases include:
– What bathymetric maps1 are available for this area2?
– What geophysical information1 is available about Project X2?
– Is this the latest version2 of this dataset1?
– Does the copyright2 on this image1 allow me to use it?
1 or other information resource 2 or other selection criterion
16
The Vision
Realize metadata standards and guidelines which enable
stakeholders in the energy industry (“the community”) to
effectively and efficiently discover, evaluate, and retrieve
information resources.
The standards and guidelines will support both proprietary
data management needs, and exchange of data between data management needs, and exchange of data between
and within organizations.
Leverage existing standards to encourage adoption within
the community and integration into the business, and exploit
existing organizational resources needed for governance
and long-term maintenance.
17
Scope
User community:
� Anyone cataloging, searching, evaluating or accessing
information with value to members of the energy industry:� Energy companies & consortia
� Data & Information providers
� Software vendors
� Government agencies & Academia
Resource types:Resource types:
� Initial focus on structured and unstructured information resources
which have associated spatial coordinates. For example,
� Geospatial data sets & web services
� Mapping, Interpretation & Modeling project data sets
� Geospatial web services
� Long-term vision is to include resources with location specified using place names
18
Scope (cont’d)
Category Representative Information Resources
Profile ver.* Type Examples
File-based resources
1 GIS & CAD Maps & Layer representation .mxd, .mxt, .lyr, .pdf, .dwg, .dxf, .dgn
1 GIS data (Vector, Raster) ESRI® shapefile, GeoDatabase,.tif, .jpg
1 Mapping application projects Z-MAP Plus™, PetroSys
1 Modeling application projects (Subsurface properties & structure, Simulation) GOCAD®, Intersect™, Petrel™
1 Seismic projects data (2D, 3D/Navigation, Raw, Processed) SeisWorks®, EPOS®, PetroBank
1 Well logs (Raw and Processed) Geolog®, .las
2 Text documents (Publications, Reports, Bid packages) .doc, .pdf, .ppt, .txt
2 Tables spreadsheets, .dbf
2 Web sites .html
Relational database resources
1 GIS data (Vector, Raster, TIN) SDE™, Oracle® Spatial, PostGIS
1 Production data (Historical, Real-time) Energy Components, TOW/cs®
1 Well data (Construction, Survey, Interpretation) OpenWorks®, Finder®, SeaBed, PPDM™
2 Document Management Systems Documentum®, FileNet®, OpenText™, SharePoint®
Web services
1 GIS data OpenGIS® WMS, WFS, WCS
1 Non GIS data WITSML™, PRODML™
2 Geoprocessing
2 Catalog metadata OpenGIS® CSW
Physical resources
1 Field samples & field documentation
1 Printed maps, logs, cross sections
2 Printed text documents
* Profile version: Resource types in-scope for version 1 have associated, explicit geospatial coordinates.
Use Cases* – Discover & Recall
3.2.1.1 Discovery A knowledge worker (user) must be able to discover and identify relevant data needed to perform his/her work tasks. Standard metadata associated with the data enables users to locate appropriate, available resources without knowledge of the locations, organization, or naming conventions of the repositories in which the data are stored.
3.2.1.2 Recall of Existing DataA user must be able to confirm that he/she has found all existing data as required in A user must be able to confirm that he/she has found all existing data as required in several scenarios. This situation arises frequently in the industry, with users new to the organization or in “look-back” scenarios where users are asked to revisit old projects, prospects, or areas given only information such as the area of interest (AOI) or project name.
* From: Roadmap for Implementing Energy Industry Metadata Standards (Sept. 2009)
Use Cases – Evaluation
3.2.1.3 Evaluation of Data / Fit for PurposeIn the energy business, a user must know the relevance or pertinence of the data to be used in processing, modeling and analysis workflows. The knowledge worker needs to determine if the data is “fit for purpose”, by evaluating criteria such as vintage, source, quality, accuracy, lineage, etc.
3.2.1.4 On-going Data UpdatesOften data becomes obsolete because one or more of its ancestors has been updated. In Often data becomes obsolete because one or more of its ancestors has been updated. In this case, updating the dependent data set requires knowledge of the processing lineage, including the complete hierarchy of relevant ancestors, as well as tools, methods, and parameters used to process the data.
3.2.1.5 Data SharingCommon practices in the energy industry require users to share data externally (e.g., with JV partners) and internally (e.g., with other organizations). A user receiving the data must be able to determine the appropriate use of shared data and ensure that it is used properly and/or combined with other data without introducing errors.
Use Cases – Access
3.2.1.6 Use ConstraintsA knowledge worker needs to know the conditions under which they are permitted to access and use a particular dataset. Commercial or purchased data is often acquired under license with use constraints. Additionally, it now is increasingly common to find use constraints imposed by foreign governments which prohibit export of data produced to support operations within their boundaries.
3.2.1.7 Appropriate UseA user needs to understand the intended or recommended use for a given dataset. Metadata produced by the publisher is critical to the appropriate use of the content, whether published by a vendor, government agency, joint-venture partner, or internal organization within a company. Examples of this kind of metadata include scale-appropriateness and vintage. Lacking this metadata from the publisher, a user may use the data inappropriately or combine the content with other data in a manner that produces erroneous results.
Exploiting the Standard
ExternalMetadata Catalog
Online (Commercial,
Government,
& Academic)
Partner & Subscription
Metadata Catalog
Subscriptiondelivery
Structured resources
Unstructured resources
Application auto-generated
Energy Industry Metadata Standards:
GIN Architecture Example
Steve Richards, Arizona State Geological Survey
Outline
• Introduction to USGS AASG Geoscience Information Network
• Metadata standards and interoperable catalogsinteroperable catalogs
• Relationship with Energistics Metadata Working Group
Motivation
• More access to geologic data via the web
• Make it simple to find • Make it simple to find and utilize geologic data
services
What is GIN:
• A collection of service definitions, interchange formats, and vocabularies
• Catalogs that lead users to • Catalogs that lead users to resources
• A community of users – data providers and consumers
GIN system overview
Current GIN development
• National Digital Catalog– USGS/AASG collaboration, driver is National Geological and Geophysical data preservation program (NGGDPP)
• GIN NSF Project – NSF funded, based at AzGS,
objective is to get geologic survey data online in objective is to get geologic survey data online in interoperable services
• National Geothermal Data System – DOE funded project, Consortium of Geothermal Reseach Organizations, based at Boise State
GeoSciML
NGGDPP catalog
NGMDB map catalog
GEON
OASISOGC
System Components
ISO19139
GEON Catalog
NADM SLTT
AGI glossary
CGI Concepts
What is interoperability
"The capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no
knowledge of the unique characteristics of those units.“ISO/IEC 2382-01 (SC36 Secretariat, 2003)
One client -> many servicesOne client -> many services
One service ->many clients
Some terminology
• ‘Catalog’ can mean different things:– A metadata database (a.k.a. registry)
– An application that allows user to search metadata
• Catalog system—1. A collection of metadata databases,
2. One or more applications that allow users to search the 2. One or more applications that allow users to search the contained metadata.
• Coupling– Tight – catalog search application works with a specific
metadata database
– Loose – search application accesses metadata databases through a standard interface (service)
Interoperable catalog system
• Aggreement in community on practices for publishing, searching, and
delivering metadata
– Standard operations (getRecord, Harvest...)
– Standard content model for what is in – Standard content model for what is in metadata (author, title, abstract, online linkage)
– Standard encoding of metadata (xml schema)
– Shared vocabularies to convey meaning
Operations
• Service Defines
– How to compose queries
• query or filter syntax—SQL, CQL
– What actions• Get records; Describe schema; Insert, delete, or
update records; Harvest records
– What response encoding• e.g. ISO 19139 xml schema
Content Model
• What kind of information is in the metadata
– Author, title, abstract, extent, date modified, identifier, publisher, language, type, format, location
• Different resources need different kinds of content
– E.g. Paper report vs. online map service– E.g. Paper report vs. online map service
• Various existing standards
– Dublin core, FGDC, ISO 19115/119, CSW common
Interchange formats—how MD is encoded
• Key to how the results will be provided
• XML markup languages– Text file, <tags>identify fields in content </tags>
– Public schema define structure
– Shared vocabularies make content intelligible
• Other common file formats work– if structure and content are consistent and well
documented
Semantics
• ‘I do not think it means what you think it means’ Montoya in The Princess Bride
• Solutions
– Shared vocabulary– Shared vocabulary
– Ontology, automated semantic mediation
Controlled vocabularies – Keywords
• Collections of keywords with definitions
• Up side– Users can access defintions to see what terms
mean
– Consistent usage of keywords leads to better search results
• Down side– Not compatible with development of new ideas
– Fossilize conceptual framework
Search application (the client)
• Interface (e.g. web page) to assist users to compose and submit queries
– Might provide pick lists from standard vocabularies
– Mapping to query schema– Mapping to query schema
• Formats results for easy interpretation
• Provides links to related resources, other features to add value for users
Lots of people have catalogs...
Mirador--NASA Earth Science Data Search
Mining Research Library Global mining and minerals library
OnePetro multi-society library of technical literature related to oil and gas
exploration and production .
USGS National Geologic Map Database (NGMDB) map catalog
Virtual Solar Terrestrial Observatory data access
Scripps Institute of Oceanography Explorer Digital Library ProjectScripps Institute of Oceanography Explorer Digital Library Project
GEON portal
Earthscope data portal
USGS Mineral resources spatial data
British Columbia Geographic data discovery service
European Marine and coastal Environmental Information Services
Search clients
• Are expensive to build
• Users have to learn how to use each different client—more learning, less efficiencylearning, less efficiency
• Standard interface allows one client to work with many catalogs
Catalog system architecture
• Distributed search
– Search queries are propagated between catalogs
– Results must be aggregated
– Maximum independence, least lag time to pick up changes
– Performance and reliability are POOR
• Harvest
– Catalog databases collect metadata from others in the system
– Data are cached, may be indexed, processed in various ways
– Changes must propagate through system
– Greatly improved performance, better reliability, queries can be kept in house
GIN catalog system
• AzGS prototype
• CSW service interface on GEON catalog at San Diego Supercomputer Center
• National Geothermal Data System kick off Nov. 2. Catalog will be first step.
• USGS National Digital Catalog in development.
AZGS Test Client, CatalogConnector
Relationships
• Goal:
– Significant overlap between Energy
industry profile, USGIN and National
Geothermal Data System profiles
– Catalog services that will allow – Catalog services that will allow
harvesting and searching transparently
across these various systems.
Thank You
•
Energy Industry Metadata Standards:
Review of ISO 19115 Standard
Scott Hills, Chevron
ISO 19115-2003. Geographic Information - Metadata
• Content specifications
– Data model (UML)
– Elements
– Terminology
• Extension procedure• Extension procedure
• Scope
– Geographic information and services
– Identity, extent, quality, time, and place
48
fileIdentifier: 3A2234641211B12
Metadata
Identification informationConstraint information
Maintenance information
Reference system information
Spatial representation infoData quality information
Distribution informationContent InformationComposed of Packages
fileIdentifier: 3A2234641211B12language: encharacterSet: (default = "utf8“)parentIdentifier: National Map TopoSeries 864hierarchyLevel: (default = "dataset“)hierarchyLevelName: (not needed)contact : CI_ResponsiblePartydateStamp : 20060417metadataStandardName: ISO 19115:2003metadataStandardVersion: x.y
Page 12
34
5
67
89
49
Key Metadata Packages
Metadata Entity
Portrayal Catalogu
e
Constraint Content
Distribution
Citation & Responsibl
e Party
Metadata Extension
Maintenance
Extension
Reference System
ExtentUnits of Measure
Spatial Representatio
n
Data Quality
Application Schema
Identification
Annex A schema object model:Identification Information Package
MD_TopicCategoryCode
+ farming+ biota+ boundaries+ climatologyMeterologyAtmosphere+ economy+ elevation+ environment+ geoscientificInformation+ health+ imageryBaseMapsEarthCover+ intelligenceMilitary+ inlandWaters+ location+ oceans+ planningCadastre+ society+ structure+ transportation+ utilitiesCommunications
<<CodeList>>
MD_Usage+ specificUsage : CharacterString+ usageDateTime[0..1] : DateTime+ userDeterminedLimitations[0..1] : CharacterString+ userContactInfo [1..*] : CI_ResponsibleParty
MD_Metadata(from Metadata entity set information)
MD_Constraints(from Constraint information)
MD_Identification+ citation : CI_Citation
+ abstract : CharacterString+ purpose [0..1] : CharacterString+ credit [0..*] : CharacterString+ status [0..*] : MD_ProgressCode+ pointOfContact [0..*] : CI_ResponsibleParty
<<Abstract>>
+resourceFormat
0..*+resourceSpecificUsage
0..*
1..*+identificationInfo
1..*
0..*
+descriptiveKeywords
0..*
0..*+resourceConstraints 0..*
MD_BrowseGraphic+ fileName : CharacterString+ fileDescription[0..1] : CharacterString+ fileType[0..1] : CharacterString 0..*
+graphicOverview
0..*
MD_KeywordTypeCode
+ discipline+ place+ stratum+ temporal+ theme
<<CodeList>>
MD_ProgressCode
+ completed+ historicalArchive+ obsolete+ onGoing+ planned+ required+ underDevelopment
<<CodeList>>
MD_Format(from Distribution information)
MD_MaintenanceInformation(from Maintenance information)
MD_Keywords+ keyword[1..*] : CharacterString+ type [0..1] : MD_KeywordTypeCode+ thesaurusName[0..1] : CI_Citation
0..*0..*
0..*+resourceMaintenance
0..*
0..*0..*
MD_Resolution
+ equivalentScale : MD_RepresentativeFraction+ distance : Distance
<<Union>>
MD_CharacterSetCode
+ ucs2+ ucs4+ utf8+ utf16+ isoIec8859oneTo15+ jis+ shiftJIS+ eucJP
<<CodeList>>
MD_DataIdentification+ spatialRepresentationType [0..*] : MD_SpatialRepresentationTypeCode+ spatialResolution [0..*] : MD_Resolution+ language [1..*] : CharacterString+ characterSet [0..1] : MD_CharacterSetCode = "utf8"+ topicCategory [1..*] : MD_TopicCategoryCode+ geographicBox [0..*] : EX_GeographicBoundingBox+ geographicDescription [0..*] : EX_GeographicDescription+ environmentDescription [0..1] : CharacterString+ extent [0..*] : EX_Extent+ supplementalInformation [0..1] : CharacterString
SV_ServiceIdentificationSee ISO 19119
MD_RepresentativeFraction
/+ denominator : Integer
<<DataType>>
Scale(from Units of Measure)
/ScaleWhere MD_RepresentativeFraction.denominator = 1/Scale.measure And Scale.targetUnits = Scale.sourceUnits
characterSet: documented if ISO 10646-1 is not used
{MD_Metadata.hierarchyLevelCode = "dataset" implies count (geographicBox) + count (geographicDescription) >=1}
MD_SpatialRepresentationTypeCode
+ vector+ grid+ textTable+ TIN+ stereoModel+ video
<<CodeList>>
51
Annex B: Metadata Data Dictionary
Name/Role
Name
Short
Name
Definition Obligation/
Condition
Maximum
occurrence
Data type Domain
29 MD_Identific
ation
ident basic
information
required to
uniquely identify
a resource
Use
obligation
from
referencing
object
Use
maximum
occurrence
for
referencing
object
Aggregated
Class
(MD_Metadata)
<<Abstract>>
Lines 30-41
30 citation idCitation citation data for
the resource
M 1 Class CI_Citation
<<DataType>>
(B3.2)
31 abstract idAbs brief narratiave M 1 CharacterString Free text 31 abstract idAbs brief narratiave
summary
M 1 CharacterString Free text
32 purpose idPurp summary of the
intentions with
which the
resource was
developed
O 1 CharacterString Free text
33 credit idCredit recognition of
those who
contributed to
the resource
O 1 CharacterString Free text
34 statusCode idStatCode status of
resource
O N Class MD_ProgressCode
<<CodeList>>
(B.6.26)
52
ISO 19115 Community Profiles
• A custom implementation of ISO 19115 tailored to a specific “community” for better and/or easier use.
ISO 19115Broad/complex
ProfileNarrow focus/often simplerBroad/complex
Generic
Optional
Undefined domains
Narrow focus/often simpler
More Specific
More Mandatory
More Explicit Domains –code value lists
53
53
Regional & organizational profiles
ISO Standard 19115ISO Standard 19115
Geographic Information Geographic Information -- MetadataMetadata
Navigation ProfileNavigation ProfileAfrican ProfileAfrican Profile
ANZLIC ProfileANZLIC Profile
North American Profile North American Profile
HydroHydro--geosciences Africa geosciences Africa
European ProfileEuropean Profile
Perfil Latinoamericano de MetadataPerfil Latinoamericano de Metadata
NATO ProfileNATO Profile
Profiles Enable Interoperability Within Communities
Navigation ProfileNavigation ProfileAfrican ProfileAfrican Profile
54
North American Profile
Canada: CAN/CGSB 171.3-95
North American
Profile
USA: FGDC CSDGM
Profile
Geospatial Metadata
Based on ISO 19115/19139
55
� Selection of items from ISO 19115:2003
� Promotion of selected optional fields to mandatory
� Extension of code lists� Addition of values to existing code lists� Addition of code lists
� Introduction of a multilingual register� Compliant to ISO 19135:2005 on registers
North American Profile
� Compliant to ISO 19135:2005 on registers� English and/et Français (and potentially Spanish)� Metadata items� Code lists
� Register will be accessible on the Web� XML document� Web Services� Web Browser
56
North American Profile Values: Examples
Extension
replacing free text
NAPMD_DateTypeCode
57
Energy Industry Metadata Standards:
Preliminary Requirements
Grant Tucker, Shell
Practical Considerations
• What data will users be willing to enter?
• What data is typically available?
• What data can be derived or calculated?
• What happens to existing metadata?
• What impact will there be on:
– Maintenance workflows?
– Discovery workflows?
– Metadata conversion?
User’s Current View
• It’s too much!
Preliminary Requirements
• Seek maximum benefit on discovery while minimizing burden on maintenance.
• Profile defines a minimum standard. It does not preclude entering supplemental data.
• Need a standard dictionary or taxonomy for • Need a standard dictionary or taxonomy for keywords.
• Must be able to preserve/convert existing metadata.
• Must be global, industry standards, not local or company standards.
Obligation Levels
• Obligation levels in ISO spec– M = Mandatory– O = Optional– C = Conditional (mandatory in some cases)
• Some optional elements cannot be made mandatory – information not always availablemandatory – information not always available
• Need a way to emphasize some optional elements– R = Recommended (mandatory if information is available)
• Initial review by BHP, Chevron, Shell– Elevate 7 Optional elements to Mandatory– Elevate 8 Optional elements to Recommended
Key Metadata Packages
Metadata Entity
Portrayal Catalogu
e
Constraint Content
Distribution
Citation & Responsibl
e Party
Metadata Extension
Maintenance
Extension
Reference System
ExtentUnits of Measure
Spatial Representatio
n
Data Quality
Application Schema
Identification
Metadata Entity
• Some elements easily populated with derived or default values
– Language, Character set, Metadata Std.
– Benefits in metadata publishing
Line # Name/Role name Definition Obligation /
Condition
Domain BHP Chevron Shell Overall Value to users Possible Default Value
1 MD_Metadata root entity which defines M Lines 2-221 MD_Metadata root entity which defines
metadata about a resource or
resources
M Lines 2-22
3 language language used for
documenting metadata
C / not defined
by encoding?
ISO 639-2, other parts
may be
R R R Required for publishing to global
metadata servers.
EN
4 characterSet full name of the character
coding standard used for the
metadata set
C / ISO/IEC
10646-1 not
used and not
defined by
encoding?
MD_CharacterSetCode
<<CodeList>> (B.5.10)
R R R Required for publishing to global
metadata servers.
UTF8
9 dateStamp date that the metadata was
created
M Date (B.4.2) M M M Users will be able to search for
recently published data sets or
identify what data sets have been
recently updated.
Today
10 metadataStandardName name of the metadata standard
(including profile name) used
O Free text R R R Required for publishing to global
metadata servers.
ISO19115
11 metadataStandardVersio
n
version (profile) of the
metadata standard used
O Free text R R R Required for publishing to global
metadata servers.
Ver # (TBD)
Identification
• Some definitions not clear to users
– Abstract vs. PurposeLine # Name/Role name Definition Obligation /
Condition
Domain BHP Chevron Shell Overall Value to users Possible
Default Value
23. MD_Identification basic information required to
uniquely identify a resource or
resources
Use obligation
from referencing
object
Lines 24-35.1
25. abstract brief narrative summary of the
content of the resource(s)
M Free text M R M M This more detailed description supplies the
pertinent information about dataset in free-form
text.
Allow user to
recall last value
used.
26. purpose summary of the intentions with
which the resource(s) was
developed
O Free text M M
developed
27. credit recognition of those who
contributed to the resource(s)
O Free text R R
28. status status of the resource(s) O MD_ProgressCode
<<CodeList>> (B.5.23)
R R R This will inform the user if they can expect any
updates.
36. MD_DataIdentification information required to identify
a dataset
Use obligation
from referencing
object
Lines 37-46 and 24-
35.1
39. language language(s) used within the
dataset
M ISO 639-2, other parts
may be used
M M M These attributes can be important for many
international datasets.
EN
40. characterSet full name of the character
coding standard used for the
dataset
C/ISO/IEC
10646-1 not
used?
MD_CharacterSetCode
<<CodeList>> (B.5.10)
M M M UTF8
41. topicCategory main theme(s) of the dataset
C / if hierarchyLevel equals
“dataset”?
C / if
hierarchyLevel
equals
“dataset”?
MD_TopicCategoryCod
e <<Enumeration>>
(B.5.27)
M M M This will not provide much value to our users, but
is compulsory for ISO compliance.
Allow user to
recall last value
used.
46. supplementalInformation any other descriptive
information about the dataset
O Free text R R This field can be used to store any technical
details or processing parameters that need to
remain with the dataset. SJH: Shouldn't this kind
of info go in the Lineage section?
52. MD_Keywords keywords, their type and
reference source
Use obligation
from referencing
object
Lines 53-55
53. keyword commonly used word(s) or
formalised word(s) or
phrase(s) used to describe the
subject
M Free text M R M M These keywords describe the data content or can
associate the data to a place name or corporate
asset.
54. Type subject matter used to group
similar keywords
O MD_KeywordTypeCod
e <<CodeList>>
(B.5.17)
R R R R
Identification
• Some elements defined by rigid code lists
– <<Enumeration>>
• Not well suited to industry
– Topic Category 1. MD_TopicCategoryCode <<Enumeration>>
TopicCatCd
2. farming 001
3. biota 002
4. boundaries 0034. boundaries 0035. climatologyMeteorologyAtmosphere 004
6. economy 005
7. elevation 0068. environment 007
9. geoscientificInformation 008
10. health 009
11. imageryBaseMapsEarthCover 01012. intelligenceMilitary 011
13. inlandWaters 012
14. location 013
15. oceans 014
16. planningCadastre 015
17. society 016
18. structure 01719. transportation 018
20. utilitiesCommunication 019
Identification
• Some elements not defined by code lists
– Free Text
• Need to be constrained to industry taxonomy
– Keyword
– Should it be extensible, allow for localization?
Line # Name/Role name Definition Obligation /
Condition
Domain BHP Chevron Shell Overall Value to users Possible
Default Value
52. MD_Keywords keywords, their type and
reference source
Use obligation
from referencing
object
Lines 53-55
53. keyword commonly used word(s) or
formalised word(s) or
phrase(s) used to describe the
subject
M Free text M R M M These keywords describe the data content or can
associate the data to a place name or corporate
asset.
54. Type subject matter used to group
similar keywords
O MD_KeywordTypeCod
e <<CodeList>>
(B.5.17)
R R R R
Constraints
• What is needed to document license restrictions and export compliance?
Line # Name/Role name Definition Obligation /
Condition
Domain BHP Chevron Shell Overall Value to users Possible Default Value
69. MD_LegalConstraints restrictions and legal
prerequisites for accessing and
using the resource or metadata
Use obligation
from referencing
object
Lines 70-72 and 68
70. accessConstraints access constraints applied to
assure the protection of privacy
or intellectual property, and any
special restrictions or
limitations on obtaining the
O MD_RestrictionCode
<<CodeList>> (B.5.24)
M R M
limitations on obtaining the
resource or metadata
71. useConstraints constraints applied to assure
the protection of privacy or
intellectual property, and any
special restrictions or
limitations or warnings on using
the resource or metadata
O MD_RestrictionCode
<<CodeList>> (B.5.24)
M R M
73. MD_SecurityConstraints handling restrictions imposed
on the resource or metadata for
national security or similar
security concerns
Use obligation
from referencing
object
Lines 74-77 and 68
74. classification name of the handling
restrictions on the resource or
metadata
M MD_ClassificationCode
<<CodeList>> (B.5.11)
M M
75. userNote explanation of the application of
the legal constraints or other
restrictions and legal
prerequisites for obtaining and
using the resource or metadata
O Free text R R The user may want to select from a
list of values (Unclassified,
restricted, etc.) but then be able to
add addition details.
Allow user to recall last value
used. Also allow the user to
choose from a standard list
and enter supplemental
information.
Constraints
• Are code lists sufficient or need to be extended?
– Classification Code, Restriction Code
1. MD_ClassificationCode ClasscationCd
2. unclassified 001
1. MD_RestrictionCode RestrictCd
2. copyright 0012. unclassified 001
3. restricted 002
4. confidential 003
5. secret 004
6. topSecret 005
2. copyright 001
3. patent 002
4. patentPending 003
5. trademark 004
6. license 005
7. intellectualPropertyRights 006
8. restricted 007
9. otherRestrictions 008
Data Quality
• Lineage statement is used to track ESRI Geoprocessing operations
– Will it be complete, dependable, useful?
– Requirements for “export” functions from subsurface applications?
Line # Name/Role name Definition Obligation /
Condition
Domain BHP Chevron Shell Overall Value to users Possible Default Value
78. DQ_DataQuality quality information for the data
specified by a data quality
scope
Use obligation
from referencing
object
Lines 79-81
81. Role name: lineage non-quantitative quality
information about the lineage of
the data specified by the scope
C / report not
provided?
LI_Lineage (B.2.4.2) R R
82. LI_Lineage information about the events or
source data used in
constructing the data specified
by the scope or lack of
knowledge about lineage
Use obligation
from referencing
object
Lines 83-85
83. statement general explanation of the data
producer’s knowledge about
the lineage of a dataset
C /
(DQ_DataQualit
y.sco
pe.DQ_Scope.le
vel = “dataset”
or “series”)?
Free text R R R This field is very important for
derivative data. GP functions from
ArcToolbox will populate or update
these values.
Updated automatically by
ArcGIS GP Tools. In 9.0 these
populate the FGDC tags, not
ISO. What about FME?
Reference System
• Complex data structure in related classes
• Need to review conditions
Line # Name/Role name Definition Obligation /
Condition
Domain BHP Chevron Shell Overall Value to users Possible Default Value
186. MD_ReferenceSystem information about the reference
system
Use
obligation/conditi
on from
referencing
object
Line 187
187. referenceSystemIdentifier name of reference system C RS_Identifier (B.2.7.3) M C R M The CRS information is critical in Allow user to recall last value 187. referenceSystemIdentifier name of reference system C
/MD_CRS.proje
ction,
MD_CRS.ellipso
id, and
MD_CRS.datum
not
documented?
RS_Identifier (B.2.7.3) M C R M The CRS information is critical in
maintaining geodetic integrity. SJH:
required "Conditional" upon
existence of EX_GeographicExtent
(Line #336)
Allow user to recall last value
used. Also allow the user to
choose from a standard list
and enter supplemental
information.
189. MD_CRS metadata about a coordinate
system in which attributes have
been derived from SC_CRS as
defined in ISO 19111 – Spatial
referencing by coordinates
Use
obligation/conditi
on from
referencing
object
Lines 190-194 and 187
190. projection identity of the projection used O RS_Identifier (B.2.7.3) M C M
191. ellipsoid identity of the ellipsoid used O RS_Identifier (B.2.7.3) C C
192. datum identity of the datum used O RS_Identifier (B.2.7.3) M C M
193. role name:
ellipsoidParameters
set of parameters that describe
the ellipsoid
O MD_EllipsoidParameter
s (B.2.7.2)
194. role name:
projectionParameters
set of parameters that describe
the projection
O MD_ProjectionParamet
ers (B.2.7.6)
195. RS_ReferenceSystem description of the spatial and
temporal reference systems
used in the dataset
Use
obligation/conditi
on from
referencing
object
Class
Distribution
• Online Resource
– Vendors URL vs. internal corporate server/service location
– How to handle redundant servers/services within a company
– Effects on publishing to metadata servers– Effects on publishing to metadata servers
Line # Name/Role name Definition Obligation /
Condition
Domain BHP Chevron Shell Overall Value to users Possible Default Value
274. MD_DigitalTransferOptions technical means and media by
which a resource is obtained
from the distributor
Use
obligation/conditi
on from
referencing
object
Lines 275-278
277. onLine information about online
sources from which the
resource can be obtained
O CI_OnlineResource
<<DataType>>
(B.3.2.5)
M M R M This UNC path, Feature service path or
SDE connection string might be used
by search tools to access the data
once a search is completed.
Derive from dataset.
284. MD_Format description of the computer
language construct that
specifies the representation of
data objects in a record, file,
message, storage device or
transmission channel
Use
obligation/conditi
on from
referencing
object
Lines 285-290
285. name name of the data transfer
format(s)
M Free text R R R
286. version version of the format (date,
number, etc.)
M Free text R R R
Energy Industry Metadata Standards:
Breakout Exercise
Lisa Derenthal, Gimmal Group
Breakout Session
• Goal: Engage workshop participants in metadata
profile development
• Worksheets
Blue Group Green Group Red GroupBlue Group
• Identification
Green Group
• Metadata
• Constraint
• Distribution
Red Group
• Data Quality
• Maintenance
• Reference System
Breakout Session
• Goal: Engage workshop participants in metadata
profile development
• Worksheets
Blue Group Green Group Red GroupBlue Group
• Identification
Green Group
• Metadata
• Constraint
• Distribution
Red Group
• Data Quality
• Maintenance
• Reference System
Breakout Session
• Team Exercise
1. Review the key* metadata elements on your worksheet(s)
2. Discuss and record team feedback on each element
• Obligation Level• Obligation Level
• Population Method
• Default Value
• Codelist – Type and Source
3. Present your team results
* Initial Mandatory and Recommended Elements
Energy Industry Metadata Standards:
Next-steps
Lisa Derenthal, Gimmal Group
Next Steps / Actions
• Profile Development - with Community Input
– Metadata attributes
– Obligation level
– Domain values
• Workgroup Feedback to ISO 19115 Organization• Workgroup Feedback to ISO 19115 Organization
– Replication issues
– Keyword categories (class-instance)
– Additional feedback from workshop participants and community
Timeline – Metadata Initiative
Develop Industry Metadata Profile
Status Report @ PUG 2010
2009 2010 2011
79
Stakeholder Reviews
Status Report @ UC 2010
Early Adoption Support
Energy Industry Metadata Standards:
Questions & Answers
Thank You
Alan Doniger
Energistics Chief Technology Officer
24 E. Greenway Plaza, Suite 1315
Houston, TX 77042 USA
+1 713 267 5124
www.energistics.org