[uf-discuss] hCalendar, geo & Operator extension
ryan at theryanking.com
Wed Dec 5 11:00:50 PST 2007
On Dec 5, 2007, at 9:28 AM, John Panzer wrote:
> James O'Donnell wrote:
>> On 4 Dec 2007, at 07:13, John Panzer wrote:
>>> I've been asked how to handle this case (you have an area, or an
>>> inexact location, and want to encode it while providing a
>>> friendly human readable but possibly ambiguous short hand name
>>> for said place). Is there any existing practices to look at?
>>> Secondly, would this be a valid geo encoding 'abbreviation' ?
>>> <abbr title='22.31119;+89.86145'>the point under my finger right
>> The thing about abbreviations is, the expanded text replaces the
>> shortened form, rather than supplementing it. So I'd guess your
>> example wouldn't work unless the text 'the point under my finger
>> right now' could be replaced by '22.31119;+89.86145' and still
>> make sense when read in its larger context.
>> <span> is probably a safer element to use for encoding lat/long
> Yes, in context this is really additional annotation, so abbr would
> be wrong. Thanks.
> But then is title appropriate if using a span?
> <span title='22.31119;+89.86145'>the point under my finger right
This won't work with any microformats. The title attribute is only
defined to work on the abbr element.
> The adr microformat also works well when you have a named location,
> but in some cases we won't. The specific use case is that the
> location is automatically generated, e.g., via GPS or other means,
> and the author can opt to have it automatically added in to the
> content they create. E.g., a photo and caption from a GPS enabled
Honestly I'd recommend that unless you can put the lat/long in a
human-visible spot, just leave it off.
More information about the microformats-discuss