Tutorial User Guide > Authoring Tutorial Applications > Definitions
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
Definitions
SGML - Standard Generalized Markup Language.
HTML - Hypertext Markup Language; a specific subset implementation of SGML.
XML - Extensible Markup Language, an enhanced SGML implementation employing HTML like tags.
Tags - used in HTML and XML to identify elements according to their content and purpose. The following is an XML tag:
<step stepid="2." stephelp="brakeparts/html/st2help.html">
For XML tag definitions, see XML Tag Definitions, 48.
For HTML tag definitions, see Supported HTML Tags and Options, 57.
Elements/Attributes - parts of a tag (in the above example, "step" is an element; "stepid" and "stephelp" are attributes).
.png - And image file format where png is an acronym for portable network graphics file. This file format is a good replace for the older and obsolete .gif file format.
Drive Page - a file with a .xml extension which scripts the work flow, sending control to sub-pages for common or repetitive tasks.
State Table - persistent memory method of recording and retrieving information
Automated Link Rules - used in the drive page to make automated hypertext-like links to the correct starting HTML dialog for each step.
Step- A scripted analysis process is divided up into manageable units called “steps”. The Tutorial software provides process control by presenting steps as defined by an expert author through the XML <step> tags. Steps may have enforced prerequisites to their execution. A step may hold the user captive in that part of the application until it is successfully completed.
Dialog- A new display event in the Tutorial interface results from the transition to a new “dialog”. A dialog always has a “mini web page” HTML display associated with it. The philosophy of a Tutorial application is that the interface is always talking to the user, giving clear instructions about what to do next. A dialog event is encoded in XML through the <dialog> tag. A step may have several dialogs. The author has available several logic processing operations for controlling the transition between dialogs including the automated link rules.
Page- In the context of this document, the word “page” refers to a physical file as opposed to one display event. A single drive page may contain several steps and many diaogs encoded in XML. Therefore, from one XML page written by the author, numerous separate displays can be shown on the user interface.