There's a lot of very specific performance improvement requirements to creating daicon files in a way that works well with CDNs. Currently these are written out in the core spec, but they should be moved out to their own file. This also allows these to be written as more clear "MUST/MAY" requirements, while specifying that readers should fall back to the core spec if any of those requirements aren't followed.
There's a lot of very specific performance improvement requirements to creating daicon files in a way that works well with CDNs. Currently these are written out in the core spec, but they should be moved out to their own file. This also allows these to be written as more clear "MUST/MAY" requirements, while specifying that readers should fall back to the core spec if any of those requirements aren't followed.