comma or semicolon in geo (was: [uf-discuss] Operator: Microformat detection for Firefox 2)

Andy Mabbett andy at
Sat Dec 16 04:45:42 PST 2006

In message
<cdc278e10612160420r6094e0a5h836aed9018b3d095 at>, Ciaran
McNulty <mail at> writes

>On 12/16/06, Andy Mabbett <andy at> wrote:
>> In message <D70357A9-B858-4531-8865-AAF28762013F at>, Alex
>> Faaborg <faaborg at> writes
>> >Today Mozilla Labs released a microformat extension for Firefox 2
>> >named Operator.
>> Looks good, but it shows the "geo" on :
>>         <>
>> as "undefined/undefined".
>It may be because you've separated the lat/long with a semicolon
>whereas the geo cheatsheet says:

Thanks, but I've tried both.

>"If the secondary classes are omitted, the two values MUST be comma
>separated and latitude MUST be first"[1]
>I'm not sure where that bit of info on the cheatsheet has come from though.

Look at the history and source of that page...

It might be best of parsers accepted either; since some schemes use
comma (e.g. ICBM), others semicolon (e.g. geotag)

Andy Mabbett
            *  Say "NO!" to compulsory ID Cards:  <>
            *  Free Our Data:  <>
            *  Are you using Microformats, yet: <> ?

More information about the microformats-discuss mailing list