Difference between revisions of "Meeting/2021.08.25/Ben,KevinTung"
Jump to navigation
Jump to search
(→Output) |
(→Output) |
||
| Line 19: | Line 19: | ||
* [[Chat/Meeting/2021.08.25/Ben,KevinTung]] | * [[Chat/Meeting/2021.08.25/Ben,KevinTung]] | ||
* [[Video/Meeting/2021.08.25/Ben,KevinTung]] | * [[Video/Meeting/2021.08.25/Ben,KevinTung]] | ||
* | * These data generated from the synchronous meeting triggers the asynchronous session to further discuss and structure them , which is in another Logic Model. | ||
== Meta == | == Meta == | ||
Latest revision as of 12:34, 25 August 2021
| Start time | 2021-08-25T08:00:00.000Z |
|---|---|
| End time | 2021-08-25T09:30:00.000Z |
| Attendees | @BenKoo, @KevinTung |
| Context | TLA Workflow/Process/Planning |
| Goal | Discuss About TLA Workflow |
| Criteria | The neccasary information is communicated |
| Meeting URL | https://zoom.us/j/92921308938?pwd=dFhwSXBreDBmd3ZLSHIzNkplaHVvUT09 |
Input
Process
Output
- Chat/Meeting/2021.08.25/Ben,KevinTung
- Video/Meeting/2021.08.25/Ben,KevinTung
- These data generated from the synchronous meeting triggers the asynchronous session to further discuss and structure them , which is in another Logic Model.
Meta
The current strategy of managing the Chat data is to place the structure of the data as its prefix, and the semantics as its postfix. Such as
Chat/Meeting/2021.08.25/Ben,KevinTung Video/Meeting/2021.08.25/Ben,KevinTun
As the structure of data is limited, the top-level of the namespace is more compact. However, it is also possible to use the primary semantic of the data as its prefix, such as
Meeting/2021.08.25/Ben,KevinTung/Chat Meeting/2021.08.25/Ben,KevinTung/Video
The possible benefit is to have better control over the resources under the prefix, which is a common practice. It is also possible to use multiple hierarchical structures to manage ontologies. So there will be fixed structure and fluid structure.
I think it is an important part of Namespace Management open to discussion.