			Copyright © 1992, 1997 International Organization for Standardization. All rights reserved. This electronic document is for use during development and review of International Standards. Official printed copies of International Standards can be purchased from the ISO and the national standards organization of your country.
Next Clause	Previous Clause

3 Definitions

For the purposes of this International Standard, the following definitions apply.

3.1
anchor
anchor

An object (or list of objects) that is linked to other objects or lists of objects by a hyperlink.

NOTE 11 The term "object" is not a formal construct in HyTime; an anchor could be a document, an element, an arbitrary chunk of data, or any other thing.

NOTE 12 An object is an anchor if and only if a hyperlink identifies it as such.

NOTE 13 An object could be identified as an anchor in several link ends, in the same or different hyperlinks.

3.2
anchloc
anchloc

Hyperlink anchor location address.

3.3
application BOS
application BOS

A bounded object set that is determined by an application according to its own rules.

NOTE 14 The rules can provide for automatic determination from a set of parameters, selection by the user, or some combination thereof. One possibility is for the application to use the entities included in a HyTime BOS as a starting point, but to allow the user to add or subtract entities from it.

3.4
architectural forms
architectural forms

Rules for creating and processing components of documents. There are four kinds: element form, attribute form, notation form, and data attribute form.

3.5
attribute form
attribute form

An architectural form that applies to attributes of elements.

3.6
auxiliary grove
auxiliary grove

A grove constructed by processing nodes in another grove.

NOTE 15 For example, the data tokenizer grove constructed for use by a data location address is an auxiliary grove.

3.7
bit combination
bit combination

An ordered collection of bits (for example, a byte is a combination of 7 or 8 bits). A bit combination represents a character in character data or markup, but can represent numeric or other values in non-character data.

3.8
bounded object set
bounded object set3.8
BOS
BOS

The subject that a HyTime application processes: a set of one or more documents and other information objects.

NOTE 16 There are three kinds: HyTime BOS, application BOS, and effective BOS.

3.9
bounding region
bounding region

The region of an FCS addressed by an fcsloc within which events are selected according to the selection precision specified for the fcsloc.

3.10
children property
children property

In groves, that subnode property of a node that is designated as the content property of the node. A node may have zero or one children properties.

NOTE 17 If a content property is not nodal, then the node does not have a children property.

3.11
client architecture
client architecture

An architecture derived from another architecture. The first architecture is said to be a client of the architecture from which it is derived.

3.12
client document
client document

A document conforming to an architecture. The document is said to be a client of the architecture to which it conforms.

3.13
client DTD
client DTD

The document type definition of a client document.

3.14
clink
clink

Contextual link element form

3.15
content property
content property

In groves, that property of a node that is designated as containing the semantic content of the node. A node may have zero or one content properties. A content property may be nodal or primitive. When a content property is nodal, the property is also the children property of the node.

NOTE 18 For example, for SGML element nodes, the content property can contain elements, data characters, or other objects that occur syntactically within SGML elements, excluding objects that the rules of SGML exclude from the semantic content, such as ignored record ends and separators in element content.

3.16
content tree
content tree

In groves, the tree formed by a node and the nodes in its children property.

3.17
contextual hyperlink
contextual hyperlink

A hyperlink that occurs "in context", meaning that one anchor of the link is the link element itself (a "self anchor") and is a traversal initiation anchor. In an interactive application, the self anchor can be accessed externally from adjacent elements or data in the document hierarchy.

NOTE 19 Any of the hyperlink element forms may be used contextually. The clink element form is always contextual.

3.18
contextual link element form
contextual link element form

An element form that represents a binary contextual hyperlink having the fixed anchor roles reference mark (refmark) for the self anchor and reference subject (refsub) for the other anchor.

3.19
data attribute form
data attribute form

An architectural form that applies to data attributes.

3.20
data location address
data location address

A location address that addresses the string and token data objects resulting from tokenization of character data.

3.21
dataloc
dataloc

Data location address.

3.22
dimension
dimension

