commoncriteria / commoncriteria/transforms
EAs should be defined at the appropriate level, rather than use the level attribute
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Going to look at defining EAs at the component or element level as appropriate, rather than use the level attribute. This will probably use a new tag: <eactivity> to replace <aactivity>, and the new test structure will be defined under this new XML element.
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 locating the existing aactivity element, its level attribute handling, and the tests that cover the current XML structure. Review how component- and element-level EAs should be represented before deciding how eactivity replaces aactivity. Done means the new structure is defined and the related tests use and validate it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100