Re: [auth48] AUTH48: RFC-to-be 9555 <draft-ietf-calext-jscontact-vcard-13> for your review

[Orie Steele <[e-mail]>]

Agree with Robert.

Thanks for making this change, in case "text/vcard" is rejected (for some
tooling reason) "text/plain" would also work... in fact it may be more
appropriate if the source code is not a fully valid vcard in text
serialization... Is it valid?

Regarding comment 4:

OLD:

   The PREF parameter (Section 5.3 of [RFC6350]) converts to the pref
   property of that JSContact object, to which the vCard property having
   this parameter converts.

NEW:

   The PREF parameter (Section 5.3 of [RFC6350]) converts to the pref
   property of the derived JSContact object.

Is this acceptable?

OS

On Thu, Apr 4, 2024 at 11:16 AM Robert Stepanek <[e-mail]>
wrote:

> On Thu, Apr 4, 2024, at 5:06 PM, Murray S. Kucherawy wrote:
>
> On Thu, Apr 4, 2024 at 3:01 AM Robert Stepanek <[e-mail]>
> wrote:
>
>
> Hi,
>
> attached is the updated document. Please see my replies below.
>
> On Thu, Apr 4, 2024, at 2:08 AM, Karen Moore wrote:
>
> 1) Note that “vcard” is not on the list of acceptable sourcecode types.
> Please review the list at "
> https://www.rfc-editor.org/materials/sourcecode-types.txt” and let us
> know if there is an applicable type that may be used instead of "vcard". If
> there isn’t one, you may suggest a new one (that we would run by RPAT for
> approval), or you can leave the “type" attribute blank.
>
>
> We now changed the sourcecode type to "text/vcard". We'll keep using
> "json" instead of "application/jscontact+json" for the JSContact examples.
>
>
> Orie will have to decide, but this feels like a significant (i.e., not
> just editorial, not correction of a simple error) change to be making in
> AUTH48.  Should the WG confirm on the record first?
>
>
> Just in case it isn't clear: this is not about changing a media type. It
> is about what goes into the "type" attribute inside the RFC XML so that the
> XML renderer can do its formatting. No one reading the rendered spec should
> even see that value, but we want it to have the right type in case we might
> want to do some automated processing of the RFC XML document.
>


-- 


ORIE STEELE
Chief Technology Officer
www.transmute.industries

<https://transmute.industries>