On 10/29/05, James M Snell <[EMAIL PROTECTED]> wrote:
>
> Luke Arno wrote:
>
> >If we really need them then maybe we need a box.
> >I don't think we need any directives, atm.
> >
> The challenge with this statement is that existing implementations are
> already using these kinds of directives.
>

Like what? (I am sincere here. No snark.)

[ snip ]

> >I would guess that all but the simplest 20 percent of
> >distributed applications built on APP will need such a
> >box so it makes a very good extension.
> >
> If all but the simplest 20 percent need it, then it's also a good
> candidate for an optional core element as well.
>

I meant 20 percent of the implementations that are
more distributed-applicationy (have more involved
processing model).

What percent of implementations is that? 20%, 50%...

80% of 20% is 16%
80% of 50% is 40%

[ snip ]

> The challenge with this is that our most common use cases (blogs, wikis,
> content management) aren't just pushing entries around; they have an
> already demonstrated need for this control stuff and are already
> starting to dump it into atom:entry (have been for some time now).  The
> argument about pub:control is: given that we know that controls elements
> will and are already being stuffed into atom:entries, does it do any
> good to provide a standard container for those to go into (regardless of
> whether that container is pub:control or atom:entry).  In so doing, do
> we help ward off any Bad JuJu Spirits implementors will face in the
> future.  If we don't provide a container and just let extensions figure
> it all out as they go, are we going to cause any significant problems
> down the road?  Telling folks to put their stuff in a box doesn't seem
> to help if everyone puts their own stuff into their own individual boxes.
>

How many processing instructions is the average
implementation using in an atom entry?
(approximately)

What are they?

Do we have a list somewhere of these?

If not, do we need a wiki page where everyone can list
the PIs for their implementations?

How many of those make sense in terms of the APP
way of doing things?

What constitutes a sufficiently extensive processing
model to call for a box? 3 instructions? 5? ...

Sorry for all the questions. :)

- Luke

Reply via email to