In Wiki With More Than Pages, this Artifactory can prove to be quite useful ThinkingOutLoud.DonaldNoyes 20101014 20120621
While thinking about how Wikis can be made to be aware (contain information about) the content and navigational properties of one of its pages, I came upon a scheme whereby the Wiki Engine can be made to account for characteristics, which either by default configuration, and/or special configuration will cause certain operations, modifications and storage and retrieval events to occur.
This is accomplished by either including code in the Wiki Engine to do so, or delegation via an External Artifactory (process) to carry it out.
While working with several of my special projects dealing with Personal Information Management, I found certain things about the pages included in the process which were derived during and because of its discovery process.
I thought, why do the same processes of discovery over and over, when more times than not, there have been no change in the discoveries found this time than existed last time.
Why not create Artifact Comprehensions?
Time can be saved in the process and loading of a page and information about associated pages and links in an Information Space consisting in thousands and tens of thousands of pages.
Time savings can become significant because the discovery is done Once Only upon the first loading of a version of the page, or when new versions containg new internal or external links make a new comprehension necessary.
How this may be accomplished and the clever programming necessary to accomplish this is not shown here.
I am in the process of structuring and processing using a process I call Artifactories or Artifact Processors, executed when special flags, messages or markers are raised in the loading of markup text during an Artifactory Create Page From Markup process.)
This scheme is surely plausible in other existing or planned Wiki Schemas. It could be something like it be already in use in a particular Wiki of which I am not aware. Are you?