- From: Florian Rivoal <florian@rivoal.net>
- Date: Thu, 4 Jun 2015 21:29:25 +0200
- To: Greg Whitworth <gwhit@microsoft.com>
- Cc: Tantek Çelik <tantek@cs.stanford.edu>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, www-style list <www-style@w3.org>, Rossen Atanassov <Rossen.Atanassov@microsoft.com>
> On 04 Jun 2015, at 21:09, Greg Whitworth <gwhit@microsoft.com> wrote: > >> I am then asking Microsoft to provide the WG with authoritative and >> stable URLs containing specification of cur and ico formats we could >> use as informative reference. If there are no such documents, create >> them? > > I just wanted to follow up here with where we stand on this. We worked with our legal team, and while we haven't found any blockers in principle, in practice we don't have one document that _completely_ specifies .ico and .cur. Based on that there are complications with how to say something definitive about licensing. Thanks for the update, I really appreciate the effort that went into researching this. It's unfortunate that there's not simple answer to the question, but given the age of these formats, it is also not surprising that they're a bit hairy. > Since we don't have any motivation for investing in writing a normative spec we suggest leaving this as a note. We can definitely do that. I do think it would be nice to have a normative spec, and that it would be beneficial to Microsoft as well, as it would reduce the incentives for people to try to move to a different format. But this isn't up to me, so if you'd rather leave it as a note, a note it shall be, and we're going to CR with it in a couple of weeks. If you change your mind, we can always change this in level 4. Thanks, - Florian
Received on Thursday, 4 June 2015 19:29:45 UTC