Re: AtomPub Multipart Open Issues

[Aristotle Pagaltzis <pagaltzis@xxxxxx>]

* Thomas Broyer <t.broyer@xxxxxxxxx> [2008-07-02 17:15]:
> And it won't work also because "form-data" isn't specific
> enough: which "fields"? how are they named? (or maybe there
> should only be one non-file field, containing an Atom Entry,
> and referencing the attached resources using their file-name:
> <content src="EntryContent.html" />)

The specification that defines a meaning for the `form-data`
value could easily prescribe additional extension elements or
attributes to carry that extra information.

It’s just that if the `multipart` attribute on `app:accept` is
a reasonable hook for advertising support in another future
multipart mechanism, avoiding boolean markup means that that
future mechanism can piggy-back on the same extension point, so
that we can hopefully avoid a proliferation of ways to advertise
support for multipart mechanisms that share a similar model.

I think this is what you meant here:

> But if you're only talking about the attribute's "style", then
> OK (see last line of this mail); you'd have to define it as
> NTOKENS though to allow things like multipart="alternative
> x-CompoundEntry"

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>