Similar to #47, but not on the record as a whole, but individually per DTS Resource object. This would widen the possibilities extremely.
Think of a Resource, which is a TEI document with a critical apparatus, which has all the text witnesses as DTS members (nested DTS Resources, if that is possible at all). Instead of keeping a separate TEI file for every member, we could produce them by passing runtime parameters to configured the transformation. At least for TEI-XML output, this would mean, that we need to also select the transformation per record, because unnesting a witness from a critical edition is not part of DTS Transformation's default document.xsl.
This issue is only for introducing the overall data model and beans for accessing the information. There should be extra issues for
- selecting transformations per record
- passing config options per record
- passing runtime parameters per record
Similar to #47, but not on the record as a whole, but individually per DTS Resource object. This would widen the possibilities extremely.
Think of a Resource, which is a TEI document with a critical apparatus, which has all the text witnesses as DTS members (nested DTS Resources, if that is possible at all). Instead of keeping a separate TEI file for every member, we could produce them by passing runtime parameters to configured the transformation. At least for TEI-XML output, this would mean, that we need to also select the transformation per record, because unnesting a witness from a critical edition is not part of DTS Transformation's default
document.xsl.This issue is only for introducing the overall data model and beans for accessing the information. There should be extra issues for