Size and position on a coordinate axis. It consists of three components: a position (the first occupied quantum), a quantum count (the total number of quanta occupied), and the last occupied quantum.

3.23
document
document

A collection of information that is identified as a unit and that is intended for human perception.

3.24
document (type) definition
document (type) definition3.24
DTD
DTD

Rules, determined by an application, that apply SGML to the markup of documents of a particular type. A document type definition includes a formal specification, expressed in a document type declaration, of the element types, element relationships and attributes, and references that can be represented by markup. It thereby defines the vocabulary of the markup for which SGML defines the syntax.

NOTE 20 A document type definition can also include comments that describe the semantics of elements and attributes, and any application conventions.

3.25
effective BOS
effective BOS

The bounded object set consisting of all the objects that at any given point have been successfully and fully integrated into the hyperdocument being processed.

3.26
element form
element form

An architectural form that applies to elements.

3.27
entity descriptor
entity descriptor

A component of an SDIF data stream that represents an external entity.

3.28
entity tree
entity tree

A tree structure whose nodes are entities, constructed by the following steps:

An SGML document entity or SGML subdocument entity is selected as the root node.
The set of external entities identified by external identifier parameters of markup declarations in the node comprise the children of the node. Each child that is an SGML document entity or SGML subdocument entity is selected as a parent node.
Step 2 is repeated for each parent node, until the leaves of the tree or a specified maximum number of levels is reached.

NOTE 21 The maximum number of levels is an attribute of a HyTime document when used as a hub, and can be overridden when a HyTime application is invoked.

3.29
event
event

The occurrence of an object in a coordinate space. It associates the object with a scheduled extent.

NOTE 22 The scheduled extent of an event gives the object a position and size. The set of first quanta on all the axes defines the position, while the set of quantum counts for all axes completes the dimension specifications and defines the size.

3.30
event projection
event projection

The conversion of the scheduled extent of an event from schedule to schedule (the "unprojected" to the "projected").

NOTE 23 For example, from music time to real time, or from user device coordinates to real space units.

3.31
(scheduled) extent
(scheduled) extent

Size and position in a coordinate space. It consists of a dimension on each axis of the space.

3.32
external identifier
external identifier

A parameter of an SGML markup declaration (typically an entity declaration) that identifies an external information object.

NOTE 24 It may do so by various means, including:

a formal public identifier; that is, a globally unique public identifier, which allows a system to access its object by means of a table look-up; and/or
a system identifier; that is, a file identifier, storage location, program invocation, data stream position, or other system-specific means of locating the object in storage.

3.33
fcsloc
fcsloc

finite coordinate space location address

3.34
finite coordinate space location address
finite coordinate space location address

A location address that addresses events in an event schedule (or the objects scheduled by those events) by defining a bounding region enclosing the events selected.

3.35
graph representation of property values.
graph representation of property values.

An abstract data structure consisting of a directed graph of nodes in which each node may be connected to other nodes by labeled arcs.

3.36
grove
grove

Graph Representation Of property ValuEs.

3.37
grove construction process
grove construction process

A process that constructs a primary or auxiliary grove.

3.38
grove definition
grove definition

The combination of a grove plan, grove construction process, and grove source object.

3.39
grove plan
grove plan

A specification of what modules, classes, and properties to include in a grove. Grove plans are used both to construct groves and to view existing groves.

3.40
grove root
grove root

The one node in a grove that does not have an origin.

3.41
grove source
grove source

The data (for primary groves) or nodes (for auxiliary groves) from which a grove is constructed.

3.42
hub document
hub document

The document in which access to a hyperdocument begins. In a HyTime hyperdocument, the hub document also defines a HyTime BOS for interchange, rendition, or other processing.

NOTE 25 "Hub document" is not a permanent state of a document and cannot be specified by means of an attribute. The designation of a hub document is a parameter of processing and is specified when an application is invoked.

NOTE 26 It is possible that several HyTime documents, when designated as a hub document, could define the same HyTime BOS.

3.43
hyperdocument
hyperdocument

Two or more documents or other information objects that are connected to one another by a web.

