W3C home > Mailing lists > Public > public-design-tokens-log@w3.org > March 2020

Re: [community-group] [RFC] Format specification (#1)

From: Dale Sande / @anotheruiguy via GitHub <@anotheruiguy>
Date: Tue, 03 Mar 2020 01:04:50 +0000
To: public-design-tokens-log@w3.org
Message-ID: <issue_comment.created-593712479-1583197488-sysbot+gh@w3.org>
@mirisuzanne 100% agree. That is one of the reasons I raised the question as to what thought has been put into defining the media type. Without that, talking about 'features' seems foolhardy IMHO as there is no real way to have that discussion. 

I like what you are saying that this is simply not data, but it's data with type structure. Data will have implicit meaning. This also means that tooling that is required today will not be needed as this spec is adopted. Data sent in the `.tokn` file can be directly consumed by the browser and applied to the CSSOM. I like that. 

I don't think we can do something like  `text/token+css` unless the tokens are written using the CSS spec. At least that is how I understand it. 

We could be looking at proposing `application/css` ... whereas we would not be restricted by the CSS spec, but that will be a really huge uphill road. 

Sorry ... ideating out loud. But in the end, I see `application/token+json` being the best option. 

GitHub Notification of comment by blackfalcon
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-593712479 using your GitHub account
Received on Tuesday, 3 March 2020 01:05:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 3 March 2020 01:05:08 UTC