[OSGeo-Standards] OWS Context and others OGC interactions

Kralidis,Tom [Burlington] Tom.Kralidis at ec.gc.ca
Tue Oct 23 13:29:03 EDT 2007


 

> -----Original Message-----
> From: Jody Garnett [mailto:jgarnett at refractions.net] 
> Sent: 23 October, 2007 1:03 PM
> To: Kralidis,Tom [Burlington]
> Cc: Lorenzo Becchi; standards at lists.osgeo.org
> Subject: Re: [OSGeo-Standards] OWS Context and others OGC interactions
> 
> Kralidis,Tom [Burlington] wrote:
> > Hi,
> >
> > Jody is correct.  OWS Context allows for an Extension element.
> >
> > Currently, in OWS Context 0.2.0
> > (http://www.ogcnetwork.net/schemas/owc/0.2.0/owsContext.xsd), 
> > extensions are allowed wihtin the General element, and _within_ the 
> > AbstractResourceType, where AbstractResourceType is
> > Layer|Coverage|FeatureType.
> >   
> Can you email us an example Tom? I cannot (obviously) see the 
> wiki page Cameron sent out earlier and I don't think the 
> example file included either of these Extentions.

Let's say we supported owc:Extension at the AbstractResourceType level,
then:

1./ Define the namespace which will apply to the owc:Extension'd
construct:

xmlns:osgeo="http://www.osgeo.org/webmapping"

2./

Encode your bits within owc:Extension:

<owc:Extension>
 <osgeo:GoogleMap>
  ...
  ...
 </osgeo:GoogleMap>
</owc:Extension>

Everything within owc:Extension of type osgeo:* is left to your own
devices (some people also call this fairy dust), and won't draw
complaints from a validating parser.

The key here would be for a community agreement on the definition of the
extension.  Has there been any effort at this to date?



> > It has been discussed to allow extension at the 
> ResourceList level, to 
> > allow for Layer|Coverage|FeatureType|whatever, but there have been 
> > concerns of hindering interoperability.  At the same time, if folks 
> > are going to do this anyway...
> >   
> We are; even for OGC projects like OWS-3 this is where we 
> needed to extend things. It was in the recomendations for 
> that project as I recall.
> > Having said this, if folks think this is useful, we could look at 
> > examples of how to use Extensions at the AbstractResourceType level.
> >   
> Please ;-)
> > Standards are useful :)
> >   
> Go Tom go!
> Jody
> 


More information about the Standards mailing list