Issue 310: Editorial status in CIDOC CRM and CRM family models releases
Τhe crm-sig proposed to add information about the editorial status of the current version of CIDOC CRM text and the text of the CRM family models. Consequently the following 6 editorial statuses along with their definitions were proposed:
Editorial status - closed: This document is no longer under editorial revision. It is no longer subject to change and its contents will remain stable.
Editorial status - open: This is an unrevised and as yet incomplete community version of the CIDOC CRM. It represents a working version of the CIDOC CRM and should not be used for implementation, reference or other official purposes. The function of this document is as a reference resource for developers of the CIDOC CRM standard to discuss on-going, proposed but not yet accepted changes to the model. The contents of this document are not stable and are subject to change
Also the following definitions are proposed about document types of CIDOC CRM text or CRM family models:
Official release with status Closed: This is a revised and complete community version of the CIDOC CRM ontology that has a direct correspondence to an official ISO version of the standard. It forms a stable release of the standard and can be used for implementation, reference and any other official purpose. The document is final and will undergo no further change
Published release with status closed: This is a revised and complete community version of the CIDOC CRM. It forms a stable release of the standard and can be used for implementation, reference and any other official purpose. Relative to official releases that it follows, it represents a stable evolution of the model relative to the last official release. The document is final and will undergo no further change
Current release with status in Progress:This is the currently edited version of the CIDOC CRM text. It is subject to open issues that are actively being worked on. The document may therefore change at any time in accordance with CIDOC CRM SIG list discussions and their conclusions. This copy of this release should be used only for the purpose of following present modelling discussions on the CIDOC CRM SIG list. This document is not meant to support implementations, referencing or other official activities
Current release with status Under Revision:This is the currently edited version of the CIDOC CRM standard. It is subject to open issues that have been declared and specified and which are scheduled to be addressed in an upcoming meeting of the CIDOC CRM SIG. The document may change relative to decisions taken at the next CIDOC CRM SIG meeting. This copy of the standard should be used only for the purpose of following present modelling discussions on the CIDOC CRM SIG list and meetings. It represents a step before a potential stable release of the standard. This document is not meant to support implementations, referencing or other official activities.
In the 36th joined meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9 and the 29th FRBR - CIDOC CRM Harmonization meeting, the crm - sig discussed and accepted the proposed defintions about editorial statuses and document types of CIDOC CRM and CRM family models texts. It remains open the definition of the complete workflow of the these documents.
Posted by George on 18/10/2020
A long time ago, we wrote up some definitions of the statuses and meanings behind the different ways of describing releases of CRM. Then a hw was assigned to GB to write up the workflow of how those were produced. The issue can be found documented here:
I wrote up some text to get the ball rolling on describing the workflow / raison d'etre behind the different versions of the specification that appear on the site:
I offer the hw as a first step. Does it capture anything like what we were hoping for? If not, what else do we need to put in there?
In the 48th CIDOC CRM and 41st FRBR CRM sig meeting (virtual),GB presented his HW (an outline of the text on the editorial statuses of CIDOC CRM and CRM family models). The sig assigned GB to incorporate comments by sig members in the document, and then pass it to a group of reviewers (MD, SdS, TV). Then put it to an e-vote.