W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2003

some initial attachment requirements

From: Mark Jones <jones@research.att.com>
Date: Fri, 3 Jan 2003 15:52:57 -0500 (EST)
Message-Id: <200301032052.PAA05685@bual.research.att.com>
To: xml-dist-app@w3.org

Here's a stab at some initial requirements for the concrete attachment
spec(s).  These are far from comprehensive I'm sure and may need some
tweaking, but hopefully it will get us going.

--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

================================================================

SOAP Attachment Specification Requirements

Representation

1. The specification must define a means to carry multiple data parts.

2. The specification must define a means for parts to carry
   arbitrary data, including non-XML data (e.g., binary data and XML
   fragments).

3. The specification must admit a reasonably time-efficient
   means of identifying parts.

4. The specification must use a reasonably space-efficient
   representation.

5. The representation must efficiently support the addition and
   deletion of parts.


Reference to Parts

6. The specification must permit parts to be identified by URIs.

7. The URI identification scheme must be robust under the addition and
   deletion of parts -- i.e., it must not require that URIs to other
   parts be altered, it must be relatively easy to avoid URI
   conflicts, etc.
Received on Friday, 3 January 2003 15:53:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:13 GMT