RE: Categories and fixed="yes"

[Joe Cheng <Joe.Cheng@xxxxxxxxxxxxx>]

> When you create a new category "Animals -> Cats", how do you know how to
> format the term attribute into "Animals/Dogs" and not "Animals -> Dogs"
> or somethng else?

It doesn't solve the problem of creating new categories, not without
explicit knowledge of the particulars of the scheme the server is using
(which you could do with features or extension attributes on <scheme>).
But at least it solves the problem for generic clients that don't know
the hierarchy exists. Users will not see the hierarchy but it will be
there implicitly (this is actually the case for all blog editing clients
working against WordPress today, except for WLW and possibly MarsEdit).

> And, similarly, how do you know that you should
> produce a tree by splitting at "/"? And, what about "Programming ->
> I/O"?

You would not be able to use the slash (or whatever string was chosen
as the delimiter) in that way. Sure, it's a limitation.

> > Still, I like the idea of preserving foreign attributes and
> > content for category elements.
>
> I think it is fair for a client to assume that it can include the
> foreign markup at its discretion; servers shouldn't put stuff in their
> that they don't accept, but they shouldn't expect to get anything more
> than the "term" and "scheme" attributes either.

In that case, if WP doesn't embed the whole path in the term and the
client doesn't preserve foreign markup, then it might be ambiguous
which category the client is trying to select. (This also is the case
for most blog editing clients today...)