Refactor the catalog and profile schema to remove unused elements

[akarmel]

User Story:

As a OSCAL consumer, I have a clearly defined catalog and profile schema with no unused elements to support OSCAL tool vendors.

Goals:

Remove unused elements from catalog and profile schema

Dependencies:

None

Acceptance Criteria

Verify that no unused elements exist in catalog and profile schema

[iMichaela]

** 3/14/2018 **
Is the listed Acceptance criteria assuming visual code review /inspection, or is there a better way of reviewing it?

[akarmel]

3/15/2018 - Sprint 9 Progress Notes

• Wendell has an idea of how this needs to be done and will begin on this early next week and loop Andrew in

[wendellpiez]

New and better schemas and schema artifacts are now available in my Github fork. At the top level there are three schemas, for catalog, profile and declarations, corresponding to the expected top-level elements of the respective "document types". ("declarations" will be used by catalog developers and perhaps advanced users, not ordinary consumers.)

Experimental features of OSCAL have been relegated to a separate module not maintained at the top level. (Where they are working and where schemas that exercise them can be tried.)

[akarmel]

3/22/2018 - Sprint 9 Progress Notes

• See Wendell's comment above
• Per Wendell, this is 80% complete. Waiting for Dave to take a look at this next week.

[akarmel]

3/29/2018 - Sprint 9 Progress Notes

• Dave will work on this early next week

[akarmel]

4/5/2018 - Sprint 9 Progress Notes

• Dave has inspected the schemas and has validated that we have no unused elements.
• Closing issue