Using periods in names with JSON

Topics: ACORD XML 2.x, JSON
Coordinator
Aug 9, 2016 at 5:31 PM
Received a lecture from a vendor this morning that I will throw out to the group. Currently ACORD requires users to preface custom fields with 'com.yourcustomwebsitename'. So for Liberty commercial lines we use com.libertymutual.ci_CustomElementName. But, vendor was saying JSON will not allow . (periods) within names. If this is true, then we need to change this rule before we move to JSON.

Just wondering if anyone could confirm that JSON does not allow periods.

The rule from ACORD is under 4.6: For example, extensions developed by ABC Corporation must use the syntax com.abccorp_Something
Developer
Aug 9, 2016 at 8:28 PM
JSON does not restrict names in that way - periods are allowed.

Source: http://www.json.org/ and https://tools.ietf.org/html/rfc7159
Coordinator
Sep 15, 2016 at 6:56 PM
We have removed that extension mechanism in 2.0

You can now create your aggregates/elements inside <*Ext> found at the end of every complex element.
Coordinator
Sep 15, 2016 at 7:07 PM

So let me make sure I understand. The expectation is that we no longer need to use the com.libertymutual.ci_ because it is implied that these are extensions simply by being placed under the ext aggregate? Understood that the mechanism was changing but did not make the leap that the naming convention was changing as well. Makes sense.

Thanks.

Steven Williams

Principal Data Analyst

150 Liberty Way

Dover, NH 03820

[email removed] | Direct: 603-245-5378 | Cell: 978-387-6940

Description: LM-reversed small

Having trouble finding something related to CI-XML? Try our Helpful Links page.

Coordinator
Sep 20, 2016 at 7:11 PM
Correct there will be no need for com. extensions inside of 2.0 or 2.x. On the JSON Note I am working a JSON SCHEMA document for ACORD "Swagger" or "OPENAPI"

I would love to have your input into that.