Re: [Tzdist] Fwd: [tzdist] #9 (): TZIDs overlap?!

[Daniel Migault <[e-mail]>]

Thank Stephen for this feed back.

As this issue has not yet been solved, I would like the WG to comment on
it, so we can reach consensus soon on that issue.



On Sun, Sep 21, 2014 at 11:47 PM, Stephen Colebourne <[e-mail]>
wrote:

> I recommend consideration of the same approach as I used in Java JSR-310:
> http://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html
>
> "Time-zone rules are defined by governments and change frequently.
> There are a number of organizations, known here as groups, that
> monitor time-zone changes and collate them. The default group is the
> IANA Time Zone Database (TZDB). Other organizations include IATA (the
> airline industry body) and Microsoft.
>
> Each group defines its own format for the region ID it provides. The
> TZDB group defines IDs such as 'Europe/London' or 'America/New_York'.
> TZDB IDs take precedence over other groups.
>
> It is strongly recommended that the group name is included in all IDs
> supplied by groups other than TZDB to avoid conflicts. For example,
> IATA airline time-zone region IDs are typically the same as the three
> letter airport code. However, the airport of Utrecht has the code
> 'UTC', which is obviously a conflict. The recommended format for
> region IDs from groups other than TZDB is 'group~region'. Thus if IATA
> data were defined, Utrecht airport would be 'IATA~UTC'. "
>
> ie. TZDB takes precedence, everyone else must use group~region
>
> Note that no central coordination is required by the text above.
>
> Stephen
>
>
>
>
> On 19 September 2014 09:30, Eliot Lear <[e-mail]> wrote:
> > Hi Cyrus,
> >
> > I'm prepared to propose changes to address this issue, that would
> > include an IANA registry for a list of authorities.  I'm also happy to
> > see other alternatives.
> >
> > Eliot
> >
> >
> > ---------- Forwarded message ----------
> > From: tzdist issue tracker <[e-mail]>
> > To: <[e-mail]>, <[e-mail]>
> > Cc: <[e-mail]>
> > Date: Tue, 19 Aug 2014 10:28:14 +0000
> > Subject: [tzdist] #9 (): TZIDs overlap?!
> > #9: TZIDs overlap?!
> >
> >  Draft: draft-douglass-timezone-service-11
> >
> >  Section 3.1 contains the following text:
> >
> >     It is possible that timezone identifiers from
> >     different publishers overlap, and there might be a need for a
> >     provider to distinguish those with some form of "namespace" prefix
> >     identifying the publisher.  However, development of a standard
> >     (global) timezone identifier naming scheme is out of scope for this
> >     specification.
> >
> >  Without getting into the business of how the publisher names time zones
> a
> >  simple distinction of who the publisher is will eliminate overlap.  One
> >  might consider a URN in this context.
> >
> > --
> > ---------------------------+-----------------------------------
> > Reporter:  [e-mail]  |      Owner:  [e-mail]
> >     Type:  defect          |     Status:  new
> > Priority:  major           |  Milestone:
> >  Version:                  |   Severity:  Candidate WG Document
> > Keywords:                  |
> > ---------------------------+-----------------------------------
> >
> > Ticket URL: <http://trac.tools.ietf.org/wg/tzdist/trac/ticket/9>
> > tzdist <http://tools.ietf.org/tzdist/>
> >
> >
> >
> >
> > _______________________________________________
> > Tzdist mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/tzdist
> >
>
> _______________________________________________
> Tzdist mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tzdist
>



-- 
Daniel Migault
Orange Labs -- Security
[phone]