Models: Amsterdam - components

• The Amsterdam Hypertext Model (AHM) extends the Dexter model by adding in handling of more complex composites, that have several components making up a composite node.
• AHM does even more to extend the Dexter model by adding in handling of time-based information, such as the timing relationships between components of a composite, that describe synchronization in terms of hypertext links or arcs. Ex., a relationship might indicate that the From-Component precedes the To-Component.
• AHM composites have children as components, that may be presented together (in parallel, such as a text block and matching image) or selected from (e.g., pick one of several language tracks).
• Each component must have its own local ID as well as when it should be started, relative to the start of the composite.
• Anchors can be into components, in which case they are indirectly specified by giving the ID of the anchor in the desired component, so following the link calls for looking up the anchor in the data structure of the component.

The Dexter model does not include Synchronization Arcs or Start Time for children and usually does not even include Composite Type.