SupportingTheCaseHello Wade,
thank you for taking the "case" seriously. The decision for supporting case is a strategic one.
Ad 1)
Not case-sensitive: Even if all other
DiigoAffiliatedBookmarkingServices would restrict their engines on not-case-sensitive, this would be not a serious problem to stick to
StrongCaseSensitivity You could transfer to them the
MixedCaseand leave them the decision, wether they apply a
"converttolowercasefunction", hampering the reading quality and
depriving them from a lot of fast analytical operations on tags.
Ad 2)
Case-sensitive for both display and search: If the underlying database respects case, then
"
IBM" (TM), the trademark of this computer-company and "
iBM", a possible rival product of IBM to the
iPodof the Apple (TM) company, are indeed different and need to be
respected as valuable tags. It is no problem to delete the
"converttolowercasefunction" somewhere in the
DiigoEngine.
You see not only communities of programmers will have an enormous gain, when using
CaseSensitiveTags, correctly handled by the
DiigoEngine.Ad 3)
Case-sensitive for display but not for search: Please don't put this unnecessary burdon (of editing tag appearances) on millions of Diigo users.
MayAllBeHappy
fridemarPS.: A simple realization for Diigo-, Trailfire and other social annotation services for
AutomaticTagging is given in the above text by manually making transforming all
WikiWords into
GoogleSearchLinks.SupportingTheCase
Hello Wade,
thank you for taking the "case" seriously. The decision for supporting case is a strategic one.
Ad 1) Not case-sensitive: Even if all other DiigoAffiliatedBookmarkingServices would restrict their engines on not-case-sensitive, this would be not a serious problem to stick to StrongCaseSensitivity You could transfer to them the MixedCase and leave them the decision, wether they apply a "converttolowercasefunction", hampering the reading quality and depriving them from a lot of fast analytical operations on tags.
Ad 2) Case-sensitive for both display and search: If the underlying database respects case, then
"IBM" (TM), the trademark of this computer-company and "iBM", a possible rival product of IBM to the iPod of the Apple (TM) company, are indeed different and need to be respected as valuable tags. It is no problem to delete the "converttolowercasefunction" somewhere in the DiigoEngine.
You see not only communities of programmers will have an enormous gain, when using CaseSensitiveTags, correctly handled by the DiigoEngine.
Ad 3) Case-sensitive for display but not for search: Please don't put this unnecessary burdon (of editing tag appearances) on millions of Diigo users.
MayAllBeHappy
fridemar
PS.: A simple realization for Diigo-, Trailfire and other social annotation services for AutomaticTagging is given in the above text by manually making transforming all WikiWords into GoogleSearchLinks.