integrate validation into data workflow

[dasch124]

incl.
RNG Schema + Schematron
Audio location

[dasch124]

on tei:w (i.e. in text documents):

• reference to <fs> in annotation document via @ana
• ensure that text() = $featureStructure/tei:f[@name='trans']

NB there's some boilerplate code already at https://github.com/acdh-oeaw/vicav-content/blob/master/tools/802_tei_odd/vicav_dicts.odd#L193

on tei:fs in annotation document (assuming that we have implemented #5):

• reference to <entry> in SHAWI dictionary via tei:f[@name='dict']/substring-after(@fVal,'dict:')
• ensure existence of doc($path-to-fLib.xml)//tei:fs[@xml:id = $featureStructure/tei:f[@name = 'pos']/substring-after(@fVal,'fLib:') [i.e. repeated as $fLibEntry below]
• ensure that $fLibEntry = $entry/tei:gram[@type='pos'] (CHECKME pos info in dict might be using a different syntax than flib - e.g. "pos.n" in flib vos "n" in dictionary)
• ensure that $featureStructure/tei:fs[@name = 'root']/tei:string = $entry/tei:gram[@type='root']

[TODO add other things like TEI header validation or audio reference integrity]

[dasch124]

Probably we need several validation reports depending:

• Annotation document errors
• Annotation errors
• Dictionary errors

[dasch124]

@charlymo has recently added a functionality to use BaseX for validation. We should re-use this method to validate the texts during annotation.