Re: draft-ietf-atompub-protocol-11: How do I create a Media Entry from an Entry?

["Yogesh Mujumdar" <yogesh.mujumdar@xxxxxxxxx>]

As per the spec the client is free to post any mime type to the media collection. If it does not support the mime type, it may reject giving a 415 response code. So, if the server accepts the mime type application/atom+xml, it should not modify it as it should treat it purely as a media. The media link entry may get changed.

On 12/8/06, Lindsley Brett-ABL001 <Brett.Lindsley@xxxxxxxxxxxx> wrote:

The system I am designing needs to create a Media Entry from an Entry.
That is, I need to post an entry to a collection and have the collection
create a media entry (I do not want the entry to be added to the
collection as a member entry).

Section 9.5 of the spec clearly indicates that if a client posts a mime
type of application/atom+xml to a collection, a member entry is created.
If any other mime type is posted, a media resource and media link entry
is created. How do I post an entry and create a media resource/media
link entry? The issue I see with the spec is the post operation
semantics are mime-type dependent.

The reason I need to do this is the entry I have is signed, thus, I can
not add it as a member entry because the server may change the entry
(e.g. create it's own ID, etc.), which will break the signature.

The solution I have prototyped is:
- Posting an entry to the collection adds the entry to the collection as
a member. The server may have additional semantics such as changing the
ID, etc.
- Posting an entry (or any other mime type) to a link called
"edit-media" creates a media link entry regardless of mime type.

Brett Lindsley
Motorola Labs
Applications Research Center

-- 
regards/Yogesh