# The lex records whose category is schema-canonical-data-semantics

This index as JSON: https://banes-lab.com/json/api/facets/lex/category/schema-canonical-data-semantics

## Entries

- [Flexible Input](https://banes-lab.com/records/lex/flexible-input.md): The degree to which strictly validating every payload rejects the loosely-shaped input a caller might legitimately send.
- [Untyped Payloads](https://banes-lab.com/records/lex/untyped-payloads.md): Accepting data at a boundary with no schema, so malformed or unexpected shapes flow in unchecked.
- [Dynamic Untyped Boundaries](https://banes-lab.com/records/lex/dynamic-untyped-boundaries.md): Passing untyped values across module or service boundaries, so type errors surface only at runtime.
- [Explicit Types](https://banes-lab.com/records/lex/explicit-types.md): The requirement that values crossing a boundary carry explicit, declared types rather than open-ended ones.
- [Rapid Scripting](https://banes-lab.com/records/lex/rapid-scripting.md): The degree to which requiring explicit types slows the quick, exploratory coding that dynamic typing allows.
- [Bounded Context Autonomy](https://banes-lab.com/records/lex/bounded-context-autonomy.md): The degree to which enforcing one canonical model limits each bounded context's freedom to model its own domain.
- [Multiple Competing Models](https://banes-lab.com/records/lex/multiple-competing-models.md): Several inconsistent models of the same concept coexisting, so translations between them drift and conflict.
- [Normalized Translation](https://banes-lab.com/records/lex/normalized-translation.md): The ability to translate between systems through one shared canonical form rather than many pairwise mappings.
- [Bounded Context Purity](https://banes-lab.com/records/lex/bounded-context-purity.md): The degree to which sharing one enterprise data model erodes the conceptual purity of each bounded context.
- [Cross-System Mapping](https://banes-lab.com/records/lex/cross-system-mapping.md): The ability to map data between systems through a single shared canonical representation.
- [Local Model Autonomy](https://banes-lab.com/records/lex/local-model-autonomy.md): The degree to which a bounded context is free to define and evolve its own data model independently of a shared canonical one.
- [Service-Specific Schemas](https://banes-lab.com/records/lex/service-specific-schemas.md): The degree to which a shared canonical schema competes with each service's need for its own tailored schema.
- [Ambiguous Encoding](https://banes-lab.com/records/lex/ambiguous-encoding.md): Representing the same value in multiple encodings without normalizing, so equal values compare as different.
- [Canonical Format](https://banes-lab.com/records/lex/canonical-format.md): The requirement that a single normalized form be defined for values before they are compared or stored.
- [Deduplication](https://banes-lab.com/records/lex/deduplication.md): The ability to recognize and collapse values that are equivalent once reduced to canonical form.
- [Lossless Preservation](https://banes-lab.com/records/lex/lossless-preservation.md): The degree to which reducing values to a canonical form can discard distinctions the original preserved.
- [Security Checks](https://banes-lab.com/records/lex/security-checks.md): The ability to apply security checks reliably by first reducing input to one unambiguous form.
- [Canonical Definition](https://banes-lab.com/records/lex/canonical-definition.md): The requirement that each fact have one authoritative definition that all consumers reference.
- [Duplicated Authority](https://banes-lab.com/records/lex/duplicated-authority.md): Two or more places each claiming to own the same fact, so they drift and disagree over time.
- [Data Semantics](https://banes-lab.com/records/lex/data-semantics.md): The requirement that the meaning and dependencies of data be understood before it is decomposed into relations.
- [Denormalized Read Models](https://banes-lab.com/records/lex/denormalized-read-models.md): A read-optimized model that deliberately duplicates data to serve queries fast, trading storage and write cost for read speed.
- [Non-Redundant Storage](https://banes-lab.com/records/lex/non-redundant-storage.md): The ability to store each fact once, so it cannot drift out of sync with copies.
- [Query Performance](https://banes-lab.com/records/lex/query-performance.md): The degree to which splitting data across normalized relations forces costly joins on read.
- [Reduced Redundancy](https://banes-lab.com/records/lex/reduced-redundancy.md): The ability to eliminate duplicated facts by referencing a single stored copy.
- [Disambiguation](https://banes-lab.com/records/lex/disambiguation.md): The ability to give each concept one unambiguous name and meaning across a domain.
- [Polysemy Across Contexts](https://banes-lab.com/records/lex/polysemy-across-contexts.md): The degree to which one term legitimately carries different meanings in different bounded contexts.
- [Cross-Context Terminology](https://banes-lab.com/records/lex/cross-context-terminology.md): The degree to which agreeing on shared terms strains against the distinct vocabularies different contexts need.
- [Domain Collaboration](https://banes-lab.com/records/lex/domain-collaboration.md): The requirement that domain experts and developers collaborate to agree on shared terminology.
- [Technical/Domain Mismatch](https://banes-lab.com/records/lex/technical-domain-mismatch.md): Naming code in technical terms disconnected from the domain, so experts and developers talk past each other.
- [Ambiguous API](https://banes-lab.com/records/lex/ambiguous-api.md): An interface whose names and parameters hide what it does, so callers must guess or read the implementation.
- [Clear Semantics](https://banes-lab.com/records/lex/clear-semantics.md): The requirement that an interface's names convey what each operation does and expects.
- [Concise Naming](https://banes-lab.com/records/lex/concise-naming.md): The degree to which naming an interface fully for clarity works against keeping names short.
- [Correct Usage](https://banes-lab.com/records/lex/correct-usage.md): The ability of callers to use an interface correctly because its names reveal its intent.
- [Naming Consistency](https://banes-lab.com/records/lex/naming-consistency.md): The requirement that names for the same concept be used consistently across an interface.
- [Clever Abstractions](https://banes-lab.com/records/lex/clever-abstractions.md): The degree to which clever, non-obvious abstractions trade familiarity for surprise to the reader.
- [Convention](https://banes-lab.com/records/lex/convention.md): The requirement that a design follow established conventions so its behavior matches expectations.
- [Safe Use](https://banes-lab.com/records/lex/safe-use.md): The ability to use an interface safely because it behaves the way its name and shape suggest.
- [Duplicated Denormalized Columns](https://banes-lab.com/records/lex/duplicated-denormalized-columns.md): The same fact copied into many columns and rows, so updates must touch every copy or leave them inconsistent.
- [Functional Dependencies](https://banes-lab.com/records/lex/functional-dependencies.md): The requirement that the dependencies determining which attributes fix others be identified before decomposing a schema.
- [Read Performance](https://banes-lab.com/records/lex/read-performance.md): The degree to which normalizing a schema into many relations forces joins that slow reads.
- [Update-Anomaly Elimination](https://banes-lab.com/records/lex/update-anomaly-elimination.md): The ability to eliminate update anomalies by storing each fact in exactly one place.