Re: [calsify] WGLC JSCalendar

Hi all,

I've just read the current draft and had a few minor nitpicks, see below.

4.1.4.  prodId 
(https://tools.ietf.org/html/draft-ietf-calext-jscalendar-20#section-4.1.4)

In this context, what is the JSCalendar object? Is it the JSON object 
(or its serialized form) I'm currently looking at or is it the calendar 
entity that is represented by this JSON object?

To put it in other words, should a JSCalendar serializer always insert 
its own "prodId" when serializing an internal representation to a 
JSCalendar JSON file (even if no data was changed)?

Or is this related to the "updated" field? Should you only update 
"prodId" when you also update "updated"?

4.3.2.  recurrenceRule 
(https://tools.ietf.org/html/draft-ietf-calext-jscalendar-20#section-4.3.2)

The limits mentioned for "byMonth", "byMonthDay" and "byYearDay" are 
specific to the Gregorian calendar scale, e.g

> Valid values are 1 to 31 or -31 to -1
>
But other calendar scales may other limits. We should make clear that 
the limits depend on the maximum values of the respective calendar scale 
and maybe add "for Gregorian calendars the valid values are 1 to 31 or 
-31 to -1".

4.3.2.1.  Interpreting recurrence rules 
(https://tools.ietf.org/html/draft-ietf-calext-jscalendar-20#section-4.3.2.1)

> which defaults to gregorian if omitted.
gregorian should be quoted, I guess.

It may also be worth stating explicitly that the "skip" parameter only 
affects "yearly" and "monthly" rules (IIRC RScale didn't address 
ambiguous/invalid times during daylight saving changes)

In this paragraph:

>   If a skip property is defined and is not "omit", there may be
>         candidates that do not correspond to valid dates (e.g. 31st
>         February in the gregorian calendar).  In this case, the
>         properties MUST be considered in the order above and:
Gregorian should be capitalized.

Regards,

Marten

Am 15.10.19 um 20:03 schrieb Daniel Migault:
>
> Hi,
>
> This email starts a WGLC for draft-ietf-calext-jscalendar [1].
>
> The WGLC will end on October 30. Please review the document and 
> provide your feed back on the mailing list. All feed back are useful 
> for our AD to move the work forward.
>
> Yours,
>
> Daniel
>
> [1] https://tools.ietf.org/html/draft-ietf-calext-jscalendar-20 
> <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-20>
>
> *From:* calsify <calsify-bounces@ietf.org> *On Behalf Of *Neil Jenkins
> *Sent:* Tuesday, October 15, 2019 11:56 AM
> *To:* calsify@ietf.org
> *Subject:* [calsify] Request to start last call for JSCalendar
>
> Hi all,
>
> As you've probably seen, I've published another update 
> <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-20> to the 
> JSCalendar draft with the changes discussed at the interim IETF 
> meeting/CalConnect last week. A quick summary of the changes:
>
>   * Added Location#categories property
>   * Added Participant#scheduleAgent property
>   * Added Participant#language property
>   * Removed Participant#attendance property (this maps to roles instead)
>   * Made Participant#sendTo optional
>   * Made Alert#trigger mandatory
>
> *Daniel*, could you please restart the last call; I think two weeks 
> should be sufficient given how extensively this draft has already been 
> reviewed over the years!
>
> Cheers,
>
> Neil.
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

-- 
Marten Gajda
CEO

dmfs GmbH
Schandauer Straße 34
01309 Dresden
GERMANY

phone: +49 177 4427167
email: marten@dmfs.org

Managing Director: Marten Gajda
Registered address: Dresden
Registered No.: AG Dresden HRB 34881
VAT Reg. No.: DE303248743