Skip to content

Define the term as 'schema dimension' (shortened to 'dimension')#239

Open
dimitri-yatsenko wants to merge 1 commit into
mainfrom
docs/schema-dimension-term
Open

Define the term as 'schema dimension' (shortened to 'dimension')#239
dimitri-yatsenko wants to merge 1 commit into
mainfrom
docs/schema-dimension-term

Conversation

@dimitri-yatsenko

Copy link
Copy Markdown
Member

Promotes schema dimension to the defined term, then shortens to dimension in-context.

Why

dimension is overloaded — data-warehouse dimension tables, OLAP cubes, and array/tensor dimensions (the type-system and npy pages already use "dimension" for array axes). Qualifying it as schema dimension on definition disambiguates cleanly. This isn't a new coinage: the Entity Integrity page already titles the section ## Schema dimensions and says "lineage through schema dimensions" — this just makes the defined term consistent with that.

Changes (definitional homes only)

  • Entity Integrity → §Schema dimensions: A **dimension** is…A **schema dimension** — often shortened to *dimension* — is…
  • Read Diagrams → §Dimensions and Underlined Names: the same promotion on the definition sentence.
  • Everything else keeps the short form dimension (define once, shorten in-context) — so all headings and anchors are unchanged.

Notes

Promote 'schema dimension' to the defined term in its two definitional homes
(Entity Integrity section Schema dimensions; Read Diagrams section Dimensions and
Underlined Names), then shorten to 'dimension' in-context. Canon already used
'Schema dimensions' as the section heading and 'lineage through schema
dimensions' in prose — this makes the defined term consistent and disambiguates
from array and data-warehouse 'dimension'. Headings/anchors unchanged.

Note: read-diagrams cell source normalized to a single string by the notebook
editor; llms-full.txt regenerates from source.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants