all-act

What was the activity tracking facility has become the activity policy association facility. The all-act attribute list form is now the activity attribute list form. The activity attribute is replaced by the actrules attribute, which points to the activity policy association rules (actrule) that govern the element. See "6.7.3 Activity policy association ".

all-id

The all-id attribute list has been redistributed as follows:

conloc

The conloc attribute (part of the original all-id attribute list), has been superceded by the more general value reference facility. The original conloc attribute is now simply an application of the value reference facility (see " 6.7.1, Value Reference").

context

The concept of elements that do not disturb the contextual rules of the elements they appear in has been moved to the opacity attribute, one of the general attributes of the General Architecture.

delims

Has been eliminated as it is superceded by more general facilities, such as data attributes for elements (see " A.5.3, Data Attributes for Elements (DAFE)") .

HyNames

The HyNames attribute is now defined via the normal architecture use declaration mechanisms defined in the AFDR facility of the SGML Extended Facilities (see " A.3"). The name "HyNames" is no longer required by the HyTime architecture as documents are free to use any names they want when configuring the use of an architecture.

id

The id attribute is now part of the common attributes for elements of the General Architecture (see "A.5.2, Common attributes of elements ").

notation

The notation attribute is eliminated. The use of data content notations with elements can now be controlled using the Data Attributes for Elements (DAFE) facility of the General Architecture (see "A.5.3").

activity

The activity element form is replaced by the actrule (activity policy association rule) element form. An activity rule associates elements with the policy specifications that govern their access according specified activity types. The HyTime architecture no longer defines a fixed set of activity types, although it does define a starter set.

all-lex

The all-lex attribute list form has been replaced by the Lexical Type Definition Requirements facility of the SGML Extended Facilities, see "Annex A.2" for details.

baton

The baton element form can now include progrp elements, in addition to proscope elements.

all-ref

The functions of the all-ref attributes have been split beween the immediate reference type control facility of the General Architecture and the reference control facility of the HyTime location address module. See "A.5.5, ID immediate referent type control" and "7.7, Reference control".

batrule

The baton rule element form has a new attribute list, replacing the original evscheds attribute with the new scheds attribute and the original pevsched attribute with the new targschd (target schedules) attribute.

bibloc

The bibliographic location address element form has been redefined. It no longer takes the query and function attributes (as it is now not a query). The bibloc form now takes the unique bibsrc (bibliographic location source) attribute, which points to another bibliographic location that defines the addressing context for the first bibloc.

calendar

The original calendar attribute list has been superceded and replaced by more complete calibration and calendar specification facilities. See "9.9, Calibrated real time axes".

clink

The clink form is now formally derived from the new hylink form. This means that clink can take all of hylink's attributes (except anchrole, which is fixed for clink in the HyTime architecture).

common data attributes

The common data attributes have been completely reorganized. The isbento, methods, modgen and degrade attributes have been removed. They are replaced by the more general facilities for formal system identifiers (FSI), part of the SGML Extended facilities (see "A.6 Formal System Identifier Requirements"), by which any of these attributes can be defined for specific storage managers. The attributes altreps and superdcn are now defined by the General Architecture, which is part of the SGML Extended Facilities (see "A.5"). The encoding attribute is now defined by the FSI facility.

dimlist

The dimlist element form has been replaced by the %dimlist parameter entity, which expands to all the possible ways in which dimension specification lists can be represented.

dimref

The notion of dimension referencing has been generalized. The original dimref element form has been redefined and enhanced to reflect the new, more generalized event schedule and finite coordinate space model. In particular, it makes it possible to distinguish references to modified and unmodified (by rendition processing) extents.

dimspec

The dimspec element form is now formally derived from the markfun (marker function) element form. As a marker function, dimension specifications can use any marker function notation, with the default being the HyTime marker list notation.

dataloc

The functionality of dataloc has been generalized into a general facility for defining data tokenizers and data parsers and parsing contexts. The dataloc element form is now a combination of a list location address with a data tokenizer grove constructor (datatok).

dvl-atts

The default value list facility is now part of the General Architecture. The following attribute has been added to dvl-atts attribute list:

selfdvl

