Annotations need to be URL-based as TrailFire does it. You can click [1] and you get ample annotations. In this case a snapshot of the whole page, of which I am the author. In wikis longer contributions are not the exception. So please get rid of the 5000 words barrier.
Each wiki on the web, talking on VirtualTwinPage, tagging itself with "VirtualTwinPage" generates in fact a VirtualTwinPage, such that both pages are twins, i.e. each twin links to the other by a StrongLink link relation.
Dear Diigos, dear TrailFire peers, Diigos can learn a lot from the Url-based design of FireTrail. This architecture promises to reach the level of the precursor annotation system of KaPingYee, where each WebPage can annotate each other. As a special case: Each annotation can be titled, referred to, googled, and be annotated by annother annotation. Congratulations to TrailFire for this architecture.
To both DiiGo and TrailFire programmers: please make the annotations like normal windows. One click should make them fullsize windows, another click minimize them as appropriate.
I leave here a copy of my wiki contribution, before the annotated page was made READONLY. Before the page was made READONLY, it allowed me the quoted entry below.
Unfortunately this Wiki page switched from READ and WRITE to READONLY, so that the author couldn't correct his contribution.
What a blessing, that there is this social annotation service Diigo. I wish, all the world would use it. It is a great help for democratic open and free expression and initiatives.
The value of social annotation is indispensible.
Quote of my wiki contribution:
My suggestion is to try to establish links by userdefined TwinPages. These links are usually at the bottom of the page, but it might be a good alternative to have them at some other visible place, e.g at the top of RecentChanges, if the resp. wiki allows users to edit the top lines. If somebody objects against a link s/he may delete it with or without an argument. If there are enough supporters for establishing a TwinPage relation between the strategically most important TwinPages (WikiNode, RecentChangesNode?, HelpNode? (for the syntax of the involved wikis), GoalStatementNote?, MissionNode?, …) then the decision will come in a most natural way by majority of the legitimated decision-makers, depending on the organisation, enterprise, corporation, community, etc. . By the way, the TwinPages format avoids doubling the name of the involved pages and so gives a faster overview over the participating wikis. Thank you all for making our common dream a reality.
WikiAnnotation means annotation of > WikiPages > . >
Why is WikiAnnotation important for Online Communities? Isn't Wiki enough? Wikis allow inline annotations with normal wiki page editing? -- FridemarPache
In this TrailFireTrail, we test the capabilities of DiiGo and TrailFire to
annotate WikiPages (WikiAnnotation)
annotate annotations (AnnotationAnnotation)
InteroperabilityOfDiiGoWithFireTrail would mean: it is possible to annotate
DiiGo annotations with FireTrailAnnotations and
FireTrailAnnotations with DiiGo annotations
It is easy to see, that DiiGo marked text (DiiGo highlighted text) can be marked by TrailFire. The converse however doesn't appear to work yet . To test this (1) I took a DiiGoMarkedText in the WikiAnnotation page and copied it into the rich text TrailFireAnnotationDIalog.
(2) I DiiGoMarked [this text in brackets, but without the brackets] and looked at the result of the TrailFireAnnotation, after having edited it.
No wonder. Trailfire is so new, that DiiGo has not settled the problems.
Enlarge Space: If there are lots of people, who make annotations, the Wiki Pages will become unmanagable. By sourcing out the ThreadMode, the need for refactoring pages is reduced considerably
Dear DiiGo programmers, we need a simple button, to toggle on/off the DiiGo markers. Currently it is very cumbersome to sign off for eliminating the markers temporarily and then again to sign in. On the other hand the markers of TrailFire are much less obtrusive, but more difficult to find.
{0 {1 {2 Hans, can you see the upper paragraphs on this page DiiGo marked in total. Currently I cannot get rid of the highlighted DiiGo text. -- fridemar } The text in curly braces, numbered 2, was copied into a FireTrailMark as temporary work text. When this page gets refactored, it can be deleted. In the meantime, it serves as an illustration, how useful TrailFire and DiiGo is for maintaining a WikiPage. The text in curly braces, numbered 1, is again copied into a FireTrailMark and a DiiGo annotation, so that later it can be deleted too, after it has served as an illustration. 1} -- fridemar dto. for block 0. Later after using the annotation tools, such collaboration interaction can be factored out straight from the start on. I hope to have demonstrated, how useful WikiAnnotation can be. 0}
{0 {1 {2 Hans, can you see the upper paragraphs on this page DiiGo marked in total. Currently I cannot get rid of the highlighted DiiGo text. -- fridemar } The text in curly braces, numbered 2, was copied into a FireTrailMark as temporary work text. When this page gets refactored, it can be deleted. In the meantime, it serves as an illustration, how useful TrailFire and DiiGo is for maintaining a WikiPage. The text in curly braces, numbered 1, is again copied into a FireTrailMark and a DiiGo annotation, so that later it can be deleted too, after it has served as an illustration. 1} -- fridemar dto. for block 0. Later after using the annotation tools, such collaboration interaction can be factored out straight from the start on. I hope to have demonstrated, how useful WikiAnnotation can be. 0}
Group Bookmarks tagged
Maggie Tsai (290)
Mah Saito (105)
Dr. Fridemar Pache (17)
Wade Ren (14)
jincheng li (12)
Please DiiGo programmers, let the 5000 word barrier.