Community Mapbuilder

If you drop the ContextCollection format, and adopt Atom Collection  
(which is the same format as an Atom feed) you might lose a little bit  
of Context-centric descriptive richness, but you will gain a lot:
1. ability to subscribe to Collections in your RSS reader (or for  
developers, ability to re-use your RSS reading code)
2. a "free" publishing and update standard
3. a "free" categorization scheme

I attach a sample Atom Publishing Protocol (APP) service document for  
an OWS Context Collection (file: context_service_document.xml) and a  
sample Collection document (file: context_feed.xml).

What do you think of this idea?

---
Raj

Raj,
I like the idea of using a standard like Atom Collection. I can't
think of any implementation arguments for sticking with a
ContextCollection instead. AtomCollection seems to have the key fields
we require which are just Title and URL. Maybe a Description for a
Summary would be useful. But I don't see it as essential.

On Thu, Feb 21, 2008 at 10:35 AM, Raj Singh <rsingh@...> wrote:
> If you drop the ContextCollection format, and adopt Atom Collection
>  (which is the same format as an Atom feed) you might lose a little bit
>  of Context-centric descriptive richness, but you will gain a lot:
>  1. ability to subscribe to Collections in your RSS reader (or for
>  developers, ability to re-use your RSS reading code)
>  2. a "free" publishing and update standard
>  3. a "free" categorization scheme
>
>  I attach a sample Atom Publishing Protocol (APP) service document for
>  an OWS Context Collection (file: context_service_document.xml) and a
>  sample Collection document (file: context_feed.xml).
>
>  What do you think of this idea?
>
>  ---
>  Raj
>
>
>  On Feb 19, 2008, at 5:21 PM, Cameron Shorter wrote:
>
>  > There has been little talk about ContextCollection which is a simple
>  > but effective way to list Context documents. It would be a useful
>  > format to be returned from a Catalog query.
>  >
>  > Files at:
>  > http://svn.codehaus.org/mapbuilder/trunk/mapbuilder/examples
>  >
>  > ContextCollection documents:
>  > projDemo/Proj4jsMapExamples.xml
>  > data/context/worldMapsCollection.xml
>  > data/context/demoCollection.xml
>  > timeSeries/timeSeriesCollection.xml
>  > shipTracks/mapCollection.xml
>  > Demis/mapCollection.xml
>
>
>



-- 
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Commercial Support for Geospatial Open Source Solutions
http://www.lisasoft.com/LISAsoft/SupportedProducts.html

Raj: this looks interesting.  I think this is a great idea in terms of
reuse and mainstream integration.

As well, 

..Tom


> -----Original Message-----
> From: Raj Singh [mailto:rsingh@...] 
> Sent: 20 February, 2008 6:36 PM
> To: Cameron Shorter
> Cc: Jody Garnett; Kralidis,Tom [Burlington]; 
> mapbuilder-devel; openlayers; context.rwg@...
> Subject: Re: [Context.RWG] WMC, OWS Context, and 
> ContextCollection examples
> 
> If you drop the ContextCollection format, and adopt Atom 
> Collection (which is the same format as an Atom feed) you 
> might lose a little bit of Context-centric descriptive 
> richness, but you will gain a lot:
> 1. ability to subscribe to Collections in your RSS reader (or 
> for developers, ability to re-use your RSS reading code) 2. a 
> "free" publishing and update standard 3. a "free" 
> categorization scheme
> 
> I attach a sample Atom Publishing Protocol (APP) service 
> document for an OWS Context Collection (file: 
> context_service_document.xml) and a sample Collection 
> document (file: context_feed.xml).
> 
> What do you think of this idea?
> 
> ---
> Raj
>

Kralidis,Tom [Burlington] wrote:
> Raj: this looks interesting.  I think this is a great idea in terms of
> reuse and mainstream integration.
> 
> As well, 
> 
> ..Tom

Any thoughts about whether we can or cannot move some of this discussion to the OSGeo standards list?

Regards, 
Arnulf. 

>> -----Original Message-----
>> From: Raj Singh [mailto:rsingh@...] 
>> Sent: 20 February, 2008 6:36 PM
>> To: Cameron Shorter
>> Cc: Jody Garnett; Kralidis,Tom [Burlington]; 
>> mapbuilder-devel; openlayers; context.rwg@...
>> Subject: Re: [Context.RWG] WMC, OWS Context, and 
>> ContextCollection examples
>>
>> If you drop the ContextCollection format, and adopt Atom 
>> Collection (which is the same format as an Atom feed) you 
>> might lose a little bit of Context-centric descriptive 
>> richness, but you will gain a lot:
>> 1. ability to subscribe to Collections in your RSS reader (or 
>> for developers, ability to re-use your RSS reading code) 2. a 
>> "free" publishing and update standard 3. a "free" 
>> categorization scheme
>>
>> I attach a sample Atom Publishing Protocol (APP) service 
>> document for an OWS Context Collection (file: 
>> context_service_document.xml) and a sample Collection 
>> document (file: context_feed.xml).
>>
>> What do you think of this idea?
>>
>> ---
>> Raj
>>
> 
> _______________________________________________
> Context.rwg mailing list
> Context.rwg@...
> https://mail.opengeospatial.org/mailman/listinfo/context.rwg

