Difference between revisions of "hcalendar-cheatsheet"

From Microformats Wiki
Jump to navigation Jump to search
m (added GEO reference from RFC 2445, there are still plenty of missing properties here)
(Notes about Geo)
Line 21: Line 21:
  
 
{{cheatsheet-key}}
 
{{cheatsheet-key}}
 +
 +
===Notes===
 +
 +
====Geo====
 +
* If latitude is present, so MUST be longitude, and vice versa.
 +
* Coordinates MAY be combined a single <abbr> element; then the latitude and longitude MUST be separated by a semicolon in the title attribute and latitude MUST be first:
 +
:<code><nowiki><abbr class="geo" title="37.386013;-122.082932">home</abbr></nowiki></code>
 +
* The same number of decimal places SHOULD be used in each value.
 +
* Coordinates use the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84].
 +
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]
  
 
==Related pages==
 
==Related pages==
 
{{hcalendar-related-pages}}
 
{{hcalendar-related-pages}}
 
*{{cheatsheets}}
 
*{{cheatsheets}}

Revision as of 19:09, 31 July 2007

hCalendar cheetsheet

Properties (Class Names)

Key

Based on Perl's standard quantifiers:

bold {1} MUST be present exactly once
italic* OPTIONAL, and MAY occur more than once
+ MUST be present, and MAY occur more than once
? OPTIONAL, but MUST NOT occur more than once
[square brackets] list of common values
(parentheses) data format
# comment
! awaiting documentation

Notes

Geo

  • If latitude is present, so MUST be longitude, and vice versa.
  • Coordinates MAY be combined a single <abbr> element; then the latitude and longitude MUST be separated by a semicolon in the title attribute and latitude MUST be first:
<abbr class="geo" title="37.386013;-122.082932">home</abbr>

Related pages

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.