[georss] [OpenLayers-Users] GeoRSS and layers

Carl Reed OGC Account creed at opengeospatial.org
Wed Jan 17 11:23:07 EST 2007


I agree with Sean that it is not such a good idea to mix content (feature 
geometry) and presentation. Always causes problems (and limitations) 
downstream.

Cheers

Carl

----- Original Message ----- 
From: "Sean Gillies" <sgillies at frii.com>
To: <georss at lists.eogeo.org>
Sent: Tuesday, January 16, 2007 7:35 AM
Subject: Re: [georss] [OpenLayers-Users] GeoRSS and layers


> Mikel Maron wrote:
>> Hi Yves
>>
>> Yes, both "GeoRSS" and "MediaRSS" are namespaces for focused extensions 
>> to RSS feeds.
>> I think it's a good idea to reuse existing standards and conventions when 
>> appropriate and easy,
>> and in worldKit, GeoRSS and elements of MediaRSS are used to do just what 
>> you intend.
>> And "category" seems a good analogy to layer.
>>
>> The SVG comment was kind of offhand and not thought through. Really I was 
>> only particularly thinking
>> of the styling properties of SVG .. 
>> http://www.w3.org/TR/SVG11/styling.html .. which more or less
>> covers the kind of things in SLD.
>>
>> With worldKit, the needs for styling (which is accomplished through a 
>> seperate xml config file) have been
>> basically (circle, square, triangle) scale, linestyle, color, alpha, & 
>> thickness. That group of styles is
>> "lightweight" .. easy to understand and implement.
>>
>> Perhaps CSS is appropriate for specifying styling information for GeoRSS. 
>> Lots of issues there, but I
>> quite like that direction.
>>
>> Mikel
>
> Mikel, I like the CSS approach too, and OpenLayers has been making big
> strides towards being more friendly to user CSS.
>
> On the other hand, I don't think that GeoRSS should get too concerned
> with feature symbolization. In my opinion, once you start mixing feature
> geometry and styling together, these elements are no longer metadata
> fields in the same class as "author", "published", and "updated", but
> become *content*. In the Atom case, you'd have to put this stuff in an
> atom content element. We're already free to put just about anything in
> an atom content element including KML, SVG, or SLD with inline features,
> so there's no need to invent anything new for that purpose.
>
> Cheers,
> Sean
>
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss 




More information about the georss mailing list