What Is Small Data, and Why Is It Important?

“fundamental characteristics of data — Volume, Velocity, and Variety” ⤴️
“Veracity and Vulnerability” ⤴️
“Loose-coupling of Database Management Systems (DBMS) and Database Files — moving from the traditional one-to-one association between a DBMS and its propriety Database Document Type, to a one-to-many association between a single DBMS and a variety of proprietary and/or open-standard” ⤴️
“xtending Storage using Clusters of Database Files” ⤴️
“ewer network-oriented filesystems (HDFS, Apache Spark, etc.) have emerged that enable the use of commodity hardware to construct vast clusters of Database Document Files that collectively increase data storage volume” ⤴️
“Mapping the Content of Database Document Files to Relations — which are then operated on declaratively by a given DBMS using query languages,” ⤴️
“he most obvious Data Challenges posed by the five Vs are being addressed by more physical storage made available” ⤴️
“his doesn’t address the deeper issues” ⤴️
““Small Data” introduces a new paradigm where puzzle-pieces are progressively discovered and applied to solve a puzzle” ⤴️
“Hyperdata (rather than Hypertext) — where hyperlinks function as “Super Keys” that offer a “deceptively simple” mechanism” ⤴️
“Data Definition — every entity is unambiguously identified using a hyperlink and described using a 3-tuple structure” ⤴️
“each part has a clear role based on existing “parts of speech” principles, i.e., subject, predicate, and object” ⤴️
“flow across traditional boundaries that underly all Data Silos (e.g., software applications, host operating systems, host machines, and networks)” ⤴️
“using declarative query languages” ⤴️
“to operate on data that flows across traditional boundaries” ⤴️
“constants and variables in the query body are resolved on an as-needed basis” ⤴️
"" ⤴️
“PARQL Service Providing “Progressive Data Access” rather than Bulk Import and Export Batch Processing Pipelines” ⤴️
“Benefits?” ⤴️
“ubiquitous support of HTTP, you can refer to data from a variety of applications and services,” ⤴️
“avoid building out new clusters of database documents” ⤴️
“Performance & Scale —by leveraging innovations in cache-invalidation schemes and data compression” ⤴️
“Data Privacy and Security — by fusing data representation with the logic that underlies entity descriptions” ⤴️
“access to data is controlled declaratively” ⤴️
“ine-grained attribute-based access controls” ⤴️
“ultural changes around data management that increase participation” ⤴️
“Adherence to Linked Data Principles implies that Entities are Identified using hyperlinks” ⤴️
“deally, an HTTP URI due to the combined effects of resolvability and global ubiquity” ⤴️
“3-tuple structure comprising a Subject, Predicate, and Object.” ⤴️
“Any user agent can look up (or “dereference”) what that hyperlink identifies.” ⤴️
“a massive collection of puzzle-pieces that describe a variety of things” ⤴️
“amenable to progressive retrieval and association.” ⤴️
“puzzle-pieces come together on request, in response to specific actions” ⤴️
“query” ⤴️
“Small Data is Big Data that’s Accessible (via Hyperlinks as Entity Identifiers) , Understandable (via Subject, Predicate, Object sentences that produce Hyperdata), and Actionable (REST-ful interactions with Actions that manifest as Hyperdata).” ⤴️
“The net effect of this approach to data access, integration, and exploitation enables the construction of Knowledge Graphs that manifest progressively as a Semantic Web of Linked Data deployed across public and/or private networks (a/k/a Hybrid Clouds).” ⤴️

What Is Small Data, and Why Is It Important?

“fundamental characteristics of data — Volume, Velocity, and Variety” ⤴️
“Veracity and Vulnerability” ⤴️
“Loose-coupling of Database Management Systems (DBMS) and Database Files — moving from the traditional one-to-one association between a DBMS and its propriety Database Document Type, to a one-to-many association between a single DBMS and a variety of proprietary and/or open-standard” ⤴️
“xtending Storage using Clusters of Database Files” ⤴️
“ewer network-oriented filesystems (HDFS, Apache Spark, etc.) have emerged that enable the use of commodity hardware to construct vast clusters of Database Document Files that collectively increase data storage volume” ⤴️
“Mapping the Content of Database Document Files to Relations — which are then operated on declaratively by a given DBMS using query languages,” ⤴️
“he most obvious Data Challenges posed by the five Vs are being addressed by more physical storage made available” ⤴️
“his doesn’t address the deeper issues” ⤴️
““Small Data” introduces a new paradigm where puzzle-pieces are progressively discovered and applied to solve a puzzle” ⤴️
“Hyperdata (rather than Hypertext) — where hyperlinks function as “Super Keys” that offer a “deceptively simple” mechanism” ⤴️
“Data Definition — every entity is unambiguously identified using a hyperlink and described using a 3-tuple structure” ⤴️
“each part has a clear role based on existing “parts of speech” principles, i.e., subject, predicate, and object” ⤴️
“flow across traditional boundaries that underly all Data Silos (e.g., software applications, host operating systems, host machines, and networks)” ⤴️
“using declarative query languages” ⤴️
“to operate on data that flows across traditional boundaries” ⤴️
“constants and variables in the query body are resolved on an as-needed basis” ⤴️
"" ⤴️
“PARQL Service Providing “Progressive Data Access” rather than Bulk Import and Export Batch Processing Pipelines” ⤴️
“Benefits?” ⤴️
“ubiquitous support of HTTP, you can refer to data from a variety of applications and services,” ⤴️
“avoid building out new clusters of database documents” ⤴️
“Performance & Scale —by leveraging innovations in cache-invalidation schemes and data compression” ⤴️
“Data Privacy and Security — by fusing data representation with the logic that underlies entity descriptions” ⤴️
“access to data is controlled declaratively” ⤴️
“ine-grained attribute-based access controls” ⤴️
“ultural changes around data management that increase participation” ⤴️
“Adherence to Linked Data Principles implies that Entities are Identified using hyperlinks” ⤴️
“deally, an HTTP URI due to the combined effects of resolvability and global ubiquity” ⤴️
“3-tuple structure comprising a Subject, Predicate, and Object.” ⤴️
“Any user agent can look up (or “dereference”) what that hyperlink identifies.” ⤴️
“a massive collection of puzzle-pieces that describe a variety of things” ⤴️
“amenable to progressive retrieval and association.” ⤴️
“puzzle-pieces come together on request, in response to specific actions” ⤴️
“query” ⤴️
“Small Data is Big Data that’s Accessible (via Hyperlinks as Entity Identifiers) , Understandable (via Subject, Predicate, Object sentences that produce Hyperdata), and Actionable (REST-ful interactions with Actions that manifest as Hyperdata).” ⤴️
“The net effect of this approach to data access, integration, and exploitation enables the construction of Knowledge Graphs that manifest progressively as a Semantic Web of Linked Data deployed across public and/or private networks (a/k/a Hybrid Clouds).” ⤴️