- From: Mark Jones <jones@research.att.com>
- Date: Fri, 21 Feb 2003 13:28:46 -0500 (EST)
- To: xml-dist-app@w3.org
In a 2003/02/21 telcon, the AFTF (Jeff Schlimmer, Noah Mendelsohn, Marc Hadley, Anish Karmarkar, Mark Jones, Martin Gudgin) discussed the remaining requirement DR28, having to do with manifest functionality: DR28. The specification may provide manifest functionality. The consensus on DR28 was that manifest functionality seemed to be precisely the type of thing that headers should be used for. There also are other requirements for message and part metadata (R21, R31, R22) that could provide the basis for doing a manifest outside of the envelope if necessary. The importance of having a normative means for expressing manifests was also noted, however. The task force recommends that the WG should encourage anyone interested in pursuing the collection of use cases and detailed requirements for such a specification to do so as an adjunct to the attachments specification. As a result, we have removed DR28 from our explicit requirements list, but will somehow note its relevance/importance in the requirements document. --mark Mark A. Jones AT&T Labs -- Strategic Standards Division Shannon Laboratory Room 2A02 180 Park Ave. Florham Park, NJ 07932-0971 email: jones@research.att.com phone: (973) 360-8326 fax: (973) 236-6453
Received on Friday, 21 February 2003 13:29:17 UTC