[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AtomPub Multipart Open Issues
- To: "Atom Protocol" <atom-protocol@xxxxxxx>
- Subject: AtomPub Multipart Open Issues
- From: "Joe Gregorio" <joe@xxxxxxxxxxxxxx>
- Date: Tue, 1 Jul 2008 15:20:59 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=BfzAmvQ/+1028UcZR/sG7VRulrESjOQysuC+l0LLhQk=; b=Zd7mL6/dbFxDU64K7jaJhcb6ga/6vshMBT4OEfp1wPX75tM0NFfyMkd3fabwuuPAlR frLNbMU2XMzsAqZE80LQhiVfC5CNKZdq2NSIYn+6VqSzuXiDl5GD0NwWbnbtIbRV1GW7 z6uG6zdvV0f/DGdhEJ0n7sNbIGNcbw5QX0agE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=i01NqcFpeEbIyzwlOWUwk7TtUaZIUfQJlIJAtk03bfDgqRjpZag5jwaB23Su3hXecu r9tyT1H5D7mhRT7ZIQYH6YLZwfJFy45/BNCkYVHsGHPqb25L55zG76KvNlvGh1/CNvTm Wf/Ffowvk6SsO1DM8c+SViQe2WLxhC0hwGRAo=
- List-archive: <http://www.imc.org/atom-protocol/mail-archive/>
- List-id: <atom-protocol.imc.org>
- List-unsubscribe: <mailto:atom-protocol-request@imc.org?body=unsubscribe>
- Sender: owner-atom-protocol@xxxxxxxxxxxx
>From the discussion so far I see the following issues that are as yet
unchanged in the spec and I believe need to be resolved:
1. The format should use multipart/related ordering and the MLE MUST
be the root part.
2. The MLE MUST be constructed with an atom:content/src="cid:..." and
that cid: URI MUST point to the included media.
2.1. A normative reference to cid: URI spec needs to be added.
3. Change multipart="yes" to be a non-boolean indicator, such
as post-options="multipart".
Presuming I haven't missed anything, I will come back
in a bit with camera ready copy proposals.
With respect to the issue of this specification 'using up' the multipart/related
media type, I believe that if later specifications come along that also
want to use multipart/related in a different manner then those follow-on
specifications can add a new parameter to the multipart/related media-type
to distinguish it from this specifications usage.
Thanks,
-joe
--
Joe Gregorio http://bitworking.org