ACTION-139: Fix section 5 "supported messaging types" in Messaging API to clarify handling of non-supported attributes

Fix section 5 "supported messaging types" in Messaging API to clarify handling of non-supported attributes

State:
closed
Person:
Max Froumentin
Due on:
March 25, 2010
Created on:
March 18, 2010
Associated Product:
Messaging API
Related emails:
  1. Re: Agenda - Distributed Meeting 2010-06-16 (from jmorris@cdt.org on 2010-06-16)
  2. Agenda - Distributed Meeting 2010-06-16 (from Frederick.Hirsch@nokia.com on 2010-06-16)
  3. Re: Agenda - Distributed Meeting 2010-06-16 (from enewland@cdt.org on 2010-06-15)
  4. Draft minutes 2010-04-28 (from frederick.hirsch@nokia.com on 2010-04-28)
  5. Draft F2F Minutes Day 3, 2010-03-18 (from frederick.hirsch@nokia.com on 2010-03-18)

Related notes:

Presumably done, with:
“By support is meant that the implementation must be able to correctly per attribute type handle non-null attributes of this type. Thus, a message may have a non-null value in a attribute which is not supported in the message's type, but the user agent is free to disregard the attribute.”

Dominique Hazaël-Massieux, 2 Jun 2010, 15:31:52

Display change log.


Anssi Kostiainen <anssi.kostiainen@intel.com>, Reilly Grant <reillyg@google.com>, Chairs, Fuqiao Xue <xfq@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $