|
1 | | -A list of all COMBINE standard documents |
| 1 | +# COMBINE coordination |
| 2 | + |
| 3 | +## COMBINE coordinator meetings |
| 4 | + |
| 5 | +The global COMBINE effort is led by the COMBINE Coordination Board which meets regularly. The notes of the meetings are made public: |
| 6 | + |
| 7 | +[2026 Coordinator Meeting Notes](https://docs.google.com/document/d/117wvWtX2DTX3NDvJmpZc72-pco4WrVgNVALmRVEhISc/edit?tab=t.0) |
| 8 | +[2025 Coordinator Meeting Notes](https://docs.google.com/document/d/1Oxu9cQAhWIYxZS0RoJG2oUWHoNERLfaMz6KNqF3By14/edit?tab=t.0) |
| 9 | +[2024 Coordinator Meeting Notes](https://docs.google.com/document/d/1MHXmt47v0x-uAT4SXsFkkyICtIpvD0angxnf_dfDlV0/edit?tab=t.0) |
| 10 | +[2023 Coordinator Meeting Notes](https://docs.google.com/document/d/1XzyiN-2QXan7RQd4RwuCTCHiNYv7RH5OMTW_ip_cXZA/edit?tab=t.0) |
| 11 | +[2022 Coordinator Meeting Notes](https://docs.google.com/document/d/1MI7YrsAnklbRfnpON69GRkd1p5f5ELqMrrQ0o9ZAlDo/edit?tab=t.0) |
| 12 | +[2021 Coordinator Meeting Notes](https://docs.google.com/document/d/1pRMUPDWJWhoSb-GrqTgNtjdGhpXPyQCquR44zmPGgTs/edit?tab=t.0) |
| 13 | +[2020 Coordinator Meeting Notes](https://docs.google.com/document/d/1pRMUPDWJWhoSb-GrqTgNtjdGhpXPyQCquR44zmPGgTs/edit?tab=t.0) |
| 14 | +[2019 Coordinator Meeting Notes](https://docs.google.com/document/d/1GTppq4VwwK3AUZnkBR6gmsgjOB2Lx09h1QNedhFSLr8/edit?tab=t.0) |
| 15 | + |
| 16 | +## COMBINE procedures |
| 17 | + |
| 18 | +### Becoming a COMBINE standard |
| 19 | +A pipeline has nevertheless emerged for the inclusion of new standards in the set of COMBINE standards. We intend to formalize it into a SOP. Meanwhile here is a short informal description of the procedure. |
| 20 | + |
| 21 | +A community wanting to add a new description format to the COMBINE set should start by having it listed as a [related or associated standard](https://co.mbine.org/standards/#associated-standards). The developers should join the COMBINE community, and in particular participate to the [annual COMBINE meetings](https://co.mbine.org/events). |
| 22 | + |
| 23 | +COMBINE aims to develop a set of robust interoperable and non-overlapping standards. Candidate standardization efforts must therefore comply a series of criteria: |
| 24 | + |
| 25 | +The aim of COMBINE is to help foster the development of a set of open, interoperable and non-overlapping standards in systems biology. In order to be included in the set of COMBINE standards, an effort must, at a minimum, fulfill the following criteria: |
| 26 | + |
| 27 | +* The standard must cover aspects of modeling in biology that are significantly different from those already catered for by the existing set of COMBINE standards. This includes, but is not limited to, covering different modeling approaches, different biological scales or biological entities, different types of representations. |
| 28 | +The standards must be described in technical specification documents as well as, when appropriate, formal specification languages (for instance, but not solely, XML Schemas, UML diagrams, and so on). The technical specifications must be precise enough to allow certifiable software support. |
| 29 | +* The specifications and other materials describing the specifications (including, for instance, XML Schemas and UML diagrams) must be publicly available free of charge to everyone and be unencumbered by licensing restrictions. If a specification material is covered by a license, it should allow use and redistribution by anyone. And example of a suitable license would be the creative commons with attribution. |
| 30 | +* The development of the standard must be open. The entire COMBINE community must be able to participate without exclusion. Proper ways of communication, must ensure that the community can express needs, criticisms and suggestions about all aspects of the standards. Examples include open development mailing lists with open archives, open source code repository, open website (no password protection). |
| 31 | +* The standard must be developed and used by more than a single team or organisation. |
| 32 | +The development process must be led by editorial boards comprised of democratically elected members, possibly assisted by expert committees nominated by the editorial boards. |
| 33 | +* There must exist a mature software support, including standard API implementations, that facilitates the use of the standard. If possible, validation tools such as test suite, validators, etc., should exist as well. |
| 34 | +* The development of the standard must be stable; for instance, it must be supported by established teams and/or reliable funding sources. The standard must be actively developed. |
| 35 | + |
| 36 | +The acceptance of the format as a COMBINE standard is then decided by the [coordinators](https://co.mbine.org/people/). |
| 37 | + |
| 38 | +### COMBINE format specification infrastructure |
| 39 | +The activities of COMBINE span several standards. Each standard is described in multiple specification documents. It is important to be able to refer precisely and consistently to a given standard or to its specification. It is also important to access the documents. In order to do so, COMBINE provides a [specification infrastructure](https://github.com/combine-org/combine-specifications). There is also a [list of all specifications](https://github.com/combine-org/combine-specifications/tree/main/specifications). |
| 40 | + |
| 41 | +### Organization of COMBINE meetings |
| 42 | +An important activity of COMBINE is to organise common meetings, where the developers of the different standards can meet and work together. If you wish to propose a meeting, or are in the process of setting one up, please read the page [Organization of COMBINE meetings](https://co.mbine.org/author/organizing-a-combine-event/). This document describes the procedures to follow to propose and organize the meetings, defines the respective responsibilities and provides practical advices. |
| 43 | + |
| 44 | +### COMBINE discussions |
| 45 | +Some technical discussions launched within the community are of COMBINE-wide interest. They are therefore documented on this website. They may, or may not, result in documents, solutions, technologies, included in the COMBINE procedures. If you want to discuss the goals, organization and operation of COMBINE, subscribe to [combine-discuss](https://groups.google.com/d/forum/combine-discuss). |
| 46 | + |
| 47 | +### Miscellanea |
| 48 | +COMBINE logos and banners at different resolution are available in [this archive](http://old_co.mbine.org/system/files/COMBINE_logo.tar__0.gz) and in [this repository](https://github.com/combine-org/Logos). |
| 49 | + |
| 50 | +Those logo are provided under the Creative Commons Attribution-ShareAlike 4.0 International licence. Feel free to copy and redistribute them in any medium or format, remix, transform, and build upon them for any COMBINE related purposes. |
| 51 | + |
| 52 | +[A list of all COMBINE standard documents](https://co.mbine.org/standards/) |
2 | 53 |
|
3 | 54 | **Please note: COMBINE specification documents are in the process of being moved over from the [old COMBINE website](http://old_co.mbine.org/). Please [go there](http://old_co.mbine.org/) to find the documents until the move is completed.** |
0 commit comments