Re: [calsify] draft-ietf-calext-jscalendar-icalendar-02

There's another issue which is touched on in the FRACTIONAL form of the 
spec -

how does a client figure out that the property value no longer matches 
the parameter?

e.g jscalendar aware system sends

DTSTART;SUBSECOND=0.0123:20201205T040506

Old client updates DTSTART but does as it should and preserves the SUBSECOND

DTSTART;SUBSECOND=0.0123:20201205T050000

The SUBSECOND parameter was for the old value. I guess we can see it 
changed but we need to have wording in there such as I added to the 
FRACTIONAL version.

On 12/21/20 10:31, Robert Stepanek wrote:
> I have updated the RFC draft on Github. Here is the excerpt, I 
> appreciate any feedback:
>
> 2.1.  SUBSECOND parameter
>
>     Parameter name:  SUBSECOND
>
>     Purpose:  To specify fractional seconds for time values and
>        durations.
>
>     Description:  This parameter MAY be specified on properties of type
>        DATE-TIME, DURATION and TIME.  It MUST be a FLOAT value less than
>        1.0 and MUST NOT be negative.  Implementations MUST ignore
>        presence of the SUBSECOND parameter on RECURRENCE-ID properties
>        when determining recurrence overrides.
>
>     Format Definition:
>
>     This parameter is defined by the following notation:
>
>         subsecond-param = "SUBSECOND" "=" float
>
>     Example:
>
>         DTSTART;SUBSECOND=0.0123:20111205T040506
>
> On Mon, Dec 21, 2020, at 2:03 PM, Ken Murchison wrote:
>>
>>
>> On 12/21/20 7:54 AM, Robert Stepanek wrote:
>>> On Mon, Dec 21, 2020, at 1:42 PM, Ken Murchison wrote:
>>>> On 12/21/20 7:31 AM, Robert Stepanek wrote:
>>>>> As noted in my previous email: we already agreed to not set the 
>>>>> complete timestamp in the FRACTIONAL parameter value.
>>>>>
>>>>> Instead we will set a SUBSECONDS parameter which will be defined 
>>>>> to a FLOAT value with MUST be positive and less than 1.0.
>>>>
>>>> OK, but if it MUST be positive, don't we still have the issue that 
>>>> Mike brought up regarding rounding?  Or we will state that the 
>>>> property value MUST NOT be rounded up.
>>>>
>>>
>>> It MUST NOT be rounded, because any client aware of SUBSECONDS would 
>>> then calculate with a wrong value. The SUBSECONDS parameter only 
>>> defines the fractional seconds part.
>>
>>
>> OK.  WFM
>>
>> -- 
>> Kenneth Murchison
>> Senior Software Developer
>> Fastmail US LLC
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org <mailto:calsify@ietf.org>
>> https://www.ietf.org/mailman/listinfo/calsify 
>> <https://www.ietf.org/mailman/listinfo/calsify>
>>
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify