- From: Chris Lilley <chris@w3.org>
- Date: Thu, 4 Jun 2015 21:58:30 +0200
- To: Greg Whitworth <gwhit@microsoft.com>, Tantek Çelik <tantek@cs.stanford.edu>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>
- CC: www-style list <www-style@w3.org>, Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Hello Greg, Thursday, June 4, 2015, 9:09:07 PM, you 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, Good to know. > in practice we don't have one document that > _completely_ specifies .ico and .cur. Are there several documents that collectively specify it? Do those documents specify a bunch of other stuff as well? > Based on that there are > complications with how to say something definitive about licensing. If the answer to my second question is "yes", licensing could be simplified by extracting out just the parts that relate to cur and ico. > Since we don't have any motivation for investing in writing a > normative spec we suggest leaving this as a note. You mean publishing it as a note? Another option is to extract out the parts relate to cur and ico into one or more documents and make them a W3C Member Submission. I can guide you through that. It avoids having to expend effort on taking it through the standards track, but at the same time allows the format to be documented at a referenceable location and for Microsoft to make an RF license commitment. In turn that allows css3-ui to informatively reference it and helps implementers (especially on non-Microsoft platforms where there is no native support). -- Best regards, Chris Lilley Technical Director, W3C Interaction Domain
Received on Thursday, 4 June 2015 19:58:34 UTC