Re: [Ietf-calsify] TZ: polygon

--nextPart1267013.6BT0GhfPaL
Content-Type: text/plain;
  charset="iso-8859-6"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Freitag, 8. Juli 2005 19:34 schrieb Doug Royer:
> I am following the open IETF processes as defined in 2445. Versions
> of this proposal on this mailing list have taken place for several
> years. The polygon idea was not mine, it was a request for addition
> to the proposal years ago. Its optional. You do not have to use it.

Cyrus was simply pointing out that while rfc 2445 gives a process for=20
registering new properties, the BNF given in the rfc does *NOT* allow them.=
=20
The grammar in rfc 2445 only allows the explicitly listed properties plus t=
he=20
x-properties, but nothing else. So any implementation that throws an error=
=20
when it encounters a POLYGON can still be rfc-compliant.

Reinhold

=2D-=20
=2D-----------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: [email protected], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer / KPilot maintain=
er

--nextPart1267013.6BT0GhfPaL
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCzr4xTqjEwhXvPN0RAgl+AKCMPT6ngGZAxQMqr7YNyk8g5Nu+zACgr6GR
0Db5MDmig6+pc7WwJxyK7Eg=
=PkQx
-----END PGP SIGNATURE-----

--nextPart1267013.6BT0GhfPaL--