1 / 11

Core Task Status, AR-07-01

Core Task Status, AR-07-01. Doug Nebert September 22, 2008. Task Elements. GEOSS Common Infrastructure (GCI) Component and Service Registry Standards and Interoperability Registry User Requirements Registry Best Practices Wiki (under separate task) Web Portal and Clearinghouse

cicada
Download Presentation

Core Task Status, AR-07-01

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Core Task Status, AR-07-01 Doug Nebert September 22, 2008

  2. Task Elements • GEOSS Common Infrastructure (GCI) • Component and Service Registry • Standards and Interoperability Registry • User Requirements Registry • Best Practices Wiki (under separate task) • Web Portal and Clearinghouse • Coordination between the Component and Service Registry and the Standards and Interoperability Registry • Reporting separately: • Best Practices Wiki • IP3 • Standards and Interoperability Forum

  3. GEOSS Common Infrastructure (GCI) • Initial Operating Capability (IOC) Task Force created to document the requirements and support evaluation of GCI offered components • Web Portal candidates: ESRI, Compusult, ESA • GEOSS Clearinghouse candidates: Compusult, ESRI, ESA/GeoNetwork, and USGS • Standards and Interoperability Registry, Component and Service Registry, Best Practices Wiki are all operational and are being maintained.

  4. Component and Service Registry • Offered by USA, deployed by George Mason University • Deployed using Sun Java Enterprise Service Registry with ebRS, CSW ebRIM, UDDI, and JAXR interfaces • 105 Components, 90 Services registered • Components are associated with SBAs • Services are linked with one or more standards registered with GEOSS • Need to increase awareness in and registration of services – will work to simplify the process to focus on Services

  5. Standards and Interoperability Registry • Over 100 standards are identified with authority references, definitions, URN (ID), and are classified in a hierarchy of standard types • Content nominated by individuals through online web form • Content checked and approved by the SIF • Standards represent official de jure and de facto standards with a maintenance body • Special arrangements represent practices that are not recognized as standards but are described as documentation for others

  6. Standards and Services • Coordination between the Service Registry and the Standards Registry is still being implemented to allow: • Nomination of a new Interoperability Arrangement (IA, standard or special arrangement) from within the Component and Service Registry • Current view of available IAs from within the Service Registry as picklist synchronized from special web service • Anticipated integration complete by November 2008

  7. UDDI JAXR ebRS Registries Interaction OGC CSW Z39.50/ SRU Z39.50/ SRU Web UI Web UI GEOSS Standards Registry GEOSS Component and Service Registry GEOSS Components GEOSS Standards GEOSS Special Arrangements GEOSS Services may become reference offer expose nominate U.S.A. IEEE GEO Members and Participating Organizations External Standards Bodies SIF Subject Matter Experts

  8. User Requirements Registry • UIC Task (US-07-01) plans to develop a registry to store EO requirements for identified classes of users in support of applications (SBAs) • White paper written to document the design of a requirements database • Database was deployed by USGS with a Web administrative interface for evaluation • Presented interface to GEO UIC Air Quality Workshop on May 5, 2008 in Toronto • Further acceptance testing and development on-hold due to time constraints of technical lead • Intention is to hand-craft archetypical users and requirements for selected applications and to develop harvest of existing requirements systems (CEOS/WMO, NASA, NOAA, ESA)

  9. EO Ontologies (Related Task) • Proposed separate task led by Japan to organize and register EO ontologies • User requirements registry will require a common set of observables that can be used to link with the Service Registry and potentially the Standards Registry • A common GEOSS ontology, recognizing each concept/term in the context of the source or authority is required to make this connection, to identify coverage, and to identify gaps in EO data collection

  10. GEO Web Portals • Three solutions offered to GEO from: • Compusult • ESRI • ESA • Common set of requirements, refined through AI Pilot Phase 1 (2007) • Provide focused access to registries, distributed resource descriptions (Clearinghouse), and other resources (RSS, web search, applications)

  11. GEOSS Clearinghouse • A federated search facility that will harvest or search all registered catalogues (registered as GEOSS services) making all content searchable through one API • Web portal provides human UI, Clearinghouse provides catalog search API • Four solutions: • ESA/GeoNetwork • Compusult • ESRI • USGS

More Related