There has been discussion on replacement of jcard. One of the
considerations in the equation is how to handle the migration. Some
people have (appropriatly) expressed concerns about this issue of
migration. While I’m not yet sure if we need to deprecate jcard, I
would like to suggest a way to manage the migration if we ever consider
the new format:
- define in RDAP RESPONSE another property additional to vcardarray, at
the same place as vcardarray appears. Say « jscontact »
- have servers to send both (for quite a long time). This is more work
from the server side, but I think it is not that bad.
- clients not able to read the new format will just ignore it and will
continue to parse the jcard.
- clients that are updated and prefer the new format just parse the new
format and ignore the jcard.
- wait a while. at some point in time, deprecate jcard.
My point here is that there is a smooth path to the new format, which
has some costs, but it is doable and not that complicated.
Regards, Marc.
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