Refers to a default value list that sets the defaults for the element making the reference (as well as for its subelements).

dvlist

The default value list (dvlist) element form has a new attribute, defatts (default-setting attributes). This attribute names attributes whose values become the new default values for attributes controlled by the default value list. This enables the definition of the propagation rules for attribute values in combination with the use of default value lists to set the initial values of implied attributes. This provides what is essentially #CURRENT behavior for attributes, but down the element tree, rather than sequentially through the document.

event

The scheduled event element form has been refined. Events can now use an attribute (object) to address the objects that they schedule as an alternative to containing them syntactically. The accessed anchor list mechanism has been replaced by the more general element forms hyperlink location address (linkloc) and hyperlink anchor location address (anchloc). The new attribute align (object alignment) specifies how the object is to be aligned within the extent of the event.

evgrp

The event group element form no longer takes the grpscope attribute, which has been superceded by more complete event grouping and control mechanisms.

fcs

The finite coordinate space module has been significantly generalized and the fcs element form has been redefined. Axes are now defined using attributes of the fcs element, rather than subelements. The original axisdefs attribute has been replaced by the axes attribute, which specifies the names of the attributes of the same element that define the axes of the coordinate space.

The association of FCSes with measurement domains and units has been extended and generalized, including the addition of the ability to calibrate axes according to some real measurement system or event (e.g., you can associate the start of a time axis with a precise point in real time).

You can now use fcs elements by reference from event schedules, in addition to having them contain event schedules directly, as was required in HyTime First Edition.

fcsloc

The finite coordinate space location address element has been completely redefined. The function of the original fcsloc form can be achieved by defining a notation-specific query notation and using it with a query location address element. The new and improved fcsloc addresses scheduled objects by addressing the region of the coordinate space within which they are scheduled. In essence, the fcsloc provides a marquee selection (bounding box) mechanism for addressing scheduled objects. This lets you address whatever objects happen to fall within a particular portion of a coordinate space (for example, at a particular time or time span along a time axis).

granule

The gd attribute has been replaced by the granule definition notation (gdnot) attribute. Granules can be defined using any notation.

HyDoc

HyDoc form has been modified by moving all the bounded object set attributes to the optional bounded object set facility, part of the base module (see "6.5.1 HyTime bounded object set attributes "). The unmspace attribute has been removed as the concept of unified name spaces has been replaced by the more general mechanism for defining name spaces with groves. The docdmu attribute has been replaced by new facilities for defining finite coordinate spaces (see "9, scheduling module").

ilink

In addition to the original ilink form, two new hyperlink forms have been added, hylink (hyperlink) and varlink (variable link). These three forms provide the three possible syntax configurations for addressing anchors. hylink uses one attribute per anchor role while varlink uses one subelement (anchspec) to address the members of each anchor. ilink still uses the single linkends attribute to address the anchors of the link.

The endterms and aggtrav attributes have been eliminated. The HyTime architecture no longer has an opinion on the issue of anchor description and the whole concept of aggregate locations has been replaced by the grove addressing model and the new agglink hyperlinking form (which is derived from hylink).

The hyperlink traversal rule attributes intra and extra have been replaced by a single attribute, linktrav. In addition, traversal among the members of an anchor is controlled with the new attribute, listtrav.

locsrc

A new attribute, cantcnst defines the behavior when a grove cannot be constructed from the location source.

