Difference between revisions of "Hyperlink-centric data asset"

From PKC
Jump to navigation Jump to search
Line 1: Line 1:
The term: [[hyperlink-centric]] data asset is an idea that all data management is about namespace management, and it would be convenient to leverage this existing namespace management technology to orchestrate all other functions and instrumentation of data management. In the case of [[PKC]], the [[hyperlink-centric]] data management is accomplished by [[MediaWiki]]. We intentionally separate the concept of hyperlink, away from the implementation of the web, or MediaWiki, because we would like to practice [[separation of concerns]], in the documentation of knowledge in [[PKC]].
The term: [[hyperlink-centric]] data asset (it can also be thought of as a data center, since it provides many operational functionalities of data management) is an idea that all data management is about namespace management, and it would be convenient to leverage this existing namespace management technology to orchestrate all other functions and instrumentation of data management. In the case of [[PKC]], the [[hyperlink-centric]] data management is accomplished by [[MediaWiki]]. We intentionally separate the concept of hyperlink, away from the implementation of the web, or MediaWiki, because we would like to practice [[separation of concerns]], in the documentation of knowledge in [[PKC]].


[[Category:MediaWiki]]
[[Category:MediaWiki]]

Revision as of 04:41, 9 June 2022

The term: hyperlink-centric data asset (it can also be thought of as a data center, since it provides many operational functionalities of data management) is an idea that all data management is about namespace management, and it would be convenient to leverage this existing namespace management technology to orchestrate all other functions and instrumentation of data management. In the case of PKC, the hyperlink-centric data management is accomplished by MediaWiki. We intentionally separate the concept of hyperlink, away from the implementation of the web, or MediaWiki, because we would like to practice separation of concerns, in the documentation of knowledge in PKC.