On Monday, November 8, 2004, at 04:29 PM, Antone Roundy wrote:
On Monday, November 8, 2004, at 02:56 PM, Tim Bray wrote:Okay, I'm slow, but I'm catching the vision of why it would be good to have a standard way of recognizing that a category specifier specifies not only the end node in the hierarchy, but the path to it. Perhaps we could say that if @domain is not specified, some particular character (whether it be / or | or something else) MUST NOT be used except as a hierarchical level separator, and if @domain is specified...it SHOULD NOT? Or would it be useful to do something like this:On Nov 8, 2004, at 12:57 PM, Antone Roundy wrote:How about if @domain is omitted, then categories should be slash-separated...but if @domain is specified, then use that domain's way of indicating categories?-1 to any MUSTs for how categories are to be expressed ("slash-separated hierarchical"...).
-0.9 to any SHOULDs on how categories are to be expressed.
I think the this/that/the-other usage is well-enough established now to qualify as prior art. Anyhow, if you want to have your own not-hierarchical categorization scheme, you can, just keep it in your own namespace. You can even put it inside atom:category. -Tim
<category domain="foo:bar" hierarchy-separator="*">Technology*Computers*Internet</category>
where, if @domain is not specified, @hierarchy-separator defaults to "/", and if @domain is specified, @hierarchy-separator defaults to undefined.
