43-EFT.WP.Data.DatasetCards v1.0 | Chapter 2 Terms & Dependencies

Home ／ Docs-Technical WhitePaper ／ 43-EFT.WP.Data.DatasetCards v1.0

Chapter 2 Terms & Dependencies

I. Chapter Position & Coverage

• Position: Define terminology sources used by this volume, the incremental glossary, unified symbols and dimensional baselines; fix cross-volume dependencies with version and anchor syntax.
• Coverage: Terminology sources and version pinning, symbols and notation, field naming and type constraints, cross-volume dependency map, citation & anchor rules, T_arr dependency posture, conflict and reserved names, machine-readable dependencies and validation.

II. Terminology Sources & Version Pinning

• General terminology: Follow EFT.WP.Core.Terms v1.0. This volume only adds dataset-card-specific incremental terms. Citations must include “Volume + Version + Chapter/Anchor”. Example: See "EFT.WP.Core.Terms v1.0" Ch.1 P10-*.
• Pinned dependencies: Default minimal set is Core.Equations v1.1, Core.Metrology v1.0, Core.DataSpec v1.0. If a higher version is required, declare it explicitly in this volume’s metadata.
• Clause-level citations: Prefer P/S/M/I anchors; avoid whole-volume generic cites and aliases.

III. Unified Symbols & Dimensional Baseline

• Inline symbols: Always wrapped with backticks (e.g., T_arr, c_ref, n_eff, phi(x,t), Xi(x,t)). Any expression with division/integral/composite operators must use parentheses and explicitly declare path gamma(ell) and measure d ell. No Chinese inside formulas.
• Dimensions/units: Use SI and the dimensional check workflow check_dim from Core.Metrology v1.0; numeric fields must pass dimensional and unit consistency checks.

Incremental glossary (minimal set for this volume):

IV. Field Naming & Type Constraints

• Naming style: Keys use snake_case; plural entities as arrays (e.g., sources[], modality[]).
• Type constraints: Fixed in this volume’s Schema via type/enum/pattern/required, with companion Lint rules.

V. Cross-Volume Dependency Map (Minimal Set)

• Terms/Definitions: EFT.WP.Core.Terms v1.0 (Ch.1–Ch.2, P10-*).
• Equations/Posture: EFT.WP.Core.Equations v1.1 (Ch.2, S20-* for arrival time; other path-integral minima).
• Metrology/Units/Uncertainty: EFT.WP.Core.Metrology v1.0 (check_dim, error-budget workflows Mx-*).
• Data contracts/Export: EFT.WP.Core.DataSpec v1.0 (file organization, release, export_manifest).

VI. Citation & Anchor Rules

• Fixed format: See "<Volume> vX.Y" Ch.<n> <Anchor>; anchor types: Postulates Pxx-?, Minimal equations Sxx-?, Metrology workflows Mx-?, Implementation bindings Ixx-?.
• Machine-readable references: Use "Volume vX.Y:Anchor" in see[]; export artifacts must include version and references[].
• Prohibitions: No shortcodes, aliases, or missing version numbers.

VII. Arrival Time T_arr Dependency Posture

1. Two equivalent expressions:
   • Constant factored: T_arr = ( 1 / c_ref ) * ( ∫ n_eff d ell )
   • General form: T_arr = ( ∫ ( n_eff / c_ref ) d ell )
2. Registration requirements: Whenever T_arr is used, register in metadata: delta_form, path="gamma(ell)", measure="d ell", and pass metrology checks. Dependencies: Core.Equations v1.1 Ch.2 S20-*, Core.Metrology v1.0 check_dim.

VIII. Conflict & Reserved Names

• Conflict enforcement: T_fil (tension) vs. T_trans (transmission coefficient) must not be mixed; n (number density) vs. n_eff (effective refractive index) strictly distinguished.
• Reserved examples: dataset_id, version, license, access, splits are reserved; semantics must not be redefined. Constraints are unified in this volume’s Schema and Core.DataSpec v1.0.

IX. Machine-Readable Dependencies & Implementation Binding

• see[] example:
• see:
• - "EFT.WP.Core.Equations v1.1:S20-1"
• - "EFT.WP.Core.Metrology v1.0:check_dim"
• - "EFT.WP.Core.DataSpec v1.0:TARR"

Export manifest requirements:

version: "v1.0"

references:

- "EFT.WP.Core.Equations v1.1:S20-1"

- "EFT.WP.Core.Metrology v1.0:check_dim"

- "EFT.WP.Core.DataSpec v1.0:EXPORT"

This syntax aligns with EFT Citation & Cross-Reference Spec v0.1.

X. Compliance Checklist (for this chapter)

• All terms traceable to Core.Terms v1.0 or the incremental table; no aliases or polysemy.
• All formulas respect backticks, parentheses, explicit path/measure, and no Chinese in math.
• Dimensional/unit checks pass via check_dim; any T_arr usage records delta_form, path, measure.
• All dependent volumes include version numbers and P/S/M/I anchors; export artifacts include references[] and version.