@adobe/design-data-spec 0.1.0 → 0.2.0

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "{}"
+replaced with your own identifying information. (Don't include
+the brackets!)  The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/conformance/invalid/SPEC-016/expected-errors.json

@@ -0,0 +1,10 @@
+{
+  "layer": 2,
+  "errors": [
+    {
+      "rule_id": "SPEC-016",
+      "severity": "error",
+      "message_pattern": "value does not validate against declared $valueType schema"
+    }
+  ]
+}

package/conformance/invalid/SPEC-016/tokens.tokens.json

@@ -0,0 +1,8 @@
+[
+  {
+    "name": { "property": "bad-typography" },
+    "$valueType": "value-types/typography.schema.json",
+    "value": "not-an-object",
+    "uuid": "aaaaaaaa-0016-4000-8000-000000000001"
+  }
+]

package/conformance/invalid/SPEC-017/expected-errors.json

@@ -0,0 +1,10 @@
+{
+  "layer": 2,
+  "errors": [
+    {
+      "rule_id": "SPEC-017",
+      "severity": "warning",
+      "message_pattern": "string name instead of a name object"
+    }
+  ]
+}

package/conformance/invalid/SPEC-017/tokens.tokens.json

@@ -0,0 +1,7 @@
+[
+  {
+    "name": "focus-ring-color-key-focus",
+    "value": "#0265dc",
+    "uuid": "aaaaaaaa-0017-4000-8000-000000000002"
+  }
+]

package/conformance/valid/composite-drop-shadow.json

@@ -0,0 +1,14 @@
+{
+  "name": { "property": "drop-shadow-default" },
+  "$valueType": "value-types/drop-shadow.schema.json",
+  "value": [
+    {
+      "x": "0px",
+      "y": "1px",
+      "blur": "4px",
+      "spread": "0px",
+      "color": "rgba(0, 0, 0, 0.16)"
+    }
+  ],
+  "uuid": "aaaaaaaa-0010-4000-8000-000000000002"
+}

package/conformance/valid/composite-typography-scale.json

@@ -0,0 +1,6 @@
+{
+  "name": { "property": "typography-scale", "scale": "desktop" },
+  "$valueType": "value-types/typography-scale.schema.json",
+  "value": { "fontSize": "14px", "lineHeight": "18px" },
+  "uuid": "aaaaaaaa-0010-4000-8000-000000000003"
+}

package/conformance/valid/composite-typography.json

@@ -0,0 +1,12 @@
+{
+  "name": { "property": "component-m-regular" },
+  "$valueType": "value-types/typography.schema.json",
+  "value": {
+    "fontFamily": "{sans-serif-font-family}",
+    "fontSize": "{font-size-100}",
+    "fontWeight": "{regular-font-weight}",
+    "letterSpacing": "{letter-spacing}",
+    "lineHeight": "{line-height-font-size-100}"
+  },
+  "uuid": "aaaaaaaa-0010-4000-8000-000000000001"
+}

package/conformance/valid/string-name-escape-hatch.json

@@ -0,0 +1,7 @@
+[
+  {
+    "name": "focus-ring-color-key-focus",
+    "value": "#0265dc",
+    "uuid": "aaaaaaaa-0017-4000-8000-000000000001"
+  }
+]

package/fields/scaleIndex.json

@@ -0,0 +1,15 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/field.schema.json",
+  "specVersion": "1.0.0-draft",
+  "name": "scaleIndex",
+  "description": "Numeric scale index appended at the end of the serialized name (e.g., 100, 200, 900). Used by foundational scale tokens for spacing, color palette, font sizes, border widths, corner radii, and drop-shadow values.",
+  "kind": "numeric",
+  "registry": null,
+  "validation": "none",
+  "serialization": {
+    "position": 16
+  },
+  "scope": null,
+  "required": false,
+  "valueType": "integer"
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adobe/design-data-spec",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Design Data Specification — prose, JSON Schemas, rule catalog, and conformance fixtures for Spectrum design data",
   "type": "module",
   "repository": {
@@ -18,7 +18,6 @@
     "node": ">=20.12.0",
     "pnpm": ">=10.17.1"
   },
