View source for PKC/Design Principle

==Design Principle==
[[PKC]] models data assets in terms of [[function]]s, which is a kind of [[scale-free]] data representation. These functional data representation are in turn categorized into [[Page]], [[File]], and [[Service]]. Each category of [[function]] is treated as the [[primitive form of data]], and can be recursively referenced to perform both computation and carry computational results. All pages in [[PKC]] are conceptualized as hyperlinked data points in a functional style. All data points or pages have their unique names. These names can be thought of as function names, and each function may have 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 [[hyperlink]]s that relate objects from one to the other, revealing the [[Topology|topological structures]], or the systematic structures of anything. Most importantly, users of [[PKC]] can think of writing down notes in various [[Page|pages]] are effectively construction functions or conducting computational work in parallel and in an explicit functionally designed [[data]] storage. The storage packages are managed in terms of [[file]]s. The availability and reliability of providing these [[page]]s and [[files]] are called [[service]]s. This completes the three categories of [[scale-free]] data representation. 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 instances of [[PKC]]s. 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 egalitarian scenario, we must reduce the barrier to entry, so [[PKC]]s should be convenient and cheap to be replicated or allowing for the creation of new instances that are independent from other instances of [[PKC]], so that the functionality of [[PKC]]s can be easily shared across many application domains.