NOTE 27 Access to a hyperdocument begins from a designated hub document.

NOTE 28 One hyperdocument may include another, otherwise independent hyperdocument, by declaring the hyperdocument's hub document to be included as a "subhub".

NOTE 29 A hyperdocument may represent a fixed or singular collection of data objects organized for a particular purpose (such as to represent common ownership or to support a particular rhetorical purpose) or it may be an arbitrary and transitory collection of objects. The HyTime bounded object set control facilities and activity policy association facilities, as well as application-specific mechanisms, can be used to define additional semantics for and constraints on the composition and use of hyperdocuments.

3.44
hyperlink
hyperlink

An information structure that represents a relationship among two or more objects.

NOTE 30 Objects that are related by a hyperlink are called the "anchors" of the hyperlink. An anchor is identified by a property of the hyperlink called a "link end".

NOTE 31 Hyperlinks can be assigned link types and names by applications and architectures that use HyTime.

NOTE 32 An SGML document can represent relationships by means other than hyperlinks; for example, the subordinate and sibling relationships of the document hierarchy are represented by the position of markup tags.

3.45
hyperlink anchor location address
hyperlink anchor location address

A form of query location address that addresses objects by the anchor role names of the anchors of which the objects are members.

3.46
hyperlink location address
hyperlink location address

A form of query location address that addresses hyperlinks by link type.

3.47
hypermedia application
hypermedia application

An information processing application that has hypertext and/or multimedia capabilities.

NOTE 33 An implication of this definition is that "hypermedia" refers to the union of hypertext and multimedia, rather than their intersection.

NOTE 34 While it would be possible to maintain a strict distinction among the terms "hypertext", "multimedia", and "hypermedia", there is generally little point in doing so in this International Standard when referring to documents or applications. Events, however, are referred to as "multimedia" rather than "hypermedia" because their nature is unaffected by whether hyperlinks are made to them. Similarly, hyperlinks may be characterized indiscriminately as "hypertext", "hypermedia", or simply "hyper", because their nature is unaffected by the objects to which they are linked.

3.48
hypermedia document
hypermedia document

A document or hyperdocument that is used in a hypermedia application.

NOTE 35 A hyperdocument is almost always a hypermedia document as well, in that it is normally used in a hypermedia application. However, not all hypermedia documents are hyperdocuments; for example, a document containing video clips but no hyperlinks.

3.49
Hypermedia/Time-based Structuring Language
Hypermedia/Time-based Structuring Language3.49
HyTime
HyTime

A standardized hypermedia structuring language for representing hypertext linking, temporal and spatial event scheduling, and synchronization. HyTime provides basic identification and addressing mechanisms and is independent of object data content notations, hyperlink types, processing and presentation functions, and other application semantics. Hyperlinks can be established to documents that conform to HyTime and to those that do not, regardless of whether those documents can be modified. The full HyTime function supports "integrated open hypermedia" (IOH) -- the "bibliographic model" of referencing that allows hyperlinks to anything, anywhere, at any time, in a variety of ways -- but systems need support only the subset that is within their present capabilities.

3.50
HyTime attribute
HyTime attribute

An attribute whose definition is included in a HyTime architectural form.

3.51
HyTime BOS
HyTime BOS

A HyTime BOS is a tree of entities rooted at and specified (directly and/or indirectly) by the entity declarations and other specifications in a HyTime hub document.

NOTE 36 A HyTime BOS can be determined automatically by a HyTime engine. The root of the entity tree is the SGML document entity of the hub document.

3.52
HyTime document
HyTime document

An SGML document whose properties are represented essentially as defined in this International Standard.

NOTE 37 A HyTime document is normally a conforming HyTime document (see 11.1 Conforming HyTime document).

3.53
HyTime element
HyTime element

An instance of a HyTime element type.

3.54
HyTime element type
HyTime element type

An element type in a HyTime document that conforms to a HyTime architectural form.

NOTE 38 The element type itself is not defined by HyTime. In addition to attributes defined by the architectural form, it may have application-specific attributes.

