The tagging feature on Diigo is far less useful if we do not give some thought to an agreed ontology. This not to suggest that free tagging should be discouraged, but it's difficult to maximize the value of tagging when you can only sort by a particular tag without an ability to specify multiple tags in a boolean search.
What triggered this thought is that we now have three competing solutions for overlapping functionality presently being branded with at least three different tags. JavaFX, Silverlight, and Adobe Air. That's useful if you want to just get the information about one of those technologies at a time, but a system of classification might allow a view of bookmarks relating to all three, a timeline of the competition in this area of sorts.
So I think we need to begin brainstorming some more hierarchical tag names. Too bad we don't have RDF to work with here. :-)
E.g., what is an appropriate name for a tag that could encompass JavaFX, Silverlight, Adobe Air, and any competing technology?
Or should we bother tagging? Maybe the Diigo search facility is a more useful solution than its free-tagging facility.
What triggered this thought is that we now have three competing solutions for overlapping functionality presently being branded with at least three different tags. JavaFX, Silverlight, and Adobe Air. That's useful if you want to just get the information about one of those technologies at a time, but a system of classification might allow a view of bookmarks relating to all three, a timeline of the competition in this area of sorts.
So I think we need to begin brainstorming some more hierarchical tag names. Too bad we don't have RDF to work with here. :-)
E.g., what is an appropriate name for a tag that could encompass JavaFX, Silverlight, Adobe Air, and any competing technology?
Or should we bother tagging? Maybe the Diigo search facility is a more useful solution than its free-tagging facility.
Thoughts?
To Top