Difference between revisions of "Separation of concerns"
Line 2: | Line 2: | ||
=SoC applied in [[PKC]]= | =SoC applied in [[PKC]]= | ||
To help minimize the dependencies of your personal knowledge repository from implementation technologies, [[PKC]] uses the [[universal data | To help minimize the dependencies of your personal knowledge repository from implementation technologies, [[PKC]] uses the [[universal data abstraction]], [[hyperlink]], to represent information of any type, and define the [[hyperlink-centric]] data encoding, storage, retrieval, and manipulation, in pure abstraction, based on properties that associates with [[hyperlink]] or [[key-value pair]] only. Then, given the abstract specification of the needs to encode, store, retrieve, and manipulate these [[hyperlink]]s, then, we can find appropriate technologies to conduct these tasks. |
Revision as of 09:47, 5 August 2021
Separation of concerns(SoC) is a design pattern that reduces information complexity in system design tasks, particularly mentioned in fields as urban planning, software architecture, information systems. In the realization of PKC, SoC is being applied to its evolution process. The tool set that drives the implementation of design decisions of PKC, will be distinctively organized to emphasize SoC.
SoC applied in PKC
To help minimize the dependencies of your personal knowledge repository from implementation technologies, PKC uses the universal data abstraction, hyperlink, to represent information of any type, and define the hyperlink-centric data encoding, storage, retrieval, and manipulation, in pure abstraction, based on properties that associates with hyperlink or key-value pair only. Then, given the abstract specification of the needs to encode, store, retrieve, and manipulate these hyperlinks, then, we can find appropriate technologies to conduct these tasks.