3.55
HyTime engine
HyTime engine

A program (or portion of a program or a combination of programs) that recognizes HyTime constructs in documents and performs application-independent processing of them.

NOTE 39 For example, a HyTime engine can interface with data base and network servers to resolve and access anchors. It can also perform the calculations to locate events consistently in a coordinate space regardless of the schedules in which they were entered or the measurement units used to define their extents.

3.56
HyTime hyperdocument
HyTime hyperdocument

A hyperdocument whose hub document is a HyTime document.

NOTE 40 The hub document must be represented in SGML; the other components of the hyperdocument need not be. The hub or any other component may conform to a document architecture.

3.57
HyTime system
HyTime system

An SGML system that includes a HyTime engine.

3.58
hypertext
hypertext

Information that can be accessed in more than one order.

NOTE 41 A hypertext can be a single document or a library of documents (a "hyperdocument"). For example:

A novel is typically not designed to be a hypertext.
A book with footnotes or internal cross-references is a single document hypertext.
A book with external cross-references (e.g., bibliographic citations) is a member of a library that as a whole constitutes a hyperdocument.
A book with both internal and external cross-references is both a single document hypertext and a member of a library that as a whole constitutes a hyperdocument.

3.59
initial referrer (to a location path)
initial referrer (to a location path)

A referrer to the first location step in a location path.

NOTE 42 An initial referrer cannot be a location address because one location address that references another becomes a location step.

NOTE 43 Every step in a given location path has the same initial referrer.

3.60
integrated open hypermedia
integrated open hypermedia3.60
IOH
IOH

The formalization, for computer processing, of the "bibliographic model" of referencing that allows representation of hyperlinks to anything, anywhere, at any time, in a variety of ways.

3.61
link
link

Depending on context, either a hyperlink or an SGML processing link ("link process").

3.62
link end
link end

In a hyperlink, the union of an anchor role name, the members of the anchor, and the other properties associated with the anchor, such as traversal rules.

3.63
link process definition
link process definition3.63
LPD
LPD

Application-specific rules that apply SGML to describe a link process. A link process definition includes a formal specification, expressed in a link type declaration, of the link between elements of the source and result, including the definitions of source attributes applicable to the link process ("link attributes").

NOTE 44 A link process definition can also include comments that describe the semantics of the process, including the meaning of the link attributes and their effect on the process.

3.64
link type
link type

A class of hyperlinks. It assigns meaning to the relationship represented by the hyperlinks, including the role in the relationship played by each anchor.

3.65
linkloc
linkloc

Hyperlink location address.

3.66
listloc
listloc

List location address.

3.67
list location address
list location address

A location address that selects nodes from a node list by specifying one or more dimension specifications, one for each contiguous sequence of nodes selected.

3.68
location ladder
location ladder

A set of location addresses, known as "location rungs", in which each rung is the location source of the rung below it.

NOTE 45 A location ladder is visualized as running from top to bottom, from location source to path step. A rung that is a step in a location path is considered to be the bottom rung with respect to that path.

NOTE 46 A location ladder represents a progressive culling of the set of addressable objects as one proceeds downward (in other words, the top rung addresses the largest possible scope from which nodes may be selected by the rungs below it).

3.69
location address
location address

An element form that represents the address of one or more objects. A reference to a location address is treated as a reference to the objects located by the location path that it begins.

NOTE 47 A location address can be the location source of another location address, thereby forming a location ladder.

NOTE 48 A location address is the HyTime representation of what is commonly known in computing as an "indirect address".

3.70
location path
location path

A set of location addresses, known as "location steps", in which the first step locates the second and so on. A location path can have branches, created when a step locates two or more objects, at least one of which is a location address. A branch terminates when its last step locates only objects that are not location addresses. The objects located by a location path are all those, other than steps, that are located by any of the steps in the path.

NOTE 49 A location path is visualized as running from left to right, from initial referrer to objects addressed. Each step is the bottom rung of a location ladder.

NOTE 50 A location address can be a step in more than one location path, but can be the first step in only one.

3.71
location source
location source

