IETF Logo Mail Archive

Re: [calsify] draft-ietf-calext-jscalendar - thoughts

Doug Royer <douglasroyer@gmail.com> Mon, 13 May 2019 22:08 UTC

Return-Path: <douglasroyer@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B043120086 for <calsify@ietfa.amsl.com>; Mon, 13 May 2019 15:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 MkZLKHmis6ZU for <calsify@ietfa.amsl.com>; Mon, 13 May 2019 15:08:58 -0700 (PDT)
Received: from mail-it1-x133.google.com (mail-it1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 27185120006 for <calsify@ietf.org>; Mon, 13 May 2019 15:08:52 -0700 (PDT)
Received: by mail-it1-x133.google.com with SMTP id 9so1613363itf.4 for <calsify@ietf.org>; Mon, 13 May 2019 15:08:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=iY/YI85+PkmrmsXc2dsxxs+ze8Gihjw3hdnk8PaXnOY=; b=X4/AQ4quJrGGd9iLNLQpsm5eHLeK9BzdtsDtZ8zSCt1aUTLS3clBxuZ7xP/APgJP0R pGfRmfLQCX5hQgLTjok5zkrylQ8hJKLL2yYZBzK2OXQnrQ85Djcyt47WgSPf4XVY/i30 +CMJhik0t6XKqlfoJzxQLkIv4xkIZzdhcjyBOpYHgqA0d+VgyZB2YBTmLbFWXg5Tm1w7 XqpSf6HKZQNIhkGw6qFoDhMqI0rOW5TYuAUbp3kcjECVebcpeHQuxFW38mf4uZeh/nJ2 5b9EsTibqB7/7upWMgcXm1fJ26m2d6MKG7c9J6K5QX/TRxEIAy9xst/1yr0gwszA4nMV l3rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=iY/YI85+PkmrmsXc2dsxxs+ze8Gihjw3hdnk8PaXnOY=; b=hYUx+ZB/Q3D1Ep1iBE3U52y9CSyxFqLIldIpB57EvwqOcD7UA1oz9wNV6MUqIkQKqO RKTXG+ZcbNM0+Dh/He8NN2ZgfTdS69Tic1Xz1s+Z/Am9YvAS0iTqMJI2GvSlI3YFSjkw rDPuvN4aoyHv/C0IbIV1MkXUm3rLS56QDXIbHyQDNiL3rxzs53bHLKt+skrvs7Sv4AQC mW8gEXrUdBqsv0R11hDs50LiRHU5xBDJOqORFv59VdzattxsGCuPKaxU3uM4AdtqZZ8A vaFP0YPg+iBwWTPdjX/wtVyjbfsScfuY0SnsgXA52X3RRiN3hrC3lLVj9l/QdHmlSQzX 5/fg==
X-Gm-Message-State: APjAAAXNJTpzVfn3HBe2FIBIWV5bd6qm33GnOHz97VHMLdKI5cY0N9s8 v1E8OP26fQm9yhLzGbZSmC3j+o/5W4c1
X-Google-Smtp-Source: APXvYqz47g7tyOICSnayqc+AqsaVclDFkgl95cha/nGJ/nzBji1dbLuR029I3r0To/+6UGncxOwn1g==
X-Received: by 2002:a05:660c:10:: with SMTP id q16mr1107186itj.149.1557785331024; Mon, 13 May 2019 15:08:51 -0700 (PDT)
Received: from [192.168.1.7] ([174.27.51.111]) by smtp.googlemail.com with ESMTPSA id h191sm475417ith.5.2019.05.13.15.08.49 for <calsify@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 13 May 2019 15:08:49 -0700 (PDT)
From: Doug Royer <douglasroyer@gmail.com>
X-Google-Original-From: Doug Royer <DouglasRoyer@gmail.com>
To: calsify@ietf.org
References: <cb1b4ab3-3aaf-e22e-e7cd-2b45bad5cb87@gmail.com> <9c2a894f-2ab1-4a05-9ced-885f1801155a@beta.fastmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <f21da174-5c0e-1ebe-1c81-542a4278ea61@gmail.com>
Date: Mon, 13 May 2019 16:08:49 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <9c2a894f-2ab1-4a05-9ced-885f1801155a@beta.fastmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms060601060707020101010501"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/vqtKBQjC_RZc9xwynsEOdMxikpE>
Subject: Re: [calsify] draft-ietf-calext-jscalendar - thoughts
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2019 22:09:00 -0000

Why change the names and some formats of existing types?
One example why were the dashes added to date? (YYYYMMDD vs YYYY-MM-DD)

It seems like a lot of work is being done to make it incompatible and 
complicate the conversion process.

In some cases only the case of the token was changed (UID -> uid).
I do not see a technical reason, and it just adds to some confusion.
Does it really matter to any code? Users will not see the contents.

It just seems that someone did not like the names and wanted to start over.

-- 

Doug Royer - (http://DougRoyer.US)
Douglas.Royer@gmail.com
714-989-6135

v2.23.0 | Report a Bug | By Email