Re: PaceCollectionControl

[Bill de hÓra <bill@xxxxxxxxxx>]

Joe Gregorio wrote:
> http://www.intertwingly.net/wiki/pie/PaceCollectionControl
> 1. Control information MUST be sent with the initial POST to create an
> entry.  (otherwise creating a draft is a two step process.)
> 2. Control information MUST be sent with the initial POST to create
> anon-entry member.
> 3. Non-entry collections MUST support control data.
> 3. Control information MUST be able to be set separately from updating
> 4. Control information MUST be extensible.
> 5. Control information MUST be in an XML document.
> 6. Control information MUST be contained inside the entry document.

[7 items not 6]

0 from me. My two observations are

- making this control code extensible has ramifications - technically it
means I have to keep adding if elses to my code or populating lookup
tables with new action for dispatch. Politically it means interested
parties can extend it in a way that is not platform neutral.

- it is not clear to me whether pub:control will enable the containment
of conflicting directives or whether directives must/may co-occur or be
must/may be mutually exclusive. If any ofthose are the case, without any
processing model to guide the interaction of extensions, it means
garbage can be sent to the server - in that case what the error handling
mechanism might be is undefined. namespaces != extensibility in this case.

I appreciate these concerns might appear academic or overly paranoid,
(hence I'm 0). If someone needs an example for clarification, I'll try
to provide it.

cheers
Bill