Re: [dxwg] Review implications of OPTIONS cacheability

I'm definitely not pushing OPTIONS as a way of listing profiles, so I'd be happy to remove that. It also means that there is one requirement less that implementers need to care about so it lowers the barrier...

And it should be mentioned that we rely on the blog post [NO OPTIONS](https://www.mnot.net/blog/2012/10/29/NO_OPTIONS) by Mark Nottingham here.

-- 
GitHub Notification of comment by larsgsvensson
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/510#issuecomment-434209296 using your GitHub account

Received on Tuesday, 30 October 2018 08:15:04 UTC