IETF Logo Mail Archive

Re: [calsify] JSCalendar duration vs. end time

Doug Royer <douglasroyer@gmail.com> Sat, 09 March 2019 20:01 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 9FB59130E68 for <calsify@ietfa.amsl.com>; Sat, 9 Mar 2019 12:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Un9OP46xgMF3 for <calsify@ietfa.amsl.com>; Sat, 9 Mar 2019 12:01:56 -0800 (PST)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 2FEB0130ECF for <calsify@ietf.org>; Sat, 9 Mar 2019 12:01:56 -0800 (PST)
Received: by mail-ot1-x330.google.com with SMTP id z19so752313otm.2 for <calsify@ietf.org>; Sat, 09 Mar 2019 12:01:56 -0800 (PST)
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=jqx6Sc2wqkh0u2d/K6PSzO3PnlrNlQtqoZZjOO/CmdI=; b=GgFm52ouNUQfk5dea6bwyfi5qqIcYnUgSDzlsB5+AdRIqv4xQVbuR9ns7Fx8c4ReEI QIkjG1yav+JoFfmI/jjvOCtirfkFyergA2g/ZXfalKpDV0/uljJ5XJZn/4fCcbFwCY1V lynekom6n/GASlGgthu/Andy7empaPpL8ERnYY2aq0u8hilqQBj8XspVDRZFTbKZ6LnW VfnOLvGy4VMArkFiSRXmxjiqwmi4CI0lrJiE32/wQb8e1kri+SdapsbD8MYXjFydIdWw D+6gHJKtlKrNZUkshkKxSkd9drHwftC3aX0rOpXa/Q6oUZhuXwltohg1f38BPtWrdTwd /fmA==
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=jqx6Sc2wqkh0u2d/K6PSzO3PnlrNlQtqoZZjOO/CmdI=; b=pCg1SRDofCsbIBVpFvDGmgz78N0vrQER9nBw0xDIXa9WuW644zOkHf21VlUlW3XQ8u ObQyXMfXq2qz24lKPAVofeLCxYU/3AuIqdxxcwErg5zmdz1GQWhyPsUXtHk3NnFvH4mr saupcIqJ7rjP+6JMi1XD7fBzcqYB6Q7/lrMgT0ImDcqAeTbHKJB0H1A304bb2pGnfvjD cnGSPE6r18lDjYJVZxZkSGKkGhuuSgURaj/5eeYSUvzUZJXD6lV3MUQj/3ayxGVuo3TM ACKof/tJdal+7QOzwCFmWdW27dREIi9JZHFkMh/ipR5ifKbd1SVDNFMswX99vK9oV/0m K8BA==
X-Gm-Message-State: APjAAAUMJqYvt2AxtG5cypdYZDZ1g3P83CaNvseJEDYbYOuWq+bolyzw z6WCHiueDTls37/lmEL7PXggUVsRpPu+
X-Google-Smtp-Source: APXvYqzBRX/EXvEK6xZxKjW4jbyR56HVpSocpfQcJjKmIDl84t20KP6Rg0JSCkLD+RBUmu6HW90Aow==
X-Received: by 2002:a9d:4809:: with SMTP id c9mr15086587otf.215.1552161715222; Sat, 09 Mar 2019 12:01:55 -0800 (PST)
Received: from [192.168.1.7] (75-174-58-238.boid.qwest.net. [75.174.58.238]) by smtp.googlemail.com with ESMTPSA id q1sm454326oth.42.2019.03.09.12.01.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Mar 2019 12:01:54 -0800 (PST)
From: Doug Royer <douglasroyer@gmail.com>
X-Google-Original-From: Doug Royer <DouglasRoyer@gmail.com>
To: Дилян Палаузов <dilyan.palauzov@aegee.org>, calsify@ietf.org
References: <1550160126.3602072.1658018976.28709BD3@webmail.messagingengine.com> <53c5912a8b973aeb0ab67a0d8b7ed0072c5f23b7.camel@aegee.org> <e8b254ac-4ff9-f889-5338-fb4fa124eab1@gmail.com> <50391a5de6edf4b9caa22c49839d6a11c0f6dde6.camel@aegee.org>
Organization: http://SoftwareAndServices.NET
Message-ID: <94a90dc2-8008-d6e2-0463-f5274d5de73f@gmail.com>
Date: Sat, 09 Mar 2019 13:01:53 -0700
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: <50391a5de6edf4b9caa22c49839d6a11c0f6dde6.camel@aegee.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040902090207060909020005"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/-6thRDXQTzwYPvwZtyATF0ycicc>
Subject: Re: [calsify] JSCalendar duration vs. end time
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: Sat, 09 Mar 2019 20:02:11 -0000

On 3/9/19 12:52 PM, Дилян Палаузов wrote:
> Hello Doug,
> 
> for an event with five slots, each slot containig six parallel meetings, there are 4 breaks and 30 sessions (so 34
> events).  If the first slot gets prolonged/shortened, 28 events (4 breaks and 24 sessions) that are in the future, need
> to be reissued, unless they have relative times.
> 
> If for each of the five slot, one of the events has relative time to the previous break, and the other parallel events
> have start/stop/duration as that event, only one event per slot needs adjustment.
> 
> The benefit of having relative times (start/end) is to reissue less changes.  In this case it could be reissuing
> one..four event(s) versus reissuing 28 events.  The latter option is … error prone.
> 
> Regards
>    Дилян

And when they end across time zone changes, it is still a mess and 
ambiguous. Coming up with more of the same examples  does not make it 
unambiguous.

-- 

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

v2.23.0 | Report a Bug | By Email