CPF Process

CPFs must be submitted through a national or organizational body (see points of contact).  When first submitted, the CPF may go through a "pre-submittal" workflow where it must gain approval within the national/organizational body before it can be put forward to the S1000D Steering Committee for consideration (view the high-level CPF Process Diagram).

CPF States

Once a CPF successfully completes its pre-submittal approval, it is submitted to the S1000D Steering Committee (SC) by the sponsoring country/organization and given a status of "New".  As it progresses through its lifecycle, the CPF will be assigned other states based on the degree of completeness and acceptance.  The list below describes all of the S1000D CPF states. 

New - The CPF has been received, registered and published on the web, ready for consideration by SC at its next meeting (or whenever it is put on the agenda).

Candidate - The CPF has a business and/or technical value to add to the spec and the CPF is declared as suitable for further work. A target issue of the specification is identified.  A Candidate has been given clearance to go on with finding a solution accepted in concept, business wise and technically, by all parties.  After the CPF has been declared as Candidate, the CPF owner develops a WP incl. business demands and conceptual technical solution (alternative solutions if necessary) to persuade the SC that this it the right way to go.

Inwork - The CPF has a concept accepted for a business demand/solution and a proposed technical solution, maybe not fully developed in all details, but the way forward is agreed.  The CPF owner can now in peace and quiet start to fully develop the necessary basis for the chapter owners like

• Update chapters (complete chapters or just parts to be included in affected chapters), i.e. introduce/produce one or more of the following:
• Minor changes (paragraphs and illustrations) can be documented in the WP.
• Completely new chapter shall be documented in the S1000D template.
• Chapters completely rewritten shall base the update on a copy of the previous issue (requested from the secretary).
• Schema summary document (with illustrations as necessary) for inclusion in the Schemas by the Electronic Publication Working Group (EPWG).

Pending approval - The CPF (including the WP with the complete documented and agreed solution) has been provisionally approved. The draft chapters and Schema changes from the given CPF have been agreed and are now parked waiting for a double check with changes of the same chapters from other CPFs and for merging process. The accepted CPFs are being checked together with overlapping CPFs with no contradictions (or contradictions solved).  A Task is raised for the merging.

Approved - The CPF has been authorized for inclusion in a specific future release of the specification.

Returned - The CPF lacks information, either in the business case and/or on the technical solution. The returned CPF will include specific comments to enable the issuing authority to give the missing information.

• Only applies to the steps New or Pending approval.
• The CPF is returned to the national/industry organization or the CPF submitter in the case of an individually raised CPF.

Rejected - The CPF has been rejected by the SC.

• The business need is not accepted.
• Sufficient information cannot be obtained from raising authority to implement CPF.

Withdrawn - The raising authority no longer requires the change and has withdrawn the CPF or it has been superseded by another CPF.

Complete - The change has been incorporated in S1000D.