Add JSON examples for FedRAMP profiles

[anweiss]

Committer Notes

Adds the following JSON examples for the FedRAMP profiles to address #197:

FedRAMP_HIGH-baseline_profile.json
FedRAMP_MODERATE-baseline_profile.json
FedRAMP_LOW-baseline_profile.json

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]

[iMichaela]

9/4/2018 PR Review

We need to decide if we want the uuid to be identical for the JSON version and for the XML version of the catalog or profile. Also the publication date it is currently identical on both versions of the file. While uuid could be the same, I think the publication date might need to remain true to the real publication date. We also discussed under #220 to look into using the NIST Beacon to obtain a unique file identifier.

Also, the examples still contain the XML paragraph markup (

). Is it possible to remove the 500+ instances from these versions of the files or do we have other dependencies or challenges (e.g. no round-trip support yet)?

[david-waltermire]

@iMichaela I believe the UUIDs for the XML and JSON versions should be different, since these are different instances. We need to address this question in the context of issues #196 and #221.

In my view we need to identify the following three things:

1. The document instance identifier, which is unique for each document.
2. The dataset identifier, which is the same for each serialization of a given catalog, profile, or implementation data revision (e.g., SP 800-53 rev4 updated on X date).
3. A subject identifier that is the same for all revisions of the same catalog, profile, or implementation. This can be used to track revisions of a given publication (e.g., SP 800-53 rev4)

The instances in this PR use the same UUID for the id. which provides #2 above. I believe it should be #1 above, but we need to talk about this.

@iMichaela I don't understand your comment about " Is it possible to remove the 500+ instances from these versions of the files". Can you clarify?

[iMichaela]

@david-waltermire-nist I concur with the file uuid structure you described:

1. The document instance identifier, which is unique for each document.
2. The dataset identifier, which is the same for each serialization of a given catalog, profile, or implementation data revision (e.g., SP 800-53 rev4 updated on X date).
3. A subject identifier that is the same for all revisions of the same catalog, profile, or implementation. This can be used to track revisions of a given publication (e.g., SP 800-53 rev4)
   I suggest though we should consider having a way of identifying coupling the XML and JSON pairs of the same information.

@david-waltermire-nist : I am referring to the 500+ instances of \u003cp\u003e that come from the paragraph tag

in XML

[iMichaela]

9/27/2018

#197 has been reassigned to @wendellpiez who will create a new PR using the metaschema toolchain.