Re: [community-group] Proposal: JSON Schema $ref for aliases (breaking change) (#259)

> > This is true. The spec is not final, so any current downstream consumers are using it at their own risk. Breaking changes are to be expected, and we cannot (should not!) let the existence of early adopters hobble development of the spec.
> 
> The people who adopted DTCG are the people who are contributing here and who are making it possible to have feedback and understand the edge cases that the format will need to support in v1. It's a long-winded journey.
> 
> Whilst indeed the spec is not final and breaking changes may happen, to say that the people who are using it, providing feedback, and contributing here are not "legitimate" users feels dismissive of their own efforts.
> 

@Sidnioulz Thank you for taking the time to respond - I want to sincerely apologise if my choice of words came off as dismissive. That was most definitely not my intent. I have the utmost respect for the work everyone here is putting into this. 

On reflection, I think I have probably come to this group with the wrong attitude - I am here because I needed a standard, then I found that standard limiting in frustrating ways - so perhaps that frustration clouded my words. I apologise for expressing that frustration in a dismissive way.

My concern was not meant to diminish the effort or legitimacy of the adopters or contributors - 'legitimate' was a poorly chosen word. I completely agree that early adopters and feedback is invaluable. I would consider myself in this group.

-- 
GitHub Notification of comment by brettdorrans
Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/259#issuecomment-3291996419 using your GitHub account


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

Received on Monday, 15 September 2025 12:44:03 UTC