-  "packageManager": "pnpm@10.17.1",
   "exports": {
     "./package.json": "./package.json",
     "./schemas/token.schema.json": "./schemas/token.schema.json",
@@ -37,4 +36,4 @@
     "README.md"
   ],
   "scripts": {}
-}
+}

package/rules/rules.yaml

@@ -118,3 +118,39 @@ rules:
     message: "Token {token} has plannedRemoval but is not marked deprecated"
     spec_ref: spec/token-format.md#lifecycle-and-metadata
     introduced_in: "1.0.0-draft"
+
+  - id: SPEC-014
+    name: composite-inline-alias-exists
+    severity: error
+    category: reference-integrity
+    assert: Inline alias references ({token-name}) within composite values MUST resolve to an existing token in the dataset.
+    message: "Inline alias target not found within composite value: {path}"
+    spec_ref: spec/token-format.md#inline-alias-references
+    introduced_in: "1.0.0-draft"
+
+  - id: SPEC-015
+    name: composite-inline-alias-type-compatible
+    severity: error
+    category: type-safety
+    assert: Resolved inline alias target within a composite value MUST have a value type compatible with the sub-value's expected type.
+    message: "Inline alias {path} within composite resolves to incompatible type"
+    spec_ref: spec/token-format.md#inline-alias-references
+    introduced_in: "1.0.0-draft"
+
+  - id: SPEC-016
+    name: value-type-match
+    severity: error
+    category: type-safety
+    assert: When $valueType is present on a token with a literal value, the value MUST validate against the referenced value-type schema.
+    message: "Token {token} value does not validate against declared $valueType schema {schema}"
+    spec_ref: spec/token-format.md#value-type-declaration-valuetype
+    introduced_in: "1.0.0-draft"
+
+  - id: SPEC-017
+    name: string-name-tech-debt
+    severity: warning
+    category: tech-debt
+    assert: Token names SHOULD be structured name objects. A plain string name is permitted as a temporary escape hatch but MUST be treated as tech debt and tracked for remediation.
+    message: 'Token "{name}" uses a string name instead of a name object — treat as tech debt and plan remediation'
+    spec_ref: spec/token-format.md#string-name-escape-hatch
+    introduced_in: "1.0.0-draft"

package/schemas/field.schema.json

