PKC/Design Principle

Design Principle

PKC is designed with functional representation in mind, that function is treated as a primitive form of data, and can be recursively referenced to perform both computation and carry computational results. By thinking about this design principle at all times, all pages in PKC will be constructed and decomposed based on a functional style, a style that has a name, as the head of a function, and many key-value-pairs as its arguments. Thinking about functions at all times in this primitive, yet generic construct, allows users to think of all functions as hyperlinks or fiber bundles that relates objects from one to the other, revealing the topological structures, or the systematic structures of anything. Most importantly, users of PKC can think of writing down notes in various pages are effectively construction functions or conducting computational work in parallel and in an explicit functionally designed data storage. The design principle that differentiate PKC from other hyperlink/hypermedia systems is that PKC considers data content within the system as an integral part of the system. Since every instance of PKC is tightly bound with its own content, all PKC must allow maximum freedom to all instance of PKC. To accomplish this design principle, it needs to give full ownership and power to conduct changes to the owners of individual instances. In the most primitive scenario, it must reduce the barrier to entry, so that it is convenient and cheap to create new instances that are independent from other instances of PKC.