Important Announcements - commoncriteria/pp-template GitHub Wiki

2021-08-19

github does not accept https urls. Not only does this affect how users clone projects, but also how the transforms are updated. To change your projects transforms url open ".gitmodules", ".git/config", and ".git/modules/transforms/config" and change all https://github.com/commoncriteria/transforms to [email protected]:commoncriteria/transforms.

2021-02-27

Reimplemented the depends element to make it simpler.

2021-02-03

Updated usecase so that decision trees can be built automatically.

2021-01-20

Two big changes:

  1. Replaced many cross-referencing mechanisms (e.g. linkref, secref, ctr-ref, fig-ref) with a single xref.
  2. Removed 'chapter' and 'subsection' elements. Everything is now a 'section'. In addition
    there are flexible sections.

2020-11-18

The transforms seem incompatible with Xalan due to a bug with how they process external document references, so use libxslt-based transformers like xsltproc if possible.

2020-10-20

New make target: little-diff. The little-diff make target attempts to diff the current release against the last release before yesterday. To use it type:

make little-diff

To include it as part of the continuous build add the line to your .travis.yml file

- make little-diff

See here for an example.

2020-01-20

PP-Template is now also the prototyping project. It showcases existing (and impending) functionality.

2020-01-15

Added equation tag which allows users to define an equation with MathML and a label for it which will appear next to the equation.

2019-11-15

An audit-event can be specified per f-component. They then can be gathered up and displayed using audit-events.

2019-11-1

f-components and f-elements are automatically discovered and linked---you don't have to explicitly link them. As such, the component-refers tags in the objectives section has been replaced by a free-formed addressed-by section.

2019-10-18

Two updates to make things easier or "easier" for PP developers:

  • f-elements are automatically assigned a CC ID. You don't need to put a CC ID attribute. You can have an id attribute on the f-element xml element, but that's only to reference the f-element within the document. The schema won't allow traditional f-element ID's there to stop people from using it as it was.
  • You don't need to call out abbreviations and terms within the document. The framework will find them and link them. (This is still being worked).

2019-09-26

THe Appendicies for PP's has been reshuffled.

  • Appendix A (In release) now combines "strictly optional", objective, and implementation-based requirements.
  • Appendix B is still selection-based
  • Appendix C starts the PP-specific appendicies

There's been schema changes Furthermore, Appendix A and Appendix B are now completely autogenerated and there are no hooks at the moment.

2019-09-20

The Codenvy tools support makefiles. You'll need to

   source /path/to/codenvy-tools/setup.sh

And then copy /path/to/codenvy-tools/User.make into the PP project's directory and probably edit it.

2019-09-15

To turn on automatic strict schema validation as part of the automated build add

  - wget -O - https://github.com/relaxng/jing-trang/releases/download/V20181222/jing-20181222.zip | jar -x

to the end of the 'before_script' section

And

  - set -e
  - make validate

to the beginning of the 'script' section.