Glossary of Keywords

• Architectural Form: HyTime and SMDL's implementation of object-oriented structures. These architectural forms may be element types, in which the syntax of an element and its attributes form the building blocks of new data structures, or attribute types, where only the attributes themselves create the form.
• Attribute: A property, usually of an element. Such properties may include names, references, and local conditions. Attributes may be extended by the use of architectural forms in HyTime and SMDL.
• Axis Marker: one of a pair of numbers that signifies a position on an axis.
• Axis: Used for scheduling in HyTime; the base upon which events are positioned. May represent either spatial or temporal position.
• baton: a schedule of projectors contained within projector scopes (proscopes).
• cantus: the logical domain of SMDL. May be thought of as that information that has both visual and gestural implications.
• conloc: addresses the content of another SGML element.
• dataloc: addressing facility that names chunks of data by locating appropriate strings and tokens in another data content notation.
• Dimension: Location of an object on an axis. Consists of specification of the first and last quanta occupied by the object, as well as the extent, or total number of quanta that the object occupies.
• dimlist: dimension list; a list of marker pairs.
• dimspec: dimension specification; a pair of axis marker lists.
• DTD: Document type definition. In SGML, HyTime and SMDL, a DTD shows the potential structures inherent in a document that follows the DTD.
• Element: A basic structural block in SGML. Elements have basic types, which are followed in each particular instance of that type.
• Entity: A resource or other chunk of information that may be defined in the DTD, and may exist physically in a different file from a document instance. This allows SGML documents to use resources without greatly expanding the size of a document.
• Event: A scheduled object. It has a starting point and an extent on an axis.
• evsched: an event schedule. The nature of the events is determined by the DTD; the content is the stuff that is being represented in each document instance.
• exspec: extent specification; an attribute that associates a scheduled exyent with an event.
• extent: the specification of the boundaries of an object on an axis. Syntactically, one or more dimension lists. Can be referenced by an ID, thus used as a resource throughout a document.
• extlist: an extended form of a axis marker list, resolving any of the measurement data structures to a list of markers.
• fcs: finite coordinate space.
• finite coordinate space: A combination of axes that together represent the position of an object. The number of axes can equal the number of dimensions represented in space/time.
• gestural domain: SMDL domain that represents performance information such as digital samples, MIDI sequences, etc.
• hmu: HyTime measurement unit; a flexible unit that unlike the smu, can be manipulated.
• Hypermedia: Any data which allow more than one sequence through the material; hypertext plus information from nontextual media.
• HyTime: Hypermedia/Time-Based Structuring Language; ISO/IEC 10744. An application of SGML, extending document capabilities to include hypermedia and multimedia information.
• marklist: a list of axis markers.
• Markup: Information added to the data content of a document to elucidate structure, hierarchy, properties and semantics of the data. In SGML, markup is contained within tags <...>.
• mdu: measurement domain unit definition; ratio that defines the base granule for an axis.
• meta-DTD: a document type definition that is general in character, and may form the basis of a more specific DTD.
• modifier: In HyTime, a modifier is any processing that occurs to an existing event or events. Examples would be light or audio filters.
• modscope: one or more modifiers given extents.
• notloc: addressing facility that names data in terms used by another data content notation.
• projector: a set of instructions for rendering objects in space or time. An example would be a tempo indication in music.
• proscope: one or more projectors given extents.
• Quatum: base (indivisible) counting unit on an axis.
• Schedule: A list of events. The order of the list may or may not have significance in the scheduling.
• schedule: a list of data objects that have a position and extent in either space or time. In HyTime, schedules are placed on coordinate axes.
• SGML: Standard Generalized Markup Language; ISO 8879. A language for showing the structure, hierarchy, semantics and properties of the data in a document.
• SMDL: Standard Music Description Language; ISO/IEC DIS 10743. An application of HyTime with constructs specific to musical information, including scores and performance information.
• smu: standard measurement unit; there are normative definitions in the HyTime standard itself.
• Tags: Characters that signify SGML, HyTime and SMDL markup. Any material within the tags is called markup. A start tag is of the form < >, whereas an end tag is of the form </ >.
• visual domain: SMDL domain that represents visual information such as score symbols that appear on a page or screen.
• wand: a schedule of modifiers contained within modifier scopes (modscopes).

[ Index ]