Re: app:accept and Atom entry MIME type

[Al Brown <albertcbrown@xxxxxxxxxx>]

>However this will not work well for CMIS as CMIS puts all of the backing
>stores repository into a single container element. So if we want PATCH
>to be able to manipulate individual properties, a different media type
>will be needed anyway. (*)

Since we are on the atom list, are there app clients where

<foo>foo1</foo>
<bar>bar2</bar>

is better (e.g., the client can display it in a way that makes sense to the end user and the user can update the values) than

<cmis>
<foo>foo1</foo>
<bar>bar2</bar>
</cmis>

inside an atom:entry?  Also if there are app clients that can update non-atom/app elements, I'd like to know so I can understand them better.

Best,
-Al

Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home

Office 714 327 3453
Mobile 714 263 6441
Email albertcbrown@xxxxxxxxxx
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.

Julian Reschke ---05/19/2009 02:39:07 AM---Al Brown wrote:

From:	Julian Reschke <julian.reschke@xxxxxx>
To:	Al Brown/Costa Mesa/IBM@IBMUS
Cc:	Peter Keane <pkeane@xxxxxxxxxxxxxxx>, atom-protocol Protocol <atom-protocol@xxxxxxx>, Nikunj Mehta <nikunj.mehta@xxxxxxxxxx>, pjkeane@xxxxxxxxx, Ryan McVeigh <ryan.mcveigh@xxxxxxxxxx>
Date:	05/19/2009 02:39 AM
Subject:	Re: app:accept and Atom entry MIME type

---

Al Brown wrote:
> I believe it is more about extensions to atom. How should a group that 
> builds on top of atom using atom extensibility advertise that it can 
> accept generic atom and/or atom+it's extensions in addition to other 
> potential media types?
> 
> In app, this is all done by media types. Both vanilla atom + atom with 
> extensions have the same media type which cause problems.
> 
> I am not sure leveraging categories as the signaling mechanism fits.
> 
> -Al
> ...

I think the issue of the media type used for Atom entries containing 
CMIS extensions will come up soonish again when we try to define the 
payload format for PATCH:

The naive approach would be to state: update elements specified in the 
application/atom+xml request body, leave the others unchanged.

However this will not work well for CMIS as CMIS puts all of the backing 
stores repository into a single container element. So if we want PATCH 
to be able to manipulate individual properties, a different media type 
will be needed anyway. (*)

BR, Julian

(*) Or properties will need to be modeled differently inside Atom entries.