Am 15.03.2007 um 20:52 schrieb Andy Mabbett:
In message <[EMAIL PROTECTED]>,
Alexander Graf <[EMAIL PROTECTED]> writes
<ol class="geo-route">
<li class="geo">
Latitude: <abbr class="latitude" title="-83.00000">-83.0000</abbr>
Longitude: <abbr class="longitude" title="43.00000">43.0000</abbr>
Elevation: <abbr class="elevation" title="2012.00000">2012.0000</
abbr>
<li>
etc....
</ol>
as geo is just used for encapsulating Lat/Lon values in hCards, I
don't think reusing is a good idea.
I don't see how the above would break any existing (or future spec-
abiding) "geo" or "hCard" implementations; the elevation data and
geo-route class would simply be discarded.
Fair enough. Someone in this discssion said "geo" was locked as it's
a subset of hCard, which is locked too.
If geo is extendable that's even better!
- Elevation is the main feature that is missing
- Elevation could be positive and negative
- Timestamps for geo data should be optional but possible
- How about coordinate formats / map projection / dates?
- alex
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
