to-do-formats: Difference between revisions
(stub from part of htodo page) |
(unlinky) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
This page is part of an attempt to make progress on a | This page is part of an attempt to make progress on a "to-do" microformat (or properties for an existing microformat like [[h-entry]]) per the microformats [[process]]. | ||
== VTODO == | == VTODO == | ||
| Line 17: | Line 17: | ||
== See Also == | == See Also == | ||
* [[to-do]] | * [[to-do-format]] | ||
* [[to-do-examples]] | * [[to-do-examples]] | ||
* [[to-do-brainstorming]] | * [[to-do-brainstorming]] | ||
Latest revision as of 22:50, 14 December 2021
This article is a stub. You can help the microformats.org wiki by expanding it.
This page is part of an attempt to make progress on a "to-do" microformat (or properties for an existing microformat like h-entry) per the microformats process.
VTODO
VTODO is part of the RFC2445 iCalendar spec used for describing todo items.
VTODO is fairly straight-forward, as it doesn't contain any nested entities, and has a fairly small list of properties. Most of these it shares with VEVENT, suggesting htodo be modeled on hevent in hcalendar, and the ground assumption is that htodo should work just like hevent with respect to these properties. The shared properties are:
class, created, description, dtstamp, dtstart, geo, last-mod, location, organizer, priority, recurid, seq, statusm summary, uid, url, duration, attach, attendee, categories, comment, contact, exdate, exrule, rstatus, related, resources, rdate, rrule, x-prop
The unique properties to VTODO are:
- completed The date/time the todo was completed
- due The date/time this todo is due
- percent Integer from 0-100, completion status