Re: [Last-Call] Artart last call review of draft-ietf-calext-vcard-jscontact-extensions-06

[Robert Stepanek <rsto=40fastmailteam.com@xxxxxxxxxxxxxx>]

Carsten, many thanks. The upcoming version of the RFC draft will incorporate all your feedback.

On Mon, May 1, 2023, at 1:07 PM, Carsten Bormann via Datatracker wrote:

## major:

Are you sure

           [I-D.ietf-calext-jscontact]

           [I-D.ietf-calext-jscontact-vcard]

should be informative references?

Are the definitions in draft-ietf-calext-vcard-jscontact-extensions

really meant to be self-contained?

We changed this to be normative references now.

E.g., I'm not sure I understand GRAMMATICAL-GENDER without first

having read those other drafts (actually, I'm not sure I understand it

*with* having read those).

We now aligned the descriptions of both the JSContact and vCard properties for grammatical gender. It now includes an example that highlights that the German language distinguishes grammatical gender in salutations such as "Sehr geehrte" (feminine) and "Sehr geehrter" (masculine).

Section 3.5:

I do not understand the syntax of ranks-param, which requires exactly

five instances of ranks-component to be present.  This is not

supported by the examples.

Have the examples been checked against the ABNF?

Fixed. One instance is required with up to 4 instances following.

## minor:

Section 2.4:

The language tag property is called "LOCALE".

The latter term usually implies characteristics beyond those of a language tag.

Thanks. We renamed this to DEFLANGUAGE (default language) in vCard. We also renamed the according property in the JSContact RFC.

Section 3.6 uses "the same type" and then "the same name" a few times.

Is name and type the same concept here?  Still, wouldn't it help to

use the same referent to that concept throughout?

Fixed, we now consistently talk about "property names" which is in line with RFC 6450.

## idnits:

  ** The abstract seems to contain references ([RFC6350]), which it

     shouldn't.  Please replace those with straight textual mentions of the

     documents in question.

Fixed.

(See Section 4.3 of RFC 7322.)

## nits:

Section 1: s/loosing/losing/

Section 2.6: s/equal is they match/equal if they match

Fixed

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call