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. I have already defined,
together with Robert Stepanek, a mapping between JSCard and JCard and it
seems to us that almost all the information described by JCard can be
represented by JSCard. Some JCard elements have a 1-to-1 mapping to as
many JSCard fields, while some others corresponds to the same field. For
example, the JCard uri type elements can be represented as items of the
"online" array, each with appropriate values for "type" and "label"
properties.
We are also evaluating to add a generic field to represent all the
information which is not considered at present but it could be in the
future.
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 is willing to implement JSCard in his own RDAP server (you, me,
maybe Andy). I think other stuff has still to be discussed. For example,
what to do to make the transition from JCard to JSCard as smooth as
possible. Should JSCard become the default and JCard an optional
capability or viceversa? How could an RDAP server inform a client that
it is able to return contact information according to the JSCard format?
We can have a short talk about it at the next meeting.
Cheers,
mario
G.
On 2 Jul 2019, at 07:58, Mario Loffredo<mario.loffr...@iit.cnr.it> wrote:
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 to give an idea of the new contact representation in the RDAP context, I
have implemented an ad-hoc optional capability in .it public test server
(e.g.https://rdap.pubtest.nic.it/domain/nic.it?jscard=1).
The draft was presented for the first time at last dispatch session in Prague
and, since then, some feedbacks have been posted on dispatch mailing list which
have contributed to improve the initial proposal.
Anyway, since the jCard replacement has been debated within this WG, it seems
to me quite obvious to bring it to your attention.
Any feedback will be very appreciated.
Thanks in advance,
mario
--
Dr. Mario Loffredo
Servizi Internet e Sviluppo Tecnologico
CNR - Istituto di Informatica e Telematica
via G. Moruzzi 1, I-56124 PISA, Italy
E-Mail:mario.loffr...@iit.cnr.it
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Servizi Internet e Sviluppo Tecnologico
CNR - Istituto di Informatica e Telematica
via G. Moruzzi 1, I-56124 PISA, Italy
E-Mail:mario.loffr...@iit.cnr.it
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
