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 resolver spec: Notation in metadata section #1155

Closed
david-waltermire opened this issue Feb 26, 2022 Discussed in #1135 · 0 comments · Fixed by #1172
Closed

Profile resolver spec: Notation in metadata section #1155

david-waltermire opened this issue Feb 26, 2022 Discussed in #1135 · 0 comments · Fixed by #1172
Assignees
Labels
Milestone

Comments

@david-waltermire
Copy link
Contributor

Discussed in #1135

Originally posted by galtm February 13, 2022
I'm having trouble understanding some notation in the Metadata Resolution section of the Profile Resolution spec. The notation metadata:last-modified describes what in XML becomes a child element named last-modified. This child element is listed in the catalog model. However, similar notations metadata:source-profile and metadata:resolution-tool map in XML to markup forms in a sample document that are not elements named source-profile or resolution-tool:

      <prop name="resolution-tool" value="some value"/>
      <link rel="source-profile" href="../base-test_profile.xml"/>

What does the colon mean in the spec syntax, and is there a legend for it?

@stephenbanghart Please answer this question in the discussion and address this in the profile resolution spec.

@david-waltermire david-waltermire added this to the OSCAL 1.0.2 milestone Feb 26, 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 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants