Hi Gavin,
Il 05/07/2019 16:57, Gavin Brown ha scritto:
Hi Mario,
I would be happy to publish a new version of draft-brown-epp-contacts-in-rdap
which uses JSContact rather than its own representation of contact data. That
would glue JSContact and RDAP together.
IMHO it would be better to wri
Hi Mario,
>> I would be happy to publish a new version of
>> draft-brown-epp-contacts-in-rdap which uses JSContact rather than its own
>> representation of contact data. That would glue JSContact and RDAP together.
>
> IMHO it would be better to write a new document with the contribution of who
Hi Gavin,
Il 02/07/2019 14:05, Gavin Brown ha scritto:
Hi Mario,
I like JSContact and the current draft certainly looks good enough to be usable
in RDAP. I imagine more work will be needed before JSContact will have feature
parity with vCard/jCard.
Yes, the JSCard structure is not completed
Hi Mario,
I like JSContact and the current draft certainly looks good enough to be usable
in RDAP. I imagine more work will be needed before JSContact will have feature
parity with vCard/jCard.
I would be happy to publish a new version of draft-brown-epp-contacts-in-rdap
which uses JSContact r
Hi all,
I would like to invite you to take a look at this document:
https://tools.ietf.org/html/draft-stepanek-jscontact-03
It aims to define a JSON representation of contact information that
fixes the issues with jCard deserialization and, at the same time,
expands vCard semantics.
Just t
