On 5/24/06, Tim Bray <[EMAIL PROTECTED]> wrote:
<co-chair-mode>
As we see it, there are really only 1.5 issues outstanding. Media
entries is obvious. I had an action item to make PaceMediaEntries
more human-readable; thus, check out http://www.intertwingly.net/wiki/
pie/PaceMediaEntries5
There's been a lot of discussion of the iterations of this Pace, and
a lot of it was of the form "sort of OK, but I'm uncomfortable with
XXX". So before we do the last-chance +/- survey, we'd like one
last call for amendments, improvements to the Pace that might move
people from negative to positive.
+1 to PaceMediaEntries5
Second: Categories. As of now, the draft is silent on the subject,
which your co-chairs think is questionable, and we want the WG to do
some more work.
...
Or, is the WG OK with explicitly giving up? http://
www.intertwingly.net/wiki/pie/PaceNoCategoryManagementInCore
That Pace proposes giving up on category management, not category listing.
While APP is most definitely useful without categories, leaving out
category listing will slow adoption by blog server and client
developers because categories are an important part of blogging --
MetaWeblog API has them and APP does not.
So, it's time for the WG to settle this. Reasonable positions to
support might be:
- give up
- something like PaceCategoryLink
- something else
I thought PaceCategoryList was pretty good and PaceCategoryList2 was
complete. Byron Reese of SixApart seemed to like it too. It had the
things I think Roller needs:
* Fixed categories and unfixed categoes (i.e. tags)
* Possibility of multiple categories schemes at service, workspace and
collection level
* In-line and out-of-line specification of comments
* And it's possible to represent hierarchical categories (as Byron
Reese explained)
Which parts of the PaceCategoryListing proposal were incomplete? What
needs to be done to complete it?
- Dave
