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)
(unlink date-time-design until we have fixed that page - sending people there doesn't help.)
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<h1>hCalendar cheetsheet</h1>
+
<h1>hCalendar cheatsheet</h1>
 +
 
 +
[[hcalendar|hCalendar]] properties and how to use them.
  
 
==Properties (Class Names)==
 
==Properties (Class Names)==
Line 7: Line 9:
 
**[[class]]?
 
**[[class]]?
 
**description?
 
**description?
**[[dtend]] ([[datetime-design-pattern |ISO date]])?
+
**[[dtend]] (ISO date)?
**'''[[dtstart]]''' ([[datetime-design-pattern |ISO date]]) {1}
+
**'''[[dtstart]]''' (ISO date) {1}
 
**duration?
 
**duration?
 
**[[geo]]?
 
**[[geo]]?
Line 19: Line 21:
 
**url?
 
**url?
 
**last-modified?
 
**last-modified?
 +
**rdate !
 +
**rrule !
 +
**attendee !
 +
**contact !
 +
**organiser !
  
 
{{cheatsheet-key}}
 
{{cheatsheet-key}}
 +
 +
===Notes===
 +
 +
====Geo====
 +
{{geo-note}}
  
 
==Related pages==
 
==Related pages==
 
{{hcalendar-related-pages}}
 
{{hcalendar-related-pages}}
 
*{{cheatsheets}}
 
*{{cheatsheets}}

Latest revision as of 20:10, 21 February 2011

hCalendar cheatsheet

hCalendar properties and how to use them.

Properties (Class Names)

  • vevent {1}
    • category*
    • class?
    • description?
    • dtend (ISO date)?
    • dtstart (ISO date) {1}
    • duration?
    • Geo?
      • latitude?
      • longitude?
    • location?
    • status?
    • summary {1}
    • uid?
    • url?
    • last-modified?
    • rdate !
    • rrule !
    • attendee !
    • contact !
    • organiser !

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

  • Coordinates MUST use the datum of WGS84.
  • 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.