[html5] r3095 - [at] (0) Introduce a vEvent vocabulary.
whatwg at whatwg.org
whatwg at whatwg.org
Wed May 13 18:14:51 PDT 2009
Author: ianh
Date: 2009-05-13 18:14:50 -0700 (Wed, 13 May 2009)
New Revision: 3095
Modified:
index
source
Log:
[at] (0) Introduce a vEvent vocabulary.
Modified: index
===================================================================
--- index 2009-05-13 01:44:27 UTC (rev 3094)
+++ index 2009-05-14 01:14:50 UTC (rev 3095)
@@ -39,7 +39,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 13 May 2009</h2>
+ <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 14 May 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<dl><dt>Multiple-page version:</dt>
@@ -681,12 +681,14 @@
<li><a href=#microdata-dom-api><span class=secno>5.3 </span>Microdata DOM API</a></li>
<li><a href=#predefined-vocabularies><span class=secno>5.4 </span>Predefined vocabularies</a>
<ol>
- <li><a href=#vcard><span class=secno>5.4.1 </span>vCard</a></ol></li>
+ <li><a href=#vcard><span class=secno>5.4.1 </span>vCard</a></li>
+ <li><a href=#vevent><span class=secno>5.4.2 </span>vEvent</a></ol></li>
<li><a href=#converting-html-to-other-formats><span class=secno>5.5 </span>Converting HTML to other formats</a>
<ol>
<li><a href=#json><span class=secno>5.5.1 </span>JSON</a></li>
<li><a href=#rdf><span class=secno>5.5.2 </span>RDF</a></li>
- <li><a href=#vcard-0><span class=secno>5.5.3 </span>vCard</a></ol></ol></li>
+ <li><a href=#vcard-0><span class=secno>5.5.3 </span>vCard</a></li>
+ <li><a href=#icalendar><span class=secno>5.5.4 </span>iCalendar</a></ol></ol></li>
<li><a href=#browsers><span class=secno>6 </span>Web browsers</a>
<ol>
<li><a href=#windows><span class=secno>6.1 </span>Browsing contexts</a>
@@ -41980,7 +41982,7 @@
<p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
text and must match the following syntax:</p>
- <ul><li>Either a U+002B PLUS SIGN character (+) or a U+002D
+ <ol><li>Either a U+002B PLUS SIGN character (+) or a U+002D
HYPHEN-MINUS character (-).</li>
<li>A <a href=#valid-non-negative-integer>valid non-negative integer</a> that is exactly two
@@ -41993,7 +41995,7 @@
digits long and that represents a number in the range
00..59.</li>
- </ul><p>Any number of properties with the name <code title=md-vcard-tz><a href=#md-vcard-tz>tz</a></code> may be present within each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vcard><a href=#md-vcard>vcard</a></code>.</p>
+ </ol><p>Any number of properties with the name <code title=md-vcard-tz><a href=#md-vcard-tz>tz</a></code> may be present within each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vcard><a href=#md-vcard>vcard</a></code>.</p>
</dd>
@@ -42008,7 +42010,7 @@
<p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
text and must match the following syntax:</p>
- <ul><li>Optionally, either a U+002B PLUS SIGN character (+) or a
+ <ol><li>Optionally, either a U+002B PLUS SIGN character (+) or a
U+002D HYPHEN-MINUS character (-).</li>
<li>One or more digits in the range U+0030 DIGIT ZERO .. U+0039
@@ -42030,7 +42032,7 @@
or more digits in the range U+0030 DIGIT ZERO .. U+0039 DIGIT
NINE.</li>
- </ul><p>The optional components marked with an asterisk (*) should be
+ </ol><p>The optional components marked with an asterisk (*) should be
included, and should have dix digits each.</p>
<!-- copied from vCard -->
@@ -42277,8 +42279,14 @@
the person or organization.</p>
<p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
- text.</p>
+ text with one of the following values:</p>
+ <ul class=brief><li><code title="">public</code></li>
+ <li><code title="">private</code></li>
+ <li><code title="">confidential</code></li>
+ </ul><p class=warning>This is merely advisory and cannot be
+ considered a confidentiality measure.</p>
+
<p>Any number of properties with the name <code title=md-vcard-class><a href=#md-vcard-class>class</a></code> may be present
within each <a href=#concept-item title=concept-item>item</a> with the type
<code title=md-vcard><a href=#md-vcard>vcard</a></code>.</p>
@@ -42437,6 +42445,522 @@
<span itemprop="region">CA</span> <span itemprop="postal-code">94043</span>
</span>
</address>
+--><h4 id=vevent><span class=secno>5.4.2 </span>vEvent</h4>
+
+ <p>An item with the <a href=#predefined-type>predefined type</a> <dfn id=md-vevent title=md-vevent><code>vevent</code></dfn> represents an event.</p>
+
+ <p>The following are the type's <a href=#predefined-property-name title="predefined property
+ name">predefined property names</a>. They are based on the
+ vocabulary defined in the iCalendar specification, which should be
+ consulted for more information about how to interpret values. <a href=#refsRFC2445>[RFC2445]</a></p>
+
+ <p class=note>Only the parts of the iCalendar vocabulary relating
+ to events are used here; this vocabulary cannot express a complete
+ iCalendar instance.</p>
+
+ <dl><dt><dfn id=md-vcevent-attach title=md-vcevent-attach><code>attach</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the address of an associated document for the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ an <a href=#absolute-url>absolute URL</a>.</p>
+
+ <p>Any number of properties with the name <code title=md-vcard-attach>attach</code> may be present within each
+ <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-categories title=md-vevent-categories><code>categories</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the name of a category or tag that the event could be
+ classified as.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text.</p>
+
+ <p>Any number of properties with the name <code title=md-vevent-categories><a href=#md-vevent-categories>categories</a></code> may be present
+ within each <a href=#concept-item title=concept-item>item</a> with the type
+ <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-class title=md-vevent-class><code>class</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the access classification of the information regarding
+ the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text with one of the following values:</p>
+
+ <ul class=brief><li><code title="">public</code></li>
+ <li><code title="">private</code></li>
+ <li><code title="">confidential</code></li>
+ </ul><p class=warning>This is merely advisory and cannot be
+ considered a confidentiality measure.</p>
+
+ <p>A single property with the name <code title=md-vevent-class><a href=#md-vevent-class>class</a></code> may be present within each
+ <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-comment title=md-vevent-comment><code>comment</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a comment regarding the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text.</p>
+
+ <p>Any number of properties with the name <code title=md-vevent-comment><a href=#md-vevent-comment>comment</a></code> may be present within each
+ <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-description title=md-vevent-description><code>description</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a detailed description of the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text.</p>
+
+ <p>A single property with the name <code title=md-vevent-description><a href=#md-vevent-description>description</a></code> may be present
+ within each <a href=#concept-item title=concept-item>item</a> with the type
+ <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-geo title=md-vevent-geo><code>geo</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the geographical position of the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text and must match the following syntax:</p>
+
+ <ol><li>Optionally, either a U+002B PLUS SIGN character (+) or a
+ U+002D HYPHEN-MINUS character (-).</li>
+
+ <li>One or more digits in the range U+0030 DIGIT ZERO .. U+0039
+ DIGIT NINE.</li>
+
+ <li>Optionally*, a U+002E FULL STOP character (.) followed by one
+ or more digits in the range U+0030 DIGIT ZERO .. U+0039 DIGIT
+ NINE.</li>
+
+ <li>A U+003B SEMICOLON character (;).</li>
+
+ <li>Optionally, either a U+002B PLUS SIGN character (+) or a
+ U+002D HYPHEN-MINUS character (-).</li>
+
+ <li>One or more digits in the range U+0030 DIGIT ZERO .. U+0039
+ DIGIT NINE.</li>
+
+ <li>Optionally*, a U+002E FULL STOP character (.) followed by one
+ or more digits in the range U+0030 DIGIT ZERO .. U+0039 DIGIT
+ NINE.</li>
+
+ </ol><p>The optional components marked with an asterisk (*) should be
+ included, and should have dix digits each.</p> <!-- iCalendar
+ actually limits the range to -91.0 < lat < 91.0; -181.0 < long <
+ 181.0, which seems weird. It also gives special meanings to
+ +90/-90 lat, and +180 long. -->
+
+ <!-- copied from vcard (not icalendar!) -->
+ <p class=note>The value specifies latitude and longitude, in
+ that order (i.e., "LAT LON" ordering), in decimal degress. The
+ longitude represents the location east and west of the prime
+ meridian as a positive or negative real number, respectively. The
+ latitude represents the location north and south of the equator as
+ a positive or negative real number, respectively.</p>
+
+ <p>A single property with the name <code title=md-vevent-geo><a href=#md-vevent-geo>geo</a></code> may be present within each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-location title=md-vevent-location><code>location</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the location of the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text.</p> <!-- v2: support vcard here -->
+
+ <p>A single property with the name <code title=md-vevent-location><a href=#md-vevent-location>location</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <!-- PRIORITY not included - always 0 - doesn't make sense for single events -->
+
+
+ <dt><dfn id=md-vevent-resources title=md-vevent-resources><code>resources</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a resource that will be needed for the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text.</p> <!-- v2: support vcard here -->
+
+ <p>Any number of properties with the name <code title=md-vevent-resources><a href=#md-vevent-resources>resources</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-status title=md-vevent-status><code>status</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the confirmation status of the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text with one of the following values:</p>
+
+ <ul class=brief><li><code title="">tentative</code></li>
+ <li><code title="">confirmed</code></li>
+ <li><code title="">cancelled</code></li> <!-- two Ls as per iCalendar spec -->
+ </ul><p>A single property with the name <code title=md-vevent-status><a href=#md-vevent-status>status</a></code> may be present within each
+ <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-summary title=md-vevent-summary><code>summary</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a short summary of the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text.</p>
+
+ <p>User agents should replace U+000A LINE FEED (LF) characters in
+ the <a href=#concept-property-value title=concept-property-value>value</a> by U+0020
+ SPACE characters when using the value.</p>
+
+ <p>A single property with the name <code title=md-vevent-summary><a href=#md-vevent-summary>summary</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-dtend title=md-vevent-dtend><code>dtend</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time by which the event ends.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is either a <a href=#valid-date-string>valid date string</a> or a
+ <a href=#valid-global-date-and-time-string>valid global date and time string</a>, and the value must
+ be later in time than the value of the <code title=md-event-dtstart>dtstart</code> property of the same <a href=#concept-item title=concept-item>item</a>.</p>
+
+ <p>A single property with the name <code title=md-vevent-dtend><a href=#md-vevent-dtend>dtend</a></code> may be present within each
+ <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>, so long as that <code title=md-vevent><a href=#md-vevent>vevent</a></code> does not have a property with the
+ name <code title=md-vevent-duration><a href=#md-vevent-duration>duration</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-dtstart title=md-vevent-dtstart><code>dtstart</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event starts.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is either a <a href=#valid-date-string>valid date string</a> or a
+ <a href=#valid-global-date-and-time-string>valid global date and time string</a>.</p>
+
+ <p>Exactly one property with the name <code title=md-vevent-dtstart><a href=#md-vevent-dtstart>dtstart</a></code> must be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-duration title=md-vevent-duration><code>duration</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event starts.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is a <a href=#valid-vevent-duration-string>valid vevent duration string</a>.</p>
+
+ <p>The duration represented is the sum of all the durations
+ represented by integers in the value.</p>
+
+ <p>A single property with the name <code title=md-vevent-duration><a href=#md-vevent-duration>duration</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>, so long as that <code title=md-vevent><a href=#md-vevent>vevent</a></code> does not have a property with the
+ name <code title=md-vevent-dtend><a href=#md-vevent-dtend>dtend</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-transp title=md-vevent-transp><code>transp</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives whether the event is to be considered as consuming time
+ on a calendar, for the purpose of free-busy time searches.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text with one of the following values:</p>
+
+ <ul class=brief><li><code title="">opaque</code></li>
+ <li><code title="">transparent</code></li>
+ </ul><p>A single property with the name <code title=md-vevent-transp><a href=#md-vevent-transp>transp</a></code> may be present within each
+ <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <!-- ATTENDEE not included; iCalendar says MUST NOT be included in
+ published events -->
+
+
+ <dt><dfn id=md-vevent-contact title=md-vevent-contact><code>contact</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the contact information for the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text.</p> <!-- v2: support vcard here -->
+
+ <p>Any number of properties with the name <code title=md-vevent-contact><a href=#md-vevent-contact>contact</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <!-- ORGANIZER not included, as it is calendar-system-specific
+ (gives a CAL-ADDRESS value); use CONTACT instead -->
+
+
+ <!-- RECURRENCE-ID not included... unclear how to make it usefully
+ work here -->
+
+
+ <!-- RELATED-TO not included, as it only makes sense for complete
+ calendars -->
+
+
+ <dt><dfn id=md-vevent-url title=md-vevent-url><code>url</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a <a href=#url>URL</a> for the event.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ an <a href=#absolute-url>absolute URL</a>.</p>
+
+ <p>A single property with the name <code title=md-vevent-url><a href=#md-vevent-url>url</a></code> may be present within each
+ <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <!-- UID not included - use "about" -->
+
+
+ <dt><dfn id=md-vevent-exdate title=md-vevent-exdate><code>exdate</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a date and time at which the event does not occur despite
+ the recurrence rules.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is either a <a href=#valid-date-string>valid date string</a> or a
+ <a href=#valid-global-date-and-time-string>valid global date and time string</a>.</p>
+
+ <p>Any number of properties with the name <code title=md-vevent-exdate><a href=#md-vevent-exdate>exdate</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-exrule title=md-vevent-exrule><code>exrule</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a rule for finding dates and times at which the event
+ does not occur despite the recurrence rules.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that matches the RECUR value type defined in the iCalendar
+ specification. <a href=#refsRFC2445>[RFC2445]</a></p>
+
+ <p>Any number of properties with the name <code title=md-vevent-exrule><a href=#md-vevent-exrule>exrule</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-rdate title=md-vevent-rdate><code>rdate</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a date and time at which the event recurs.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is one of the following:
+
+ <ul><li>A <a href=#valid-date-string>valid date string</a>.</li>
+
+ <li>A <a href=#valid-global-date-and-time-string>valid global date and time string</a>.</li>
+
+ <li>A <a href=#valid-global-date-and-time-string>valid global date and time string</a> followed by
+ a U+002F SOLIDUS character (/) followed by a second <a href=#valid-global-date-and-time-string>valid
+ global date and time string</a> representing a later time.</li>
+
+ <li>A <a href=#valid-global-date-and-time-string>valid global date and time string</a> followed by
+ a U+002F SOLIDUS character (/) followed by a <a href=#valid-vevent-duration-string>valid vevent
+ duration string</a>.</li>
+
+ </ul><p>Any number of properties with the name <code title=md-vevent-rdate><a href=#md-vevent-rdate>rdate</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-rrule title=md-vevent-rrule><code>rrule</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a rule for finding dates and times at which the event
+ occurs.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that matches the RECUR value type defined in the iCalendar
+ specification. <a href=#refsRFC2445>[RFC2445]</a></p>
+
+ <p>Any number of properties with the name <code title=md-vevent-rrule><a href=#md-vevent-rrule>rrule</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-created title=md-vevent-created><code>created</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event information was first
+ created in a calendaring system.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is a <a href=#valid-global-date-and-time-string>valid global date and time string</a>.</p>
+
+ <p>A single property with the name <code title=md-vevent-created><a href=#md-vevent-created>created</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <!-- DTSTAMP not included, it gets added when serialising -->
+
+
+ <dt><dfn id=md-vevent-last-modified title=md-vevent-last-modified><code>last-modified</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event information was last
+ modified in a calendaring system.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is a <a href=#valid-global-date-and-time-string>valid global date and time string</a>.</p>
+
+ <p>A single property with the name <code title=md-vevent-last-modified><a href=#md-vevent-last-modified>last-modified</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <dt><dfn id=md-vevent-sequence title=md-vevent-sequence><code>sequence</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a revision number for the event information.</p>
+
+ <p>The <a href=#concept-property-value title=concept-property-value>value</a> must be
+ text that is a <a href=#valid-non-negative-integer>valid non-negative integer</a>.</p>
+
+ <p>A single property with the name <code title=md-vevent-sequence><a href=#md-vevent-sequence>sequence</a></code> may be present within
+ each <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vevent><a href=#md-vevent>vevent</a></code>.</p>
+
+ </dd>
+
+
+ <!-- REQUEST-STATUS not included, calendaring system interop
+ feature -->
+
+
+ </dl><p>A string is a <dfn id=valid-vevent-duration-string>valid vevent duration string</dfn> if it
+ matches the following pattern:</p>
+
+ <ol><li>A U+0050 LATIN CAPITAL LETTER P character.</li>
+
+ <li>One of the following:
+
+ <ul><li> A <a href=#valid-non-negative-integer>valid non-negative integer</a> followed by a
+ U+0057 LATIN CAPITAL LETTER W character. The integer represents
+ a duration of that number of weeks. </li>
+
+ <li> At least one, and possible both in this order, of the
+ following:
+
+ <ol><li> A <a href=#valid-non-negative-integer>valid non-negative integer</a> followed by a
+ U+0044 LATIN CAPITAL LETTER D character. The integer
+ represents a duration of that number of days. </li>
+
+ <li> A U+0054 LATIN CAPITAL LETTER T character followed by
+ any one of the following, or the first and second of the
+ following in that order, or the second and third of the
+ following in that order, or all three of the following in
+ this order:
+
+ <ol><li> A <a href=#valid-non-negative-integer>valid non-negative integer</a> followed by
+ a U+0048 LATIN CAPITAL LETTER H character. The integer
+ represents a duration of that number of hours. </li>
+
+ <li> A <a href=#valid-non-negative-integer>valid non-negative integer</a> followed by
+ a U+004D LATIN CAPITAL LETTER M character. The integer
+ represents a duration of that number of minutes. </li>
+
+ <li> A <a href=#valid-non-negative-integer>valid non-negative integer</a> followed by
+ a U+0053 LATIN CAPITAL LETTER S character. The integer
+ represents a duration of that number of seconds. </li>
+
+ </ol></ol></li>
+
+ </ul></li>
+
+ </ol><!--XXX
+
+ <h5>Examples</h5>
+
+from http://www.ietf.org/rfc/rfc2445.txt
+
--><h3 id=converting-html-to-other-formats><span class=secno>5.5 </span>Converting HTML to other formats</h3>
@@ -42709,8 +43233,15 @@
<p class=XXX>...</p>
+ <h4 id=icalendar><span class=secno>5.5.4 </span>iCalendar</h4>
+ <p class=XXX>...</p>
+ <!-- value datetime vs date for dtstart, dtend, rdate, exdate; must include new dtstamp -->
+
+
+
+
<h2 id=browsers><span class=secno>6 </span>Web browsers</h2>
<div class=impl>
Modified: source
===================================================================
--- source 2009-05-13 01:44:27 UTC (rev 3094)
+++ source 2009-05-14 01:14:50 UTC (rev 3095)
@@ -47493,7 +47493,7 @@
<p>The <span title="concept-property-value">value</span> must be
text and must match the following syntax:</p>
- <ul>
+ <ol>
<li>Either a U+002B PLUS SIGN character (+) or a U+002D
HYPHEN-MINUS character (-).</li>
@@ -47508,7 +47508,7 @@
digits long and that represents a number in the range
00..59.</li>
- </ul>
+ </ol>
<p>Any number of properties with the name <code
title="md-vcard-tz">tz</code> may be present within each <span
@@ -47528,7 +47528,7 @@
<p>The <span title="concept-property-value">value</span> must be
text and must match the following syntax:</p>
- <ul>
+ <ol>
<li>Optionally, either a U+002B PLUS SIGN character (+) or a
U+002D HYPHEN-MINUS character (-).</li>
@@ -47552,7 +47552,7 @@
or more digits in the range U+0030 DIGIT ZERO .. U+0039 DIGIT
NINE.</li>
- </ul>
+ </ol>
<p>The optional components marked with an asterisk (*) should be
included, and should have dix digits each.</p>
@@ -47834,8 +47834,17 @@
the person or organization.</p>
<p>The <span title="concept-property-value">value</span> must be
- text.</p>
+ text with one of the following values:</p>
+ <ul class="brief">
+ <li><code title="">public</code></li>
+ <li><code title="">private</code></li>
+ <li><code title="">confidential</code></li>
+ </ul>
+
+ <p class="warning">This is merely advisory and cannot be
+ considered a confidentiality measure.</p>
+
<p>Any number of properties with the name <code
title="md-vcard-class">class</code> may be present
within each <span title="concept-item">item</span> with the type
@@ -48014,6 +48023,616 @@
-->
+ <h4>vEvent</h4>
+
+ <p>An item with the <span>predefined type</span> <dfn
+ title="md-vevent"><code>vevent</code></dfn> represents an event.</p>
+
+ <p>The following are the type's <span title="predefined property
+ name">predefined property names</span>. They are based on the
+ vocabulary defined in the iCalendar specification, which should be
+ consulted for more information about how to interpret values. <a
+ href="#refsRFC2445">[RFC2445]</a></p>
+
+ <p class="note">Only the parts of the iCalendar vocabulary relating
+ to events are used here; this vocabulary cannot express a complete
+ iCalendar instance.</p>
+
+ <dl>
+
+
+ <dt><dfn title="md-vcevent-attach"><code>attach</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the address of an associated document for the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ an <span>absolute URL</span>.</p>
+
+ <p>Any number of properties with the name <code
+ title="md-vcard-attach">attach</code> may be present within each
+ <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-categories"><code>categories</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the name of a category or tag that the event could be
+ classified as.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text.</p>
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-categories">categories</code> may be present
+ within each <span title="concept-item">item</span> with the type
+ <code title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-class"><code>class</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the access classification of the information regarding
+ the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text with one of the following values:</p>
+
+ <ul class="brief">
+ <li><code title="">public</code></li>
+ <li><code title="">private</code></li>
+ <li><code title="">confidential</code></li>
+ </ul>
+
+ <p class="warning">This is merely advisory and cannot be
+ considered a confidentiality measure.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-class">class</code> may be present within each
+ <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-comment"><code>comment</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a comment regarding the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text.</p>
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-comment">comment</code> may be present within each
+ <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-description"><code>description</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a detailed description of the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-description">description</code> may be present
+ within each <span title="concept-item">item</span> with the type
+ <code title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-geo"><code>geo</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the geographical position of the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text and must match the following syntax:</p>
+
+ <ol>
+
+ <li>Optionally, either a U+002B PLUS SIGN character (+) or a
+ U+002D HYPHEN-MINUS character (-).</li>
+
+ <li>One or more digits in the range U+0030 DIGIT ZERO .. U+0039
+ DIGIT NINE.</li>
+
+ <li>Optionally*, a U+002E FULL STOP character (.) followed by one
+ or more digits in the range U+0030 DIGIT ZERO .. U+0039 DIGIT
+ NINE.</li>
+
+ <li>A U+003B SEMICOLON character (;).</li>
+
+ <li>Optionally, either a U+002B PLUS SIGN character (+) or a
+ U+002D HYPHEN-MINUS character (-).</li>
+
+ <li>One or more digits in the range U+0030 DIGIT ZERO .. U+0039
+ DIGIT NINE.</li>
+
+ <li>Optionally*, a U+002E FULL STOP character (.) followed by one
+ or more digits in the range U+0030 DIGIT ZERO .. U+0039 DIGIT
+ NINE.</li>
+
+ </ol>
+
+ <p>The optional components marked with an asterisk (*) should be
+ included, and should have dix digits each.</p> <!-- iCalendar
+ actually limits the range to -91.0 < lat < 91.0; -181.0 < long <
+ 181.0, which seems weird. It also gives special meanings to
+ +90/-90 lat, and +180 long. -->
+
+ <!-- copied from vcard (not icalendar!) -->
+ <p class="note">The value specifies latitude and longitude, in
+ that order (i.e., "LAT LON" ordering), in decimal degress. The
+ longitude represents the location east and west of the prime
+ meridian as a positive or negative real number, respectively. The
+ latitude represents the location north and south of the equator as
+ a positive or negative real number, respectively.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-geo">geo</code> may be present within each <span
+ title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-location"><code>location</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the location of the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text.</p> <!-- v2: support vcard here -->
+
+ <p>A single property with the name <code
+ title="md-vevent-location">location</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <!-- PRIORITY not included - always 0 - doesn't make sense for single events -->
+
+
+ <dt><dfn title="md-vevent-resources"><code>resources</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a resource that will be needed for the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text.</p> <!-- v2: support vcard here -->
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-resources">resources</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-status"><code>status</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the confirmation status of the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text with one of the following values:</p>
+
+ <ul class="brief">
+ <li><code title="">tentative</code></li>
+ <li><code title="">confirmed</code></li>
+ <li><code title="">cancelled</code></li> <!-- two Ls as per iCalendar spec -->
+ </ul>
+
+ <p>A single property with the name <code
+ title="md-vevent-status">status</code> may be present within each
+ <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-summary"><code>summary</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a short summary of the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text.</p>
+
+ <p>User agents should replace U+000A LINE FEED (LF) characters in
+ the <span title="concept-property-value">value</span> by U+0020
+ SPACE characters when using the value.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-summary">summary</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-dtend"><code>dtend</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time by which the event ends.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is either a <span>valid date string</span> or a
+ <span>valid global date and time string</span>, and the value must
+ be later in time than the value of the <code
+ title="md-event-dtstart">dtstart</code> property of the same <span
+ title="concept-item">item</span>.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-dtend">dtend</code> may be present within each
+ <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>, so long as that <code
+ title="md-vevent">vevent</code> does not have a property with the
+ name <code title="md-vevent-duration">duration</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-dtstart"><code>dtstart</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event starts.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is either a <span>valid date string</span> or a
+ <span>valid global date and time string</span>.</p>
+
+ <p>Exactly one property with the name <code
+ title="md-vevent-dtstart">dtstart</code> must be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-duration"><code>duration</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event starts.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is a <span>valid vevent duration string</span>.</p>
+
+ <p>The duration represented is the sum of all the durations
+ represented by integers in the value.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-duration">duration</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>, so long as that <code
+ title="md-vevent">vevent</code> does not have a property with the
+ name <code title="md-vevent-dtend">dtend</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-transp"><code>transp</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives whether the event is to be considered as consuming time
+ on a calendar, for the purpose of free-busy time searches.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text with one of the following values:</p>
+
+ <ul class="brief">
+ <li><code title="">opaque</code></li>
+ <li><code title="">transparent</code></li>
+ </ul>
+
+ <p>A single property with the name <code
+ title="md-vevent-transp">transp</code> may be present within each
+ <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <!-- ATTENDEE not included; iCalendar says MUST NOT be included in
+ published events -->
+
+
+ <dt><dfn title="md-vevent-contact"><code>contact</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the contact information for the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text.</p> <!-- v2: support vcard here -->
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-contact">contact</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <!-- ORGANIZER not included, as it is calendar-system-specific
+ (gives a CAL-ADDRESS value); use CONTACT instead -->
+
+
+ <!-- RECURRENCE-ID not included... unclear how to make it usefully
+ work here -->
+
+
+ <!-- RELATED-TO not included, as it only makes sense for complete
+ calendars -->
+
+
+ <dt><dfn title="md-vevent-url"><code>url</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a <span>URL</span> for the event.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ an <span>absolute URL</span>.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-url">url</code> may be present within each
+ <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <!-- UID not included - use "about" -->
+
+
+ <dt><dfn title="md-vevent-exdate"><code>exdate</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a date and time at which the event does not occur despite
+ the recurrence rules.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is either a <span>valid date string</span> or a
+ <span>valid global date and time string</span>.</p>
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-exdate">exdate</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-exrule"><code>exrule</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a rule for finding dates and times at which the event
+ does not occur despite the recurrence rules.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that matches the RECUR value type defined in the iCalendar
+ specification. <a href="#refsRFC2445">[RFC2445]</a></p>
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-exrule">exrule</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-rdate"><code>rdate</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a date and time at which the event recurs.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is one of the following:
+
+ <ul>
+
+ <li>A <span>valid date string</span>.</li>
+
+ <li>A <span>valid global date and time string</span>.</li>
+
+ <li>A <span>valid global date and time string</span> followed by
+ a U+002F SOLIDUS character (/) followed by a second <span>valid
+ global date and time string</span> representing a later time.</li>
+
+ <li>A <span>valid global date and time string</span> followed by
+ a U+002F SOLIDUS character (/) followed by a <span>valid vevent
+ duration string</span>.</li>
+
+ </ul>
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-rdate">rdate</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-rrule"><code>rrule</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a rule for finding dates and times at which the event
+ occurs.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that matches the RECUR value type defined in the iCalendar
+ specification. <a href="#refsRFC2445">[RFC2445]</a></p>
+
+ <p>Any number of properties with the name <code
+ title="md-vevent-rrule">rrule</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-created"><code>created</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event information was first
+ created in a calendaring system.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is a <span>valid global date and time string</span>.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-created">created</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <!-- DTSTAMP not included, it gets added when serialising -->
+
+
+ <dt><dfn title="md-vevent-last-modified"><code>last-modified</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives the date and time at which the event information was last
+ modified in a calendaring system.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is a <span>valid global date and time string</span>.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-last-modified">last-modified</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <dt><dfn title="md-vevent-sequence"><code>sequence</code></dfn></dt>
+
+ <dd>
+
+ <p>Gives a revision number for the event information.</p>
+
+ <p>The <span title="concept-property-value">value</span> must be
+ text that is a <span>valid non-negative integer</span>.</p>
+
+ <p>A single property with the name <code
+ title="md-vevent-sequence">sequence</code> may be present within
+ each <span title="concept-item">item</span> with the type <code
+ title="md-vevent">vevent</code>.</p>
+
+ </dd>
+
+
+ <!-- REQUEST-STATUS not included, calendaring system interop
+ feature -->
+
+
+ </dl>
+
+ <p>A string is a <dfn>valid vevent duration string</dfn> if it
+ matches the following pattern:</p>
+
+ <ol>
+
+ <li>A U+0050 LATIN CAPITAL LETTER P character.</li>
+
+ <li>One of the following:
+
+ <ul>
+
+ <li> A <span>valid non-negative integer</span> followed by a
+ U+0057 LATIN CAPITAL LETTER W character. The integer represents
+ a duration of that number of weeks. </li>
+
+ <li> At least one, and possible both in this order, of the
+ following:
+
+ <ol>
+
+ <li> A <span>valid non-negative integer</span> followed by a
+ U+0044 LATIN CAPITAL LETTER D character. The integer
+ represents a duration of that number of days. </li>
+
+ <li> A U+0054 LATIN CAPITAL LETTER T character followed by
+ any one of the following, or the first and second of the
+ following in that order, or the second and third of the
+ following in that order, or all three of the following in
+ this order:
+
+ <ol>
+
+ <li> A <span>valid non-negative integer</span> followed by
+ a U+0048 LATIN CAPITAL LETTER H character. The integer
+ represents a duration of that number of hours. </li>
+
+ <li> A <span>valid non-negative integer</span> followed by
+ a U+004D LATIN CAPITAL LETTER M character. The integer
+ represents a duration of that number of minutes. </li>
+
+ <li> A <span>valid non-negative integer</span> followed by
+ a U+0053 LATIN CAPITAL LETTER S character. The integer
+ represents a duration of that number of seconds. </li>
+
+ </ol>
+
+ </ol>
+
+ </li>
+
+ </ul>
+
+ </li>
+
+ </ol>
+
+
+<!--XXX
+
+ <h5>Examples</h5>
+
+from http://www.ietf.org/rfc/rfc2445.txt
+
+-->
+
+
+
<h3>Converting HTML to other formats</h3>
@@ -48386,8 +49005,15 @@
<p class="XXX">...</p>
+ <h4>iCalendar</h4>
+ <p class="XXX">...</p>
+ <!-- value datetime vs date for dtstart, dtend, rdate, exdate; must include new dtstamp -->
+
+
+
+
<h2 id="browsers">Web browsers</h2>
<div class="impl">
More information about the Commit-Watchers
mailing list