Document Implementation Layer

[brian-ruf]

User Story:

As an OSCAL adopter, I need to understand the concepts behind the OSCAL Implementation layer model, as well as the syntax.

Goals:

• Publish existing concept descriptions in markdown, including diagrams.
• Ensure syntax is properly documented in the metaschema, generated, and published.
• Document the concepts defined in OSCAL Implementation: Core System Metadata #213, OSCAL Implementation: System Specification #214 , OSCAL Implementation: Component Specification #215 , OSCAL Implementation: Component Definition #216, and OSCAL Implementation: Capability Specification #217 on the website.

Dependencies:

Issue #246

Acceptance Criteria

• Existing Visio diagram(s) converted to graphics suitable for inclusion with markdown.
• Content migrated to markdown.
• Content is complete and published
• Formal Names, Descriptions, and Examples are up-to-date in Implementation layer metaschema
• Syntax documentation is generated from metaschema, and published

[david-waltermire]

There is work to be done to document the implementation layer concepts on the website. This can be done in the "architecture" section of the site. Specifically, we can add concepts for "SSP", and "component" as subnavs under architecture, and flesh out the "implementation" bullet to link to these.

[iMichaela]

7/11/2019

No progress made in the past week.

[david-waltermire]

Drafts of the SSP and component models are in PR #464, and will be available once the PR is pulled. We will need to carry this forward to sprint 23.

[wendellpiez]

Sprint 23 Update 2019 Sep 19

Slated for work in upcoming session (Monday). The Issue possibly needs some refactoring.

[secautobuilder]

It looks like the metaschema work has been completed, but the website work has not. Adding the remainder of this work to Sprint 25.

[david-waltermire]

PR #653 is updating the website documentation for the implementation layer. A bunch of new content has been posted. No work on schema docs has been complete at this point. We should split out the schema docs work from the website work in this issue.