For historical reasons, this trail starts here.

The TrailFire URL , hosting the trail AnnotationWiki is here.
We always can find the trail URL, by using the "Search Trailfire" box. In our case, we searched for "AnnotationWiki".

This is the page, where the initiative started.

Now let's see, if we can put several marks on a page, which are elements of the same trail. If we can see this second mark on the same page, the answer is: YES

This annotation tests, if it is possible to annotate a Mark with a public diigo annotation.

If this works, it will be a valuable tool for inter community communication.
Diigo members get a shortcut into the heart of TrailFire annotations.
As soon as they see the value of this bridging tool, they probably will want to become members of TrailFire and vice versa.

I am so excited to test this.

At first sight, it appeared to work. Test it yourself. But,  when revisiting the  page, the DiiGo  annotation  was  gone  :-(

After a second visit, some hours later, it  works. Hey  it   works!!!  Thank dear Diigo programmers for your fast internal upgrade.  :-)

Now again, it doesn't work. I think this problem will be solved soon (hopefully).

The original CritOrgMediator allowed each URL page to be an annotation of each other page.  Let's see which annotation system reaches faster this convenience.
The benefit of such an approach would be, that each annotation can interact with each other annotation in two ways:

• referencing other annotations, together with their annotated page.
• annotating annotations in form of arbitrarily nested annotations.

Let's see how cross communication between different annotation communities works.
With the positioning of the trailfire mark, I test, if it is possible to get a synergy-effect by letting both systems work in tandem. As the markers of Diigo are more eyecatching, I set TrailFireMarkers on corresponding DiiGo markers and copy my DiigGo annotation into this mark:

Don't confuse WikiAnnotation with an AnnotationWiki.
Actually WikiAnnotation should become a separate trail.

MarkUrl

MeatballWiki | RecentChanges | Random Page | Indices | Categories

---

A MarkUrl is an Url for a TrailMark. Each TrailFire annotation is saved on its own Url. This design allows each TrailMark to point to each other TrailMark from within its content. -- FridemarPache

Discussion:

• The current implementation generates automatic names, based on the trails and numbers.
• Suggestion: Why not preset the TrailMark title in the mark dialog box to this number (inviting the user to replace it by a better memorable string. If the string is not available, prompt for a new one.)
• A TrailMark can be seen as a prototype for a WikiPage and a FireTrail as a prototype for a whole wiki.

-- [fridemar]

---

MeatballWiki | RecentChanges | Random Page | Indices | Categories
Edit text of this page | View other revisions | Search MetaWiki
Search:

MarkUrl

MeatballWiki | RecentChanges | Random Page | Indices | Categories

---

A MarkUrl is an Url for a TrailMark. Each TrailFire annotation is saved on its own Url. This design allows each TrailMark to point to each other TrailMark. even from within its content. -- FridemarPache

Discussion:

• The current implementation generates automatic numbers instead of names, based on trail, marknames, date-time.
• Suggestion: Why not preset the TrailMark title in the mark dialog box to something synthetic, may be a copy of the page title (inviting the user to replace it by their own choice. If the string is not available, prompt for a new one.)
• A TrailMark can be seen as a prototype for a WikiPage, a FireTrail as a prototype for a whole wiki and TrailFire as a WikiFarm
• E.g. this special TrailMark on this page could serve as [an additional snapshot backup of this living wiki page].

-- [fridemar]

---

DiiGo [1] TrailFire [2][3] Google:MarkUrl

---

MeatballWiki | RecentChanges | Random Page | Indices | Categories
Edit text of this page | View other revisions | Search MetaWiki
Search: