Difference between revisions of "Abstract Specification of PKC/Boundary"

From PKC
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
*The PKC system architecture specification must be future-proof and eliminate design dependencies on extant data storage, communication, and computation tools.
*The [[PKC]] system architecture specification might be irrelevant due to revolutionary or competing solutions that were not known to the designers becoming available.
*The abstract specification document must segregate logical specifications from implementation and be distributed alongside all deployed copies of the PKC's concrete implementation.
*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.

Latest revision as of 05:31, 29 March 2023

  • The PKC system architecture specification might be irrelevant 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.
Retrieved from "https://pkc.pub/index.php?title=Abstract_Specification_of_PKC/Boundary&oldid=38636"