energy industry metadata standard - home - energistics...2011/04/19 · existing standards - •...
TRANSCRIPT
Energy Industry Metadata Standard
What, Why, When and Where?
Initiative Update
ESRI PUG Conference
April 19, 2011
Workshop Goals
• Build awareness and provide update on the
Energy Industry Metadata Standard
• Review ISO 19115 framework
• Discuss outstanding issues and solicit
community involvement
– Immediate comments
– Feedback on release candidate
– Plan for adoption
2
Agenda
• Overview - Energy Industry Metadata Initiative
• ISO 19115 Revision Project
• Energy Industry Profile (EIP) Overview & Status
• USGIN Project Lessons, Examples
• Audience Comments / Q&A
3
Agenda
• Overview - Energy Industry Metadata Initiative
– Vision, Scope, Participants
– The Product: Energy Industry Profile
– Status & Timeline
• ISO 19115 Revision Project
• Energy Industry Profile (EIP) Overview & Status
• USGIN Project Lessons, Examples
• Audience Comments / Q&A
4
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 is 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
5
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 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.
6
The Big Picture
Metadata
Catalog
External
Metadata
Catalog
Online
(Commercial,
Government,
& Academic)
Partner &
Subscription
delivery
Structured
resources Unstructured
resources
Application auto-
generated
7
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:
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
8
Initiative Participants
9
AAPG
Apache
Boise State Univ.
Carbon Lifecycle Technology
ConocoPhillips
DCP Midstream
Deloitte Services LP
Devon Energy
ETL Solutions
Exprodat
ExxonMobil1
First American Spatial Solutions
Flare Solutions
Fugro Robertson
Geoscience Australia
Geosoft
Ies Brazil Consulting & Services
IHS Energy
Maersk Oil1
New Century Software
North West Geomatics
Oracle1
ORNL
P2 Energy Solutions
PEMEX
PennWell
PetroWEB
Pioneer Natural Resources1
PPDM1
Priemere Consulting Group
SAS Global Oil & Gas
Schlumberger1
Shell1
Univ. of Auckland, NZ
Virginia Dept of MM&E
Wood Mackenzie
Dave Danko, ESRI
Lisa Derenthal, Gimmal
Alan Doniger, ACD Consulting Solutions2
Scott Hills, Chevron1
Steve Richard, USGIN, AZ Geol Survey1
Steering Team Active Participants (SMEs)
1 Energistics member; 2 Energistics Project Manager ; Bold Contributing to the current RFC
Asset/Data Management SIG
Metadata Work Group
Energistics
The Product / Deliverables
• Profile Documentation
– Normative Specification
– Implementation Guidelines
– Selected XML Examples
• Exemplar Resources & Conformant Metadata
Data Type Donating Organization(s)
Dataset
Publication
Web Service ESRI
10
Build on existing standard(s)
Our approach leverages
existing standards -
• ISO 19115 metadata standard
for geographic information –
internationally accepted
• Existing profiles:
– North American Profile (NAP)-
adapts 19115 to FGDC standard
– European INSPIRE guidelines
– ANZLIC—Australia, New Zealand
• Use same approach to deliver a
―Energy Profile‖ built on these
11
Current Status / Activity Summary
Requirements Gathering - Completed
• Initial Community Workshop
• Follow up Survey – 16 organizations
• Integrate with ISO 19115 Revision – Ongoing
• Direct input to TC 211 Revision Project
• Profile Development – Ongoing
• Release Candidate nearing completion
• Energistics‘ A&DM SIG Review – 2Q2011
• Community Review – 2Q2011
12
Metadata Initiative Timeline
13
Metadata Profile Development
Status Report @ PUG 2011
SIG Reviews
Status Report @ ESRI UC 2011
2010 2011
Pilot Projects
Stakeholder Reviews
Profile 1.0 Published
2012
Agenda
• Overview - Energy Industry Metadata Initiative
• ISO 19115 Revision Project
– Background
– Profiles
– Timeline
– Relevance to EIP Initiative
• Energy Industry Profile (EIP) Overview & Status
• USGIN Project Lessons, Examples
• Audience Comments / Q&A
14
ISO TC211 Standards Standardization in the field of digital geographic information
ISO 19101:2002 - Reference model
ISO 19105:2000 - Conformance and testing
ISO 19106:2004 - Profiles
ISO 19107:2003 - Spatial schema
ISO 19108:2002 - Temporal schema
ISO 19111:2003 - Spatial referencing by coordinates
ISO 19112:2003 - Spatial referencing by geographic identifiers
ISO 19123:2005 - Schema for coverage geometry and functions
ISO 19109:2005 - Rules for application schema
ISO 19110:2005 - Feature cataloguing methodology
ISO 19113:2002 - Quality principles
ISO 19114:2003 - Quality evaluation procedures
ISO 19115:2003 - Metadata
ISO 19116:2004 - Positioning Services
ISO 19125:2004 - Simple feature access – Part 1-2
ISO 19117:2005 - Portrayal
ISO 19118:2005 - Encoding
ISO 19119:2005 - Services
ISO 19128:2005 - Web Map server interface
ISO 19139:2006 – Metadata XML Schema
Data Management
Visualization
Data Formats
Web Services
Content Description
Basic
Geographic
Structures
15
Existing ISO TC 211 Metadata Standards
• ISO 19110:2005 Methodology for feature cataloguing
• ISO 19113:2002 Quality principles
• ISO 19114:2003 Quality evaluation procedures
• ISO 19115:2003 Metadata
• ISO 19115-2:2009 Metadata -- Part 2: Extensions for imagery and
gridded data
• ISO 19119:2005 Services and extensions for service metadata
model
• ISO 19130:2010 Imagery sensor models for geopositioning
• ISO 19138:2006 Data quality measures
• ISO 19139:2007 Metadata-XML schema implementation
16
ISO 19115:2003
• Designed:
– specifically to support geographic information;
– to work with wider information technology standards
and practices;
– to support minimal to comprehensive metadata
• simple catalog to the full description of resources
– to support datasets, series, features, attributes…
– to serve the global community, in a multi-national,
multi-language environment;
– based on a foundation of national, regional, and
special information community standards and
experiences
• Developed through a rigorous, consensus
ISO process
17
Identification
Information
Metadata Packages
Content
Information
19110, 21, 23, 24
Application
Schema
Information
19109
Reference
System Information
19108, 11, 12
Metadata
Extension
Information
Portrayal
Catalogue
Information
Spatial
Representation
Information 19107
Employ
Extract Distribution
Information
Metadata
Constraint
Information
Maintenance
Information
Data Quality
Information
19113,14
Evaluate
• Defines metadata elements;
• Provides a schema (UML);
• Establishes a common set of metadata terminology, definitions (data dictionary)
Locate
18
ISO/TS 19139:2007 Geographic Information – Metadata XML Schema Implementation
19
<xs:complexType name="MD_DataIdentification_Type">
- <xs:complexContent>
- <xs:extension base="gmd:AbstractMD_Identification_Type">
- <xs:sequence>
<xs:element name="spatialRepresentationType"
type="gmd:MD_SpatialRepresentationTypeCode_PropertyType
minOccurs="0" maxOccurs="unbounded" />
<xs:element name="spatialResolution"
type="gmd:MD_Resolution_PropertyType" minOccurs
maxOccurs="unbounded" />
<xs:element name="language"
type="gco:CharacterString_PropertyType" maxOccurs
<xs:element name="characterSet"
type="gmd:MD_CharacterSetCode_PropertyType" minOccurs
maxOccurs="unbounded" />
<xs:element name="topicCategory"
type="gmd:MD_TopicCategoryCode_PropertyType"
maxOccurs="unbounded" />
<xs:element name="environmentDescription"
type="gco:CharacterString_PropertyType" minOccurs
<xs:element name="extent" type="gmd:EX_Extent_PropertyType
minOccurs="0" maxOccurs="unbounded" />
<xs:element name="supplementalInformation"
type="gco:CharacterString_PropertyType" minOccurs
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Standard Broad/complex
Generic
Optional
Undefined domains
Profile A standard tailored for a ―Community‖
Profile Narrow focus/often simpler
Specific
Mandatory
Explicit Domains – codelists
Easier implementation
ISO 19106 Profiles:
“...set of one or more base standards or sub-sets
of base standards…that are necessary for
accomplishing a particular function.”
20
Regional, national, & organizational profiles
ANZLIC Profile
North American Profile
Energy Industry Profile
INSPIRE
Perfil Latinoamericano de Metadatos
NATO Profile
Profiles Enable Interoperability Between Communities
ISO Standard 19115
Geographic Information - Metadata
State Profile Navigation Profile
Communities with a common need for metadata
21
ISO 19115 Implementation The ISO 19115 ―Brand‖
• Australia-New Zealand Profile
• North American Profile of ISO 19115
• INSPIRE (INfrastructure for SPatial InfoRmation in Europe)
• Marine Community Metadata Profile of ISO 19115
• A metadata profile for precision agriculture based
on ISO 19115 standard.
• WMO Core Profile of the ISO 19115 Metadata
Standard
• Latin American Profile
• . . .
22
ISO 19115 Tools
– CATMDEdit (metadata
production/viewing)
– terraCatalog (production,
serving, and searching)
– ArcCatalog (production and
browsing)
– ArcGIS Server Portal (production, serving, searching)
– GeoNetwork (production,
serving, searching)
– IME (production and viewer)
– M3CAT (production and management)
– MetaD (production and export)
– Parcs Canada Metadata
Editor (production)
– NOKIS Editor (production and
exposure)
– . . .
Many open source and proprietary metadata editors
have been developed
23
ISO 19115:2003 Revision
• ISO 19115:2003 Metadata
• ISO 19115 Corrigendum
• ISO 19119:2005 Services
and extensions for service
metadata model (Part)
• User suggestions
• Lessons learned
• New methods
• Changes in related
standards
ISO 19115-1
Metadata -
Fundamentals
ISO standards are reviewed every 5 years
24
LI_Source
+ description: CharacterString [0..1]
+ scaleDenominator: MD_RepresentativeFraction [0..1]
+ sourceReferenceSystem: MD_ReferenceSystem [0..1]
+ sourceCitation: CI_Citation [0..1]
+ sourceExtent: EX_Extent [0..*]
LI_ProcessStep
+ description: CharacterString
+ rationale: CharacterString [0..1]
+ dateTime: DateTime [0..1]
+ processor: CI_ResponsibleParty [0..*]
LI_Lineage
+ statement: CharacterString [0..1]
DQ_DataQuality
+ scope: DQ_Scope
+source
0..*
+sourceStep
0..*
+processStep 0..*+source 0..*
+lineage 0..1
ISO 19115:2003 Data Quality Information
DQ_GriddedDataPositionalAccuracy
DQ_LogicalConsistency DQ_PositionalAccuracy
DQ_ThematicAccuracy
DQ_TemporalAccuracy
DQ_CompletenessCommission
DQ_CompletenessOmission
DQ_ConceptualConsistency
DQ_DomainConsistency
DQ_FormatConsistency
DQ_Completeness
DQ_AbsoluteExternalPositionalAccuracy
DQ_DataQuality
+ scope: DQ_Scope
DQ_RelativeInternalPositionalAccuracy
DQ_ThematicClassificationCorrectness
DQ_NonQuantitativeAttributeAccuracy
DQ_QuantitativeAttributeAccuracy
DQ_AccuracyOfATimeMeasurement
DQ_TemporalConsistency
DQ_TemporalValidity
LI_Lineage DQ_Element
DQ_TopologicalConsistency
+lineage 0..1 0..* +report
0..*
0..*Data Quality
Information
DQ_Result
DQ_QuantitativeResult
+ valueType: RecordType [0..1]
+ valueUnit: UnitOfMeasure
+ errorStatistic: CharacterString [0..1]
+ value: Record [1..*]
DQ_ConformanceResult
+ specification: CI_Citation
+ explanation: CharacterString
+ pass: Boolean
Data Quality Classes
Lineage
25
New Standards Development: ISO 19157 Data Quality
ISO 19113:2002 Quality principles
ISO 19114:2003 Quality evaluation
procedures
ISO 19138:2006 Data quality measures
(Part)
ISO 19115:2003 Metadata (Part)
ISO
19157
DQ_GriddedDataPositionalAccuracy
DQ_LogicalConsistency DQ_PositionalAccuracy
DQ_ThematicAccuracy
DQ_TemporalAccuracy
DQ_CompletenessCommission
DQ_CompletenessOmission
DQ_ConceptualConsistency
DQ_DomainConsistency
DQ_FormatConsistency
DQ_Completeness
DQ_AbsoluteExternalPositionalAccuracy
DQ_DataQuality
+ scope: DQ_Scope
DQ_RelativeInternalPositionalAccuracy
DQ_ThematicClassificationCorrectness
DQ_NonQuantitativeAttributeAccuracy
DQ_QuantitativeAttributeAccuracy
DQ_AccuracyOfATimeMeasurement
DQ_TemporalConsistency
DQ_TemporalValidity
LI_Lineage DQ_Element
DQ_TopologicalConsistency
+lineage 0..1 0..* +report
0..*
0..*
Data quality
classes
26
Other Changes to ISO 19115-1
• Fully backward compatible
– No new mandatory
– <<Deprecated>> elements remain until next revision
– All new elements stereotyped as <<new>>
• Feature catalog included (physically or by link)
• Many new elements added (online linkage in
Citation, Reference system type code attribute
added to reference system identifier
• Responsible party restructured to enable reuse
for different roles
27
ISO Revision Schedules
• ISO 19115-1 Metadata - Fundamentals
– Editing committee meeting in Delft: 2011-05-23-27
– Draft International Standard 2011-11
– Final Draft International Standard 2012-11
– International Standard 2013-05
• ISO 19157 Data Quality
– Committee Draft 2010-7
– Draft International Standard 2011-06
– Final Draft International Standard 2012-06
– International Standard 2013-01
• ISO/TS 19139 Metadata XML schema implementation
– Work to generate new schema and revise the document will begin when ISO 19115 is technically stable
28
ISO 19115-1 Review Participation
EIP Metadata Working Group Participation in ISO 19115 Revision
• Energistics granted Class A Liaison status to TC 211
• Metadata WG participated in Project Team meeting, Quebec City (11/2009): proposed changes to 19115:2006
• WG provided input and detailed comments about WD0 and WD1
• Comments in prep. about ISO 19115-1 CD (―Committee Draft‖)
• WG to participate in Editing Committee Mtg, Delft
29
Agenda
• Overview - Energy Industry Metadata Initiative
• ISO 19115 Revision Project
• Energy Industry Profile (EIP)
– Status & Overview
– Context, Considerations
– Resource Classes: Types & Definition
– Element Obligations
• USGIN Project Lessons, Examples
• Audience Comments / Q&A
30
EIP Specification: Status
• Energy Industry Profile of
ISO/CD 19115-1:2011
• v1.0 Release Candidate
• Normative Specifications &
Implementation Guidelines
• Document draft v0.7
• Currently 90 pp.
31
EIP Specification Document
Table of Contents: pages
1. Introduction <1
2. Scope 3
3. Conformance 1
4. Normative References 1
5. Abbreviations <1
6. Content Model Overview <1
7. Requirements of the Profile 5
8. Element Specifications 63
9. Annexes 10
32
Core
Reminder: The Vision
Metadata
Catalog
External
Metadata
Catalog
Online
(Commercial,
Government,
& Academic)
Partner &
Subscription
delivery
Structured
resources Unstructured
resources
Application auto-
generated
33
Consider
• Usage Scope:
“… efficiently catalog, discover, evaluate, and
retrieve available information resources”
• Resources in Scope:
“… types of information resources commonly
used within the energy community”
• Conclusion:
– Scope implies need to maintain & handle (producer,
consumer) significant volumes of metadata
– Manual maintenance & handling not practical
– Profile must enable organizations to fully automate
maintenance & handling, if desired
34
Scope Control: Metadata Packages
Metadata
Entity
Portrayal
Catalogue
Constraint Content
Distribution
Metadata
Extension
Reference
System
Units of
Measure
Spatial
Representation
Data Quality
Application
Schema
Maintenance
Identification
Extent
Citation &
Responsible
Party
35
Resource Classes
• Differentiate Three Classes of Resource:
1. Digital products
2. Physical products
3. Digital services
• ―Base‖ group of Metadata Required of All
• Option to Georeference Any Resource
• Flow diagram to Identify Metadata Elements
Needed for Each Resource Class
36
Resource Classes: Definition
MD_ScopeCode value Behavior Form Geospatial content … maps to Resource Class
activity activity conceptual mixed Not in scope for EIP.
nonGeographicDataset product electronic absent Digital Product
electronicDocument product electronic present or absent
dataset product electronic present
Geolocated Digital Product model product electronic present
dataRepository product electronic present
physicalDocument product physical present or absent Physical Product
sample product physical present Geolocated Physical Product
nonGeographicService service electronic absent Digital Service
service service electronic present Geolocated Digital Service
37
• … identified by MD_ScopeCode values,
• defined using three properties/attributes
Element Group Selection
38
Populate
Base Group
elements
Table 3
Populate
Digital Product Group
elements
Table 4
MD_ScopeCode
value is type of
Digital Product?
Populate
Physical Product Group
elements
Table 5
Populate
Geolocated Resource
Group elements
Table 7
MD_ScopeCode
value is type of
Physical Product?
MD_ScopeCode
value is type of
Digital Service?
Yes
No No
YesPopulate
Digital Service Group
elements
Table 6
Yes
MD_ScopeCode
value is type of
Geolocated Resource?
Yes
No
Completed
resource metadata
• Based on Resource Class
Base Element Group
Content Name Content and Implementation Details
Minimum M/C
element values1
Changes to
ISO 191152
Metadata language 8.1.1 Metadata Language 1/0 O
Metadata character set 8.1.2 Metadata Character Set 1/0 O
Metadata contact 8.1.3 Metadata Contact Information 3/0 O,Do
Metadata create date 8.1.4
Metadata Create Date
1/0 O
Metadata identifier 8.1.5
Metadata Identifier
1/0
Metadata standard 8.1.6 Metadata Standard 1/3
Metadata parent identifier 8.1.7 Parent Metadata Identifier 1/0 O
Metadata update date 8.1.8
Metadata Update Date
2/0
Metadata scope 8.1.9 Metadata Scope 1/0 O,Do
Resource citation title 8.2.1 Resource Citation Title 1/0
Resource citation date 8.2.2 Resource Citation Date 2/0
Resource identifier 8.2.3 Resource Identifier 1/0 O
Resource cited responsible party 8.2.4 Cited Responsible Party 3/0 O
Abstract 8.2.5 Abstract 1/0
Resource status 8.2.6 Resource Status 1/0 O
Resource owner or custodian 8.2.7 Resource Point of Contact 3/0 O
Resource content topic 8.2.8 Resource Topic Category 0/1
Descriptive keywords 8.2.9 Descriptive Keywords 1/1 O
Constraints on resource access and
usage
8.2.10 Constraints on Resource Access and
Usage
3/0 O
Resource distributor 8.2.11
Resource Distributor
3/0 O
Total: 31/4
39
Element Groups (1/2)
Content Name Content and Implementation Details
Min. M/C
Elements
Changes to
ISO 19115
Resource language 8.7.2 Resource Language 1/0 O
Resource character set 8.7.3 Resource Character Set 1/0 O
Digital product format 8.3.1 Digital Product Format 1/0 O
Digital product access 8.4.2 Product Ordering Process 0/1 O
Total (including “Base Elements”): +3/1
40
• Digital Products
• Physical Products
Content Name Content and Implementation Details
Min. M/C
Elements
Changes to
ISO 19115
Resource language 8.7.2 Resource Language 1/0 O
Resource character set 8.7.3 Resource Character Set 1/0 O
Physical product format 8.4.1 Physical Product Format 1/0 O
Product ordering process 8.4.2 Product Ordering Process 1/0
Total (including “Base Elements”): +4/0
Element Groups (2/2)
Content Name Content and Implementation Details
Min. M/C
Elements
Changes to
ISO 19115
Service type 8.5.1 Service Type 1/1 C
Coupled resources 8.5.3 Coupled Resources 1/2 C
Coupling type 8.5.2 Coupling Type 1/0
Connection information 8.5.3 Service Operations Metadata 3/0
Service distribution 8.5.5 Service Distribution 7/0 O
Total (including “Base Elements”): +13/3
41
• Digital Services
• Geolocated Resources
Content Name Content and Implementation Details
Min. M/C
Elements
Changes to
ISO 19115
Spatial representation 9.7.1 Spatial Representation 6/0 C
Spatial reference system 9.7.2 Spatial Reference System 2/1 C
Spatial extent 9.7.3 Spatial Extent 4/0 C
Spatial resolution 9.7.4 Spatial Resolution 1/0 C
Table total (must be added to Totals in Table 4-6): +13/1
Spatial Metadata
42
Draft EIP Release Candidate considers only: • Spatial Representation
• Reference System (CRS)
• Extent (bounding box)
• Spatial Resolution
Obligation of each is ―Conditional‖ • Reference System and Extent required if resource type has spatial
coordinates (e.g., MD_ScopeCode=―dataset‖)
EPSG codes will be the
required CRS domain
standard • E.g., RS_Identifier/code>―EPSG:5701‖
Element Obligations
43
• Count By Resource Class
• Mandatory / Conditional
Agenda
• Overview - Energy Industry Metadata Initiative
• ISO 19115 Revision Project
• Energy Industry Profile (EIP) Overview & Status
• USGIN Project Lessons, Examples
– USGIN Project
– Catalog Implementations
– Example metadata elements
• Audience Comments / Q&A
44
Geoscience Information Network (USGIN)
45
Make data accessible through standardized web-
accessible interfaces
• Service definitions, interchange formats, and vocabularies
• USGS and State Geological Surveys (AASG)
• DOE Geothermal Data System
• Catalog system for
registering resources
Distributed Linked Data System
• Catalog is key component in system
– I can’t use what I don’t know about
– I can’t use what I can’t get
• Metadata is free
– Records circulate freely
– Advertisement for resource
• System requires:
– Shared content model
– Standard protocols for query and harvest
– Tools for metadata creation
– Training for metadata creators
46
USGIN Metadata
• USGIN ISO Profile– developed to get system going
– Informs EIP development, v2 will harmonize with updates in EIP
• Enable automated parsing of metadata documents
– Reduce (remove?) ambiguity about where to locate information
– Promote inclusion of key information
– Enable harvesting of metadata records
• Most significant difference is high importance put
on Use and Access Constraints in EIP
47
Catalog Implementations Tested
Server-side application for searching and
maintaining metadata repository • Deegree (v2, now at v3)
– Xml parsed into relational database
– Performance and scaling issues
• Geonetwork
– Mature open-source project with large community
– Multiple metadata schema; map to abstract model
– Lucene indexing
• ESRI Geoportal
– Implementation architecture similar to Geonetwork
– Less complex implementation and configuration
48
Food for Thought
• Development of profile requires making
decisions on a variety of questions– here are
a few to think about when reviewing the spec
49
Vertical Extent
• USE CASE: metadata for logs, core,
subsurface samples
• Depth – most useful for wells; have to report
surface elevation
• Elevation – more useful for surface features;
easier with ISO extent elements.
• Meters? Feet?
50
Distribution – How to get the resource
• USE CASE: I want to get the document
described by the metadata record
– Can a resource have more than one distributor?
– Where does URL go for linkage to resource
(distribution transfer option, distributor transfer options)?
• USE CASE: I‘m writing a client that will connect to
the service based on what‘s in the metadata
– Is service endpoint a distribution linkage?
– How much service operation to describe in metadata and how
much in service-specific document like GetCapabilities, ArcGIS
Rest pages, WSDL…?
51
‗Responsible Party‘
• USE CASE: credit to authors, contact
information to access offline resource, contact
information to report metadata errors
• What if any, is the minimum amount of information for
a contact? – Individual name, organization name, position title – nilable?
– E-mail, telephone?
• How to encode multiple authors?
• Associate icon with organization for generating page
displays
52
Codelists
USE CASE: search for status codes from a
particular vocabulary
• Code list URI’s must be consistently encoded
to enable use of multiple vocabularies
• Should codelist value be considered an
opaque identifier?
• Linkage of codelist terms to ontologies for
semantic query – concept ID vs. concept label
53
Binding Between Service and Data
USE CASE: Where did the data provided by
this service come from—can I trust it?
• Standard offers several choices:
– Operates on
– Coupled resource
– Multiple identification sections in metadata record
54
Other Questions
• When should a metadata record be rejected from
catalog?
• What are possible approaches to quality
assessment, feed back on metadata quality?
• How important is collecting and reporting metadata
usage statistics back to metadata creator?
• How to report entity and attribute description
• How to identify metadata standard and profile used
in a metadata document
55
Summary
• EIP profile is designed to enable metadata
interoperability in Energy Resources Community
– International
– Balance business, science, and engineering concerns
• Draft version will be circulated for comment this
summer
• Intention is to provide a basis for data product
specifications
• If you are a data producer or consumer, your input
on the specification is important
56
For more information …
57
• Go to www.energistics.org
– Asset and Data Management SIG under Communities
• Email: [email protected] or [email protected] or [email protected]
Reactions
And
Questions?
58