Difference between revisions of "Abstract Specification of PKC/Boundary"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
*The [[PKC]] system architecture specification might be challenged due to revolutionary or competing solutions that were not known to the designers becoming available. | *The [[PKC]] system architecture specification might be challenged due to revolutionary or competing solutions that were not known to the designers becoming available. | ||
* | *Unforeseen insights into what data or computational should be better represented becoming available and requires significant modification of this specification. | ||
*All changes of PKC content should be version controlled and replicated with multiple copies. | *All changes of PKC content should be version controlled and replicated with multiple copies. | ||
Revision as of 05:31, 29 March 2023
- The PKC system architecture specification might be challenged due to revolutionary or competing solutions that were not known to the designers becoming available.
- Unforeseen insights into what data or computational should be better represented becoming available and requires significant modification of this specification.
- All changes of PKC content should be version controlled and replicated with multiple copies.