Skip to content

Commit

Permalink
Added explicit novel scheme support
Browse files Browse the repository at this point in the history
  • Loading branch information
Ryan Williams committed Jul 27, 2023
1 parent 6ff87f2 commit a9fc20d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion CIP-0001/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ Name | Description
Preamble | Headers containing metadata about the CIP ([see below](#header-preamble)).
Abstract | A short (\~200 word) description of the proposed solution and the technical issue being addressed.
Motivation: why is this CIP necessary? | A clear explanation that introduces a proposal's purpose, use cases, and stakeholders. If the CIP changes an established design, it must outline design issues that motivate a rework. For complex proposals, authors must write a [Cardano Problem Statement (CPS) as defined in CIP-9999][CPS] and link to it as the `Motivation`.
Specification | The technical specification should describe the proposed improvement in sufficient technical detail. In particular, it should provide enough information that an implementation can be performed solely based on the design outlined in the CIP. A complete and unambiguous design is necessary to facilitate multiple interoperable implementations. <br/><br/>This must include how the CIP should be versioned. Having stipulation that the proposal must be superseded by another is valid versioning as well as tradition software versioning schemes. Adequate description must be given to allow versioned alterations to be added without author oversight. <br/><br/> If a proposal defines structure of on-chain data it must include a CDDL schema.
Specification | The technical specification should describe the proposed improvement in sufficient technical detail. In particular, it should provide enough information that an implementation can be performed solely based on the design outlined in the CIP. A complete and unambiguous design is necessary to facilitate multiple interoperable implementations. <br/><br/>This must include how the CIP should be versioned. Having stipulation that the proposal must be superseded by another is valid versioning as well as tradition software versioning schemes. Authors are welcome to pursue novel versioning schemes, as long as the schemes enable versioned alterations to be added without author oversight. <br/><br/> If a proposal defines structure of on-chain data it must include a CDDL schema.
Rationale: how does this CIP achieve its goals? | The rationale fleshes out the specification by describing what motivated the design and what led to particular design decisions. It should describe alternate designs considered and related work. The rationale should provide evidence of consensus within the community and discuss significant objections or concerns raised during the discussion. <br/><br/>It must also explain how the proposal affects the backward compatibility of existing solutions when applicable. If the proposal responds to a [CPS][], the 'Rationale' section should explain how it addresses the CPS and answer any questions that the CPS poses for potential solutions.
Path to Active | Organised in two sub-sections (see [Path to Active](#path-to-active) for detail):<br/><h5>Acceptance Criteria</h5>Describes what are the acceptance criteria whereby a proposal becomes _'Active'_.<br/><h5>Implementation Plan</h5>Either a plan to meet those criteria or `N/A` if not applicable.
Copyright | The CIP must be explicitly licensed under acceptable copyright terms ([see below](#licensing)).
Expand Down

0 comments on commit a9fc20d

Please sign in to comment.