commoncriteria / commoncriteria/transforms

ECD alphabetization

Open
#94 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

This is more of a quality-of-life issue than an actual problem needing a solution (in case the solution is not trivial to execute) but ideally the ECD should be in alphabetical order. Right not it looks like it just scrapes the document for extended components in line order and then builds the section out of that, rather than re-ordering. This can be mitigated to some extent by having a single body text section for SFRs and then using tags to indicate those that are non-mandatory (rather than having them in appendices off by themselves at the end) but this trick doesn't work if you have a Module with multiple Base-PPs and the Additional SFRs sections of those Base-PPs define their own extended components that would be out of order w/r/t the rest of the list.

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

No file, test, or entry point is named. Start by tracing how the transforms scrape extended components and assemble the ECD section, including modules with multiple Base-PPs. Done means the resulting ECD is alphabetized consistently across those cases without relying on a single body-text section workaround.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.