Re: [uf-discuss] Resoling the "exclusive end date" issue

[Andy Mabbett]

In message <[EMAIL PROTECTED]>, Andy Mabbett 
<[EMAIL PROTECTED]> writes


In message <[EMAIL PROTECTED]>, 
Andy Mabbett <[EMAIL PROTECTED]> writes



There is an outstanding hCalendar "issue" [...] around the use of
exclusive dtend for whole-day dates [...] which is also one of the
concerns with the misuse of abbr.



One of the proposed remedies is to create a new class in hCalendar (and
other microformats requiring and end date), perhaps "dtendinc" (for
"inclusive date end") or "dtendwhole" (for "whole-day date end"), such
that [...]
parsers are instructed, when exporting iCalendars, to increment the date
in order to generate the exclusive date-end required by iCalendar.



As discussed previously [...]
it would be sensible for this solution to be implemented, subject to the
usual caveats about process and testing, before the watershed formed by
the release of Firefox 3.


This would also be in accordance with the stated microformats principle 
of "lowering barriers for publishers":


   


Which accordance is not negated by this edit:

  

--
Andy Mabbett
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] Resoling the "exclusive end date" issue

[Andy Mabbett]

In message <[EMAIL PROTECTED]>,
Andy Mabbett <[EMAIL PROTECTED]> writes

>There is an outstanding hCalendar "issue" [...] around the use of
>exclusive dtend for whole-day dates [...] which is also one of the
>concerns with the misuse of abbr.

>One of the proposed remedies is to create a new class in hCalendar (and
>other microformats requiring and end date), perhaps "dtendinc" (for
>"inclusive date end") or "dtendwhole" (for "whole-day date end"), such
>that [...]
>parsers are instructed, when exporting iCalendars, to increment the date
>in order to generate the exclusive date-end required by iCalendar.

>As discussed previously [...]
>it would be sensible for this solution to be implemented, subject to the
>usual caveats about process and testing, before the watershed formed by
>the release of Firefox 3.

This would also be in accordance with the stated microformats principle
of "lowering barriers for publishers":



Is anyone interested in taking this forward?

-- 
Andy Mabbett
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss