X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Frecordmodel-alvisxslt.xml;h=8df95b94ba580e1026657e66a2d1c48fa864470d;hb=e7ac5d718e802430433faca1e4f040b2cfcf4977;hp=8eee9b945e25690bf962824ddb914766e78b1797;hpb=b00064c85119fb3a6ca07f809f41d8f97f192165;p=idzebra-moved-to-github.git diff --git a/doc/recordmodel-alvisxslt.xml b/doc/recordmodel-alvisxslt.xml index 8eee9b9..8df95b9 100644 --- a/doc/recordmodel-alvisxslt.xml +++ b/doc/recordmodel-alvisxslt.xml @@ -1,14 +1,16 @@ - - + + ALVIS &xml; Record Model and Filter Module - + The functionality of this record model has been improved and - replaced by the DOM &xml; record model. See - . + replaced by the DOM &xml; record model, see + . The Alvis &xml; record + model is considered obsolete, and will eventually be removed + from future releases of the &zebra; software. - + The record model described in this chapter applies to the fundamental, @@ -116,8 +118,7 @@ <?xml version="1.0" encoding="UTF-8"?> <z:record xmlns:z="http://indexdata.dk/zebra/xslt/1" z:id="oai:JTRS:CP-3290---Volume-I" - z:rank="47896" - z:type="update"> + z:rank="47896"> <z:index name="oai_identifier" type="0"> oai:JTRS:CP-3290---Volume-I</z:index> <z:index name="oai_datestamp" type="0">2004-07-09</z:index> @@ -134,7 +135,7 @@ This means the following: From the original &xml; file one-record.xml (or from the &xml; record &dom; of the - same form coming from a splitted input file), the indexing + same form coming from a split input file), the indexing stylesheet produces an indexing &xml; record, which is defined by the record element in the magic namespace xmlns:z="http://indexdata.dk/zebra/xslt/1". @@ -146,10 +147,10 @@ we see that this records is internally ordered lexicographically according to the value of the string oai:JTRS:CP-3290---Volume-I47896. - The type of action performed during indexing is defined by + In this example, the following literal indexes are constructed: @@ -166,7 +167,7 @@ file default.idx will do). Finally, any text() node content recursively contained inside the index will be filtered through the - appropriate charmap for character normalization, and will be + appropriate char map for character normalization, and will be inserted in the index. @@ -179,7 +180,7 @@ will be inserted using the w character normalization defined in default.idx into the index dc:creator (that is, after character - normalization the index will keep the inidividual words + normalization the index will keep the individual words kumar, krishen, and, calvin, burnham, and editors), and @@ -208,7 +209,7 @@ ]]> or the proprietary - extentions x-pquery and + extensions x-pquery and x-pScanClause to &sru;, and &srw; @@ -246,7 +247,7 @@ . Obviously, there are million of different ways to accomplish this task, and some comments and code snippets are in order to lead - our paduans on the right track to the good side of the force. + our Padawan's on the right track to the good side of the force. Stylesheets can be written in the pull or @@ -255,12 +256,12 @@ the internal structure of the &xslt; stylesheet, and portions of the input &xml; are pulled out and inserted into the right spots of the output &xml; structure. On the other - side, push &xslt; stylesheets are recursavly + side, push &xslt; stylesheets are recursively calling their template definitions, a process which is commanded - by the input &xml; structure, and avake to produce some output &xml; - whenever some special conditions in the input styelsheets are + by the input &xml; structure, and are triggered to produce some output &xml; + whenever some special conditions in the input stylesheets are met. The pull type is well-suited for input - &xml; with strong and well-defined structure and semantcs, like the + &xml; with strong and well-defined structure and semantics, like the following &oai; indexing example, whereas the push type might be the only possible way to sort out deeply recursive input &xml; formats. @@ -285,8 +286,7 @@ - + @@ -319,14 +319,14 @@ that the names and types of the indexes can be defined in the indexing &xslt; stylesheet dynamically according to content in the original &xml; records, which has - opportunities for great power and wizardery as well as grande + opportunities for great power and wizardry as well as grande disaster. The following excerpt of a push stylesheet might be a good idea according to your strict control of the &xml; - input format (due to rigerours checking against well-defined and + input format (due to rigorous checking against well-defined and tight RelaxNG or &xml; Schema's, for example): - + @@ -370,9 +370,9 @@ ]]> Don't be tempted to cross - the line to the dark side of the force, paduan; this leads + the line to the dark side of the force, Padawan; this leads to suffering and pain, and universal - disentigration of your project schedule. + disintegration of your project schedule. @@ -428,12 +428,12 @@
ALVIS Filter &oai; Indexing Example - The sourcecode tarball contains a working Alvis filter example in + The source code tarball contains a working Alvis filter example in the directory examples/alvis-oai/, which should get you started. - More example data can be harvested from any &oai; complient server, + More example data can be harvested from any &oai; compliant server, see details at the &oai; http://www.openarchives.org/ web site, and the community @@ -453,72 +453,6 @@ - - - -