Re: [Jcardcal] [Gen-art] Genart LC review: draft-ietf-jcardcal-jcal-09

Philipp Kewisch <kewisch@gmail.com> Thu, 20 March 2014 20:39 UTC

Return-Path: <kewisch@gmail.com>
X-Original-To: jcardcal@ietfa.amsl.com
Delivered-To: jcardcal@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D771A07DC; Thu, 20 Mar 2014 13:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ykxTbwCwVLE5; Thu, 20 Mar 2014 13:39:46 -0700 (PDT)
Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 4F09B1A07F8; Thu, 20 Mar 2014 13:39:40 -0700 (PDT)
Received: by mail-bk0-f53.google.com with SMTP id r7so110091bkg.12 for <multiple recipients>; Thu, 20 Mar 2014 13:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=/AFnX1M4ZJrXGjg3xn0nwPN4n8yCFHKeGJwYgQ+6fpg=; b=li96Ls2eIxrdSoQ+vTHTQLcgjjmI8fjmk34ChQVYH5rBe27opL/qbQDKZX0hkQHecr fXhd+FzpfWOTRfzw/L1vow4IXShq94rVYSwE4me9xnY5eCaaHm+95G1jMyRLJxzVGdm8 1gL0/W/AhBm/K4Mw/qGy8pbmyGfZoi5NBtPPJOSq9GWKx5yCIuoRcnzyKep1jPRn6taz hxL7C22ISLq1zrKw9CslkcWcRqjkHs9PetwAH/cnSYoA8UlBBGu/wzcI8Ip66WWkBwAN dIr3vfJQpHhfNL7zjNbtobCxIrHUnX3oscHcptj/gDoxWfwLG4WqlOrlLMnfV/o271PW LzOw==
X-Received: by 10.205.100.200 with SMTP id cx8mr47469bkc.68.1395347970664; Thu, 20 Mar 2014 13:39:30 -0700 (PDT)
Received: from [192.168.2.104] (p5DC1549E.dip0.t-ipconnect.de. [93.193.84.158]) by mx.google.com with ESMTPSA id v12sm3151290bko.17.2014.03.20.13.39.29 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Mar 2014 13:39:30 -0700 (PDT)
Message-ID: <532B5201.8020508@gmail.com>
Date: Thu, 20 Mar 2014 21:39:29 +0100
From: Philipp Kewisch <kewisch@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Thunderbird/28.0
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>, General Area Review Team <gen-art@ietf.org>, draft-ietf-jcardcal-jcal@tools.ietf.org, jcardcal@ietf.org
References: <531F5C0D.5040903@nostrum.com> <531F5EC6.5010306@nostrum.com>
In-Reply-To: <531F5EC6.5010306@nostrum.com>
Content-Type: multipart/alternative; boundary="------------010004030805090105050806"
Archived-At: http://mailarchive.ietf.org/arch/msg/jcardcal/0iC4lrxkOXm0g4utJCjmP-JZfuc
Subject: Re: [Jcardcal] [Gen-art] Genart LC review: draft-ietf-jcardcal-jcal-09
X-BeenThere: jcardcal@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: JSON data formats for vCard and iCalendar WG <jcardcal.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jcardcal/>
List-Post: <mailto:jcardcal@ietf.org>
List-Help: <mailto:jcardcal-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Mar 2014 20:39:48 -0000

On 3/11/14, 8:06 PM, Robert Sparks wrote:
> Actually, there are perhaps some corners to consider knocking off
> related to:
>> * I verified that the syntax numbers with fractional parts is the
>> same in both iCal in jCal. Specifically "4." is not valid in either
>> grammar, so there is no need to discuss something like adding a 0 or
>> remove the decimal point during conversion.
> [...]
>
> So, in iCal, you could have '+4' . json doesn't allow the plus sign.
>
> iCal appears to allow leading 0s. json does not.

Maybe this just requires some adjustment in wording. The gist is that
numbers should be represented in whatever way needed by the underlying
rfc, i.e 5545 or 7159. If a number represented with a leading + sign is
found in iCal, the same number can be represented without a leading +
sign in JSON. Analogous for leading zeros. Would you prefer this is
explicitly stated?


>
>
>
>
>
> _______________________________________________
> jcardcal mailing list
> jcardcal@ietf.org
> https://www.ietf.org/mailman/listinfo/jcardcal