commoncriteria / commoncriteria/transforms

Modified SFRs where the modification is a note and not an updated requirement

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
XSLT
Stars
1
Forks
4
PR merge metrics
No merged PRs in 30d

Description

In many cases, PP-Modules will have Modified SFRs from the Base-PP where there is no change to the actual text of the SFR. The most common situation is when a selection-based requirement in the Base-PP is mandatory when the TOE conforms to the Module because the Module requires that functionality as a dependency.

Right now an f-component must contain at least one f-element so the only ways to address this scenario are to reproduce the SFR in its entirety and then add an app note to the bottom (not preferred) or to simply fill out an f-element with the desired note (which has the drawback of then incorrectly labeling that as an SFR element XXX_YYY_n.1).

In the case of Modified SFRs specifically it is requested that an f-component be able to have just raw text underneath it. Perhaps a no-elements tag that you could then populate with raw text and then the contents of that tag go underneath the component heading.

The only complicating factor to this is that we also want there to be evaluation activities in cases like this, but the aactivity tag has to go inside of an f-element

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the transform and schema handling for f-components, f-elements, and aactivity. Determine how a component can contain note text without creating a falsely labeled SFR element while still supporting evaluation activities; done means the representation and resulting output are defined for this case.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.