Re: [emergency-cap] CAP Issue 23 - Specify JSON serialization

emergency-cap message

I guess this proposal is for the EM TC to post an informative Committee Note that discusses considerations when JSON is used for processing a CAP alert. The status of such a document would be similar to the OASIS Committee titled "Example Practices: CAP Feeds Version 1.0." (issued 04 March 2014, available at http://docs.oasis-open.org/emergency-adopt/cap-feeds/v1.0/cn02/cap-feeds-v1.0-cn02.doc ).

It is important that the EM TC would not reference such a note in the CAP specification. Rather, the specification should remain very clear that a CAP alert message can only be considered "valid" and "compliant" as it is represented in XML format.

On Tue, Oct 28, 2014 at 1:08 PM, Jacob Westfall <jake@jpw.biz> wrote:

The CAP SC meeting ran out of time yesterday to discuss Issue 23 regarding JSON. In the interests of moving the issues along, I'd like to suggest we discuss this issue via the email list/issue tracker and move to quickly resolve it on the Nov 3 call.

I am supporting the issue. I've been working with a JSON schema of CAP for some time now with good success. There are some differences in the schema versus XML and how to implement it, just like with ASN.1.

I would suggest we follow the path that the OASIS OData standard has taken and produce a separate specification for CAP JSON that merely denotes the differences between the serializations with the XML spec remaining as the primary document. In addition to OData, I found that other OASIS specs like XDI, XACML, CAL, CMIS, and CAM are all working on JSON serializations as well.