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.

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

Profile Resolution Output Namespaces #1142

Closed
stephenbanghart opened this issue Feb 17, 2022 · 2 comments · Fixed by #1172
Closed

Profile Resolution Output Namespaces #1142

stephenbanghart opened this issue Feb 17, 2022 · 2 comments · Fixed by #1172
Assignees
Labels
Discussion Needed This issues needs to be reviewed by the OSCAL development team. enhancement User Story
Milestone

Comments

@stephenbanghart
Copy link
Contributor

In the "Dealing with Multiple Formats" section of the specification, we do not specify any name spacing requirements for any of the formats.

Is this covered by requirements elsewhere in OSCAL, or do we need to establish requirements here?

@david-waltermire david-waltermire added the Discussion Needed This issues needs to be reviewed by the OSCAL development team. label Feb 24, 2022
@david-waltermire
Copy link
Contributor

@stephenbanghart is scheduling a meeting with the NIST design team for the week of 3/7/2022.

@david-waltermire david-waltermire added this to the OSCAL 1.0.2 milestone Feb 25, 2022
@wendellpiez
Copy link
Contributor

On the XML side, the applicable XML namespace for a valid catalog is defined by the catalog format. The spec might well say something about it but it doesn't have to define them: the namespace is always the same and what appears in the docs.

On the JSON/YAML sides I am not sure if the question is applicable.

I can contrive some language describing the applicability of the XML namespace to elements on the XML side (whether expressed in prefixed or unprefixed element names), if called on.

stephenbanghart pushed a commit to stephenbanghart/OSCAL that referenced this issue Mar 14, 2022
stephenbanghart pushed a commit to stephenbanghart/OSCAL that referenced this issue Mar 14, 2022
stephenbanghart pushed a commit to stephenbanghart/OSCAL that referenced this issue Mar 15, 2022
@david-waltermire david-waltermire linked a pull request Mar 17, 2022 that will close this issue
david-waltermire pushed a commit that referenced this issue Mar 17, 2022
* Specification changes, #1141 #1142 #1155
* Mapping documentation, UUID RFC reference
* Apply suggestions from AJ's review

Co-authored-by: Stephen Banghart <[email protected]>
Co-authored-by: Alexander Stein <[email protected]>
david-waltermire pushed a commit that referenced this issue Mar 18, 2022
* Specification changes, #1141 #1142 #1155
* Mapping documentation, UUID RFC reference
* Apply suggestions from AJ's review

Co-authored-by: Stephen Banghart <[email protected]>
Co-authored-by: Alexander Stein <[email protected]>
iMichaela pushed a commit to iMichaela/OSCAL that referenced this issue Apr 7, 2022
* Specification changes, usnistgov#1141 usnistgov#1142 usnistgov#1155
* Mapping documentation, UUID RFC reference
* Apply suggestions from AJ's review

Co-authored-by: Stephen Banghart <[email protected]>
Co-authored-by: Alexander Stein <[email protected]>
Rene2mt pushed a commit to Rene2mt/OSCAL that referenced this issue May 17, 2022
* Specification changes, usnistgov#1141 usnistgov#1142 usnistgov#1155
* Mapping documentation, UUID RFC reference
* Apply suggestions from AJ's review

Co-authored-by: Stephen Banghart <[email protected]>
Co-authored-by: Alexander Stein <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Needed This issues needs to be reviewed by the OSCAL development team. enhancement User Story
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants