Difference between revisions of "Meeting/2021.08.25/Ben,KevinTung"

From PKC
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 3: Line 3:
|End time=2021-08-25T09:30:00.000Z
|End time=2021-08-25T09:30:00.000Z
|Attendees=@BenKoo, @KevinTung
|Attendees=@BenKoo, @KevinTung
|Context=[[PKC Workflow/TLA Workflow/Planning]]
|Context=TLA Workflow/Process/Planning
|Goal=Discuss About TLA Workflow
|Goal=Discuss About TLA Workflow
|Criteria=The neccasary information is communicated
|Criteria=The neccasary information is communicated
Line 10: Line 10:


== Input ==  
== Input ==  
* [[PKC Workflow/TLA Workflow/Planning]]
* [[TLA Workflow/Process/Planning]]




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 ==  
The strategy of namespace management now is to place the form of the data as its prefix, and the semantics as its postfix. Such as  
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
  Chat/Meeting/2021.08.25/Ben,KevinTung
  Video/Meeting/2021.08.25/Ben,KevinTun
  Video/Meeting/2021.08.25/Ben,KevinTun


As the form is limited, the top-level of the namespace is more compact.   
As [[Math is assigning the same name to different thing|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  
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/Chat
Line 32: Line 32:
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.  
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 [[to discuss::Namespace Management]] open to discussion.
 
I think it is an important part of namespace management open to discussion.

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

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.

Retrieved from "https://pkc.pub/index.php?title=Meeting/2021.08.25/Ben,KevinTung&oldid=10205"