commoncriteria / commoncriteria/transforms
sel-based SFRs in module can't reach into base-PP
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This issue is related to the tag within a reference in a sel-based requirement that is in a PP-Module.
When the ref attribute of the parameter points to a functional package, it works correctly. But when it points to a Base-PP, it is not able to pick up the reference and so the prompt box doesn't identify it.
See for example in the following screenshot, where both FDP_PDC_EXT.3.1/KM in the module and FDP_SWI_EXT.1.1 in the base-PP are meant to be selection triggers per the app note, but only the module SFR is referenced in the box. In the XML, the external-doc ref attribute was set to be "psd", which is both the id value of the as well as the github project repo name, but this had no effect.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the XML external-doc ref inside a depends reference is resolved for sel-based requirements in a PP-Module, comparing functional-package lookup with Base-PP lookup. Verify the prompt box handling for the psd Base-PP and consider the issue done when the base-PP SFR is identified alongside the module SFR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100