> -----Original Message----- > From: regext <[email protected]> On Behalf Of Gavin Brown > Sent: Friday, February 22, 2019 8:42 AM > To: Andy Newton <[email protected]>; Mario Loffredo > <[email protected]> > Cc: [email protected] > Subject: [EXTERNAL] Re: [regext] EPP Contact Mapping for RDAP > > Thanks Andy, Mario and Bernhard for the useful feedback. > > It seems to me that there is a lot of appetite for a way to replace > jCard: in addition to F2F conversations and discussions in the ICANN world, > I've also had private feedback on this draft which indicates a lot of > frustration > with jCard from implementers. > > If anyone implementing an RDAP client or server has some experiences with > jCard that they can share that would be very helpful in understanding the > demand for an alternative. > > jCard was added in draft-ietf-weirds-json-response-03, so the last version to > have "native" contacts was -02. > > In it, entities in DNRs had a different syntax to entities in RIRs, however, > there was a lot of similarity. Adding jCard helped in that the contact > information got moved into a subordinate object property rather than being > mixed in with the metadata (handle, roles, links, etc). > > You can use the syntax for the contact info in the -02 draft and replace the > "eppContactInfo" object in my draft with a generic "contactInfo" > object such as the following: > > { > "objectClassName": "entity", > "handle": "XXXX", > > "contactInfo": { > "entityNames": [ > "Joe Bob, Inc.", > "Bobby Joe Shopping" > ], > "postalAddress": [ > "123 Maple Ave", > "Suite 90001", > "Vancouver", > "BC", > "12393" > ],
Could we represent both an internationalized form of the postal address and an optional localized form, perhaps like this? "postalAddressInt": [], "postalAddressLoc": [], Scott _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
