On Nov 8, 2004, at 11:59 AM, Joe Gregorio wrote:
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.
Consider the categories in http://www.tbray.org/ongoing/When/200x/2004/11/06/WearingFast - I think it has two categories, each of which has a /-separated "pathname".
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.
Hmm, I don't care that much about the syntax, but check my example again, some of the category names have white space in them.
What value of @domain should be used if a pre-existing classification scheme is not used?
domain= is not required. In my own case, I'd make up a value in www.tbray.org/ongoing/
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."
I can go for that. -Tim
