[community-group] Conflicting language in "References and JSON Pointer Integration" (#383)

mindplay-dk has just created a new issue for https://github.com/design-tokens/community-group:

== Conflicting language in "References and JSON Pointer Integration" ==
I noticed some conflicting language in the "References and JSON Pointer Integration" part of the spec.

"tools **MAY** also support JSON Pointer notation"

https://github.com/design-tokens/community-group/blob/21dac16da36e70abf8b55d92c985dc8816f21ea1/technical-reports/format/groups.md?plain=1#L511

"Tools **MUST** support JSON Pointer references"

https://github.com/design-tokens/community-group/blob/21dac16da36e70abf8b55d92c985dc8816f21ea1/technical-reports/format/groups.md?plain=1#L534

In addition, the spec says the `{group.token}` syntax is "**maintained for backward compatibility**"

https://github.com/design-tokens/community-group/blob/21dac16da36e70abf8b55d92c985dc8816f21ea1/technical-reports/format/groups.md?plain=1#L511

Yet, the `{group.token}` syntax is defined under the title "**Current** Reference Syntax (**Recommended**)"

https://github.com/design-tokens/community-group/blob/21dac16da36e70abf8b55d92c985dc8816f21ea1/technical-reports/format/groups.md?plain=1#L513

Has the working group decided on a syntax?

Personally, I prefer the simpler syntax, which is immediately easy to parse and implement - whereas JSON pointers require a library.

JSON pointers would let you write valid expressions that reference array elements - is that useful or does it create problems?

JSON pointers would also let you reference reserved schema elements like `$type` and `$name` - is that a "by design" feature or by accident?

Does simpler syntax lack anything, or why were JSON pointers added with a "MUST" requirement?


Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/383 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 16 January 2026 12:27:14 UTC