How To Contribute to SAF?

The SAF Specification is published as markdown documentation in the SAF-Specification github repository. It is generated from a model.

Reporting Issues

Problems should be reported via github issue tracking. It should be stated what the problem is and a short solution should be suggested, ideally accompanied by a pull request.

Proposing Changes (pull request)

In general, changes should be proposed by forking the main branch of the SAF-Specification repository into a user’s own repository and creating a pull request. This allows the proposed change to be discussed separately without interfering with the development of SAF and without being interfered with by the development of SAF. The pull request is checked, and if the changes are accepted, they are incorporated into the model. A newly created model specification can then be compared with the merged pull request and should be identical.

Proposing new viewpoints

For new viewpoints, the existing viewpoints should be reviewed first, as the concerns may already be covered. Only if a new viewpoint is required, an existing viewpoint should be used as a template and all required viewpoint specification attributes should be completed by the submitter. The procedure is the same as for a change request, but the change request must be supported by a conceptual model showing the relationships and the elements to be represented. This conceptual model must be discussed with the SAF architects and compared with the existing concepts.

Proposing Changes or Viewpoints using GitHub Discussions

Changes may be proposed using the Discussions on the Specification Repository

Developing SAF

he development of the SAF viewpoints comprises several interlinked elements and concepts. How the SAF is developed is explained in more detail in this article SAF-Development.