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

Spiral: Determine approach to mapping with context of evidence #30

Open
Compton-US opened this issue Jun 21, 2023 · 2 comments
Open

Spiral: Determine approach to mapping with context of evidence #30

Compton-US opened this issue Jun 21, 2023 · 2 comments
Labels
Help Wanted This issue is soliciting help from the community for assistance and/or feedback. Holding This issue is holding for action. Priority: LOW Spiral This issue is tracking a spiral. Progress, Concurrence and Feedback.

Comments

@Compton-US
Copy link
Contributor

Problem Statement

Belongs to #18

Consider evidence as an important dimension of equivalency in some contexts, particularly if an organization is using a mapping to prepare for meeting a new standard based on another framework. If this particular approach requires a more in-depth synthesis using profiles and SSP documents, we should produce a guide for this.

@Compton-US Compton-US added Spiral This issue is tracking a spiral. Progress, Concurrence and Feedback. Holding This issue is holding for action. labels Jun 21, 2023
@Compton-US Compton-US changed the title Spiral 4: Determine approach to mapping with context of evidence Spiral 5: Determine approach to mapping with context of evidence Jun 21, 2023
@Compton-US Compton-US added Help Wanted This issue is soliciting help from the community for assistance and/or feedback. Priority: LOW labels Jun 21, 2023
@Compton-US Compton-US changed the title Spiral 5: Determine approach to mapping with context of evidence Spiral: Determine approach to mapping with context of evidence Jun 21, 2023
@iMichaela
Copy link
Collaborator

The evidence requirement could (potentially) be a property of a mapping-record assembly ( #32 ) which would allow documenting a particular mapping relation for a control-implementation/implemented-requirements/by-components or control-implementation/implemented-requirements/statements/by-components.

The information will then be conveyed to AP, AR, POAM through the import mechanism.

@iMichaela
Copy link
Collaborator

The evidence requirement could (potentially) be a property of a mapping-record assembly ( #32 ) which would allow documenting a particular mapping relation for a control-implementation/implemented-requirements/by-components or control-implementation/implemented-requirements/statements/by-components.

The information will then be conveyed to AP, AR, POAM through the import mechanism.

Alternatively, the re-defined property category of the qualifier (see note in issue #27) could be used to define which aspect of the source, target or both is the predicate applicable to: requirement, parameter, objective, assessment method, or evidence, addressing in this way this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help Wanted This issue is soliciting help from the community for assistance and/or feedback. Holding This issue is holding for action. Priority: LOW Spiral This issue is tracking a spiral. Progress, Concurrence and Feedback.
Projects
None yet
Development

No branches or pull requests

2 participants