[OASIS Issue Tracker] (EMERGENCY-23) Specify JSON serialization

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/EMERGENCY-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37811#comment-37811 ] 

Eliot Christian commented on EMERGENCY-23:
------------------------------------------

We can note that tools like XMLSpy and FreeFormatter are available to convert in both directions between XML and JSON. However, such conversions are lossy, so in a life-critical application like CAP it is important that implementors have a very good understanding of exactly what is entailed. 
Perhaps a proposal would be to seek consensus on an OASIS EM TC Committee Note that would reflect expert consensus on issues that may arise when implementors use tools in a CAP context to convert from XML to JSON and from JSON to XML.
I don't think the EM TC should reference JSON in the CAP Specification itself until such an expert consensus has been developed and vetted broadly. 
In any case, I think that specifying anything normative about JSON would be very disruptive for implementors.

> Specify JSON serialization
> --------------------------
>
>                 Key: EMERGENCY-23
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-23
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Art Botterell
>
> JSON (officially "JavaScript Object Notation," although it's no longer specific to JavaScript) is a lightweight data-interchange format that has become extremely popular in Web-based applications.  JSON preserves the human-readable characteristic of XML while substantially reducing the overhead of XML "taggage" and parsing.
> Adding an accepted JSON serialization of CAP messages would significantly simplify technical implementation and thereby speed and broaden adoption.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)