Below in no particular order, is the complete set of Dissemino terms.
| Web Application | The prefered Dissemino term for a website |
| HTTP Resource | A resource (e.g. webpage), available at a particular URL. Note that technically, HTTP resources are either declared or undeclared. A declared HTTP resource is formally part of a webapp and is defined in the webapp configs. An undeclared HTTP resource is an uploaded file and so is application data. The term 'HTTP resource', should be taken as a declared HTTP resource, unless otherwise stated. |
| Page/Article | Under the Dissemino regime, a (web)page is a full HTML document while an article is only a partial page. Articles lack the <head> and <body> tags of a page, and so must be framed within a page. Articles are page sections that are usually selected from a navigation tree (navtree), and loaded by means of AJAX (Asynchronous Javascript and XML) commands, operated by scripts that are supplied with the host page. |
| Visual Entity | Internal component of a HTTP resource, responsible for producing HTML |
| Active/Passive | A visual entity is active if the HTML it produces is in any way conditional. It is otherwise passive. Any HTTP resource is active if it contains one or more active visual entities. The resource is passive only if no part of the resource is conditional. |
| Executive Command Tag | Dissemino Executive Commands. Must lay within a <procdata> block |
| User Session | User sessions are created on the server when a user authenticates. They are complex structures able to support complex user date. |
| HadronZoo Program | Any program that includes the HadronZoo library in its build, is said to be a HadronZoo based program or simply a HadronZoo program. It is 'official' if it has been written by HadronZoo, and/or is available from the HadronZoo website. |