NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 565 - Clarify a requirement regarding dtend's syntax which I had missed when going through vevent before.
Clarify a requirement regarding dtend's syntax which I had missed when going ...
Status: RESOLVED INTENTIONAL
Product: Validator.nu
Classification: Unclassified
Component: General
HEAD
All All
: P2 normal
Assigned To: Henri Sivonen
http://svn.whatwg.org/webapps/source?...
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-27 14:34 CEST by Henri Sivonen
Modified: 2009-05-27 14:52 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henri Sivonen 2009-05-27 14:34:59 CEST
Index: source
===================================================================
--- source	(revision 3097)
+++ source	(revision 3098)
@@ -48281,22 +48281,30 @@
 
     <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>
-
-<!--XXX
-   The "VEVENT" is also the calendar component used to specify an
-   anniversary or daily reminder within a calendar. These events have a
-   DATE value type for the "DTSTART" property instead of the default
-   data type of DATE-TIME. If such a "VEVENT" has a "DTEND" property, it
-   MUST be specified as a DATE value also. The anniversary type of
-   "VEVENT" can span more than one date (i.e, "DTEND" property value is
-   set to a calendar date after the "DTSTART" property value).
--->
+    <p>If the property with the name <code
+    title="md-vevent-dtend">dtend</code> is present within an <span
+    title="concept-item">item</span> with the type <code
+    title="md-vevent">vevent</code> that has a property with the name
+    <code title="md-vevent-dtstart">dtstart</code> whose value is a
+    <span>valid date string</span>, then the <span
+    title="concept-property-value">value</span> of the property with
+    the name <code title="md-vevent-dtend">dtend</code> must be text
+    that is a <span>valid date string</span> also. Otherwise, the
+    <span title="concept-property-value">value</span> of the property
+    must be text that is a <span>valid global date and time
+    string</span>.</p>
+
+    <p>In either case, the <span
+    title="concept-property-value">value</span> 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 class="note">The time given by the <code
+    title="md-vevent-dtend">dtend</code> property is not
+    inclusive. For day-long events, therefore, the the <code
+    title="md-vevent-dtend">dtend</code> property's <span
+    title="concept-property-value">value</span> will be the day
+    <em>after</em> the end of the event.</p>
 
     <p>A single property with the name <code
     title="md-vevent-dtend">dtend</code> may be present within each