The set of objects from which a location address selects the objects that it addresses.

NOTE 51 For example, the location source of a treeloc is the tree in which the node addressed by the treeloc is found.

3.72
mixedloc
mixedloc3.72
mixed location address
mixed location address

A location address that addresses objects indirectly through its child location address elements.

3.73
multimedia
multimedia

(Adjective) Employing more than one means of communicating something, such as forms used by artists, musical composers, etc.

3.74
(object) modification
(object) modification

The modification of an object by another object during rendition.

NOTE 52 For example, routing audio signals through an effects box.

NOTE 53 HyTime deals with the scheduling and association of modifiers, but not the semantics of modification.

3.75
nameloc
nameloc

Named location address.

3.76
named location address
named location address

A specialized form of mixed location address that addresses objects by their element IDs or entity names.

3.77
named node list
named node list

In groves, a node list in which all the member nodes exhibit a unique value for a common "name" property. The value of a name property may be either a string or a single node where the node is unique among all the nodes in the name values of the members of the node list.

3.78
name-space location address
name-space location address

A location address that addresses nodes in named node lists.

3.79
nmsploc
nmsploc

Name-space location address.

3.80
node
node

In groves, an ordered set of properties representing a single object.

3.81
notation form
notation form

An architectural form that applies to data entities and notation data content.

3.82
origin
origin

In groves, for a node, the node of which the node is a subnode. Every node in a grove, except the grove root, has exactly one origin node.

3.83
patch
patch

An interconnection of modifiers.

3.84
pathloc
pathloc

Path location address.

3.85
path location address
path location address

A location address that addresses nodes in a tree by viewing the tree as a matrix where each column is the list of nodes from the root to a leaf.

3.86
pelement
pelement

Pseudo-element.

3.87
presentation
presentation

A state of processing of a document in which it is ready for human perception.

3.88
previous specified element
previous specified element

The element in the SGML representation of the document that was most recently parsed.

NOTE 54 It is typically also the one most recently occurring when the SGML representation is viewed as a character string, although an entity reference could cause other elements to be parsed more recently than that one.

3.89
primary grove
primary grove

A grove constructed by processing source data.

NOTE 55 For example, the grove constructed for an SGML document after the initial parse of the SGML source data is a primary grove.

3.90
principal tree
principal tree

In groves, that content tree designated as being the principal tree by the grove's property set. In HyTime, the principal tree is the default implicit location source for tree location addresses.

3.91
principal tree root
principal tree root

In groves, the node that is the root of the grove's principal tree. In the SGML property set, the document element is the principal tree root.

3.92
projection
projection

Event projection.

3.93
property location address
property location address

A location address that addresses the value of a property of a node in a grove.

3.94
property set
property set

A formal definition document, conforming to the requirements of the Property Set Definition Requirements in this International Standard, that specifies the node classes and properties to be used in constructing a grove.

3.95
proploc
proploc

property location address.

3.96
pseudo-element
pseudo-element

In the SGML property set, an object whose children are derived from the data and other constructs occurring between a tag close and the next tag open. Pseudo-elements are children of elements.

3.97
quantum
quantum

Countable division of a coordinate axis.

3.98
queryloc
queryloc

Query location address.

3.99
query location address
query location address

A location address that uses a query to address nodes in a grove by their properties.

3.100
real time
real time

Time in the every-day sense, as measured in seconds, minutes, hours, etc.

3.101
referent (of an ID reference)
referent (of an ID reference)

An element whose ID is a value of an ID reference or ID reference list attribute (or content).

3.102
referential attribute
referential attribute

An attribute of an element that is designated as being a reference either by declaring it as an IDREF, IDREFS, ENTITY, or ENTITIES attribute or through the use of the HyTime refloc facility.

NOTE 56 In the HyTime meta-DTD, referential attributes are identified by the conventional comment "-- Reference --".

NOTE 57 Content may also be designated as referential.

3.103
referrer (to a referent element)
referrer (to a referent element)

An element with a referential attribute (or content) that addresses the referent element.

3.104
relative location address
relative location address

