On 22/10/05 9:28 AM, "Eric Scheid" <[EMAIL PROTECTED]> wrote:
>> I like James' Blog Publishing Control draft, too. Why do we need to
>> wrap these in pub:control?
>
> How do you propose signalling that a particular piece of control meta data
> should be stripped before publishing?
I was thinking for a bit that stripping can be done by the publisher on the
basis that they would know what would be control because they would be the
one that would handle it ... but then I thought of client side control meta
data.
Some examples of client side control meta data might be
<pub:control>
<x:editorial-notes>
I really need to do some fact checking on this.
Must get around to writing a more concise summary
Here are some more private editorial notes.
</x:editorial-notes>
<y:window-state>
<y:top>50</height>
<y:left>20</height>
<y:height>500</height>
<y:width>200</height>
<y:summary-open>true</y:summary-open>
<y:content-open>false</y:content-open>
</y:window-state>
</pub:control>
My custom built APP CMS might understand those, but 6A won't, nor will
Blogger.
Why store editorial notes and window size gunk in the entry, and not in some
locally stored data file? Because I like using a web based editor from
multiple computers.
Why not just have the client strip this stuff before publishing? Because
there will be some client side stuff I'll want to be able to see via APP
even after publishing. An editorial change history, for example.
e.