@@ -23,8 +23,8 @@
     },
     "kind": {
       "type": "string",
-      "enum": ["semantic", "dimension"],
-      "description": "Whether this field participates in cascade resolution. 'dimension' fields drive cascade specificity; 'semantic' fields describe identity only."
+      "enum": ["semantic", "dimension", "numeric"],
+      "description": "Whether this field participates in serialization ordering or cascade resolution. 'semantic' fields describe identity and appear in the standard serialization order; 'dimension' fields drive cascade specificity; 'numeric' fields hold integer indices appended at the end of the serialized name."
     },
     "registry": {
       "oneOf": [

package/schemas/token.schema.json

@@ -99,7 +99,19 @@
           "const": "1.0.0-draft"
         },
         "name": {
-          "$ref": "#/$defs/nameObject"
+          "oneOf": [
+            { "$ref": "#/$defs/nameObject" },
+            {
+              "type": "string",
+              "minLength": 1,
+              "description": "String escape hatch for tokens that cannot be expressed as a name object. Valid but triggers SPEC-017 (tech-debt warning). See token-format.md#string-name-escape-hatch."
+            }
+          ]
+        },
+        "$valueType": {
+          "type": "string",
+          "format": "uri-reference",
+          "description": "URI reference to a value-type schema under schemas/value-types/. When present, value MUST validate against the referenced schema (rule SPEC-016)."
         },
         "value": {
           "description": "Literal value; type narrowed by value-type schemas where applicable.",
@@ -174,7 +186,19 @@
           "const": "1.0.0-draft"
         },
         "name": {
-          "$ref": "#/$defs/nameObject"
+          "oneOf": [
+            { "$ref": "#/$defs/nameObject" },
+            {
+              "type": "string",
+              "minLength": 1,
+              "description": "String escape hatch for tokens that cannot be expressed as a name object. Valid but triggers SPEC-017 (tech-debt warning). See token-format.md#string-name-escape-hatch."
+            }
+          ]
+        },
+        "$valueType": {
+          "type": "string",
+          "format": "uri-reference",
+          "description": "URI reference to a value-type schema under schemas/value-types/. When present, the alias resolution chain MUST terminate at a token whose value validates against this schema."
         },
         "$ref": {
           "type": "string",

package/schemas/value-types/drop-shadow.schema.json

@@ -0,0 +1,20 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/value-types/drop-shadow.schema.json",
+  "title": "Drop shadow composite value",
+  "description": "Array of shadow layers. Each layer defines offset, blur, spread, and color.",
+  "type": "array",
+  "items": {
+    "type": "object",
+    "properties": {
+      "x": { "type": "string" },
+      "y": { "type": "string" },
+      "blur": { "type": "string" },
+      "spread": { "type": "string" },
+      "color": { "type": "string" }
+    },
+    "required": ["x", "y", "blur", "spread", "color"],
+    "additionalProperties": false
+  },
+  "minItems": 1
+}

package/schemas/value-types/typography-scale.schema.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/value-types/typography-scale.schema.json",
+  "title": "Typography scale composite value",
+  "description": "Pairs a font size with its corresponding line height at a single typographic tier.",
+  "type": "object",
+  "properties": {
+    "fontSize": { "type": "string" },
+    "lineHeight": { "type": "string" }
+  },
+  "required": ["fontSize", "lineHeight"],
+  "additionalProperties": false
+}

package/schemas/value-types/typography.schema.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/value-types/typography.schema.json",
+  "title": "Typography composite value",
+  "description": "Object bundling font properties for a typographic style. Sub-values may be literal strings or inline alias references ({token-name}).",
+  "type": "object",
+  "properties": {
+    "fontFamily": { "type": "string" },
+    "fontSize": { "type": "string" },
+    "fontWeight": { "type": "string" },
+    "letterSpacing": { "type": "string" },
+    "lineHeight": { "type": "string" }
+  },
+  "required": ["fontFamily", "fontSize", "fontWeight", "lineHeight"],
+  "additionalProperties": false
+}

package/spec/token-format.md

