commoncriteria / commoncriteria/transforms
when to define the acronym "OE" in modules
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
The intro text to the SPD section (typically section 3) uses the term "OE" without defining it as "operational environment" but the intro text for the assumptions (which is typically section 3.2) specifies "operational environment (OE)" - it is recommended that for the sake of readability, the OE acronym is specified in the SPD intro text and then only the acronym is used in the assumptions section.
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
Review the SPD section intro, typically section 3, alongside the assumptions section, typically section 3.2, in the relevant transforms. Confirm where "OE" first appears, define it there as "operational environment (OE)", and verify the assumptions text can then use only the acronym.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100