Quoting Joe Gregorio <[EMAIL PROTECTED]>: > > On Mon, 08 Nov 2004 11:28:18 -0800, Tim Bray <[EMAIL PROTECTED]> wrote: > > > > Somehow, we don't seem to have any category element in the > > format-draft. Huh? It's in RSS2 and it's widely deployed, although it > > hasn't been all that useful. Also I note that the protocol design team > > is worrying about querying and defining categories. I don't see > > anything wrong with RSS2's category element, so I've proposed something > > along the same lines: > > http://www.intertwingly.net/wiki/pie/PaceCategoryElement -Tim > > Looks good. > > I think allowing multiple atom:category elements > *and* allowing the textual content of the element to be a "/" separated > multi-part string is a bit too much. I think we should pick one or the > other mechanism, not both.
I read the textual content part as that would be the specific category an item was posted to, not that the / would separate the categories. Example: <category>/music/NIN/</category> Meaning this item was posted into the specific NIN category. Is this your thinking Tim? > > If we do go with a separated list, I would prefer a white space separated > list > as opposed to "/". I will point to the HTML link elements @rel > attribute as prior art. What about the following? <category>Nine Inch Nails</category> You'd want, <category>Nine+Inch+Nails</category>? > > What value of @domain should be used if a pre-existing classification > scheme is not used? Should this be an optional attribute as with RSS 2.0? > > Should we mimic the dublin core definition of 'subject' which says: > "Recommended best practice is to select a value from > a controlled vocabulary or formal classification scheme." > > > > Thanks, > -joe > > -- > Joe Gregorio http://bitworking.org > >
