Difference between revisions of "PKC/Goal"

From PKC
Jump to navigation Jump to search
 
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
To help improve the [[trust-worthiness]] of personalized and project-based data, [[PKC]] is designed as a low entry-barrier data container technology by minimize the operational complexity of data backup, verification, and restore process as a [[sound data validation workflow]], while using [[public-key infrastructure]] and [[networked timestamp]]s to ensure the trust-worthiness of [[PKC]] contained data.
To offer personal data asset management at scale [[PKC]] aims at minimizing the operational complexity of [[data backup]], [[data verification|verification]], and [[data restore|restore]] process as a [[sound data validation workflow]], while using [[public-key infrastructure]] and [[networked timestamp]]s to ensure the [[trust-worthiness]] of [[PKC]] contained data.
<noinclude>
<noinclude>
[[PKC]] should also be used as a pedagogical tool for using and understanding topological structure in a computational way. It will try to enable users see that all relationships can be explicitly managed, represented, and understood as topological entities. This revelation should help people better orchestrate data management practices, and see that computation and decision making are just dynamical topological entities that transform themselves in some ordered sequences, that should all be modeled and [[universally]] treated as directed edges or [[arrow]]s.
=References=
=References=
<references/>
<references/>
</noinclude>
</noinclude>

Latest revision as of 06:43, 1 November 2022

To offer personal data asset management at scale PKC aims at minimizing the operational complexity of data backup, verification, and restore process as a sound data validation workflow, while using public-key infrastructure and networked timestamps to ensure the trust-worthiness of PKC contained data.

PKC should also be used as a pedagogical tool for using and understanding topological structure in a computational way. It will try to enable users see that all relationships can be explicitly managed, represented, and understood as topological entities. This revelation should help people better orchestrate data management practices, and see that computation and decision making are just dynamical topological entities that transform themselves in some ordered sequences, that should all be modeled and universally treated as directed edges or arrows.

References