https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=NroJh0 2026-05-05T21:58:44Z User contributions MediaWiki 1.38.4 https://microformats.org/wiki/index.php?title=htodo&diff=15428 2007-04-11T01:10:42Z

<p>NroJh0: </p> <hr /> <div>&lt;h1&gt;hToDo&lt;/h1&gt;<br /> <br /> ''This is just an initial draft''<br /> <br /> [http://en.wikipedia.org/wiki/ICalendar#To-do_.28VTODO.29 VTODO] is part of the [http://www.ietf.org/rfc/rfc2445.txt RFC2445 iCalendar spec] used for describing todo items.<br /> <br /> 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:<br /> <br /> ''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''<br /> <br /> The unique properties to VTODO are:<br /> <br /> * '''completed''' The date/time the todo was completed<br /> * '''due''' The date/time this todo is due<br /> * '''percent''' Integer from 0-100, completion status<br /> <br /> As the data types for '''completed''' and '''due''' are the same as, e.g., '''dtstart''', then the usage should be the same. For example,</div>

NroJh0