W3C home > Mailing lists > Public > uri@w3.org > January 2014

Re: Standardizing on IDNA 2003 in the URL Standard

From: Gannon Dick <gannon_dick@yahoo.com>
Date: Fri, 17 Jan 2014 11:03:10 -0800 (PST)
Message-ID: <1389985390.69420.YahooMailBasic@web122904.mail.ne1.yahoo.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: Anne van Kesteren <annevk@annevk.nl>, John C Klensin <klensin@jck.com>, "PUBLIC-IRI@W3.ORG" <public-iri@w3.org>, "uri@w3.org" <uri@w3.org>, IDNA update work <idna-update@alvestrand.no>, "www-tag.w3.org" <www-tag@w3.org>
FWIW Björn,

Civil Time is injective, Watches are injective, Sun Dials are not.  A quarter day is 6 hours, a half day 12.  The American Workday is 1/3 of a day with a weekend (two days off).  This is a forward looking solution.  It only works until the next Leap Day.
If you want steady state (Noon to Noon or Midnight to Midnight) ...
Start Year = Julian Day + .5 on (YEAR-1)-12-31
End Year = Julian Day + .5 on (Year+1)-01-01
The "correction" to (reversible) periodic motion is good for 16 digits.

Otherwise you are accumulating Atmospheric Refraction going forward and have no way to subtract it out going in the reverse direction.

--Gannon
--------------------------------------------
On Fri, 1/17/14, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

 Subject: Re: Standardizing on IDNA 2003 in the URL Standard
 To: "Andrew Sullivan" <ajs@anvilwalrusden.com>
 Cc: "Anne van Kesteren" <annevk@annevk.nl>, "John C Klensin" <klensin@jck.com>, "PUBLIC-IRI@W3.ORG" <public-iri@w3.org>, "uri@w3.org" <uri@w3.org>, "IDNA update work" <idna-update@alvestrand.no>, "www-tag.w3.org" <www-tag@w3.org>
 Date: Friday, January 17, 2014, 10:11 AM
 
 * Andrew Sullivan
 wrote:
 >On Fri, Jan 17, 2014 at 02:23:44PM +0100,
 Anne van Kesteren wrote:
 >> 
 >> What's important for
 interoperability in domain names is translation
 >> of a sequence of code points to a
 sequence of bytes that can be used
 >>
 within the DNS.
 >
 >This is part of where we disagree.  What
 is important for
 >interoperability is not
 only what you say, but also a reversible
 >translation so that when you get the octets
 used in the DNS back, they
 >can always be
 turned back into the sequence of code points you started
 >with.  IDNA2003 doesn't have that
 property, which is the reason for
 >the
 backward incompatibility.
 
 I read Anne as saying, for the purposes of this
 discussion, he cares
 about the definition of
 a `uint8_t* f(codepoint_t* input) { ... }`
 function and not user interface or other
 issues. There was no impli-
 cation in the
 quoted text whether he cares about `f` being injective.
 (He might have said something about this
 elsewhere, but not here).
 -- 
 Björn Höhrmann · mailto:bjoern@hoehrmann.de
 · http://bjoern.hoehrmann.de
 Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
 http://www.bjoernsworld.de
 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78
 · http://www.websitedev.de/ 
 
 
Received on Friday, 17 January 2014 19:03:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:16 UTC