Google Structured Data Quotes

Data about your thoughts goes into a database owned by Google, what you buy into Amazon or Walmart, and what you owe into Experian or Equifax. You live in a world structured by concentrated corporate power.

Features of Cassandra In order to keep this chapter short, the following bullet list covers the great features provided by Cassandra: Written in Java and hence providing native Java support Blend of Google BigTable and Amazon Dynamo Flexible schemaless column-family data model Support for structured and unstructured data Decentralized, distributed peer-to-peer architecture Multi-data center and rack-aware data replication Location transparent Cloud enabled Fault-tolerant with no single point of failure An automatic and transparent failover Elastic, massively, and linearly scalable Online node addition or removal High Performance Built-in data compression Built-in caching layer Write-optimized Tunable consistency providing choices from very strong consistency to different levels of eventual consistency Provision of Cassandra Query Language (CQL), a SQL-like language imitating INSERT, UPDATE, DELETE, SELECT syntax of SQL Open source and community-driven

Unfortunately, like Jonathan’s failed gate-based product development framework, most management processes in place at companies today are designed with something else in mind. They were devised over a century ago, at a time when mistakes were expensive and only the top executives had comprehensive information, and their primary objectives are lowering risk and ensuring that decisions are made only by the few executives with lots of information. In this traditional command-and-control structure, data flows up to the executives from all over the organization, and decisions subsequently flow down. This approach is designed to slow things down, and it accomplishes the task very well. Meaning that at the very moment when businesses must permanently accelerate, their architecture is working against them.

In this traditional command-and-control structure, data flows up to the executives from all over the organization, and decisions subsequently flow down. This approach is designed to slow things down, and it accomplishes the task very well. Meaning that at the very moment when businesses must permanently accelerate, their architecture is working against them.

NEW BIBLIOGRAPHIC FRAMEWORK To sustain broader partnerships—and to be seen in the non-library specific realm of the Internet—metadata in future library systems will undoubtedly take on new and varied forms. It is essential that future library metadata be understood and open to general formats and technology standards that are used universally. Libraries should still define what data is gathered and what is essential for resource use, keeping in mind the specific needs of information access and discovery. However, the means of storage and structure for this metadata must not be proprietary to library systems. Use of the MARC standard format has locked down library bibliographic information. The format was useful in stand-alone systems for retrieval of holdings in separate libraries, but future library systems will employ non-library-specific formats enabling the discovery of library information by any other system desiring to access the information. We can expect library systems to ingest non-MARC formats such as Dublin Core; likewise, we can expect library discovery interfaces to expose metadata in formats such as Microdata and other Semantic Web formats that can be indexed by search engines. Adoption of open cloud-based systems will allow library data and metadata to be accessible to non-library entities without special arrangements. Libraries spent decades creating and storing information that was only accessible, for the most part, to others within the same profession. Libraries have begun to make partnerships with other non-library entities to share metadata in formats that can be useful to those entities. OCLC has worked on partnerships with Google for programs such as Google Books, where provided library metadata can direct users back to libraries. ONIX for Books, the international standard for electronic distribution of publisher bibliographic data, has opened the exchange of metadata between publishers and libraries for the enhancements of records on both sides of the partnership. To have a presence in the web of information available on the Internet is the only means by which any data organization will survive in the future. Information access is increasingly done online, whether via computer, tablet, or mobile device. If library metadata does not exist where users are—on the Internet—then libraries do not exist to those users. Exchanging metadata with non-library entities on the Internet will allow libraries to be seen and used. In addition to adopting open systems, libraries will be able to collectively work on implementation of a planned new bibliographic framework when using library platforms. This new framework will be based on standards relevant to the web of linked data rather than standards proprietary to libraries

Product development has become a faster, more flexible process, where radically better products don’t stand on the shoulders of giants, but on the shoulders of lots of iterations. The basis for success then, and for continual product excellence, is speed. Unfortunately, like Jonathan’s failed gate-based product development framework, most management processes in place at companies today are designed with something else in mind. They were devised over a century ago, at a time when mistakes were expensive and only the top executives had comprehensive information, and their primary objectives are lowering risk and ensuring that decisions are made only by the few executives with lots of information. In this traditional command-and-control structure, data flows up to the executives from all over the organization, and decisions subsequently flow down. This approach is designed to slow things down, and it accomplishes the task very well. Meaning that at the very moment when businesses must permanently accelerate, their architecture is working against them.

Turing showed that just as the uncertainties of physics stem from using electrons and photons to measure themselves, the limitations of computers stem from recursive self-reference. Just as quantum theory fell into self-referential loops of uncertainty because it measured atoms and electrons using instruments composed of atoms and electrons, computer logic could not escape self-referential loops as its own logical structures informed its own algorithms.12

If the fork in question is provably limited in scope, that helps, as well — avoid forks for interfaces that could operate across time or project-time boundaries (data structures, serialization formats, networking protocols).