[georss] Request For Comments

Peter Borissow peter.borissow at yahoo.com
Tue Mar 20 15:25:17 EDT 2007


I suggest adopting gml multipoint, multiline, and multipolygon to address the issue of multiple geometries instead of creating multiple "where" nodes for a single item.

I know this doesn't address the issue of time but it does keep us closer to gml and kml.

As for the notion of time, perhaps it's time to introduce a "georss:when" tag - a child of the "georss:where" node?

Since it appears the xml schema is broken anyway, perhaps we can add multi-geometries now before it's too late.

Any thoughts? 
Peter





----- Original Message ----
From: "Knoth, Brian D." <bknoth at mitre.org>
To: georss at lists.eogeo.org
Sent: Tuesday, March 20, 2007 12:24:12 PM
Subject: [georss] Request For Comments


You all might remember that a while back I started a discussion on
representing multiple locations for a single rss item and also
associating time periods with those locations. I've received many
suggestions for loosely associating time with locations by using a
separate time extension under the item and link that to the location it
represents. As much as I'm not very comfortable with this approach, it
does address the problem without any modifications to the georss
specification. As such, here is an example of what I have come up with
and I'd appreciate any comments before we move forward with this
implementation. Thanks for all the help - brian.

<rss version="2.0" xmlns:kml="http://earth.google.com/kml/2.1";
xmlns:georss="http://www.georss.org/georss"; >
    <channel>
    .
    .
    .
        <item>
            <title>...</title>
            <link>...</link>
            <description>...</description>
            <guid>...</guid>
            <pubDate>...</pubDate>
            <author>...</author>
            <kml:TimeSpan targetId="is-routepoint-2.1">
    
<kml:begin>2006-05-19T14:30:00Z</kml:begin>
                <kml:end>2006-05-19T14:30:00Z</kml:end>
            </kml:TimeSpan>
            <kml:TimeSpan targetId="is-routepoint-0.1">
    
<kml:begin>2006-05-19T15:00:00Z</kml:begin>
                <kml:end>2006-05-19T17:00:00Z</kml:end>
            </kml:TimeSpan>
            <kml:TimeSpan targetId="is-routepoint-3.1">
    
<kml:begin>2006-05-19T17:26:00Z</kml:begin>
                <kml:end>2006-05-19T17:26:00Z</kml:end>
            </kml:TimeSpan>
            <georss:where
relationshiptag="is-routepoint-2.1" featuretypetag="location-TKF">
                <gml:Point
xmlns:gml="http://www.opengis.net/gml";>
                    <gml:pos>26.27083378146544
50.63361197482741</gml:pos>
                </gml:Point>
            </georss:where>
            <georss:where
relationshiptag="is-routepoint-0.1" featuretypetag="location-ARCP">
                <gml:Point
xmlns:gml="http://www.opengis.net/gml";>
                    <gml:pos>28.3524375
47.991434393914595 24000.0</gml:pos>
                </gml:Point>
            </georss:where>
            <georss:where
relationshiptag="is-routepoint-3.1" featuretypetag="location-LND">
                <gml:Point
xmlns:gml="http://www.opengis.net/gml";>
                    <gml:pos>26.27083378146544
50.63361197482741</gml:pos>
                </gml:Point>
            </georss:where>
        </item>
    </channel>
</rss>
_______________________________________________
georss mailing list
georss at lists.eogeo.org
http://lists.eogeo.org/mailman/listinfo/georss


 
____________________________________________________________________________________
TV dinner still cooling? 
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/



More information about the georss mailing list