Re: [Jcardcal] Barry Leiba's Discuss on draft-ietf-jcardcal-jcal-09: (with DISCUSS and COMMENT)

[Philipp Kewisch <[e-mail]>]

On 3/24/14, 11:40 PM, Barry Leiba wrote:
>>> Of course, one could also ask why the same normative requirements are
>>> in both sections 3.1 and 4.  Shouldn't it be in one place only?
>> The excerpt in Section 3.1 speaks of the reverse process, which is of
>> course described in more detail in section 4. Its there for convenience
>> and to complement the former paragraph. I guess what we could do is move
>> that paragraph to Section 4 and just mention that the reverse process
>> works similarly, as further described in Section 4. Would you prefer that?
> I would prefer that, because I prefer to have information in one
> place, avoiding errors and confusion caused by imperfect duplication.
> But check with your responsible AD (Pete) for further instruction.
> You have certainly resolved all my DISCUSS issues.
>
> Barry
Hi Barry, Pete, all,

I have taken a look at this issue, here is my proposal to fix it:

First of all, the paragraphs in Section 3.1:

OLD
   When converting from iCalendar to jCal, first iCalendar lines MUST be
   unfolded.  Afterwards, any iCalendar escaping MUST be unescaped.
   Finally JSON escaping (e.g., for control characters) MUST be applied.

   The reverse order applies when converting from jCal to iCalendar.
   First, JSON escaping MUST be unescaped.  Afterwards, iCalendar
   escaping MUST be applied.  Finally, long lines SHOULD be folded as
   described in [RFC5545].
NEW
  When converting from iCalendar to jCal, first iCalendar lines MUST be
   unfolded.  Afterwards, any iCalendar escaping MUST be unescaped.
   Finally JSON escaping, as described in [RFC7159] Section 7, MUST be
   applied.  The reverse order applies when converting from jCal to
   iCalendar, which is further described in Section 4.
END

Then I looked into Section 4, I think it requires some additional words
in general. Here is what I changed:


OLD
   When converting component, property and property parameter values,
   the names SHOULD be converted to uppercase.  Although iCalendar names
   are case insensitive, common practice is to keep them all uppercase
   following the actual definitions in [RFC5545].
  
   Character escaping and line folding MUST be applied to the resulting
   iCalendar data as required by [RFC5545] and [RFC6868].
NEW
   Converting jCal to iCalendar reverses the process described in
   Section 3.  This section describes a few additional requirements for
   conversion.

   When converting component, property and property parameter names,
   they names SHOULD be converted to uppercase.  Although iCalendar
   names are case insensitive, common practice is to keep them all
   uppercase following the actual definitions in [RFC5545].

   During conversion, JSON escaping MUST be unescaped.  Afterwards,
   iCalendar escaping, as defined by [RFC5545] and [RFC6868] MUST be
   applied.  Finally, long lines SHOULD be folded as described in
   [RFC5545], Section 3.1.
END

Let me know what you think.
Philipp