The problem isn't that JSON is hard to parse, my problem is that fields in the JSON returned are not documented and that different registries return different JSON formatted fields.
Also because JSON also doesn't allow inline comments, I personally prefer a well commented CSV file over an un-documented JSON one. /re On Sat, Jul 20, 2019 at 5:52 PM Owen DeLong <[email protected]> wrote: > > This is an operational matter for staff… Why would it need to go through the > policy process? > > The policy in the CPM does not and should not specify the reporting format. > > I do find it interesting, however, that he considers JSON difficult to parse > vs. CSV. > > I find the opposite. There are many libraries available for parsing both > formats, but the level of > consistency in the definition and syntax specification for JSON, especially > around quoting and > handling of strings containing quote and delimiter characters plus the > hierarchical dictionary > nature of JSON are, IMHO, a vastly superior format that is easier to parse > while providing much > greater flexibility in the type of content delivered. > > Owen > > > On Jul 20, 2019, at 16:54 , DANIEL NANGHAKA <[email protected]> wrote: > > Hi Raymond, > This is interesting, it has to go through a policy proposal. Policy proposal > are discussed at AFRINIC meetings. > > After discussion then it is passed for implementation. > > Daniel K. Nanghaka > > On Saturday, July 20, 2019, raymond <[email protected]> wrote: >> >> Hi, >> Would it be possible for AFRINIC to adopt the transfer log format used by >> APNIC? >> If so, who do I need to contact to make this happen? If not, can the fields >> in the JSON >> format be documented for reference? >> >> APNIC has a well documented policy[1] on the CSV logs they produce daily at >> [2] >> >> [1] >> https://www.apnic.net/about-apnic/corporate-documents/documents/policy-development/transfer-log-format/ >> [2] https://ftp.apnic.net/transfers/apnic/ >> >> APNICs format stands out as it is easy to parse the data >> compared to the various JSON formats used by other registries(including >> AFRINICs) >> >> RIPENCC https://ftp.ripe.net/pub/stats/ripencc/transfers/ JSON >> ARIN https://ftp.arin.net/pub/stats/arin/transfers/ JSON >> LACNIC https://ftp.lacnic.net/pub/stats/lacnic/transfers/ JSON >> AFRINIC http://ftp.afrinic.net/stats/afrinic/transfers/ JSON >> >> >> /re >> > _______________________________________________ > Community-Discuss mailing list > [email protected] > https://lists.afrinic.net/mailman/listinfo/community-discuss > > _______________________________________________ Community-Discuss mailing list [email protected] https://lists.afrinic.net/mailman/listinfo/community-discuss
