[weirds] on the subject of vcard

[Andy Newton <[e-mail]>]

All,

I started looking at the vCard JSON draft. You can find it here:
http://datatracker.ietf.org/doc/draft-bhat-vcarddav-json/

In my opinion there are a couple of issues we need to keep in mind:

First, the current draft expired over a month ago. Even if it were kept
current, it doesn't look like that draft has a working group home, and
therefore placing a dependency on it could delay the WEIRDS work. Our
working group could adopt it, but that seems rather odd as vCard is not
the focus of WEIRDS.

Second, the vCard JSON draft has a section carved out for a JSON schema.
At present, there is no standardized JSON schema language. I think making
our work depend on a JSON schema language could delay our deliverables.
And I say this as the author of the JSON Content Rules draft
(https://datatracker.ietf.org/doc/draft-newton-json-content-rules/)Š I.e.
I'm not willing to subject WEIRDS to my own JSON schema language
preferences.

While I do think vCard is a good idea, I'd like to also note that
supporting it has never been stated as a goal of this working group. Given
the timeline for our milestones, I propose the following compromise: let
us go forward with the current flat postal address structure, and when
vCard JSON comes to maturity we can revisit the issue and extend the
protocol to use vCard JSON.

Is this compromise acceptable? What do you all think?

-andy