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

Ability to set the source-profile link @href value #16

Open
3 tasks
david-waltermire opened this issue May 10, 2022 · 1 comment · May be fixed by #151
Open
3 tasks

Ability to set the source-profile link @href value #16

david-waltermire opened this issue May 10, 2022 · 1 comment · May be fixed by #151
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@david-waltermire
Copy link
Collaborator

User Story:

As an liboscal-java user, I would like for the ability to set the source-profile link @href value to a user provided path on profile resolution.

Goals:

  • Allow for relative source-profile link @href values to be included on the output.
    • The current output (example shown below) is likely to be of little benefit to the consumers of the resolved profile.
       <link href="file:/C:/tmp/liboscal-java/oscal/src/specifications/profile-resolution/profile-resolution-examples/base-test_profile.xml" rel="source-profile"/>
       <link href="file:///tmp/liboscal-java/oscal/src/specifications/profile-resolution/profile-resolution-examples/base-test_profile.xml" rel="source-profile"/>
  • Optionally support the usage of the canonical /profile/metadata/link/@rel value.

Dependencies:

None

Acceptance Criteria

  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.
@david-waltermire david-waltermire added the enhancement New feature or request label May 10, 2022
@david-waltermire david-waltermire added this to the v1.0.5 Release milestone Jun 24, 2022
aj-stein-nist added a commit that referenced this issue Jul 3, 2023
@aj-stein-nist aj-stein-nist linked a pull request Jul 3, 2023 that will close this issue
8 tasks
@aj-stein-nist aj-stein-nist linked a pull request Jul 3, 2023 that will close this issue
8 tasks
@aj-stein-nist aj-stein-nist removed this from the v2.0.0 Release milestone Jul 22, 2023
@aj-stein-nist aj-stein-nist added this to the Next milestone Aug 15, 2023
@aj-stein-nist
Copy link
Collaborator

I have to come back to this work and will move this to a future milestone. It does not belong in an upcoming patch release.

@aj-stein-nist aj-stein-nist modified the milestones: Next, Future Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

Successfully merging a pull request may close this issue.

2 participants