The location source can be omitted for any location address that is not an intermediate rung in a location ladder. For all location address forms except mixedloc and nameloc (which don't take the locsrc attribute), when the locsrc attribute is omitted, the location source is defined according to the settings of the implied location source attributes (impsrc). By default, the implicit location source is the non-location-address element that directly or indirectly addresses the location ladder of which the location address is the top (or only) rung.

markfun

Marker specification and marker functions have been generalized to enable the use of any marker specification or query notation. The original function attributes have been superceded by a more general, notation-based function specification mechanism where each function notation defines its own attributes.

marklist

The marklist element form has been replaced by the %marklist parameter entity, which expands to all the possible ways in which marker lists can be represented.

multloc

The attribute aggloc has been eliminated from the multloc attribute list. The concept of aggregate locations has been replaced by a clearer definition of multi-object anchors and by the agglink hyperlinking form.

nameloc

The nameloc form is now formally derived from the new mixedloc element form, which has the semantic of addressing whatever the location address elements in its content address.

nmlist

The nmlist element form is now formally derived from the new nmsploc (name space location address) element form. The nmsploc form provides the ability to address nodes in any named node list in any grove.

The obnames and dtdorlpd attributes have been eliminated. The function of obnames has been subsumed by the implications of grove-based addressing and the general semantics of location addresses. The dtdorlpd attribute has been replaced by the active data attribute defined by the SGML notation, which is defined as part of the definition of the SGML property set (see "A.7, SGML property set").

nmquery

The name list query element form is now formally derived from the general queryloc element form. It maintains the original qdomain attribute from the original query attribute list but it's now simply a renaming of the normal locsrc attribute. It also takes the new attribute notfound, which indicates the behavior when the query fails to find any nodes.

proploc

The proploc (property location address) form has been updated to reflect the new grove model. It now addresses the value of the property of a node in a grove by property name. The attribute joint is no longer relevant and has been eliminated. A new attribute, direct, lets you address either the direct value of a property or the effective value resulting from the application of the value reference facility (see "Value Reference").

rendrule

The attribute apporder is eleminated as the ordering of rendition rules is inherent in their grove representation.

relloc

The relative location address (relloc) element form has been refined. The original attribute root has been replaced by the normal meaning of the location source attributes (in particular, the new implied location source facility means that an omitted location source is, by default, the root of the primary tree, which is what the root attribute meant). The new attribute starting node (strtnode) addresses the node whose relatives are being addressed.

sched

The schedule attribute list has the new attributes fcs (governing finite coordinate space), coverage (extent coverage), and overlap (is overlap allowed?). The attribute apporder is eleminated as the ordering of events is inherent in their grove representation.

spanloc

The spanloc attribute of the spanloc attribute list has been redefined to remove the spanlink keyword. Span addressing has been formalized and clarified as well.

wand

The wand element form can now include modgrp elements, in addition to modscope elements.

abstime

The original abstime element form has been superceded and replaced by more complete calibration and calendar specification facilities. See "9.9, Calibrated real time axes".

accanch

The accessed anchor list mechanism has been generalized through the definition of the hyperlink addressing element forms hyperlink location address (linkloc) and hyperlink anchor location address (anchloc). These location addresses can be used with events to associate an event with a link or one of its anchors. Specific applications could also define more specialized queries for expressing the semantic relationship between events and hyperlinks and their anchors (or any other addressible object for that matter).

axis

The axis element form has been eliminated. The axes of finite coordinate spaces are now defined directly by attributes of the fcs element.

date

The original date element form has been superceded and replaced by more complete calibration and calendar specification facilities. See "9.9, Calibrated real time axes".

docmdu

The docmdu attribute has been eliminated as it is replaced by facilities of the redesigned finite coordinate space mechanism.

exrecon

[Fix Me: Determined what exrecon became.]

grprepet

The group repetition specification attribute list provides the repscope attribute for controlling the repetition of an event group.

juledate

The original juldate element form has been superceded and replaced by more complete calibration and calendar specification facilities. See "9.9, Calibrated real time axes".

lexmodel

The lexmodel form has been replaced by the more general Lexical Type Definition facility (see "A.2, Lexical Type Definition Requirements (LTDR) ").

lexord

The lexord form has been replaced by the more general Lexical Type Definition facility (see "A.2, Lexical Type Definition Requirements (LTDR) ").

mallobj

The malliable object element form was eliminated because the modification of objects is a style issue that cannot be separated from the nature of the object itself. The HyTime architecture avoids constructs or semantics that depend on knowledge of a specific object type (other than SGML-defined objects).

mrkquery

The marker query element form has been eliminated, as it is subsummed by the redesigned axis marker function mechanism (see "6.8.1.2, Marker Functions"). In essence, any marker query is just a form of marker function.

notloc

The notation-specific location address element form has been replaced by the queryloc (query location address) element form. The difference between these two is that the results of a notation-specific location address were undefined, while the results of a query location address must be nodes in a grove. However, a query location address can still use any query notation.

pls2gran

The pulse-to-granule-ratio attribute list has been replaced by the new, more general pulse map facility (see "9.7, Pulse maps").

profun

Replaced by the generalized expro element form.

propdef

Property sets are now defined by the Property Set Definition facility of the SGML Extended Facilities, which defines a separate architecture for property set definition documents. See "A.4, Property Set Definition Requirements (PSDR) ".

pulsemap

The pulse map attribute relates pulse definition schedules to events and event-like elements.

query

The original query attribute list has been superceded and replaced by the queryloc (query location address) element form. The original qdomain and qcontext attributes are replaced by the general facilities for defining and addressing location sources.

scaleref

The original scaleref element form has been superceded and replaced by more complete projection specification facilities. See "10.3, Projection".

select

The precision of selection attribute list controls the precision with which projected events, modscopes, and proscopes are selected.

timeoff

The original timeoff element form has been superceded and replaced by more complete calibration and calendar specification facilities. See "9.9, Calibrated real time axes".

The mechanism for declaring the use of the HyTime architecture and specifying the modules and features needed by a document has been changed to reflect the new enabling architecture facility defined in "A.3, Architectural Form Definition Requirements (AFDR) ", part of the SGML Extended Facilities. In general, the use of processing instructions has been replaced by the use of data content notation declarations and data attributes, except for the architecture use declaration processing instruction, provided by Ammendment 1 to ISO/IEC 10744:1997.

Clause A.2, Lexical Type Definition Requirements (LTDR)

Defines a general mechanism for defining lexical types that can be used to constrain attribute values and element content. This facility replaces the original lextype attributes from the base module.

Clause A.3, Architectural Form Definition Requirements (AFDR)

Defines the general mechanism for creating and using SGML architectures, of which the HyTime architecture is an example. Using the AFDR, any SGML or XML document can formally declare its derivation from one or more architectures. The AFDR is notably implemented by the SP parser from James Clark (who is largely responsible for the design and details of the AFDR facility).

The architectures defined in ISO/IEC 10744:1997 and ISO/IEC 10179 (DSSSL) conform to this clause.

Clause A.4, Property Set Definition Requirements (PSDR)

Defines the general grove mechanism. Property sets are the object schemas to which groves conform. All HyTime and DSSSL (ISO/IEC 10179:1996) processing is defined in terms of operations on nodes in groves. The HyTime and SGML property sets, also published in ISO/IEC 10744:1997, conform to this clause.

Clause A.5, General Architecture

The General Architecture provides facilities that are useful for any SGML application. Most of the General Architecture comes from the original base module of the HyTime architecture.

Clause A.6, Formal System Identifier Definition Requirements (FSIDR)

Defines a formal mechanism for associating the system identifiers of entities and notations with storage managers, that is, the programs or system services that know how to interpret the system identifies. The FSIDR facility solves a long-standing problem in SGML, the interchange and interpretation of system identifiers.

Clause A.7, SGML Property Set

The SGML property set is the formal definition of the in-memory abstraction reflecting the result of parsing SGML documents. The version of the SGML property set published in ISO/IEC 10744:1997 supercedes and adds to the version originally published in ISO/IEC 10179:1996. The 1997 version adds additional classes and properties but does not modify any existing properties.

The reference location address facility of the location address module enables the direct use of any addressing method from attributes of elements, rather than using indirect addressing. This includes the ability to use query location addresses. This means you can use any form of query directly from elements in a way that is meaningful and well defined in a larger HyTime framework. This enables, for example, the declaration of the HTML A element as a conforming HyTime contextual link. See "7.8, Reference location address".

The implied location source facility allows you to create indirect location addresses that do not address their location sources explicitly. This enables, for example, location addresses that are relative to the non-location-address elements that use them. It can greatly simplify the syntax of location addresses. See "7.3, Implied location source".

The calibration facility of the scheduling module makes it possible to calibrate time axes of finite coordinate spaces in terms of real measurements, such as real time. This facility replaces and generalizes the original calendar specification facility. See "9.3.1, Axis calibration", and "9.9, Calibrated real time axes".

agglink

The aggregation link element form is a link that simply represents the semantic of aggregation of a list of objects under a single semantic label. It serves primarily to enable navigation among the members of the aggregate without implying any more than that they are aggregated together. The agglink form, along with a clearer definition of multi-object anchors, replaces the original aggregate link concept. Any existing nameloc element that used the aggloc attribute can be redefined as an agglink without modifying element instances.

agrovdef

The auxiliary grove definition element form defines groves constructed from other groves. Grove definition elements enable explicit reference to auxiliary groves (rather than relying on the grove construction implicit in the use of queries).

anchloc

The hyperlink anchor location address element is a specialized form of query location address that addresses hyperlink anchors by link type and anchor role. It enables addressing objects based purely on their membership in one or more hyperlink anchors. This enables the interrelation of hyperlinks and other objects, such as events in event schedules. For example, you can define the content of an event to be whatever objects are the members of a particular anchor of a particular link or link type.

batonseq

The baton sequence element form defines an ordered sequence of batons, which will be applied in the order specified.

bosdatt

The bounded object set control data attributes let you control the participation of external data entities in the HyTime bounded object set. You can specify whether or not an entity is in the HyTime BOS (inbos), what it's processing priority is (bosprrty), and whether or not it's a sub hub document (subhub).

bosspcat

The BOS specification attribute list provides the bosspec attribute for the HyTime document element. The bosspec attribute points to bosspec elements in the same document that modify the inclusion or exclusion of entities in the HyTime BOS.

bosspec

The BOS specification element form is used to irrevocably include or exclude an entity from the HyTime BOS. It is is used in hub or subhub documents and can modify any attribute declared in any document in the HyTime BOS.

datatok

The datatok element form is the data tokenizer grove constructor. It can be used to define data tokenizer groves not provided by the dataloc element form (which combines a data tokenizer with a list location).

dimpro

The dimension projector element form defines dimension projection functions.

expro

The extent projector element form defines extent projection functions. It replaces the original profun element form.

grovplan

The grove plan element form is used to define explicit grove plans for use by location address elements and with data entities to override their default grove plans.

hylink

The hyperlink element form provides the primary element form for representing hyperlinks. It differs from the original ilink form in that it uses separate attributes to address the anchors of the link, one for each anchor. The original clink and new agglink forms are derived from the hylink form.

impsrc

The implied location source attribute list provides new attributes defining the result when a location address element does not explicitly address its location source. An implicit location source can be the non-location address element that uses the location address (directly or indirectly through a location path) ("referrer"), the result of resolving an address made by the non-location address element that uses the location address ("referatt"), the principle tree root of the grove that contains the location address (i.e., the document element node), or the grove root. For queries, the location source can be implicit in the query itself.

linkloc

The hyperlink location address element form is a specialized form of query location address that addresses hyperlinks by link type.

mixedloc

The mixed location address element addresses whatever the location address elements in its content address. This enables the grouping of related location address elements together under a single ID, making it easy to create organized and re-usable multiple locations. The mixedloc form is the base from which the nameloc form is derived.

modgrp

The modifier scope group element form groups continguously-specified modifiers within a wand.

modified

The project modified or unmodified objects attribute controls whether or not projection is of modified or unmodified objects governed by baton or projector rules.

nmsploc

The name-space location address form can address nodes by name in any named node list in any grove. This provides a completely general name-space addressing method. It can be used as an alternative to named location address (nameloc) elements.

pgrovdef

The primary grove definition element form defines groves constructed from data that is not already in grove form (such as an SGML document). Grove definition elements enable explicit reference to groves (rather than relying on the implicit grove references that result from using data entities as location sources).

prorule

The projector rule element form associates events and event-like objects with projectors.

progrp

The projector scope group element form groups continguously-specified projectors within a schedule.

proseq

The projector sequence element form defines an ordered sequence of projectors, which will be applied in the order specified.

queryloc

The query location address element generalizes the use of non-HyTime-defined addressing notations within a HyTime framework. It replaces the original notloc (notation-specific location address) form. Query location addresses differ from notation-specific location addresses in that the results of resolving a queryloc query must be nodes in a grove. This makes all HyTime location addressing closed over nodes in groves while enabling the clean and clear integration of any addressing method into a HyTime framework.

refloc

The reference location address attribute list makes it possible to use any HyTime-defined location address method directly from attributes of otherwise non-location address elements (e.g., hyperlinks). Almost anything that can be done with HyTime indirect addresses can also be done directly with attributes using the reference location address facility. One of the implications of the reference location address facility is that it makes it possible to define any existing hyperlink element in terms of HyTime-defined facilities (although some element designs may require more effort to so define than others). When used with the query location address facility, any form of address can be used directly from elements meaningfully within a HyTime framework.

varlink

The variable link element form provides a third syntax choice for link representation. It differs from hylink and ilink by using subelements to define and address each anchor, rather than using attributes of the link element. It does not require that the anchor roles be fixed within a link type. The XML Link extended element form can be derived from the varlink form.

AFDRMeta

Notation for architectural DTDs that use the syntax extensions defined in clause A.3.4.3.

CHNYUAN

Yuan currency unit of China.

container

Container storage manager notation. Used for storage managers that use files to store other storage objects, such as TAR and Zip files.

datatok

Data tokenizer grove construction process notation. Used to construct groves from character strings. The basis from which the dataloc element form is defined.

dcnsm

Data content notation assocation storage manager. Manages the association of notations with their processors.

dimref

Dimension reference marker function notation.

EUC-JP

EUC-JP character encoding notation. Used with storage managers.

entuse

Entity usage notation. Used to provide the entity usage attributes for storage manager start tags in formal system identifiers.

fixed-2

Fixed-2 BCTF algorithm. Used with formal system identifiers.

fixed-3

Fixed-3 BCTF algorithm. Used with formal system identifiers.

fixed-4

Fixed-4 BCTF algorithm. Used with formal system identifiers.

gQuantum

Virtual measurement unit. Used in defining finite coordinate spaces.

GBRPOUND

Pound Sterling currency unit of United Kingdom.

global

Global storage manager, one whose system identifiers never need to be converted because they are not part of a real storage system.

HyBridN

The HyTime architectural bridging notation. This notation is used for architectural data entities, that is, data entities in client documents that are architectural with respect to the HyTime architecture.

HyAncLoc

HyTime hyperlink anchor location address notation. Provides a syntax for addressing hyperlink anchors by anchor role name. Used with the anchloc location address element form.

HyCalFun

HyTime calendar marker function notation.

HyCalSpc

HyTime calendar specification notation.

HyDatTok

The HyTime data tokenizer grove constructor notation. Used with the dataloc element form.

HyDimPro

HyTime dimension projector function notation..

HyDimSpec

The HyTime dimension specification notation. It is the fundamental notation for specifying dimensions in HyTime. All other dimension specification notations must be defined in terms of their translation to the HyDimSpc notation.

HyExtLst

The HyTime extent list specification notation.

HyExPro

HyTime extent projector function notation..

HyExSpc

The HyTime extent specification notation. This is the default notation for extent specifications.

HyFunk

The HyTime marker function notation. Provides the minimum functions needed to perform arithmetic on axis markers. The second edition's HyFunk is not the same as the HyFunk in the first edition.

HyGrand

HyTime granule definition notation. Defines the mathematical relationship between a granule and its measurement domain.

HyMrkLst

The HyTime marker list notation. It is the default notation for specifying axis marker lists.

HyLex

HyTime lexical model notation. The new version of HyLex, is similar to, but different from the original HyLex notation.

HyLexTok

The HyTime lexical tokenizer grove constructor notation. Used with the dataloc element form.

HyLnkLoc

HyTime hyperlink location address notation. Provides a syntax for addressing hyperlinks by link type. Used with the linkloc location address element form.

HyOrd

HyTime lexicographic ordering notation.

HyPro

HyTime projector function notation.

HyTime

The data content notation HyTime replaces the use of processing instructions for the declaration of use of the HyTime architecture and the specific modules and options used. See " 11.6, HyTime system declaration".

identity

Identity BCTF algorithm. Used with formal system identifiers.

IS8859-1

ISO 8859-1 character encoding notation. Used with storage managers.

IS8859-2

ISO 8859-2 character encoding notation. Used with storage managers.

IS8859-3

ISO 8859-3 character encoding notation. Used with storage managers.

IS8859-4

ISO 8859-4 character encoding notation. Used with storage managers.

IS8859-5

ISO 8859-5 character encoding notation. Used with storage managers.

IS8859-6

ISO 8859-6 character encoding notation. Used with storage managers.

IS8859-7

ISO 8859-7 character encoding notation. Used with storage managers.

IS8859-8

ISO 8859-8 character encoding notation. Used with storage managers.

IS8859-9

ISO 8859-9 character encoding notation. Used with storage managers.

literal

Literal storage manager notation. The system identifier is the replacement text for entities that use this storage manager.

localsm

Local storage manager notation. Used for storage managers that are local to a particular system, such as purpose-built document management systems.

md5

Content-MD5 Header Field. Used for "sealing" entities.

MIME

Multimedia Internet Mail Extensions container storage manager.

mimetype

MIME type storage manager. A MIME type storage manager manages the association between MIME types and their processors.

neutral

Operating system file storage manager.

osfd

Operating system file descriptor storage manager (e.g., "fd:0").

osfile

Operating system file storage manager.

REGEX

POSIX regular expression notation. Used in defining lexical models.

plaintxt

Plain text notation. Used in defining the plain text property set, used to inform the construction of groves from unstructured text (e.g., text files). Unlike the data tokenizer grove constructor, a plain text grove is simply a list of data characters.

portblsm

Portable storage manager. A storage manager for which the storage object identifiers are expected to be interpretable by a variety of systems.

SAME

Same encoding as the declaring document character notation. Used with storage managers.

sbento

Standard bento container storage manager.

SGML

The SGML notation is defined to have the public ID "ISO 8879:1986//NOTATION Standard Generalized Markup Language//EN". This notation is intended to be used for external data entities that are SGML documents. The primary groves constructed from data entities with this notation reflec the SGML property set. See " A.7, SGML property set".

SGMLGC

SGML grove construction process.

SIampere

Systeme International ampere (unit of electrical current). Used in defining finite coordinate spaces.

SIC

Systeme International celsius. Used in defining finite coordinate spaces.

SIcd

Systeme International candela (unit of luminous intensity). Used in defining finite coordinate spaces.

SIkelvin

Systeme International kelvin. Used in defining finite coordinate spaces.

SIkg

Systeme International kilogram. Used in defining finite coordinate spaces.

SImeter

Systeme International meter. Used in defining finite coordinate spaces.

SImole

Systeme International mole (unit of amount of substance). Used in defining finite coordinate spaces.

SIradian

Systeme International radian. Used in defining finite coordinate spaces.

SIsecond

Systeme International (metric) seconds. Used in defining finite coordinate spaces.

SIsr

Systeme International steradian. Used in defining finite coordinate spaces.

SJIS

SJIS character encoding notation. Used with storage managers.

tar

Tape archive and recovery container storage manager.

ThisOne

"This one" storage manager. Refers to the storage object in which the entity that uses this storage manager is declared.

UCS-2

UCS-2 character encoding notation. Used with storage managers.

UCS-4

UCS-4 character encoding notation. Used with storage managers.

UNICODE

Unicode character encoding notation. Used with storage managers.

URL

Uniform resource locator storage manager (that is, Web servers).

UTF-8

utf-8 character encoding notation. Used with storage managers.

UTF-16

utf-16 character encoding notation. Used with storage managers.

UTF-7

utf-7 character encoding notation. Used with storage managers.

virSpace

Virtual space measurement unit.

virTime

Virtual time measurement unit.

VTN

Value-to-node grove construction process notation. Used to construct groves from non-nodal properties of grove nodes so that HyTime location addresses can be used with them.

HyOp

The HyOp notation has been replaced by the reworked HyFunk notation (see "6.8.6 HyTime Marker Function Language (HyFunk) ").

HyQ

The HyTime query language has been eliminated. The Standard Document Query Language, published in the DSSSL standard (ISO/IEC 10179:1996) is the recommended query language, although you can use any query language within a HyTime framework.