2006/5/23, Nicolas Krebs <[EMAIL PROTECTED]>:
Could you explain if there is a standardized way to fin the uri of the category,
There isn't.
an give piece of information about mandatory feature of sheme and term ?
There isn't either.
Is concatenation(shme, term) a wrong/good/allowed/mandatory method ?
wrong (because not aknowledged by the spec), allowed (because not explicitly forbidden).
If it is a forbiden method, will you add an atom:href or atom:uri attribute to the atom:category element ?
I'm not aware of any plan to do so. However, you might want to make up an extension. In this case, try to avoid using foreign attributes on the atom:category element or you'll run into the same problems James in fighting wrt his Fead Thread Extension [1]. The problem is that, as atom:category isn't listed in section 6.4 as containing Metadata Elements, there's no explicit request for processors to surface any extension to atom:category in their model representation, so they might just be discarded. IMO, the Simplest Thing That Could Possibily Work is to define a new link relation, say "category", and use atom:link elements to link to "category-related" resources. The drawback is that those atom:link elements won't be associated in any way to the atom:category elements, so aggregators/readers won't be able, for example, to list categories with links on the one where an "href" is provided, all they could do then is to list categories extracted from the atom:category elements and list "category links" extracted from the atom:link elements with rel="category", as two completely distinct sets. So finally, maybe a attribute or child-element -based extension might be better... On the rationale side, I suspect you want to link to an HTML page listing entries associated with the given category? First, I think this is a too specific case for a "generic" @href. I also don't see the need for it: those "category HTML pages" would generally be available from the HTML representation fo the entry (which I suspect would also exist), so they're only two clicks away. What _could_ be useful eventually would be a link to a *feed* containing entries associated with the given category, and in that case I think an atom:link with a new "category" relation would be enough. But even then I suspect "category feeds" to be not so common or not so commonly used (I'm personnaly not subscribed to any "category feed" and I don't even think sites I'm subscribed to provide "category feeds"; I'd like XML.com to provide an "articles only" feed instead of their "articles and blogs" feed, but that's not a matter of categories –"columns" are a category for articles, and blog posts have their own categories–). In conclusion: YAGNI. [1] http://www.ietf.org/internet-drafts/draft-snell-atompub-feed-thread-10.txt -- Thomas Broyer
