- From: Thomas Roessler <tlr@w3.org>
- Date: Thu, 22 Jan 2009 14:26:37 +0100
- To: mzurko@us.ibm.com
- Cc: public-usable-authentication@w3.org, timeless@gmail.com
Since I was channeling timeless here, I'll ask him to respond. -- Thomas Roessler, W3C <tlr@w3.org> On 22 Jan 2009, at 14:18, mzurko@us.ibm.com wrote: > > Dear Thomas Roessler , > > The Web Security Context Working Group has reviewed the comments you > sent > [1] on the Last Call Working Draft [2] of the Web Security Context: > User > Interface Guidelines published on 24 Jul 2008. Thank you for having > taken > the time to review the document and to send us comments! > > The Working Group's response to your comment is included below. > > Please review it carefully and let us know by email at > public-usable-authentication@w3.org if you agree with it or not > before 29 > January 2009. In case of disagreement, you are requested to provide a > specific solution for or a path to a consensus with the Working > Group. If > such a consensus cannot be achieved, you will be given the > opportunity to > raise a formal objection which will then be reviewed by the Director > during the transition of this document to the next stage in the W3C > Recommendation Track. > > Thanks, > > For the Web Security Context Working Group, > Thomas Roessler > W3C Staff Contact > > 1. > http://www.w3.org/mid/20080806163050.GX4194@iCoaster.does-not- > exist.org > 2. http://www.w3.org/TR/2008/WD-wsc-ui-20080724/ > > > ===== > > Your comment on 6.1.2 Identity Signal Content: >>> Subject logotypes derived from certificates SHOULD NOT be >> rendered, unless the certificate used is an augmented assurance >> certificate. >> >> why is this a should not instead of a must not? > > > Working Group Resolution (LC-2087): > Thank you. While we have discussed this, and decided on MUST NOT. > > ---- > >
Received on Thursday, 22 January 2009 13:26:48 UTC