Alignment of CIP and GEO Profiles of Z39'50

1
Alignment of CIP and GEO Profiles of Z39.50

• Clive Best, CEO
• CEOS-PTT
• EOGEO 98, Salzburg

2
What is Z39.50 ?

• A protocol for standard search of and retrieval
  from remote databases.
• Defines a single search interface to multiple
  databases.
• In principle requires no prior knowledge of
  target database.
• Record formats SUTRS (text) GRS-1.

3
Profiles

• Specific communities supported by different
  application profiles of Z.
• Profiles based on Metadata (elements,schemas,attri
  butes).
• Reuse attributes from different profiles for a
  minimum level of interoperable search.
• Z39.50 is session based. Client-Server model.

4
Geospatial Profiles of Z39.50

• Catalogue Interoperable Protocol (CIP)
• International Space Agency effort to define a
  single interface to Earth Observation catalogues.
• Middleware of Retrieval Managers
• GEO Profile
• Federal Geospatial Data commitee ( FGDC)
• Based on FGDC metadata defintion.

5
Geospatial Metadata needed to

• document existing data holdings for internal use
  and application
• support discovery of existing data sets by
  internal and organisations in catalogues
• provide detailed background information to
  accompany a data transfer for advised re-use

6
What is GEO ?

• Implementers guidelines for defining the content
  and potential operations for FGDC geospatial
  metadata in a compliant Z39.50 software system
• GEO is a nested profile, borrowing data
  elements and operations (Relations) from the GILS
  and bib-1 Profiles.

7
GEO Server Side Gateway
8
GEO Client Side Gateway
9
What is CIP ?

• Catalogue Interoperable Profile
  ( CEOS PTT)
• Profile of Z39.50
• Built on Z39.50 Version 3
• Supports Explain
• Supports Extended Services - Ordering, Persistent
  result sets.

10
Retrieval Managers

• CIP is built on Middleware
• Retrieval Managers
• CIP Geospatial Metadata Model
• Collections
• Product Archives
• CIP V2.4 spec planned for April 1998

11
CIP Space
12
Motivation for Collections
13
Distributed Collection Searching
14
CIP/GEO Alignment

• Objective To maximise Interoperability
• Let GEO users search CIP Space
• Let CIP users seach GEO Space
• Support for minimal BIB,GILS search

Alignment Model
15
Alignment Goals

• To provide access to EO, GIS and document
  archives to as wide a user group as possible.
• EO/GEO Resource discovery through Web systems .
• To maximise interoperability across profiles.

16
Alignment Goals 2

• To allow profile specific clients to have shared
  multiple access.
• To allow new geospatial JAVA based Z39.50 clients
  to be constructed.
• EO applications need access to non-space GIS
  data.
• GEO applications need access to EO product
  archives

17
PA
CIP Interoperability with GEO
GS
GS
GS
GS
RM
GS
RM
CIP Client
PA
PA
RM
PA
CIPcommunication
TR
RM
PA
GS - Geo Server TR - Translator PA - Product
Archive
TR
18
GEO interoperating with CIP
GS
GS
GS
GS
http
GS
Client
CH
RM
TR
PA
HTTP
RM
RM
TR
GEO
PA
CIP
PA
TR
TR
PA
19
Alignment details

• Map Common elements from both profiles
• Renumber attributes of CIP
• Add SUTR SGML support to CIP
• New Interoperable attribute set
• Collection discovery through IDN and Clearing
  House
• Product search through RMs.

20
A. Collection/GEO Discovery B. Remote Search
GEO Client
A
Clearing House or CEONet
FGDC Metadata
B
...............
C1
C2
G1
G2
RM local pr/search
RM local pr/search
GEO DB
GEO DB
FGDC Metadata
Product Archives
CIP Metadata Product Descriptors
C1
C2
21
(No Transcript)
22
Next Steps

• GEO has 60 operational servers
• CIP becomes operational in 1998.
• CEO Enabling Services Release A
• CEO Release B end of 1998
• NASA gateway to ECS
• ESA Gateway to MUIS
• CIP V2.4 and GEO 2.X will be aligned

23
Future Plans

• First Clients giving access to EO and GIS
  metadata late 1998 early 1999.
• Longer term CIP GEO move towards a common
  schema TC211.