Here is an illustrative (though simplified) example:

• A set of "class" pages define entities (e.g., file, control_file, log_file, program) and relationships (e.g., reads_from, writes_to), as:

  • file and program can play, respectively, the target and actor roles in reads_from and writes_to relationships

  • control_file and log_file are subclasses of file

  • reads_from and writes_to support the actor and target roles

• Based on these definitions, "instance" pages could be created for assorted files and programs:

  • /etc/crontab and /var/log/cron play target roles in instances of reads_from and writes_to relationships.

  • /usr/sbin/cron plays the actor role in these relationships.

Navigating to the /etc/crontab page, an Ontiki user could find out about all of its relationships: who reads it, who can edit it, etc. Clickable context diagrams would show these relationships and allow convenient navigation to related pages (e.g., /usr/sbin/cron, /var/log/cron).