What? You find jCard difficult. I'm shocked!
On Tue, Feb 12, 2019 at 03:50:08AM +0000, Mack, Justin wrote:
> Once we publish these documents to "the world", many registries and
> registrars will [loudly] give feedback about implementation difficulties
> with jCard.
>
> My lead engineer today was unable to use a library to "marshall" the
> data into a suitable JSON object for the jCard data inside the RDAP
> object. This is due to requirements such as multiline addresses in
> array-only vs single-line non-array, various empty elements that must
> exist but are non-null (first two fields of the address), recent/future
> extensions such as "cc" (which I support but the country field should
> have allowed ISO 2-char to begin with), and the difficulty of inserting
> this block of jCard data embedded in a larger JSON document - which
> means at best we must "toString" the jCard data separately and insert it
> inside a more "pure" RDAP object, or simply print it out manually.
In my validation of RDAP, jCard is the single biggest source of
interoperability issues common among all server implementers.
>
> I hereby volunteer to co-author a future RFC for RDAP to deprecate jCard
> and output common key/value pairs of contact data in JSON, similar to
> the simple structure of WHOIS today. I'm withholding this time
> commitment until after the EPDP outcome and temp spec expiration so we
> can adapt to then-established policy, but I feel this effort will
> benefit the longevity of RDAP. (Who thought WHOIS would last this long?
> Long live RDAP!)
I support such an effort.
While you are bringing this up in an ICANN domain context, there may be overlaps
with the other communities of use.
For NicInfo, I ended up injecting extra data in the JSON because culling
that information could be difficult at times. An example:
"nicinfo_summary_data": {
"service_operator": "apnic.net",
"listed_name": "Bob Smurd ( BS1-AP )",
"abuse_email": "ab...@example.com",
"last_changed_date": "Wed, 30 Aug 2017 07:19:11 -0000",
"listed_country": "AU",
"CIDRs": [
"192.149.36.0/24"
]
}
However, this is more than just contact data. It is overall summary data... the
idea here being that there are certain items have are commonly important. Just
a thought.
-andy
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
