Difference between revisions of "to-do-formats"

From Microformats Wiki
Jump to navigation Jump to search
(drop htodo, it's nothing more than a very old brainstorm)
(format effort overall)
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]]

Revision as of 22:49, 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 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 1.0, 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

See Also