hcalendar-cheatsheet: Difference between revisions
Jump to navigation
Jump to search
m (added GEO reference from RFC 2445, there are still plenty of missing properties here) |
AndyMabbett (talk | contribs) (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)
- vevent {1}
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>
- The same number of decimal places SHOULD be used in each value.
- Coordinates use the datum of WGS84.
- Sources for latitude/ longitude coordinates
Related pages
- hCalendar - specification
- hCalendar intro - plain English introduction
- hCalendar authoring - learn how to add hCalendar markup to your existing events.
- hCalendar creator (hCalendar creator feedback) - create your own hCalendar events.
- hCalendar cheatsheet - hCalendar properties
- hCalendar examples in the wild - an on-going list of websites which use hCalendars.
- hCalendar implementations - websites or tools which either generate or parse hCalendars
- hCalendar FAQ - If you have any questions about hCalendar, check here.
- hCalendar parsing - normative details of how to parse hCalendar.
- hCalendar profile - the XMDP profile for hCalendar
- hCalendar singular properties - an explanation of the list of singular properties in hCalendar.
- hCalendar tests - a wiki page with actual embedded hCalendar events to try parsing.
- hCalendar "to do" - jobs to do
- hCalendar advocacy - encourage others to use hCalendar.
- iCalendar implementations
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.
- hCalendar Brainstorming - brainstorms and other explorations relating to hCalendar
- hCalendar issues - issues with the specification
- Other cheatsheets: hAtom cheatsheet, hCard cheatsheet (also adr cheatsheet + geo cheatsheet), hCalendar cheatsheet, hResume cheatsheet, hReview cheatsheet, PDF cheatsheet