[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [regrep] OGC Web Services and ebRIM, Part II
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
Attachment:
Chiusano_Joseph.vcf
Description: Card for Joseph Chiusano
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC