<noun devi Goddess> <exclamation aum Om> <verb namo I-bow> <noun deva God> <? N[(.*)(a)/$1esha of-pl.Ns> <adj para greater> <? Adj[(.*)(a)]/$1aat the-most-Adj> <noun jagat world> <noun guru teacher> <adj sadaa auspicious> <personal_name shiva Shiva> <adj mahaa great> <noun diikshaa initiation> <verb pradehi give> <pron me to_me> </dictionary> ------------------------------------------------------------------- ---------------------------- A TG with ---------------------------- --------------------- bits of a movie in tiers -------------------- ------------------------------------------------------------------- Examples: A movie represented in the following form: <node id="MovieStart">file:movie.mp4<node id="MovieEnd"> is a Document comprising a single tier. Retaining and elaborating that segmentation, further segmenting it into scenes, one may add to the above Document a second tier, perhaps in a second file, for example: <node id="MovieStart"> <node id="#credits"> t=0.0,120.5 <node id="#opening"> t=120.5,240 <node id="#development"> t=240,1440 <node id="#denouement"> t=1440,4000 <node id="#closing_credits"> t=4000,4200 <node id="MovieEnd"> Observe how the nodes from the first tier carry over into and remain consistent in the second tier. '#x' and 'x#' are convenient notations intended to refer to a node or boundary on one side or another of content labelled x. Further, the times in these arcs are interpreted within a given context, here, an mp4 file specified on another tier, which gives the time-pairs meaning as segments containing specific content. Separately, consider a set of image files enumerated by file name in a listing file, separated by named <node>s. That would be another definition for a Document, including some content by reference. <node id="#ImageArchive"> <node id="#1">img_001.jpg <node id="#2">img_002.jpg .. <node id="ImageArchive#"> Associated with the ImageArchive Document, one might enumerate as a more fine-grained Tier a set of bounding boxes, in a certain order, to be understood as located within the segment's associated image, each box bounding all the pixels associated with a character glyph. That enumeration would be a tier of an elaboration of the previous ImageArchive Document. An added tier, drafted by image processing algorithm, corrected by a human, might be a sequence of character-sized arcs between character-bounding nodes, this tier representing the transcription of the imaged page. Stripped of <node> annotations, it is equivalent or identical to the digitized text of the image.

Examples of TGs: ------------------------------------------------------------------- ---------------------------- A TG with ---------------------------- -------------- verse-by-verse and word-by-word tiers -------------- ------------------------------------------------------------------- kailaasashikhare ramye bhaktisa~dhaananaayakam praNamya paarvatii bhaktyaa sha~kara~ paryaprchchhata shrii devyuvaacha aum namo devadevesha paraatpara jagadguro sadaashiva mahaadeva gurudiikshaa~ pradehi me suuta uvaacha etc. ------------------------------------------------------------------- ---------------------- and some ancillary data -------------------- ------------------------------------------------------------------- <noun devi Goddess> <exclamation aum Om> <verb namo I-bow> <noun deva God> <? N[(.*)(a)/$1esha of-pl.Ns> <adj para greater> <? Adj[(.*)(a)]/$1aat the-most-Adj> <noun jagat world> <noun guru teacher> <adj sadaa auspicious> <personal_name shiva Shiva> <adj mahaa great> <noun diikshaa initiation> <verb pradehi give> <pron me to_me> </dictionary> ------------------------------------------------------------------- ---------------------------- A TG with ---------------------------- --------------------- bits of a movie in tiers -------------------- ------------------------------------------------------------------- Examples: A movie represented in the following form: <node id="MovieStart">file:movie.mp4<node id="MovieEnd"> is a Document comprising a single tier. Retaining and elaborating that segmentation, further segmenting it into scenes, one may add to the above Document a second tier, perhaps in a second file, for example: <node id="MovieStart"> <node id="#credits"> t=0.0,120.5 <node id="#opening"> t=120.5,240 <node id="#development"> t=240,1440 <node id="#denouement"> t=1440,4000 <node id="#closing_credits"> t=4000,4200 <node id="MovieEnd"> Observe how the nodes from the first tier carry over into and remain consistent in the second tier. '#x' and 'x#' are convenient notations intended to refer to a node or boundary on one side or another of content labelled x. Further, the times in these arcs are interpreted within a given context, here, an mp4 file specified on another tier, which gives the time-pairs meaning as segments containing specific content. Separately, consider a set of image files enumerated by file name in a listing file, separated by named <node>s. That would be another definition for a Document, including some content by reference. <node id="#ImageArchive"> <node id="#1">img_001.jpg <node id="#2">img_002.jpg .. <node id="ImageArchive#"> Associated with the ImageArchive Document, one might enumerate as a more fine-grained Tier a set of bounding boxes, in a certain order, to be understood as located within the segment's associated image, each box bounding all the pixels associated with a character glyph. That enumeration would be a tier of an elaboration of the previous ImageArchive Document. An added tier, drafted by image processing algorithm, corrected by a human, might be a sequence of character-sized arcs between character-bounding nodes, this tier representing the transcription of the imaged page. Stripped of <node> annotations, it is equivalent or identical to the digitized text of the image.