[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AtomPub Multipart Open Issues



On Thu, Jul 3, 2008 at 11:41 AM, Sylvain Hellegouarch wrote:
>
> I see your point. I think the multipart="..." attribute is just a way for
> a AtomPub service to advertise it supports a given extension that
> describes how the MIME subtype would be handled.
>
> In other words multipart="form-data" would just be a way of saying "I
> support ID XXXX" assuming the AtomPub community has created an ID
> describing how form-data could be handled.
>
> For instance multipart="related" would thus mean "I support
> multipart/related as describe in ID (defined by Joe)".
>
> In case of multipart="form-data", an ID could then introduce a new
> attribute to handle the specifics of that subtype, e.g.
> form-data-field="name" (I'm just making a gross example here).
>
> Obviously there is a problem when more than one ID exist for a given
> subtype because that attribute mechanism doesn't offer a way to
> differentiate them.
>
> Somehow we are back to the problem the WG had tried to tackle a few months
> ago regarding "the formal way to advertise support for a given feature".

<app:accept>multipart/related;type=application/atom+xml;start-info=draft-gregorio-atompub-multipart</app:accept>

or simply

<app:accept>multipart/related;start-info=draft-gregorio-atompub-multipart</app:accept>

?

;-)

-- 
Thomas Broyer