A sample trailfire ... the idea of "overcoming constraints" seems like one appropriate bridge-building ingredient. Explore. Enjoy. Encourage. Evolve.

WikiAnnotationByTransclusion

Hello

Dear Maggie, dear Hans

the idea of combining annotation with transclusion is an excellent idea of HansWobbe. This solves several problem with one clap:

* UrlBasedAnnotation: now each annotation can have it's own Url like TrailFire does it, but with the added advantage, that those WikiPageUrls have the form: WikiPrefixColonFollowedByWikiPagename and not only coded by cryptic numbers. So the readability in GoogleSearchResults is improved.

* GlobalWikiEngineSupport:
** EachWikiAnnotationAsPartialPageOrFullpage 'quite normal windows, no more tiny stickies, that must be manually resized.'
** EachWikiAnnotationWithLookAndFeelConserved

* LocalWikiEngineSupport 'where each wiki word is tagged automatically by a TagWiki'

The main advantage appears to be using host wikis as source for RichLinkContext and NestingOfAnnotations in the sense of KaPingYee, who invented WebAnnotation. This means each WikiPage itself can be annotated or edited, thus CreatingSpaceForSocialCollaboration.

Some people may object, if you have a WikiPage, you don't need annotations.

If millions of peers of the social annotations communities, would edit the WikiPedia, what a mess.
Unobtrusive annotations solve the problem.

MayAllBeHappy

-- fridemar