As someone who uses a similar system for some of my own tags, and has seen it
all over certain communities, the downsides to "foo: bar" are as follows:
1. When entering tags manually, it means instead of typing, say, "robert
redford" and having it come up as an autofill after getting to "rob", you have
to type "actor: rob" or "producer: rob" or "director: rob" to get the same
result. And if it's someone who comes up under multiple categories, you have to
rinse and repeat every time.
2. It can be anti-intuitive for people looking through a large set of tags to
look for "foo" first rather than just looking for "bar".
------------------------
I'm guessing that the intent of adding nested/hierarchical tags support to the
coding would be to let people add the "foo" part as an attribute to "bar", so
you could have a tags list that has headers for each given section, and repeats
"bar" underneath each of the categories to which it belongs? So, for instance,
you could just enter "robert redford" as a tag, and if you didn't indicate
otherwise it would just add him to all of the categories to which the journal
owner has assigned him?
The one element I'm not quite sure of is how you'd implement being able to
select only certain parent categories for a particular tag. For instance, if
you were talking about a movie Robert Redford directed but didn't act in, you
might want to only have that particular entry show up under "director: robert
redford" rather than all of the categories to which he could belong. Would this
be something that would show up as a drop-down when you enter a tag?
Thanks,
principia_coh
Alexis Carpenter
----- Kirrily Robert wrote:
| What are the downsides to "foo: bar"?
|
| K.
|
| --
| Kirrily Robert
| [email protected]
| http://infotrope.net
_______________________________________________
dw-discuss mailing list
[email protected]
http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
