In message <[EMAIL PROTECTED]>, Paul Wilkins <[EMAIL PROTECTED]> writes
>> My first question is whether elevation has been proposed as part of >> the geo draft specification? Adding the third dimension would seem >> natural and would add additional precision when adopted. > >Unfortunately the third dimension is being rejected at this time. How very two dimensional! > However, if the vCard spec is updated to include an altitude >component, then it will definately become a part of the hCard spec too. >http://microformats.org/wiki/hcard-issues I have yet to see any good reason why hCard (and Geo) cannot have extra fields, which are simply dropped when generating vCards (likewise hCalendar - see the "date of death" debate) >> My second question is whether or not, for line data, it is acceptable >> to include multiple latitude and longitude classes, in sequence, which >> make up the line in sequence or if there is a better way to do it? > >What kind of use do you envisage web tools being able to use that line >sequence information for? Route mapping? Boundary description? >This may be a case where something greater than the Geo microformat >(which is point specific) is required. There is no reason why this could not be an extension of Geo. Note also: <http://microformats.org/wiki/geo-extension-strawman> -- Andy Mabbett * Say "NO!" to compulsory ID Cards: <http://www.no2id.net/> * Free Our Data: <http://www.freeourdata.org.uk> * Are you using Microformats, yet: <http://microformats.org/> ? _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
