|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
|
|
Yet another flavor of GeoRSS?I'm having a discussion in an OpenLayers ticket about whether users
ought to be able to expect the following two feeds to be treated equivalently: 1) Atom feed with GeoRSS location metadata: <feed xmlns="http://www.w3.org/2005/Atom" xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml" /> <entry> <title>Foo</title> <summary>Yet another item about Foo</summary> <georss:where> <gml:Point> <gml:pos>0.0 51.0</gml:pos> </gml:Point> </georss:where> </entry> </feed> 2) Google Maps Data API feature feed: <feed xmlns="http://www.w3.org/2005/Atom"> <entry> <title>Foo</title> <content type="application/vnd.google-earth.kml+xml"> <Placemark xmlns="http://www.opengis.net/kml/2.2"> <name>Foo</name> <description>Yet another item about Foo</description> <Point> <coordinates>51.0,0.0,0.0</coordinates> </Point> </Placemark> </content> </entry> </feed> Thoughts? -- Sean _______________________________________________ georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
|
|
Re: Yet another flavor of GeoRSS?I think so. Title/Summary in Atom and Name/Description in KML are
designed to serve the same purpose. On Wed, Sep 9, 2009 at 10:00 PM, Sean Gillies<sean.gillies@...> wrote: > I'm having a discussion in an OpenLayers ticket about whether users > ought to be able to expect the following two feeds to be treated > equivalently: > > 1) Atom feed with GeoRSS location metadata: > > <feed > xmlns="http://www.w3.org/2005/Atom" > xmlns:georss="http://www.georss.org/georss" > xmlns:gml="http://www.opengis.net/gml" > /> > <entry> > <title>Foo</title> > <summary>Yet another item about Foo</summary> > <georss:where> > <gml:Point> > <gml:pos>0.0 51.0</gml:pos> > </gml:Point> > </georss:where> > </entry> > </feed> > > 2) Google Maps Data API feature feed: > > <feed xmlns="http://www.w3.org/2005/Atom"> > <entry> > <title>Foo</title> > <content type="application/vnd.google-earth.kml+xml"> > <Placemark xmlns="http://www.opengis.net/kml/2.2"> > <name>Foo</name> > <description>Yet another item about Foo</description> > <Point> > <coordinates>51.0,0.0,0.0</coordinates> > </Point> > </Placemark> > </content> > </entry> > </feed> > > Thoughts? > > -- > Sean > > _______________________________________________ > georss mailing list > georss@... > http://lists.eogeo.org/mailman/listinfo/georss > georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
|
|
Re: Yet another flavor of GeoRSS?Don't think so.
You need to specify a new namespace for the Atom extension (georss). Now, the difference between pos and coordinates tags is beyond me. Pat. On Sep 9, 2009, at 8:00 AM, Sean Gillies wrote: > I'm having a discussion in an OpenLayers ticket about whether users > ought to be able to expect the following two feeds to be treated > equivalently: > > 1) Atom feed with GeoRSS location metadata: > > <feed > xmlns="http://www.w3.org/2005/Atom" > xmlns:georss="http://www.georss.org/georss" > xmlns:gml="http://www.opengis.net/gml" > /> > <entry> > <title>Foo</title> > <summary>Yet another item about Foo</summary> > <georss:where> > <gml:Point> > <gml:pos>0.0 51.0</gml:pos> > </gml:Point> > </georss:where> > </entry> > </feed> > > 2) Google Maps Data API feature feed: > > <feed xmlns="http://www.w3.org/2005/Atom"> > <entry> > <title>Foo</title> > <content type="application/vnd.google-earth.kml+xml"> > <Placemark xmlns="http://www.opengis.net/kml/2.2"> > <name>Foo</name> > <description>Yet another item about Foo</description> > <Point> > <coordinates>51.0,0.0,0.0</coordinates> > </Point> > </Placemark> > </content> > </entry> > </feed> > > Thoughts? > > -- > Sean > > _______________________________________________ > georss mailing list > georss@... > http://lists.eogeo.org/mailman/listinfo/georss _______________________________________________ georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
|
|
|
|
|
Re: Yet another flavor of GeoRSS?Hi Sean,
I don't think they are the same thing, although perhaps the effect should be the same. In my view, the georss is metadata about the content, whereas the KML is the content. The gdata feed is just one organization's implementation of content. Other organizations are going to have different content, geospatial or otherwise. The georss should be at a conceptual level above content, allowing any content to be mapped/located. Then an individual organization can implement how to handle their own content appropriately, based on the mime type. My $0.02 Cheers, Peter > -----Original Message----- > From: georss-bounces@... > [mailto:georss-bounces@...] On Behalf Of Sean Gillies > Sent: September 9, 2009 8:00 AM > To: GeoRss georss@... > Subject: [georss] Yet another flavor of GeoRSS? > > I'm having a discussion in an OpenLayers ticket about whether > users ought to be able to expect the following two feeds to be treated > equivalently: > > 1) Atom feed with GeoRSS location metadata: > > <feed > xmlns="http://www.w3.org/2005/Atom" > xmlns:georss="http://www.georss.org/georss" > xmlns:gml="http://www.opengis.net/gml" > /> > <entry> > <title>Foo</title> > <summary>Yet another item about Foo</summary> > <georss:where> > <gml:Point> > <gml:pos>0.0 51.0</gml:pos> > </gml:Point> > </georss:where> > </entry> > </feed> > > 2) Google Maps Data API feature feed: > > <feed xmlns="http://www.w3.org/2005/Atom"> > <entry> > <title>Foo</title> > <content type="application/vnd.google-earth.kml+xml"> > <Placemark xmlns="http://www.opengis.net/kml/2.2"> > <name>Foo</name> > <description>Yet another item about Foo</description> > <Point> > <coordinates>51.0,0.0,0.0</coordinates> > </Point> > </Placemark> > </content> > </entry> > </feed> > > Thoughts? > > -- > Sean > > _______________________________________________ > georss mailing list > georss@... > http://lists.eogeo.org/mailman/listinfo/georss > georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
|
|
Re: Yet another flavor of GeoRSS?Expecting RSS parsers to also be able to parse KML content and use the
GeoData as it would a more standard GeoRSS feed just seems wrong to me. So I say no that not really a 'flavor' of GeoRSS, but just KML encapsulated in a RSS feed, and should be treated differently. On 09/09/2009, Sean Gillies <sean.gillies@...> wrote: > I'm having a discussion in an OpenLayers ticket about whether users > ought to be able to expect the following two feeds to be treated > equivalently: > > 1) Atom feed with GeoRSS location metadata: > > <feed > xmlns="http://www.w3.org/2005/Atom" > xmlns:georss="http://www.georss.org/georss" > xmlns:gml="http://www.opengis.net/gml" > /> > <entry> > <title>Foo</title> > <summary>Yet another item about Foo</summary> > <georss:where> > <gml:Point> > <gml:pos>0.0 51.0</gml:pos> > </gml:Point> > </georss:where> > </entry> > </feed> > > 2) Google Maps Data API feature feed: > > <feed xmlns="http://www.w3.org/2005/Atom"> > <entry> > <title>Foo</title> > <content type="application/vnd.google-earth.kml+xml"> > <Placemark xmlns="http://www.opengis.net/kml/2.2"> > <name>Foo</name> > <description>Yet another item about Foo</description> > <Point> > <coordinates>51.0,0.0,0.0</coordinates> > </Point> > </Placemark> > </content> > </entry> > </feed> > > Thoughts? > > > -- > Sean > > _______________________________________________ > georss mailing list > georss@... > http://lists.eogeo.org/mailman/listinfo/georss > georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
|
|
Re: Yet another flavor of GeoRSS?I concur -
Just some additional input to consider: GML is grounded in the abstract model ISO 19107 spatial schema (as well as other ISO standards) and has the abstraction "feature". GML defines features distinct from geometry objects. A feature is an application object that represents a physical entity. Geometry is a property of a feature. While GeoRSS does not explicitly utilize "feature", KML has no concept of "feature" (I suspect some would argue this . . .). KML is a grammar for expressing geographic annotation and visualization in Earth Browser apps. As such, remember that GML and KML evolved from a different set of requirements and use cases. Hence, stating "equivalence" can be difficult at best. Regards Carl ----- Original Message ----- From: "Barry Hunter" <barry@...> To: "Sean Gillies" <sean.gillies@...> Cc: <georss@...> Sent: Wednesday, September 09, 2009 7:51 AM Subject: Re: [georss] Yet another flavor of GeoRSS? > Expecting RSS parsers to also be able to parse KML content and use the > GeoData as it would a more standard GeoRSS feed just seems wrong to > me. > > So I say no that not really a 'flavor' of GeoRSS, but just KML > encapsulated in a RSS feed, and should be treated differently. > > > On 09/09/2009, Sean Gillies <sean.gillies@...> wrote: >> I'm having a discussion in an OpenLayers ticket about whether users >> ought to be able to expect the following two feeds to be treated >> equivalently: >> >> 1) Atom feed with GeoRSS location metadata: >> >> <feed >> xmlns="http://www.w3.org/2005/Atom" >> xmlns:georss="http://www.georss.org/georss" >> xmlns:gml="http://www.opengis.net/gml" >> /> >> <entry> >> <title>Foo</title> >> <summary>Yet another item about Foo</summary> >> <georss:where> >> <gml:Point> >> <gml:pos>0.0 51.0</gml:pos> >> </gml:Point> >> </georss:where> >> </entry> >> </feed> >> >> 2) Google Maps Data API feature feed: >> >> <feed xmlns="http://www.w3.org/2005/Atom"> >> <entry> >> <title>Foo</title> >> <content type="application/vnd.google-earth.kml+xml"> >> <Placemark xmlns="http://www.opengis.net/kml/2.2"> >> <name>Foo</name> >> <description>Yet another item about Foo</description> >> <Point> >> <coordinates>51.0,0.0,0.0</coordinates> >> </Point> >> </Placemark> >> </content> >> </entry> >> </feed> >> >> Thoughts? >> >> >> -- >> Sean >> >> _______________________________________________ >> georss mailing list >> georss@... >> http://lists.eogeo.org/mailman/listinfo/georss >> > _______________________________________________ > georss mailing list > georss@... > http://lists.eogeo.org/mailman/listinfo/georss _______________________________________________ georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
|
|
Re: Yet another flavor of GeoRSS?I agree, Peter, and it would be nice to see georss:where elements in
the Google feature feeds. I think there's inevitable dissonance when syndicating XML-based geographic data. As Andrew said, it's like embedding OOXML chapters in an ODF book. Thanks for the comments, everyone. Cheers, Sean On Sep 9, 2009, at 3:25 PM, Rushforth, Peter wrote: > Hi Sean, > > I don't think they are the same thing, although perhaps the effect > should be the same. > In my view, the georss is metadata about the content, whereas the > KML is > the content. > > The gdata feed is just one organization's implementation of content. > Other organizations > are going to have different content, geospatial or otherwise. The > georss should > be at a conceptual level above content, allowing any content to be > mapped/located. > > Then an individual organization can implement how to handle their own > content appropriately, based > on the mime type. > > My $0.02 > > Cheers, > Peter > >> -----Original Message----- >> From: georss-bounces@... >> [mailto:georss-bounces@...] On Behalf Of Sean Gillies >> Sent: September 9, 2009 8:00 AM >> To: GeoRss georss@... >> Subject: [georss] Yet another flavor of GeoRSS? >> >> I'm having a discussion in an OpenLayers ticket about whether >> users ought to be able to expect the following two feeds to be >> treated >> equivalently: >> >> 1) Atom feed with GeoRSS location metadata: >> >> <feed >> xmlns="http://www.w3.org/2005/Atom" >> xmlns:georss="http://www.georss.org/georss" >> xmlns:gml="http://www.opengis.net/gml" >> /> >> <entry> >> <title>Foo</title> >> <summary>Yet another item about Foo</summary> >> <georss:where> >> <gml:Point> >> <gml:pos>0.0 51.0</gml:pos> >> </gml:Point> >> </georss:where> >> </entry> >> </feed> >> >> 2) Google Maps Data API feature feed: >> >> <feed xmlns="http://www.w3.org/2005/Atom"> >> <entry> >> <title>Foo</title> >> <content type="application/vnd.google-earth.kml+xml"> >> <Placemark xmlns="http://www.opengis.net/kml/2.2"> >> <name>Foo</name> >> <description>Yet another item about Foo</description> >> <Point> >> <coordinates>51.0,0.0,0.0</coordinates> >> </Point> >> </Placemark> >> </content> >> </entry> >> </feed> >> >> Thoughts? >> >> -- >> Sean >> >> _______________________________________________ >> georss mailing list >> georss@... >> http://lists.eogeo.org/mailman/listinfo/georss >> -- Sean _______________________________________________ georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
|
|
Re: Yet another flavor of GeoRSS?Carl,
The premise of GeoRSS + Atom (in my mind, at least) is that we can apply "feature" semantics to resources like an Atom entry that exist only on the web, and "feature collection" semantics likewise to Atom feeds. In the architecture of the web, semantics are conveyed by links, not by formal schemas. If I write <link rel="search" href="http://sgillies.net/blog/find" /> This is how an HTML processor knows (in theory) that http://sgillies.net/blog/find has "search" semantics. We're not practicing this yet for GeoRSS, but I have been trying to promote the practice with a "where" link relation. Something like <link rel="where" href="http://example.com/geo/feed" /> could tell Atom processors that feature collection semantics should be applied to the feed. Cheers, On Sep 9, 2009, at 6:36 PM, Carl Reed wrote: > I concur - > > Just some additional input to consider: GML is grounded in the > abstract model ISO 19107 spatial schema (as well as other ISO > standards) and has the abstraction "feature". GML defines features > distinct from geometry objects. A feature is an application object > that represents a physical entity. Geometry is a property of a > feature. While GeoRSS does not explicitly utilize "feature", KML has > no concept of "feature" (I suspect some would argue this . . .). KML > is a grammar for expressing geographic annotation and visualization > in Earth Browser apps. As such, remember that GML and KML evolved > from a different set of requirements and use cases. Hence, stating > "equivalence" can be difficult at best. > > Regards > > Carl > > > > ----- Original Message ----- From: "Barry Hunter" <barry@... > > > To: "Sean Gillies" <sean.gillies@...> > Cc: <georss@...> > Sent: Wednesday, September 09, 2009 7:51 AM > Subject: Re: [georss] Yet another flavor of GeoRSS? > > >> Expecting RSS parsers to also be able to parse KML content and use >> the >> GeoData as it would a more standard GeoRSS feed just seems wrong to >> me. >> >> So I say no that not really a 'flavor' of GeoRSS, but just KML >> encapsulated in a RSS feed, and should be treated differently. >> >> >> On 09/09/2009, Sean Gillies <sean.gillies@...> wrote: >>> I'm having a discussion in an OpenLayers ticket about whether users >>> ought to be able to expect the following two feeds to be treated >>> equivalently: >>> >>> 1) Atom feed with GeoRSS location metadata: >>> >>> <feed >>> xmlns="http://www.w3.org/2005/Atom" >>> xmlns:georss="http://www.georss.org/georss" >>> xmlns:gml="http://www.opengis.net/gml" >>> /> >>> <entry> >>> <title>Foo</title> >>> <summary>Yet another item about Foo</summary> >>> <georss:where> >>> <gml:Point> >>> <gml:pos>0.0 51.0</gml:pos> >>> </gml:Point> >>> </georss:where> >>> </entry> >>> </feed> >>> >>> 2) Google Maps Data API feature feed: >>> >>> <feed xmlns="http://www.w3.org/2005/Atom"> >>> <entry> >>> <title>Foo</title> >>> <content type="application/vnd.google-earth.kml+xml"> >>> <Placemark xmlns="http://www.opengis.net/kml/2.2"> >>> <name>Foo</name> >>> <description>Yet another item about Foo</description> >>> <Point> >>> <coordinates>51.0,0.0,0.0</coordinates> >>> </Point> >>> </Placemark> >>> </content> >>> </entry> >>> </feed> >>> >>> Thoughts? >>> >>> >>> -- >>> Sean >>> >>> _______________________________________________ >>> georss mailing list >>> georss@... >>> http://lists.eogeo.org/mailman/listinfo/georss >>> >> _______________________________________________ >> georss mailing list >> georss@... >> http://lists.eogeo.org/mailman/listinfo/georss > -- Sean _______________________________________________ georss mailing list georss@... http://lists.eogeo.org/mailman/listinfo/georss |
| Free embeddable forum powered by Nabble | Forum Help |