| Submitting proposals |
1 Proposals for changes in the TS are standardized in written forms, containing information on: Proposer ID, i.e., identification of the person who suggests a change, Version number, i.e., the unique version number of the TS for which the change is requested, Concept information, i.e., concept ID, concept code and concept name, Change type, i.e., change operation as described in the change model, Change definition, i.e., description of the desired change. |
| Validating the proposals and verifying the changes |
2 Proposals for changes in the TS are validated, on: Necessity, i.e., change is relevant for the domain of TS and does not lead to duplicate information, Possibility to incorporate a change, i.e., change is consistent with scientific knowledge, doest not lead to redundancies and does not violate the TS structure. 3 In case of uncertainty, the acceptance of proposals is based on group consensus. 4 In case a proposal is rejected, feedback is given to the proposer. 5 In case a proposal is accepted, changes made in the TS are verified by the maintenance team, on: Completeness, i.e., all aspects of the change are taken into consideration, Textual correctness, i.e., textual errors are corrected, Consistency of hierarchic relations. the change does not lead to inconsistencies in the relations, Consistency of mappings to other TSs, i.e., the change does not lead to inconsistencies in the mappings to other TSs, Consistency of mappings to other languages, i.e., the change does not lead to inconsistencies in the mappings to other languages. 6 After incorporation of the changes into the TS, feedback is given to the proposer, to: Inform the proposer, i.e., notify that the suggested change is implemented, Ask them to verify the changes, i.e., validate whether the adopted change is in compliance with the suggestion. |
| Documentation |
7 Documentation is structured and standardized. 8 Proposals for changes are documented, with: Proposal Date, i.e., the date on which the suggestion for a change was received, Proposer ID, i.e., information on the proposer like name, address etc., Concept information, i.e., Concept ID, Concept code and Concept name, Change type, i.e., suggested change operation based on the change model, Acceptance method .e.g. whether consensus rounds were used, Status, i.e., is the suggestion accepted or rejected, Acceptation/rejection date, i.e., the date on which it was decided to accept or reject the change. 9 Changes made in the TS are documented, with: Concept information, i.e., concept ID, concept code and concept name, Implementation date, i.e., the date on which the change is incorporated in the system, Change type, i.e., change operation that was performed, Editor ID, i.e., identification of the person who processed the change, Version ID, i.e., version number of the TS in which the change was adopted. |
| Version management |
10 New versions of the TS have a unique identification number, including the publication date and are distributed as: Complete new version, i.e., the whole knowledge of the TS is provided, Incremental update, i.e., list with changes that can be imported into the previous version. 11 On average, twice a year a new release of the system is launched (depending on the type of TS). |
