-
Notifications
You must be signed in to change notification settings - Fork 184
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
Comments
@stephenbanghart is scheduling a meeting with the NIST design team for the week of 3/7/2022. |
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. |
* Specification changes, usnistgov#1141 usnistgov#1142 usnistgov#1155 * Mapping documentation, UUID RFC reference * Apply suggestions from AJ's review Co-authored-by: Stephen Banghart <stephen.banghart@outlook.com> Co-authored-by: Alexander Stein <alexander.stein@nist.gov>
* Specification changes, usnistgov#1141 usnistgov#1142 usnistgov#1155 * Mapping documentation, UUID RFC reference * Apply suggestions from AJ's review Co-authored-by: Stephen Banghart <stephen.banghart@outlook.com> Co-authored-by: Alexander Stein <alexander.stein@nist.gov>
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?
The text was updated successfully, but these errors were encountered: