- From: Matthew Ström via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Dec 2023 18:29:55 +0000
- To: public-design-tokens-log@w3.org
I think this could actually be as simple as having a `url` type which follows exactly the [whatwg standard](https://url.spec.whatwg.org/). Urls can be relative paths, which would be combined with a base path (which might be a file path for local files) by the parser. We can provide a standard (like [RFC 3986](https://www.rfc-editor.org/rfc/rfc3986) for resolving relative paths. As for the security of URLs, I think we get into trouble when we start talking about a translator actually fetching something on the url. The original comment's author mentioned wanting a token translator to combine svgs into a sprite sheet or generate a font file; to me this seems like a job for another tool, not a token translator. -- GitHub Notification of comment by ilikescience Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/132#issuecomment-1863282832 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 December 2023 18:29:57 UTC