Difference between revisions of "Meeting/2021.08.22/Ben, Kevin"
Jump to navigation
Jump to search
(→Notes) |
|||
Line 32: | Line 32: | ||
** every input is addressible | ** every input is addressible | ||
* link -> conflict -> jump to others namespace -> collaborate -> neccesesity to collaborate | * link -> conflict -> jump to others namespace -> collaborate -> neccesesity to collaborate | ||
* What we did : | |||
Why science progress halt: namespace of contribution is a mess. | |||
K8s: use [[etcd]] to manage namespace | |||
== Actions == | == Actions == |
Latest revision as of 12:55, 22 August 2021
Start time | 2021-08-22T12:00:00.000Z |
---|---|
End time | 2021-08-22T13:00:00.000Z |
Attendees | @BenKoo, @KevinTung |
Context | This is the last week of the PKC summer project |
Goal | Conclusion of the project, Future Work Discussion |
Criteria | Have a framework for the PKC project |
Meeting URL |
Progress
- The context of conclusion:
- it is required by the summer course
- it serves as the conclusion for the 2-month work
- it serves as theorization of PKC, Ideation, and related domains
- Original Plan
- System integration of CMS and automation tools like Jenkins
- Formal method on top of data
- Actual work
- Practice of data/content management on Mediawiki during work.
- Investigate K-framkework, TLA, Jenkins; successfully installed these tools; but not integrate in a theoretical view
- Research of semantic framework in several perspectives
- Mathematica and its functional representation
- Using Logic Model to model knowledge.
- Namespace management
- Knowledge organization, knowledge representation, and its relation with AI (still working)
- Investigate and practice K8s
- Engineering of the PKC system
Notes
- A function is a carrier for information
- every input is addressible
- link -> conflict -> jump to others namespace -> collaborate -> neccesesity to collaborate
- What we did :
Why science progress halt: namespace of contribution is a mess. K8s: use etcd to manage namespace