HMA Catalogue ICD

1
HMA Catalogue ICD
HMA Standards Workshop, 28 April 2006,
Frascati Yves Coene, SPACEBEL Jolyon Martin, ESA
EOP-G
2
Approach

• Current
• EOLI-XML ICD
• Two new approaches using same base schemas
• OGC WFS
• OGC CSW ISO Profile
• Two different catalogue interfaces metadata
  for
• Collection metadata
• Product metadata

3
Background

• Abstract specifications
• ISO19115 - products
• ISO19119 services
• OGC CAT CSW 2.0 will be submitted to ISO
• XML Encoding
• ISO19139 XML encoding for ISO19115/19119
• OGC CAT CSW Profile ISO19115/19119 (draft)

4

• PART I Product Catalogues

5
Comparison

• OGC CSW ISO Profile
• GetRecords
• GetRecordsById
• OGC Filter ISO 19143
• SOAP, WSDL
• Is not an ISO standard
• Is draft OGC specification
• EOLI-XML
• Search
• Present
• Ad hoc "Filter", hard-coded
• SOAP, WSDL
• OGC Best Practices

• OGC WFS
• GetFeature(ohrdatastrip)
• GetFeature
• OGC Filter ISO 19143
• SOAP, WSDL (?)
• Is ISO standard 19142
• Is stable OGC specification

6
Namespaces
sar.xsd
ohr.xsd
atm.xsd
Catalogue metadata for specific EO mission type
hma.xsd
Catalogue metadata for Earth Observation
smXML - gmd (ISO 19139)
Generic and geometric catalogue metadata
gml
Namespaces for radar missions
Namespaces for optical missions
Namespaces for atmospheric products
7
Namespaces
phr.xsd
Additional metadata for Pleiades
ohr.xsd
Catalogue metadata for optical high
resolution EO mission type
hma.xsd
Catalogue metadata for Earth Observation
gmd.xsd (ISO 19139)
Generic and geometric catalogue metadata
gml (OGC)
Namespaces for optical mission, e.g. Pleiades,
which has additional requirements
8
Namespaces

• gmd deprecates smXML in ISO 19139. Also used in
  Metafor specification which is the profile
  implementation of 19139 for French Defense users.

9
Product Catalogue

• TBD

10
Requirements

• Server must implement namespaces gml, smXML, hma.
• Server can optionally implement atm, ohr, sar or
  higher.
• Client only understanding gml, smXML/gmd and hma
  should be able to query all of the above servers.
• Issue what with unsupported namespaces returned
  by server ?

11
EODAIL workflow
OGC CSW ISO Profile / HMA Web service endpoint
WSDL SOAP getRecords()
HMA CSW Catalogue
BPEL process
sar
request
Radar CSW Catalogue
ohr
Optical CSW Catalogue
12
OGC CSW ?

• Where does datastrip fit in ? Replaces "other"
  in OGC CSW ISO Profile schema ?
• Does it become hmadatastrip or ohrdatastrip ?

13
Issues ...

• in CSW ISO Profile r4, the WSDL file
  csw201_ApIso.wsdl cannot be validated using
  XMLSpy 2006 "target namespace of imported
  schemas must differ from namespace of enclosing
  schema".
• What determines compliance with OGC CSW ISO
  Profile ?
• Can we thus replace the schema in annex D by ours
  ? This seems to be suggested by the sentence
  "ltSearchResultsgt element is a generic XML
  container". What constraints are to be respected
  to remain "complaint" ? According to 8.4.3,
  annex D provides "examples" and thus not
  mandatory schemas ?

14
Issues ...

• OGC CSW ISO Profile
• 8.2.2.1.2 "The actual records returned by the
  catalogue are a substitute of the element
  ltcswAbstractRecordgt.... " and "Catalogue
  services implementing this application profile
  MUST NOT substitute ltcswAbstractRecordgt but
  rather ltxsanygt with XML documents that comply
  with one of the schemas defined in Annex D "
• Purpose of "ltxsdelement ref"cswAbstractRecord"
  minOccurs"0" maxOccurs"unbounded"/gt"?
• Does gml fit with gmd namespace ?

15
Proposed Actions

• Agree on gmd field inclusion
• Agree on allocation of fields to hma, ohr, gmd
  fields.
• Agree on dataset / collection columns
• Agree on brief, summary, full columns
• Agree on atm.xsd
• Agree on sar.xsd
• Define OGC CSW ISO Profile (variant) using hma
  schemas (only for dataset catalogues ?)

16
Proposed Actions

• Check feasibility of approach with COTS and
  open-source components.

17

• PART II Collection Catalogues

18
Collection Catalogue

• TBD

