Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Misleading or incorrect recursion indicators in XML Format Outline #848

Closed
canb227 opened this issue Mar 11, 2021 · 1 comment · Fixed by #880
Closed

Misleading or incorrect recursion indicators in XML Format Outline #848

canb227 opened this issue Mar 11, 2021 · 1 comment · Fixed by #880
Assignees
@wendellpiez
Labels
bug Scope: Documentation This issue relates to OSCAL documentation.
Milestone
OSCAL 1.0.0 RC 2

Comments

@canb227
Copy link
Contributor

canb227 commented Mar 11, 2021

Describe the bug

The XML Format Outline uses the <tagname/> [0 to inf] format to describe a recursive element, but this format leads the reader to believe that the recursed elements have no children (they do).

Example (See part and control tags):
image

What is affected by this bug?

Documentation

How do we replicate the issue?

Firefox 87.0b8 (64-bit)
https://pages.nist.gov/OSCAL/documentation/schema/catalog-layer/catalog/xml-model-map/

Expected behavior (i.e. solution)

Should probably be represented using <tagname>...</tagname> [0 to inf] instead, or similar.
@canb227 canb227 added the bug label Mar 11, 2021
@wendellpiez wendellpiez added the Scope: Documentation This issue relates to OSCAL documentation. label Mar 11, 2021
@wendellpiez wendellpiez mentioned this issue Mar 15, 2021
Closed
@wendellpiez
Copy link
Contributor

wendellpiez commented Mar 17, 2021 •
edited
Loading

New concept:

image

(It says 'parent' when it's a parent and 'ancestor' for a more distant ancestor.)

Comments welcome @canb227 @david-waltermire-nist

wendellpiez added a commit to wendellpiez/metaschema that referenced this issue Mar 17, 2021
@wendellpiez
First cut at usnistgov/OSCAL#847 and usnistgov/OSCAL#848 - XML model …
f49fd56 
…mapping
@wendellpiez wendellpiez mentioned this issue Jun 30, 2023
Open
12 tasks
@david-waltermire david-waltermire added this to the OSCAL 1.0.0 RC 2 milestone Mar 23, 2021
@david-waltermire david-waltermire linked a pull request Mar 30, 2021 that will close this issue
Updated broken doc links to fix #866 #877
Merged
8 tasks
@david-waltermire david-waltermire removed a link to a pull request Mar 30, 2021
Updated broken doc links to fix #866 #877
Merged
8 tasks
wendellpiez added a commit to wendellpiez/metaschema that referenced this issue Mar 30, 2021
@wendellpiez
First cut at usnistgov/OSCAL#847 and usnistgov/OSCAL#848 - XML model …
01365c2 
…mapping
david-waltermire pushed a commit to usnistgov/metaschema that referenced this issue Mar 30, 2021
@wendellpiez @david-waltermire
First cut at usnistgov/OSCAL#847 and usnistgov/OSCAL#848 - XML model …
0d2b18d 
…mapping
@wendellpiez wendellpiez mentioned this issue Mar 30, 2021
Merged
8 tasks
@wendellpiez wendellpiez linked a pull request Mar 30, 2021 that will close this issue
Enhancements and improvements to (generated) OSCAL model documentation #880
Merged
8 tasks
nikitawootten-nist pushed a commit to nikitawootten-nist/metaschema-xslt that referenced this issue Jul 21, 2023
@wendellpiez @david-waltermire
First cut at usnistgov/OSCAL#847 and usnistgov/OSCAL#848 - XML model …
da72fc4 
…mapping
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wendellpiez wendellpiez

Labels
bug Scope: Documentation This issue relates to OSCAL documentation.
Projects
None yet
Milestone
OSCAL 1.0.0 RC 2
Development

Successfully merging a pull request may close this issue.

Enhancements and improvements to (generated) OSCAL model documentation wendellpiez/OSCAL
3 participants
@wendellpiez @david-waltermire @canb227