Re: [Ietf-calsify] TZ: polygon

[Cyrus Daboo <daboo@xxxxxxxxxx>]

Hi Doug,

--On Friday, July 08, 2005 11:03:09 AM -0600 Doug Royer <Doug@xxxxxxxxx> 
wrote:

> > The point is POLYGON is not defined in 2445 - it something new and we
> > should have some solid justification for adding new things to iCalendar
> > right now.
>
> It is not being proposed as part of CALSIFY.
>
> I simply replied to the email on this list.
> I have redirected it to calsch to avoid the confusion.

Well strictly speaking calsify has taken over from calsch. Certainly in 
this case 2445 is clear that new properties have to be registered and it 
does describe an approval process for doing that, but does not define the 
registry itself. That would certainly have to be fixed BEFORE you could 
even define POLYGON etc in your draft. If I am mistaken, one of calsify's 
jobs was to formalise the property/parameter etc registry.

I believe we should not wait for that registry to be setup. We need to get 
a timezone registry up and running as it might be crucial for helping 
vendors and users migrate their timezone definitions if the US government 
ultimately decides to proceed with its plan to change the definition of 
daylight savings time in the US next year. If you're not aware of what I am 
talking about see:

<http://www.calconnect.org/dstadvisorynotice.html>

My preference is to remove POLYGON etc from the timezone registry draft and 
move that forward quickly. Once calsify has defined a viable process for 
creating new standard parameters/properties, POLYGON etc can be defined in 
another draft and IANA can choose to include those in its definitions. But 
until then they should be left out.

--
Cyrus Daboo