Goals:

1. Ensure that the JSON representation of OSCAL is equivalent in all functionality to the XML representation. This means that content can be round-tripped between the XML-JSON-XML representations. Whitespace preservation may not be possible,
2. Develop a prose markup capability in JSON to support the equivalent features in XML (e.g., parameter insertion, etc.). Consider using markdown to do this, with some extensions.
3. Answer how namespaces will be handled in JSON. OSCAL currently has a single namespace.

Dependencies:

1. Examples of OSCAL XML-based catalog and profile content. These examples are SP 800-53 based.
2. Pull request (Add JSON schema and examples #63) is merged into the sprint-5 branch,

Acceptance Criteria:

1. Demonstrate that content can be round-tripped. Content can be converted from XML-to-JSON-to-XML without any semantic loss of information. (Addresses JSON data sources as well? #59)
2. Demonstrate that OSCAL JSON content can be validated to be well-formed. (JSON schema #10)