Crosswalker Core Tool Workflow

(See CrossWalker page for more detailed specs and files)

In diagram above:

• crosswalker.xsl and kv2epidoc.xsl are the core CrossWalker scripts
• hgv2kv.xml and hgvkv2epidoc.xml are local, user-defined files (for "hgv" substitute name of local project/schema)
• HGV.xml is the input file
• all other files are generated by the process and therefore should not need hand-editing at any stage

The elements:

1. hgv2kv.xml
1. (local file)
2. defines the key value pairs (data fields or elements) that are to be exported from the source database/schema
3. may include element definitions, copy or combine instructions, or XSLT 2.0 templates
2. crosswalker.xsl
1. (core xWalker script)
2. a stylesheet that acts upon hgv2kv.xml and creates hgv2kv.xsl
3. hgv2kv.xsl
1. (generated)
2. a stylesheet that acts upon HGV.xml (the database dump) to create epidocHGV.xml
3. at this stage a runner.sh may also be generated if Transcode, CHET-C, or other processes also need to be run (e.g. on epigraphic text field, translation)
4. epidocHGV.xml
1. (generated)
2. an XML file containing the key value pairs in the form of variables needed for import into EpiDoc XML
5. hgvkv2epidoc.xml
1. (local file)
2. a template defining the placement of key values into EpiDoc XML (context + variables)
6. kv2epidoc.xsl
1. (core xWalker script)
2. ...

 Create your own educational wiki!HelpPublic, not yet premium Privacy Policy RSS