Difference between revisions of "Category:CPs"

This page currently describes our requirements for CPs and ideas for using the Wiki. Once we have figured it out and are ready to start drafting a proper CP page we should move this text to Discussion and draft here.

We could organize this page several ways.

1) We could have a manually edited table (probably similar to the Frameworks page, one table for each domain, that lists each CP, maybe indicates the Profile it affects, it's current status and a link to a file with the CP (or a bunch of them).

2) We could have an automatically generated list (similar to the Category:Profile Implementations page. We would then have a page for each CP (based on a template). This might work best if the page was the actual master copy of the CP. The CP pages could have several categories like (XDS CPs) (IT Infra CPs) (Final Text CPs) which give us a bunch of handy autopopulating index pages. ...

Implementor Needs

Q. What CPs do I need to apply (based on what actor/transaction/profile I've implemented and which "version" of the spec I was working from)

Q. What CPs are currently under consideration/development

Q. How do I submit a CP?

Q. What is the current status of a particular CP

Tech Cmte Needs

Q. What CPs are currently under consideration/development

Q. How do I submit a CP?

Q. What is the current status of a particular CP

Q. What CPs are assigned to me?

Q. [TF Editor] What CPs do I need to fold into the next draft of the TF?

CP Management

<describe the phases a CP goes through>

Maintenance of existing Technical Framework content

Despite the best efforts of the Technical Committee, a published current version of the Technical Framework or Trial Implementation documents may contain text that is incorrect, incomplete or unclear. Such issues are handled as Change Proposals and cover:

• Corrections: technical issues causing non-interoperability of implementations are fixed without introducing changes in functionality of a stable Integration Profile.
• Clarifications: text that can be misunderstood or is ambiguous is made easier to understand or disambiguated, without introducing any technical changes.

The publication process is the same for both Corrections and Clarifications, and addresses both changes to Trial Implementations and changes to a current version of the Technical Framework.

A Submitted Change Proposal results from issues raised by users, vendors or Technical Committee members, e.g. from experiences with Trial Implementation or Final Text Integration Profiles or at a Connect-a-thon. The resulting Change Proposal document should explicitly state:

• the parts of the Technical Framework requested to be changed,
• a problem description,
• a rationale why the change is considered necessary,
• and a solution or approach to the problem.

The Technical Committee regularly considers Change Proposals which are then either accepted or rejected.

A Rejected Change Proposal is published with a rationale from the Technical Committee explaining why the change is not appropriate.

An Accepted Change Proposal is assigned to a member of the Technical Committee as a work item for further investigation with the goal to produce adequate clarifications or corrections. The resulting text will again be reviewed by the Technical Committee before being approved.

Once approved, a Final Text Change Proposal is published by the Technical Committee, and then is to be considered as effective. It will be merged into the next version of the Technical Framework at the end of the annual development cycle. Submitting a Change Proposal to a Final Text Change Proposal or a Final Text Supplement is not possible.

The current version of the Technical Framework is considered the primary reference document. Final Text Supplements and Final Text Change Proposals from the current annual cycle complement this document. Past Final Text documents are retained to provide convenient summaries of differences to prior versions of the Technical Framework or Trial Implementation versions of Supplements.

Write the rationale for a rejected CP into the CP and then link from the status page.

Current FTP Usage for organizing/ managing CP documents