Posted: Nov, 2007Written: early 2007A Brief Introduction to Binding.

Binding values to variables. A binding time principle. Binding semantics to syntax. Binding and data models. Binding costs.

Posted: Nov, 2007Written: Aug, 2006Notes on Enterprise Architecture.

Point-to-point vs. Hub and Spoke Architectures: So How Come the Legacy Airlines are Failing? Why Operational and Historical Data Should be Managed as a Single Unit of Access. How to do this. Three roles of an enterprise data warehouse: (a) a single source of truth; (b) a data switch to solve the "n * (n-1)" problem; (c) a semantically single data repository; (d) a warehouse of pre-fabricated parts.

Posted: Nov, 2007Written: Nov 25, 2007Relational Theory and Data Independence: Unfinished Business.

Logical data independence and the Create View statement. Physical data independence and the Create Table statement. Three ANSI/SPARC Layers, Two CREATE Statements, One Problem. CREATE TABLE As a Conceptual And As a Physical Specification. How Relational Theory and Products Fail to Support Physical Data Independence.

Posted: Mar, 2008Written: Jul, 2007Principles, Policies, Procedures and Standards.

Not quite as brief!

Posted: Mar, 2008Written: Feb, 2007SOA, Semantics and Ontology.

Enterprise architecture: a future state vision. Service oriented architecture. The SOA messaging paradigm. Three high-level architectural patterns. A brief description of semantic management. Terminological taxonomies. Terminological ontologies. The semantics of structured data. Left-over semantics in structured data: relationship labels. Left-over semantics in structured data: data dictionaries. Managing left-over semantics.

Posted: Mar, 2008Written: Aug, 2007The Key to Minimizing Software Total Cost Of Ownership.

Metadata and late binding. Data modeling and software development. Lousy data models. Ontologies and taxonomies.

Posted: Mar, 2008Written: May, 2006What is an ODS?

A single source of truth. A data switch in a non-point-to-point architecture. A warehouse of pre-fabricated sub-assemblies.

Posted: May, 2008Written: May, 2008Enterprise Data Management Principles.

Definitions of Accuracy, Completeness, Consistency, Currency, Effectivity and Efficiency.

Posted: Jun, 2008Published: Oct, 1991 in Database Programming and Design.Cracks in the Foundation.

Architectural flaws in relational theory and practice.

Posted: Jun, 2008Published: Nov, 1991 in Database Programming and Design.Rebuilding the Foundation.

Architectural flaws in relational theory and practice.

Posted: Jun 24, 2008Written: 2007, last revised Jun, 2008.How to Develop and Evolve to an Enterprise IT Architectue at Both the Physical and Semantic Levels: a Proposal.

Posted: Jun 25, 2008Written: 2001. A Flexibility Architectue.