dido:public:ra:1.2_views:3_taxonomic:4_data_tax:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.2_views:3_taxonomic:4_data_tax:start [2021/09/27 18:48] nick ↷ Links adapted because of a move operation |
dido:public:ra:1.2_views:3_taxonomic:4_data_tax:start [2022/05/27 20:08] (current) nick grammar |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:ra:1.2_views:3_taxonomic:start | return to Taxonomic Views ]] | [[dido:public:ra:1.2_views:3_taxonomic:start | return to Taxonomic Views ]] | ||
| - | * [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:01_cog_taxonomy:start]] | + | On the surface, Data may appear to be a simple, straightforward concept that "everyone" understands, but it's not. It is actually a complex concept with multiple facets and interpretations. Data is generally considered a plural term with the singular form being **datum**, however, common usage allows for data to be considered as singular with the singular-plural differentiation being restricted to academic and scientific usage. (( |
| - | * [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:03_state_taxonomy:start]] | + | __Data Is or Are: Is Data Singular or Plural?__, |
| - | * [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:digi_taxonomy:start]] | + | The Editor's Manual, |
| + | Accessed: 28 September 2021, | ||
| + | [[https://editorsmanual.com/articles/data-singular-or-plural/]] | ||
| + | )) | ||
| + | A more formal definition of data is provided by the Organisation for Economic Co-operation and Development (OECD)(( | ||
| + | __DATA__, | ||
| + | Organization for Economic Co-operation and Development (OECD), | ||
| + | Accessed: 28 September 2021, | ||
| + | [[https://stats.oecd.org/glossary/detail.asp?ID=532]] | ||
| + | )): | ||
| + | : //Characteristics or information, usually numerical, that are collected through observation.// | ||
| + | In essence, Data are individual elemental facts, statistics, or items of information, often numeric, collected through observation. Technically, data is a set of qualitative or quantitative values about one or more persons or objects, (( | ||
| + | __DATA__, | ||
| + | Organization for Economic Co-operation and Development (OECD), | ||
| + | Accessed: 28 September 2021, | ||
| + | [[https://stats.oecd.org/glossary/detail.asp?ID=532]] | ||
| + | )) while a datum (singular of data) is a single value of a single variable. (( | ||
| + | __Data__, | ||
| + | Wikipedia, | ||
| + | Accessed: 28 September 2021, | ||
| + | [[https://en.wikipedia.org/wiki/Data#cite_note-:0-1]] | ||
| + | )) | ||
| - | Data is a complex concept and unfortunately the term is overloaded. Generically, it can describe all a range of concepts from a simple data point to the complex range of data and its association. In the [[dido:public:ra:xapend:xapend.i_cog_model | Cognitive Model]] data is just one level in the human cognitive hierachy. | + | Unfortunately, the terms "data" and "information" are commonly used interchangeably. Nevertheless, these terms have distinct meanings and are part of a larger framework defining an increasingly ordered set of cognitive layers. See: [[dido:public:ra:xapend:xapend.i_cog_model:start]]. |
| + | At the lowest layer of the Cognitive Model, data forms the basis for the other layers with each layer above being a transformation of the layer(s) below. For example, at the lowest Business Management cognitive layer is the //Data// layer, which includes basic data like sales data, revenue, profits, and stock prices. The next layer of the Cognitive model is for //information// that is usually an association of data to each other. For example, stock prices as related to profits. The next layer is //knowledge// which might be a correlation of how profits are related to stock price. At the highest layers of the cognitive models -- //Understanding// and //Wisdom// -- data, information and knowledge are presented in the form of data visualizations (e.g., scatter plots, heat maps, and network models). | ||
| - | : //In any data project, there are likely to be two components. The first is the data collected, assembled, or generated. Think of it as the raw content in the system. It could be hourly temperature readings from a sensor, the age of individuals in a survey, recordings of individual voices, or photographs of plant specimens. The second component is the data system in which the data is stored and managed.(( | + | Data has been described as the new oil of the digital economy. (( |
| + | Yonego, Joris Toonders, | ||
| + | __Data Is the New Oil of the Digital Economy__, | ||
| + | July 23, 2014, | ||
| + | Accessed: 28 September 2021, | ||
| + | [[https://www.wired.com/insights/2014/07/data-new-oil-digital-economy/]] | ||
| + | ))(( | ||
| + | __Data is the new oil__, | ||
| + | July 16, 2018, | ||
| + | Accessed: 28 September 2021, | ||
| + | [[https://spotlessdata.com/blog/data-new-oil]] | ||
| + | )) | ||
| + | |||
| + | There are several taxonomies that cover Data within a DIDO. These taxonomies are not additive in nature but also not mutually exclusive. For example, any data within the DIDO can have a Cognitive classification, as well as, a state and/or a digital taxonomy. A piece of data can be classified as **Knowledge**, **At Rest**, and a **Coin**; or might just as easily have been classified as **Understanding**, **In Motion**, and a **Non-Fungible** asset. | ||
| + | |||
| + | Data taxonomies are described in detail in the following sections: | ||
| + | |||
| + | <nspages -tree dido:public:ra:1.2_views:3_taxonomic:4_data_tax: -exclude -subns -pagesInNs -h1 -textNs=""> | ||
| + | |||
| + | |||
| + | Data is a complex concept that, unfortunately, when employed as a term is overloaded. Generically, it can describe any of a range of concepts from a simple data point to a complex range of data and their associations. In the [[dido:public:ra:xapend:xapend.i_cog_model:start| Cognitive Model]] data is just one level in the human cognitive hierarchy. | ||
| + | |||
| + | |||
| + | : //In any data project, there are likely to be two components. The first is the data collected, assembled, or generated. Think of it as the raw content in the system. It could be hourly temperature readings from a sensor, the age of individuals in a survey, recordings of individual voices, or photographs of plant specimens. The second component is the data system in which the data is stored and managed. (( | ||
| __Introduction to intellectual property rights in data management__, | __Introduction to intellectual property rights in data management__, | ||
| Cornell University, | Cornell University, | ||
| Line 20: | Line 65: | ||
| ))// | ))// | ||
| - | We usually do not think of data content separate from the system in which it is stored, but the distinction is important in terms of intellectual property rights. The question is what, if anything, is protected by [[dido:public:ra:xapend:xapend.a_glossary:c:copyright]]. Data that is factual has no copyright protection under U.S. law; it is not possible to copyright facts. Not all data is in the public domain. A project might, for example, use copyrighted photographs; the photographs are part of the project’s “data.” In many cases, the data in a data management system as well as the metadata describing that data will be factual, and hence not protected by copyright. | + | We usually do not think of data content as separate from the system in which it is stored; however, this distinction is very important from the perspective of intellectual property rights. The question is what, if anything, is protected by [[dido:public:ra:xapend:xapend.a_glossary:c:copyright]]. Under U.S. law, data that is merely factual has no copyright protection; it is not possible to copyright facts. Not all data is in the public domain. A project might, for example, use copyrighted photographs because the photographs are part of the project’s “data.” In many cases, the data in a data management system, as well as, the metadata describing that data will be factual, and hence not protected by copyright. |
| A database, on the other hand, can have a thin layer of copyright protection. Deciding what data needs to be included in a database, how to organize the data, and how to relate different data elements are all creative decisions that may receive copyright protection. | A database, on the other hand, can have a thin layer of copyright protection. Deciding what data needs to be included in a database, how to organize the data, and how to relate different data elements are all creative decisions that may receive copyright protection. | ||
| - | Because of the different copyright status of databases and data content, different mechanisms are required to manage each. Copyright can govern the use of databases and some data content (that which is itself original), but contract law, trademarks, and other mechanisms are required to regulate factual data. | + | Because of the different copyright statuses accorded to databases and their data content, different mechanisms are required to manage each. Copyright can govern the use of databases and some data content (that which is itself original). In contrast, contract law, trademarks, and other mechanisms are required to regulate factual data. |
| + | The third word in the acronym DIDO is __//Data//__, therefore every [[dido:public:ra:xapend:xapend.a_glossary:n:node|node]] manages and controls data. The data within a node is classified as either: | ||
| + | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:03_digi_taxonomy:1_ledger| ledger data]], | ||
| + | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:03_digi_taxonomy:2_ancillary| ancillary data]] or | ||
| + | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:03_digi_taxonomy:3_external| external data]]. | ||
| - | The third word in the acronym DIDO is __//Data//__ and every [[dido:public:ra:xapend:xapend.a_glossary:n:node|node]] therefore, manages and controls data. The data within the node is classified as either: | + | <color red><todo @char>This section has been heavily revised -- need to review</todo></color> |
| - | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:1_ledger| ledger data]], | + | |
| - | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:2_ancillary| ancillary data]] or | + | |
| - | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:3_external| external data]]. | + | |
| - | + | ||
| - | <figure> | + | |
| - | {{ dido:public:ra:1.2_views:1_stake:2_tech_views:2-nodenet:3_node:nodedata.png?300 |}} | + | |
| - | <caption>Types of Node Data | + | |
| - | </caption> | + | |
| - | </figure> | + | |
| - | <nspages -tree dido:public:ra:1.2_views:3_taxonomic:4_data_tax: -exclude -subns -pagesInNs -h1 -textNs=""> | + | |
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.2_views/3_taxonomic/4_data_tax/start.1632782886.txt.gz · Last modified: 2021/09/27 18:48 by nick
