W3C home > Mailing lists > Public > public-device-apis@w3.org > April 2011

Remarks on http://www.w3.org/TR/2011/WD-calendar-api-20110419/

From: Innovimax SARL <innovimax@gmail.com>
Date: Tue, 19 Apr 2011 21:49:43 +0200
Message-ID: <BANLkTi=3PetNVvEYGe67Rd+hVr_tOfk6+g@mail.gmail.com>
To: public-device-apis@w3.org
Dear all,

Please find few remarks on


*reminder* of type DOMString, nullable

A reminder for the event.

This attribute can be specified as a positive valid date or time string.

, denoting a one-time reminder or as a negative value in milliseconds
denoting a relative relationship to the start time of the calendar event.

A relative reminder is recommended for setting a reminder for recurrent


There is a line starting by a COMMA ","

Proposed fix : remove the "." after string, the newline and the COMMA



   *status* of type DOMString, nullable

An indication of the user's status of the event.

This parameter may be set to one of the following constants:

'pending', 'tentative', 'confirmed', 'cancelled'.


It may be worth explaining what the expected behaviour for each value since
the keyword are different from iCALENDAR RFC 5545


*transparency* of type DOMString, nullable

An indication of the display status to set for the event.

This parameter may be set to one of the following constants:

'transparent', 'opaque'.

{freebusy: 'transparent'} *// Mark event as transparent in Calendar*

In the example, you should replace "freebusy" by "transparency"

In *4.6.1 Attributes*
   Many sentences end up with TWO DOT ".."

== Internationalization ==
Is this spec supposed to be able to deal with other Calendars (wether solar,
lunar or lunisolar) ?

== Various questions ==
How is supposed to behave an UI with a date that appear multiple time
(because of negative leap seconds or daylight saving time) ?

How is supposed to behave a UI with a repeat time too short (which could
block the UI) ?

== Reference ==


Document Object Model (DOM) Level 3 Events Specification
W3C Working Draft 07 September 2010

*HTML5 is still moving so no hurry, interestingly the reference in NORMATIVE
section is older than the one in INFORMATIVE (which is the DEV version)


W3C Working Draft *21 October 2010*

File API
W3C Working Draft *26 October 2010*
* FILEWRITER is now in TR space

File API: Writer
W3C Working Draft 19 April 2011

Best regards,

Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Tuesday, 19 April 2011 19:50:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:46:03 UTC