A location address that addresses nodes in a tree by specifying the genealogical relationship of the nodes to a starting node and then selecting nodes from the list of relatives.

3.105
relloc
relloc

relative location address.

3.106
rendition
rendition

A process performed on a HyTime document to prepare it for presentation. It may include event projection and object modification as defined by HyTime, in addition to application-specific processing.

NOTE 58 Several renditions might be performed in sequence in order to create the presentation that is ultimately perceived by a user. The renditions could involve projecting events to a new coordinate space; for example, from virtual time to real time.

3.107
reportable HyTime error
reportable HyTime error3.107
RHE
RHE

A failure of a HyTime document to conform to the requirements of this International Standard other than one that:

cannot be detected without processing the document; or
is identified in this International Standard as not being reportable.

3.108
(location) rung
(location) rung

An element in a location ladder.

3.109
SDIF packer
SDIF packer

A program that creates an SDIF data stream.

3.110
SDIF unpacker
SDIF unpacker

A program that decomposes an SDIF data stream into its constituent entities.

NOTE 59 If necessary, the SDIF unpacker will modify the system identifier parameter of markup declarations to be consistent with storage addresses in its environment.

3.111
self anchor
self anchor

A hyperlink that addresses itself as one or more of its anchors.

3.112
semantic grove
semantic grove

A grove created by an application or architecture engine. The nodes of a semantic grove reflect the data structures required to implement the application- or architecture-specific semantics.

NOTE 60 The HyTime architecture's semantic grove is defined by the HyTime property set (see B HyTime Property Set).

3.113
SGML Document Interchange Format
SGML Document Interchange Format3.113
SDIF
SDIF

A data structure that enables a main document and its related documents, each of which might be stored in several entities, to be combined into a single data stream for interchange in a manner that will permit the recipient to reconstitute the separate entities.

NOTE 61 When SDIF is used as a hyperdocument interchange format for HyTime, the "main" document, if there is more than one, is the hub document.

3.114
SGML processing link
SGML processing link

The "link process" feature of SGML; it allows multiple context-sensitive sets of presentation and processing specifications to be associated with elements of a document.

3.115
SGML subdocument entity
SGML subdocument entity3.115
SUBDOC
SUBDOC

An SGML entity that conforms to the SGML declaration of the SGML document entity, while conforming to its own document type and link type declarations. It contains, at a minimum, a base document type declaration and the start and end of a base document element.

3.116
subhub
subhub

A hub document declared in another hub document and whose own HyTime BOS is added to the parent document's HyTime BOS.

3.117
SMU name
SMU name

A name, declared by a notation declaration, that identifies a standard measurement unit.

3.118
(location) step
(location) step

An element in a location path.

3.119
subnode
subnode

In groves, a node whose origin node exhibits a property of which the node is a member.

3.120
subnode property
subnode property

In groves, a property whose value must consist of nodes whose origin is the node exhibiting the property.

3.121
subnode tree
subnode tree

The tree of nodes consisting of a node and all of its subnodes.

3.122
target (of an ID reference)
target (of an ID reference)

The referent or, if that is a location address, the objects located by the location path that the referent begins.

3.123
treeloc
treeloc

Tree location address.

3.124
tree location address
tree location address

A location address that addresses a single node of a tree in the classical manner by selecting a node from an addressable range at each level of the tree, starting at the root.

3.125
validating HyTime engine
validating HyTime engine

A conforming HyTime engine that can find and report a reportable HyTime error if (and only if) one exists.

3.126
view
view

A presentation of a web and the anchors that it connects.

3.127
web
web

A set of one or more hyperlinks that are used together.

NOTE 62 Typically, the hyperlinks deal with a common topic and/or they can be traversed continuously through common anchors and/or anchors occurring in the same object.

Next Clause

Previous Clause

This electronic document is for use during development and review of International Standards. Official printed copies of International Standards can be purchased from the ISO and the national standards organization of your country.

HTML generated from the original SGML source using a DSSSL style specification and the SGML output back-end of the JADE DSSSL engine.