@@ -12,13 +12,33 @@ A **token** is a JSON object that satisfies the Layer 1 schema [`token.schema.js
 
 A token **MUST** contain:
 
-1. **`name`** — a JSON object (the **name object**) as defined below.
+1. **`name`** — a JSON object (the **name object**) as defined below, or a non-empty plain string (escape hatch — see [String-name escape hatch](#string-name-escape-hatch)).
 2. Exactly one of:
    * **`value`** — a literal token value (type depends on value-type schema), or
    * **`$ref`** — a string reference to another token (alias).
 
 A token **MUST NOT** include both `value` and `$ref`.
 
+### String-name escape hatch
+
+A token's `name` field **MAY** be a non-empty plain string instead of a name object when the token's identity cannot be expressed using the structured taxonomy fields.
+
+```json
+{
+  "name": "focus-ring-color-key-focus",
+  "value": "#0265dc",
+  "uuid": "aaaaaaaa-0012-4000-8000-000000000001"
+}
+```
+
+**NORMATIVE:** String-named tokens are schema-valid. Validators **MUST** accept them without a structural error.
+
+**NORMATIVE:** String-named tokens **MUST** trigger rule SPEC-017 (severity: `warning`, category: `tech-debt`). The warning surfaces the token as tracked debt requiring future remediation.
+
+**NORMATIVE:** String-named tokens **MUST NOT** participate in name-object cascade dimension matching, specificity calculation, or registry vocabulary checks (SPEC-009 does not apply).
+
+**RECOMMENDED:** Authors **SHOULD** treat string names as a temporary escape hatch and track a remediation plan. Each string-named token **SHOULD** eventually be given a structured name object, at which point SPEC-017 no longer fires.
+
 ### Name object
 
 The **name object** identifies the token in a structured way. Implementations use it for cascade matching, specificity, and tooling.
@@ -149,6 +169,55 @@ Example:
 
 Individual types (color, dimension, opacity, etc.) **MUST** be defined as JSON Schemas under `schemas/value-types/` and **MUST** use `$id` under the same `v0` base path as [Overview — JSON Schema `$id`](index.md).
 
+### Value-type declaration (`$valueType`)
+
+A token **MAY** include a `$valueType` field: a URI reference pointing to a value-type schema under `schemas/value-types/`.
+
+```json
+{
+  "name": { "property": "typography-scale", "scale": "desktop" },
+  "$valueType": "value-types/typography-scale.schema.json",
+  "value": { "fontSize": "14px", "lineHeight": "18px" },
+  "uuid": "377145e8-079b-43fd-b522-8f16b1b8f883"
+}
+```
+
+**NORMATIVE:** When `$valueType` is present on a token with a literal `value`, the value **MUST** validate against the referenced schema (rule SPEC-016).
+
+**NORMATIVE:** When `$valueType` is present on an alias token (`$ref`), the alias resolution chain **MUST** terminate at a token whose value validates against the same value-type schema (rule SPEC-002, extended).
+
+**RECOMMENDED:** All tokens with composite values (see below) **SHOULD** include `$valueType` to enable tooling discovery and validation. Tokens without `$valueType` remain valid under the permissive `anyOf` union in `token.schema.json`.
+
+### Composite value types
+
+A **composite value type** is a value-type schema whose root type is `object` or `array`. Composite values bundle multiple sub-values into a single token.
+
+**NORMATIVE:** Composite value types **MUST** be defined as JSON Schemas under `schemas/value-types/` following the same conventions as primitive value types.
+
+**NORMATIVE:** A composite token participates in cascade resolution as an **atomic unit**. Sub-values within a composite **MUST NOT** independently match, override, or participate in specificity calculation.
+
+### Inline alias references
+
+Within a composite value, a string sub-value **MAY** be an **inline alias**: a reference to another token that is resolved to produce the final sub-value.
+
+```json
+{
+  "name": { "property": "component-m-regular" },
+  "$valueType": "value-types/typography.schema.json",
+  "value": {
+    "fontFamily": "{sans-serif-font-family}",
+    "fontSize": "{font-size-100}",
+    "fontWeight": "{regular-font-weight}",
+    "letterSpacing": "{letter-spacing}",
+    "lineHeight": "{line-height-font-size-100}"
+  }
+}
+```
+
+**NORMATIVE:** In legacy format, inline aliases use the syntax `{token-name}` (curly-brace-wrapped token property name). In cascade format, the inline alias syntax is `{token-name}` for backward compatibility; UUID-based inline aliases are reserved for a future spec version.
+
+**NORMATIVE:** Inline aliases within composite values are subject to alias resolution rules. Validators **MUST** resolve inline aliases and report errors for missing targets (SPEC-014), type mismatches (SPEC-015), and circular references (SPEC-003, extended).
+
 ## Relationship to legacy Spectrum tokens
 
 The current `@adobe/spectrum-tokens` JSON uses **sets** (`color-set`, `scale-set`, …). This specification describes the **target** per-token model. Mapping from legacy to this format is out of scope for this document; see [#743](https://github.com/adobe/spectrum-design-data/issues/743).