[georss] GeoAtom (split from Re: GeoRSS Location References)

[Andrew Turner]

On Tue, Apr 1, 2008 at 10:27 AM, Sean Gillies <sgillies at frii.com> wrote:
>
> Mikel Maron wrote:
>  > This is a great timely discussion. I actually have a need for a location reference construct for a project right this very moment.
>  >
>  > Our feed will associate an annotation with a specified countries, and those country borders will be stored in the consuming application.
>  > Whatever format we come up with is fine for me .. I slightly favor using atom:link, since it doesn't involve any new thing, just a definition of what it means in this context.
>  >
>  > Another thing, seems like country borders are going to be widely needed. Wonder if we could think about a common resource for these, perhaps out of OpenStreetMap or Geonames.
>  >
>  > -Mikel
>
>  At some point (post April Fool's Day) we should discuss whether we'd
>  want to promote the use of fragment identifiers in links. That could be
>  a neat solution for you. Keep one world borders KML document in the
>  client application with IDs for every placemark, and have entries link
>  to the placemarks like
>
>  <link href="world_borders.kml#Alabamastan/>

I think this is a really great option as well. The problem may be that
the world borders would be a huge KML file - so wouldn't want to
always do this. But a smart client could download the file once and
then refer to it for all subsequent look-ups. Could also image a
publishing client that generated this geometry file for each "Story"
that had multiple geometries. So it would end up being a "here are hte
geometries in this story" using the anchors/ids.


This also reminds me of something I talked about with Raj & Josh about
extra-flavored multiple locations referring to story entries. Using
Sean's example, you could still also link to inside a story:

(snipped non-illustrative bits from these entries)

  <entry>
    <link href="http://example.org/entries/1"/>
    <title>Cedarburg Trip</title>
    <summary>We <span id="downtown">went to visit downtown
Cedarburg</span> before the
    conference. Had some great sandwiches at Joe's. If you
    haven't been to Cedarburg, Wisconsin, then you haven't
    really experienced the MidWest...</summary>
  </entry>
  <entry>
    <link rel="related" href="http://example.org/entries/1#downtown"/>
    <title>Downtown Cedarburg, Wis.</title>
    <summary>Went to visit downtown Cedarburg...</summary>
    <georss:where> ...    </georss:where>
  </entry>

where the second entry's link points to the element in the first
entry's content by ID. Not that this is a required dereferencing by
clients - but just another suggestion for implementations to use. This
way a really nice viewer could have, say, a sidebar/hover map on that
section of the story.

>
>  Sean
>
>
>
>  _______________________________________________
>  georss mailing list
>  georss at lists.eogeo.org
>  http://lists.eogeo.org/mailman/listinfo/georss
>



-- 
Andrew Turner
mobile: 248.982.3609
andrew at mapufacture.com 42.2774N x 83.7611W
http://highearthorbit.com Ann Arbor, Michigan, USA

http://mapufacture.com Helping build the Geospatial Web
Introduction to Neogeography - http://oreilly.com/catalog/neogeography