Tenor

Tenor

http://appeal.kde.org/wiki/Tenor

Excerpts from Tenor architecture document

Tenor architecture, by Scott Wheeler, April 2005

"Our present interfaces for interacting with desktop computers do not re?ect the increasing complexity of the information that we regularly work with, yet fundamentally little has changed in the last decade of desktop computing interfaces. To address this problem Tenor is being implemented as general framework for tracking relationships between data in desktop applications in KDE. It enables applications to represent relationships via sets of nodes and links and to move towards a contextual web of information rather than relying on traditional data hierarchies. This type of framework lends itself to applications such as desktop search and contextual navigation, as well as a host of other emerging interface paradigms."

"At present the Tenor architecture is most similar to an Attribute Value System, speci?cally in its ad hoc approach to metadata and associations, but is used to supplement the hierarchical ?le system rather than replace it."

"The framework provides the basis for building a contextual web where concrete desktop resources such as documents, applications, individual mails, music ?les and more abstract entities such as search terms or personal contacts are connected through indexing, usage patterns or explicit linkage. Tenor provides an API (application programming interface) for managing these relationships from within applications and ways to query the relationships when building applications that are able to take advantage of contextual linkage."

SeeAlso Scott Wheeler