You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an OSCAL user and developer, I need to understand the content models of the various elements (objects) in OSCAL. An XSLT now in a dev branch can produce an element map from a metaschema, showing a map of element containment.
Maps can be created from the root of a metaschema or from any element. Mini-maps per element could be used on the element's page.
Here's a screen shot of a smaller element map, rooted at part:
Goals:
Consider and determine whether and how element maps can be used in the schema documentation.
Where CSS is involved and perhaps Javascript (maybe we wish the maps to expand/collapse as well as link), we need to determine how to integrate with Jekyll/USWDS in a way that is robust across upgrades.
Acceptance Criteria
Element maps are integrated according to our determination
A JSON version has been produced, or another Issue has been created for this work item
The text was updated successfully, but these errors were encountered:
wendellpiez
changed the title
OSCAL element maps for schema documentation
OSCAL *element maps* for schema documentation
Apr 5, 2019
wendellpiez
changed the title
OSCAL *element maps* for schema documentation
OSCAL element maps for schema documentation
Apr 5, 2019
User Story:
As an OSCAL user and developer, I need to understand the content models of the various elements (objects) in OSCAL. An XSLT now in a dev branch can produce an element map from a metaschema, showing a map of element containment.
Maps can be created from the root of a metaschema or from any element. Mini-maps per element could be used on the element's page.
Here's a screen shot of a smaller element map, rooted at
part
:Goals:
Dependencies:
Stable schema documentation as described in #314.
Where CSS is involved and perhaps Javascript (maybe we wish the maps to expand/collapse as well as link), we need to determine how to integrate with Jekyll/USWDS in a way that is robust across upgrades.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: