- From: Dr. Dirk Schnelle-Walka <dirk.schnelle@jvoicexml.org>
- Date: Mon, 11 Jun 2012 10:13:37 +0200
- To: Deborah Dahl <dahl@conversational-technologies.com>
- Cc: www-multimodal@w3.org
Hey Debbie, I am not sure if this really removes my problems with the interpretation of the specification. Although it is considered to be at risk of removal, the specification should be clear about the intention. Maybe, you should add that the implementation is application specific. I really miss that in the specification. Also, I am not sure if all those possible behaviors (I mentioned some possible interpretations in my first email) can be toggled by a simple switch. Especially, if you want to support more than one of those behaviors at the same time. >From that point of view this solution is not acceptable, sorry. Maybe, adding that hint that the interpretation of the confidential is application specific and further hints can be submitted in the data field could help to overcome this weakness. As a consequence the hint about logging should be removed since this is only one possible interpretation. Maybe, it could still serve as an example? Best, Dirk > Hi Dirk, > We've discussed your question about the confidential flag in the Working > Group. Our intention was that the exact interpretation of the confidential > flag would be implementation-specific. However, it's also worth pointing out > that this feature was called out as "at risk" in the Candidate > Recommendation spec, due to a potential lack of implementations. If we don't > get two implementations of this feature it will be removed from the spec. > Since we are tracking all comment threads at this point, please let us know > by June 15 if this resolution is acceptable, otherwise we will assume that > you agree with our decision (but it is very helpful to have an explicit > response). > Best regards, > Debbie Dahl, MMI WG Chair > >
Received on Monday, 11 June 2012 08:14:01 UTC