Re: [Tzdist-bis] [calsify] JSCalendar timezones

Daniel Migault <daniel.migault@ericsson.com> Thu, 14 February 2019 17:18 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: tzdist-bis@ietfa.amsl.com
Delivered-To: tzdist-bis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28EF12426A; Thu, 14 Feb 2019 09:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.018, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iuZdYyFTWMSt; Thu, 14 Feb 2019 09:18:08 -0800 (PST)
Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BDD3131088; Thu, 14 Feb 2019 09:18:07 -0800 (PST)
Received: by mail-lf1-f52.google.com with SMTP id j1so5102855lfb.10; Thu, 14 Feb 2019 09:18:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=SZmyrpR1vrZ7AW5zvPS9FA2CCK0Bncw3AvyQRQ3h1JY=; b=YPxyp8gMy4+GW3/UruJTqufhnpQf8IUlT+SqoAshKd+/4m2/FU3Nl+DqQZ28g+Lqyx h7nACed6xD0dUktHcUi3Bo4aDv0lyoUNcjVE+pQap5a+NFpC4Orzrk+jzpxOyxYw13UY HQGAeD2dvCzksxah463p4wVKEefdvSUxSK2y1P+h09Xb0LGpMSNzX4WTzJBlIZSWr0Gr aXax/w78hoBLsK5mzp2uE8Y7AdKmFdq276c1ODDaOpgAJHyNV7X/XYLJRFmystq6H4Dx yfsowqhYDoxBDQyOErWTX6EGeEobGyesy6fTgd2P2fCC0vaZ4Qy7cL2WLFPUfNveB0Jl uRjQ==
X-Gm-Message-State: AHQUAubdycRrVBdpqxLlhX7/lUN4B6upXp8bWFP7ZGp0UNwystEPr6XQ 1i2UKq+JAx143R9WoUef+4LFTXY0IrFMhZkPd5I=
X-Google-Smtp-Source: AHgI3IYjGDhAo3n9qFbvenT0jy7vNqtW0mBgUrFMqTO1XO8ypQuYBZ/MVtofOK7xNFhoFFNQt8C2iRUgzL2Jh37JpUw=
X-Received: by 2002:a19:f619:: with SMTP id x25mr2978507lfe.57.1550164685591; Thu, 14 Feb 2019 09:18:05 -0800 (PST)
MIME-Version: 1.0
References: <1550160111.3612386.1658010576.0F11D14D@webmail.messagingengine.com>
In-Reply-To: <1550160111.3612386.1658010576.0F11D14D@webmail.messagingengine.com>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Thu, 14 Feb 2019 12:17:53 -0500
Message-ID: <CADZyTknf0OTxRJxHxMb5m6B+jaC46n1OGG1Ogip=V3+u6Y3j8A@mail.gmail.com>
To: Robert Stepanek <rsto@fastmailteam.com>, calsify@ietf.org, tzdist-bis@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006d99dd0581ddd7ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tzdist-bis/WtYWLQp_BcmgqKWmPwWoM0-pSy4>
Subject: Re: [Tzdist-bis] [calsify] JSCalendar timezones
X-BeenThere: tzdist-bis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Extensions to Time Zone Data Distribution Service <tzdist-bis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist-bis/>
List-Post: <mailto:tzdist-bis@ietf.org>
List-Help: <mailto:tzdist-bis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2019 17:18:11 -0000

Hi Robert,

I am adding tzdist-bis in the discussion.

Not being URN expert, I have the feeling that using a SOLIDUS would be used
to define global identifiers versus non global and that URI might be more
appropriated. I would as much as possible prevent global identifiers scheme
be impacted by ill-clients.

I believe inputs from people that have more expertise on urn would be
welcome.

Yours,
Daniel

On Thu, Feb 14, 2019 at 11:03 AM Robert Stepanek <rsto@fastmailteam.com>
wrote:

> At CalConnect XLIV last week, the need for a non-IANA time zone
> identifiers and custom time zone definitions was raised. We'd like to
> discuss options how to support them in JSCalendar.
>
> Currently, an event's timezone in JSCalendar is defined in the timeZone
> property, which is of string type.  Its value must be a name in the IANA
> time zone database, or null for floating time (see the latest spec here
> <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-11>).
>
> We discussed, if to replace the string value with a URI. That way we could
> either use a IANA time zone database name in a to be defined URI scheme, or
> e.g. could embed custom VTIMEZONEs in a data URI.
> However, on second thought we'd rather prefer a different solution,
> because URIs in iCalendar parameters could cause breakage on ill-behaving
> clients. There also wouldn't be an obvious urn namespace or URI scheme to
> use for IANA names, AFAIK.
>
> Alternatively, we could keep the time zone identifier as string value, and
> use the same escape mechanism with a SOLIDUS character as specified in RFC
> 5545  (see section 3.8.3.1
> <https://tools.ietf.org/html/rfc5545#section-3.8.3.1>). All time zone
> identifiers that do not start with SOLIDUS must be an IANA time zone. For
> custom timezones, we might want to consider defining a JSON representation
> of time zones, which could be defined in a timeZones property on the
> JSCalendar object, keyed by their time zone identifier.
>
> Do you have other suggestions on how to handle non-IANA timezones in
> JSCalendar?
>
> Cheers,
> Robert
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>