James M Snell wrote: > > > > Bill de hÓra wrote: > >>> PaceCategoryListing >> >> >> +0 only because I am unsure of the mechanism proposed, it looks bloated >> (I might come back with questions), but listing categories is valuable. >> > > > Bloated? It's one new element with three possible attributes. Could > you explain a bit more about what you don't like?
I think you have to consider the use of the element in the context of all the workspaces and collections and the number of categories that might be available. Has anyone who's pro this mechanism considered how the markup shapes up when you have 50, 100, or 500 such categories to hand, or what happens when they repeat across collections? For example, I'm a lightweight del.icio.us user (going by others use of it in some blogs I'm subscribed to) and I seem to have used 278 different categories on my links. I have about 50 in my weblog (I have no idea whether that's a few or lots). I should say I'm not sure if this pace is intended to scope categories to some level. How do I markup my 50 categories? It doesn't provide any explanation as to why you'd put categories where it says to put them or how a client can apply them (ie if there are implicit acquisition rules). Finally, it's not clear to me whether people won't go off and use collections to de facto map the categories - it's not like we're providing any guidance as to how to model the damn things. All that said, please note I'm +0, not -1. cheers Bill
