[BACK]Return to soft-cgi.tex CVS log [TXT] [DIR] Up to [Repository] / texttool-architecture

Diff for /texttool-architecture/soft-cgi.tex between versions 1.8 and 1.9

version 1.8, 2004/01/13 11:01:18 version 1.9, 2004/01/13 11:26:11
Line 49  The input metadata file must have the fo Line 49  The input metadata file must have the fo
 \paragraph{plan of this section }  \paragraph{plan of this section }
   
 \begin{enumeration}  \begin{enumeration}
   \item An overview of toc.cgi architecture
 \item A walk-through of typical cgi queries for toc.cgi  \item A walk-through of typical cgi queries for toc.cgi
 \item An index of cgi parameters and values with short descriptions of function  \item An index of cgi parameters and values with short descriptions of function
 \end{enumeration}  \end{enumeration}
   
 \paragraph{}  \paragraph{Overview of toc.cgi architecture}
   
   \subparagraph{}
 toc.cgi is a perl script for displaying collections of xml texts and   toc.cgi is a perl script for displaying collections of xml texts and 
 linking them to related resources such as page-images, morphological  linking them to related resources such as page-images, morphological
 analysis, commentaries, dictionaries, etc. It implements generic methods  analysis, commentaries, dictionaries, etc. It implements generic methods
 for resource-linking provided by a series of perl modules which are in  for resource-linking provided by a series of perl modules which are in
 turn based mainly on generic tools for xml manipulation and networking  turn based mainly on generic open-source tools for xml manipulation and networking
 written in C.   written in C. 
   
   \subparagraph{toc.cgi collections--Network transparency}
   Each of the collections in toc.cgi is a ``virtual'' collection, that
   is, a collection of links or uri's to resources that reside somewhere on an accessible
   network, local or remote.  
   
   \subparagraph{toc.cgi collections--remote resources}
   
   What is at the other end of the link is of no concern to toc.cgi, as
   long as the resource referenced by the link meets minimal toc.cgi
   requirements--how the resource is actually implemented and exposed is
   a matter for the resource provider. The link may, for instance, point
   directly to an xml text or it may point to a container which exposes a
   particular xml view of an underlying resource that is perhaps not in
   xml format at all. 
   
   
   \subparagraph{resource registry}
   
   
   
   
 \paragraph{cgi parameters -- standard queries}  \paragraph{cgi parameters -- standard queries}
   
 \htmladdnormallink{ http://archimedes.mpiwg-berlin.mpg.de/cgi-bin/toc/toc.cgi?step=corpus }{ http://archimedes.mpiwg-berlin.mpg.de/cgi-bin/toc/toc.cgi?step=corpus }  \htmladdnormallink{ http://archimedes.mpiwg-berlin.mpg.de/cgi-bin/toc/toc.cgi?step=corpus }{ http://archimedes.mpiwg-berlin.mpg.de/cgi-bin/toc/toc.cgi?step=corpus }
Removed from v.1.8  
changed lines
  Added in v.1.9

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>