19
JRC-Conterra-ESA test
OGC CSW ISO Profile Web service endpoint
WSDL SOAP getRecords()
BPEL process
Requestfrom JRC Portal
Collectionmetadata
Any API
INFEO collection descriptions in XML files

• Main issues
• Core queryables meaningless for product data
• Parse/interpret Filter language with "and", "or"
• Convert response to CSW response

20

• INFEO-style collection descriptions in XML format

21
Example Asa.xml

• lt?xml version"1.0" encoding"UTF-8"?gt
• ltCollectionDescriptor xmlnsxsi"http//www.w3.org
  /2001/XMLSchema-instance" urn"URNCIPESAENVISAT
  _ASA_IMx_xS" version"2.4" approved"yes"
  gatewaydb"http//muiscx3.esrin.esa.int8090/ARC_E
  SA.EECF.ENVISAT_ASA_IMx_xS" collectionid"z39.50s
  //mwnd.infeo.org10000/ARC_ENVISAT_ASA_IMx_xS965"
  gateway"193.204.228.9212345" schema"1.2.840.100
  03.13.1000.99.2" attributedetails"DEF-DB-CIP-PROD
  UCT" termlistinfo"DEF-DB-CIP-PRODUCT"gt
• ltItemDescriptorIdgtENVISAT_ASA_IMx_xSlt/ItemDescrip
  torIdgt
• ltItemDescriptorNamegtESA ENVISAT ASAR Image Mode
  Striplineslt/ItemDescriptorNamegt
• ltAuthoritative/gt
• ltItemDescriptorLongName/gt
• ltItemDescriptorLanguagegtenlt/ItemDescriptorLanguag
  egt
• ltCollectionTypegt
• ltCollectionHierarchyCategorygtproductlt/Collection
  HierarchyCategorygt
• ltCollectionHierarchyPositiongtterminallt/Collectio
  nHierarchyPositiongt
• ltCollectionCategorygtproviderlt/CollectionCategory
  gt
• lt/CollectionTypegt
• ltProductCollectionSpecificgt
• ltArchivingCentreIdgtESA/ESRINlt/ArchivingCentreIdgt
  
• ltDataOriginatorgt
• ltOriginator/gt
• ltProjectName/gt
• ltPlatformgt
• ltMissionIdgtENVISATlt/MissionIdgt

22
HMA Prototype

• GeoNetwork
• Collection catalogue as part of DAIL
• User interface to allow Partners to enter
  metadata in Collection Catalogue
• OGC CSW ISO Profile compliant version for
  September 2006 ?

23
Issue Web services

• W3C / OASIS Web services versus OGC HTTP/Post and
  KVP Web services
• SOAP/WSDL are part of (large) Web service stack
• Allows adding security (ws-security),
  asynchronous communication (ws-addressing),
  policy management (ws-policy, SAML), discovery
  (UDDI), reliable messaging etc.
• COTS and open-source available implementing this
  stack instead of ad-hoc implementations
  security, policy management, workflow, discovery,
  ...

24
Service Discovery
HMA Standards Workshop, 27 April 2006, FAO,
Rome Yves Coene, SPACEBEL Jolyon Martin, ESA
EOP-G
25
Session Objective

• Raise some issues to start discussion
• Get as much feedback as possible

26

• Two mutual exclusive approaches
• UDDI for discovery of service bindings from COTS
  (e.g. Workflow tools).
• OGC CSW needed for discovery based on
  geographical coverage as UDDI v3 too limited ?
• Best of two worlds ?

27

• Is all of this needed ?
• UDDI for finding WSDL files
• GetWSDL() as part of OWS-Common for each OGC Web
  service ?
• GetCapabilities()

28

• From data to services or vice versa ?
• Find services and then which data sets they apply
  to
• Or find datasets and then which services can be
  applied to them (WMS, WCS, ...)
• How to do this in a "standard" way with UDDI and
  or CSW ?
• Is this "discovery" needed in both directions ?

29

• Agree on minimal reqs for discovery (related to
  EO catalogue) ?
• Find collection names provided by the catalogue
• Find query model supported by catalogue (e.g.
  Filter Encoding or a subset)
• Find schema supported by catalogue, e.g. hma.wsd
  or ohr.xsd.

30

• Metadata for services in
• ISO 19119 catalogue
• OASIS UDDI
• GetCapability of OGC service
• Is this duplication/redundancy causing a problem
  of ownership/authority ?
• Which of these three is the "original" data ?
• Can duplication be avoided ?

31

• OGC CSW ISO Profile
• "Future work may include the extension of the
  profile to interoperate with UDDI service
  registry instances."

32
Discussion

• Discussion ...