ZedDist Spec Terminology
From zedwiki
Contents |
General
Profile
A profile is a definition of a concrete DTB fileset, as defined by the activated Profile Composition Modules and supported features.
Feature
A feature is a functionality add-on to a Profile that provides support for specialized constructs, such as mathematical formulas and graphic rendering. A feature extends a DTB grammar by injecting a set of concrete contributions to the DTB logic along with its associated normative and informative prose.
Profile Composition Modules
The Profile Composition Modules contain the unique functionality sets that underpin profile defnitions. The characteristics of the modules define the maximum amount of variability between profiles, and inversely, a set of traits that all profiles must share.
Module
Profile Composition Module (was: component)
Resource directory
A package of information regarding a profile or feature, including normative schemas, informative schemas, RDF vocabularies, documentation, stylesheets, or other associated resources. Resource directories are expressed in XHTML+RDFa (per [RDFa]).
Reading System
The hardware/software platform that renders the contents of a DTB to a reader.
Schema Module
An abstract unit within a markup model expressed as a schema fragment, used to consolidate markup declarations to increase the flexibility, modifiability, reuse and understanding of specific logical or semantic structures.
Compostion Module Definitions (recurring subheads)
Purpose
Description
Inclusion
Not necessary in specification? Profiles aren't open for creation
Defines
Possibly merge with purpose into informative prose
Extension Points
Slots which the Profile creator may activate to allow injection of "foreign" constructs dynamically in instances. In a concrete Profile, these extension points are typically used as slots for optional Features.
Dependencies
The inclusion of Component X in a Profile may be dependent on (a specific aspect of) Component Y to also being included. Component X is responsible to declare these dependencies.
Actions at profile creation time
Composition Framework
Needed for internal composition of profiles?