I think that would be fine. The latest schemas are already in a public  
place on OGC Network, so it's not a major change in policy.
---
Raj


On Feb 21, 2008, at 9:54 AM, Arnulf Christl wrote:

> Any thoughts about whether we can or cannot move some of this  
> discussion to the OSGeo standards list?

I just realised that I incorrectly linked to Tom's OWS Context schema 
and example page. Which is at: http://www.ogcnetwork.net/schemas/owc/

Cameron Shorter wrote:
> A few days back, Jody asked for some Context and OWS Context examples, 
> muttering something about updating context support in UDig. I've CCed 
> a couple of other lists that may be interested. Jody, feel free to 
> forward onto the UDig list.
>
> Currently, the authoritative source for OWS Context is Tom Kralidis's 
> site which links to the schema and examples at:
> http://www.opengeospatial.org/standards/wmc 
> <http://www.opengeospatial.org/standards/wmc>
>
> Below are examples from Mapbuilder which can be browsed or downloaded 
> with SVN. They should validate against the spec, but I have not checked.
>
> There has been little talk about ContextCollection which is a simple 
> but effective way to list Context documents. It would be a useful 
> format to be returned from a Catalog query.
>
> Files at:
> http://svn.codehaus.org/mapbuilder/trunk/mapbuilder/examples
>
> ContextCollection documents:
> projDemo/Proj4jsMapExamples.xml
> data/context/worldMapsCollection.xml
> data/context/demoCollection.xml
> timeSeries/timeSeriesCollection.xml
> shipTracks/mapCollection.xml
> Demis/mapCollection.xml
>
> Web Map Context documents:
> data/tasmania/TasmaniaSld.xml
> data/context/locatorCanada.xml
> data/context/worldMapsCollection.xml
> data/context/demoCollection.xml
> data/context/DM_Canada.xml
> data/context/demisWorldMap.xml
> data/context/mars.xml
> data/context/cded.xml
> data/context/cite.xml
> data/context/dutchCbs.xml
> data/context/atlasWorldgroup.xml
> data/context/locatorDemis.xml
> data/context/locatorMap.xml
> data/context/radarsatMosaic.xml
> data/context/boston.xml
> data/context/SLDParamExample.xml
> data/context/metacartaWorldMap.xml
> data/context/local.xml
> data/context/modisWorld.xml
> data/context/lsat7Ortho.xml
> data/context/cite_deegree.xml
> data/context/atlasWorld.xml
> Demis/mapCollection.xml
> Demis/CollectionList.xsl
> Demis/DemisWorldMap.xml
> Demis/BlueMarble.xml
> Demis/USAMap.xml
> Demis/atlasWorld.xml
> mapViewer/LegendOpaque.xsl
> mapViewer/bejingWind.xml
> projDemo/Proj4jsMapExamples.xml
> shipTracks/mapCollection.xml
> shipTracks/CollectionList.xsl
> timeSeries/tsEstPrecip10Day.xml
> timeSeries/timeSeriesCollection.xml
> timeSeries/tsIFGITemp.xml
> timeSeries/tsWorldTemp.xml
> timeSeries/tsGeocomp.xml
> timeSeries/tsEstPrecip.xml
> timeSeries/tsPrecipAnomaly.xml
> wfs-t/tasmania.xml
> wfs-t/tasmaniaSld.xml
>
> OWS Context Documents:
> openlayers/context2.xml
> openlayers/Legend2.xsl
> data/tasmania/TasmaniaContext.xml
> data/context/google.xml
> mergeModels/google.xml
> shipTracks/DemisWorldMap.xml
> shipTracks/BlueMarble.xml
> shipTracks/Legend.xsl
> GeoBliki/DemisWorldMap.xml
> flickr/DemisWorldMap.xml
> flickr/Legend.xsl
> flickr/atlasWorld.xml
>
> -- Cameron Shorter Geospatial Systems Architect Tel: +61 (0)2 8570 
> 5050 Mob: +61 (0)419 142 254 Think Globally, Fix Locally Commercial 
> Support for Geospatial Open Source Solutions 
> http://www.lisasoft.com/LISAsoft/SupportedProducts.html
>
>


-- 
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Commercial Support for Geospatial Open Source Solutions
http://www.lisasoft.com/LISAsoft/SupportedProducts.html