You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The distinction between data and metadata has become blurrier over the past few years. With the ability to "translate" data from one data structure to another, some of the schema information (metadata) becomes data in the process, and vice versa, e.g. moving content between long and wide. In addition, whether a given piece of information can be viewed as data or metadata depends heavily in the context of use, e.g. locations, which are data in an address register, can become classification items, which are metadata in a classification management system. GSIM has historically treated data and metadata very differently, perhaps it's time to look now at the ways data and metadata are structured and put together in GSIM with the aim of using common constructs.
The text was updated successfully, but these errors were encountered:
The distinction between data and metadata has become blurrier over the past few years. With the ability to "translate" data from one data structure to another, some of the schema information (metadata) becomes data in the process, and vice versa, e.g. moving content between long and wide. In addition, whether a given piece of information can be viewed as data or metadata depends heavily in the context of use, e.g. locations, which are data in an address register, can become classification items, which are metadata in a classification management system. GSIM has historically treated data and metadata very differently, perhaps it's time to look now at the ways data and metadata are structured and put together in GSIM with the aim of using common constructs.
The text was updated successfully, but these errors were encountered: