DiigoTrailfireWikiCollaboration

The initiator of a group at Diigo with this name , which is at the same time a MixedCaseTag , opened this WikiTrail to stimulate collaboration between the two great social annotation communities and diverse wikis.

As this AnnotationEngine is not yet a TagWiki, the author presets all wiki words manually to GoogleSearchLinks.

This FireTrail started in the midst of some discussions on the DiigoGroupForum
The following pseudo-links are made to illustrate, how much work could be taken away from users of annotation systems, if the software itself transformed any WikiWord automatically into a LongTag  or into a GoogleSearch. (Estimated less then 100 LOC Lines of Code)


AllLowerCaseModeForTagsAsOption:

alllowercasemodefortagsasoption

Hi Soulgrind:

I can feel with you and all the other peers, who are used to work in a relaxed way without the need to bother about the case. As long as Diigo is used for private tagging, why not.
But when subcommunities within the DiiGo sphere want to build SocialCollaboration , they need
precise tags. Think of distributed teams of C++ programmers, who are very sensitive in questions of case.

For non-programmers, please rethink the iPOD (TM) versus iBM (TM) example.

Your example could be used for differentiating tags by TypingShortCuts

Tech=HIghTech
tech=LowTech

In the author's view this is not at all "annoying". It is indeed very convenient.

It takes some carefulness of the SocialTagCommunityUser, but they will
learn the advantage of CaseSensitivity very fast, as soon as they see more examples. On the other hand, as Maggie pointed out, the (private) tags remain editable.

Even the PluralSingularIssue, well known
in the different WikiCommunities, would have a total different importance in TagCommunities.

"game" and "games" could precisely
differentiate between a site, devoted to one game only versus a site,
where more than one game is offered.

MayAllBeHappy
fridemar