[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [regrep] OGC Web Services and ebRIM, Part II
To followup on Joe's message... I was invited to speak at the meeting of the OGC Catalog RWG on Monday 2/10 at the OGC meeting in Washngton DC. Here are some summary impressions from that meeting: -I was impressed by the depth and breadth of knowledge that the Catalog RWG members had about registries in general, ebXML Registry, JAXR and related specifications. -They seemed to like the new V3 capabilities and had a good discussion on various features. I came back with several good suggestions for V4. -The OGC OWS1 Registry Service v0.74 specification builds upon ebRIM 2.1 and extends it. -There was at least one (possibly 2 or 3) companies there that had prototyped an OGC OWS1 Registry Service based upon ebRIM 2.1. -I suggested that they consider a slight change to their approach and define their own OGC Information Model and define a normative binding to ebXML Registry V3. -The OGC OWS1 Registry Service work is an excellent test case for ebXML Registry. IMO, We should invite a member of OGC Catalog RWG to be active in our TC as a recognized liaison and to influence our V4 work positively. I very much look forward to continued interactions and cooperation between OGC and ebXML Registry. PS: If anyone from OGC Catalog RWG present at the meeting on 2/10 wishes to followup, please feel free to post your own impresions. -- Regards, Farrukh Chiusano Joseph wrote: >I attended a session on OpenGIS at yesterday's Web-Enabled Government >conference here in Washington, and I asked the presenter about the ebRIM >plans for the OGC Web Services Registry. He stated that this aspect >will not be incorporated until some time in 2004. > >- Joe > >Chiusano Joseph wrote: > > >>For those interested in learning more about this topic: >> >>I found an even better reference [1] this morning - I've summarized the >>highlights from that document below, and have extracted some of the >>figures into a separate (attached) Word doc for your quick reference. >> >>If you're still curious (and have not deleted this by now!), the >>following topics are covered below: >> >>- GENERAL INFO >>- GOAL/NEED >>- WHY NOT JUST WSDL? >>- ARCHITECTURE >>- BINDING TEMPLATES >>- ebRIM >> >>Thanks! >>Joe >> >>GENERAL INFO: >> >>- This document describes the OGC (Open Geodata Consortium) Web Services >>Architecture; >> >>- OGC Web Services (OWS) provide a vendor-neutral, interoperable >>framework for Web-based discovery, access, integration, analysis, >>exploitation, and visualization of multiple online geodata sources, >>sensor-derived information, and geoprocessing capabilities; >> >>GOAL/NEED: >> >>- Goal is transparent access to heterogeneous geodata and geoprocessing >>services; >> >>- The strong information- and content-oriented focus of GIS Web services >>has led to a further development of architectural patterns for flexible >>information search and retrieval for general content-oriented Web >>services, based on a dynamic binding template; >> >>- There has also been a need to support early binding and a consistent >>way of "chaining" of Web services (as described in ISO19119) >> >>WHY NOT JUST WSDL?: >> >>- WSDL provides only some of what is needed >> >>- Granularity does not match early/late binding behavior >> >>- Datatypes not expressive enough >> >>- Enumerations not powerful enough for real world content >> >>- OpenGIS interface specifications mainly provide semantic definitions >>of parameters - these are not per-service >> >>ARCHITECTURE: >> >>- OpenGIS Web Services Architecture: See Figure 1 in attached document >>(note that OGC Web Services are comprised of various services such as >>"Web Registry Service", "Web Map Service", etc.) >> >>BINDING TEMPLATES: >> >>- Reference objects from registries that define the semantics of a >>service >> >>- May reference each other, creating the service chain to be invoked and >>allowing mix of early and late binding >> >>- Web Map Server example: See Figure 2 in attached document >> >>ebRIM: >> >>- Relationship of Binding Template to RegistryEntry: See Figure 3 in >>attached document >> >>[1] >>http://www.google.com/url?sa=U&start=3&q=http://www.omg.org/news/meetings/workshops/presentations/WebServices_2002/11-1_Atkinson-Berre-ArchPattOpenGISWS2.pdf&e=912 >> >> ------------------------------------------------------------------------ >> Name: OpenGIS Figures.doc >> OpenGIS Figures.doc Type: Microsoft Word Document (application/msword) >> Encoding: BASE64 >> >>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC