openchain:specification-questions-and-answers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
openchain:specification-questions-and-answers [2019/02/23 15:25] mgisi [Does the specification serve as a best practice guide?] |
openchain:specification-questions-and-answers [2019/11/11 15:07] mgisi [What are the Specification Guiding Principles?] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| * Embrace the implementation of different practices to solve a given requirement | * Embrace the implementation of different practices to solve a given requirement | ||
| * Avoid providing specific legal advice or specific common practices | * Avoid providing specific legal advice or specific common practices | ||
| - | - Function as an open development initiative - open to all to contribute - inclusion via discussion and consensus that adhere to these guiding principles. Consider adopting best practices from standard initiatives which complement the open development approach. | + | - Function as an open development initiative - open to all to contribute - inclusion via discussion and consensus that adhere to these guiding principles. Consider adopting best practices from standard initiatives which complement an open development approach. |
| Line 77: | Line 77: | ||
| ==== What is the different between Conformance vs Compliance ==== | ==== What is the different between Conformance vs Compliance ==== | ||
| - | In the specification text we do *not* use the term "Compliance" with respect to satisfying the spec requirements not to confuse it with "license compliance" or "Open Source Compliance program" which is frequently mentioned through out the spec. We use the term "Conformance" instead to mean a program has satisfied all the spec's requirements. It is possible that someone might make reference to the fact that their program "complies" with version X of the spec or that the program is "compliant" with version X of the spec which would be equivalent to stating the program "conforms" or has achieved "conformance" with version X. | + | In the specification text we do *not* use the term "Compliance" with respect to satisfying the spec requirements - so not to confuse it with "license compliance" or "Open Source Compliance program" which is frequently mentioned through out the spec. We use the term "Conformance" instead to mean a program has satisfied all the spec's requirements. It is possible that someone might make reference to the fact that their program "complies" with version X of the spec or that the program is "compliant" with version X of the spec which would be equivalent to stating the program "conforms"; "is conformant"; or "has achieved conformance" with version X. |
openchain/specification-questions-and-answers.txt ยท Last modified: 2019/11/17 19:12 by mgisi
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
