Difference between revisions of "Page/File/Service"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
=Tri-fold Data Abstraction= | =Tri-fold Data Abstraction= | ||
The reason for organizing data assets into this tri-fold abstraction is to create a unifying workflow pipeline to deal with content creation. | The reason for organizing data assets into this tri-fold abstraction is to create a unifying workflow pipeline to deal with content creation. The three kinds of data assets each representing a time-oriented aspect of data. Specifically, [[File]] represents past data, [[Page]] represents current data, [[Service]] represents data to be provision into the future. | ||
<noinclude> | <noinclude> | ||
[[Category:Namespace]] | [[Category:Namespace]] | ||
</noinclude> | </noinclude> | ||
Revision as of 02:05, 15 January 2022
Page/File/Service is a data abstraction scheme dedicated to match the current usage patterns of three kinds of users:
- Page: for all users, including Non-Digital Natives.
- File: for users who are willing to read and follow technical manuals, Content Creators.
- Service: for users who can independently operate their private data services, Self-Service Agents.
Tri-fold Data Abstraction
The reason for organizing data assets into this tri-fold abstraction is to create a unifying workflow pipeline to deal with content creation. The three kinds of data assets each representing a time-oriented aspect of data. Specifically, File represents past data, Page represents current data, Service represents data to be provision into the future.