![JAR search and dependency download from the Maven repository](/logo.png)
xslt.pre-processing.ddi.multimodal-selection.xsl Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of eno-core Show documentation
Show all versions of eno-core Show documentation
Eno is a tool that generates survey questionnaires starting from their formal description in DDI
This xslt stylesheet is used before the dereferencing step.
The purpose is to keep the relevant components for the target output.
In its current form, it only works for multi-modal declarations.
The output format provided by the call to the transformation
The parameter file used by the stylesheet.
The mode parameter is stored in a variable.
Root template.
Default template for every element and every attribute, simply copying to the
output.
This template is meant to keep instructions if and only if the Instruction (AFTER_QUESTION_TEXT in Pogues) is meant to
be kept for the mode
Rules are as follow :
- all mode (ddi and fodt output) to keep everything
- papi mode (Fo output) only keeps SelfAdministeredQuestionnaire.Paper
- cawi mode (Xforms output and some Lunatic output) only keeps SelfAdministeredQuestionnaire.WebBased
- cati mode (some Lunatic output) keeps Interview.Telephone.CATI
- capi mode (some Lunatic output) keeps Interview.FaceToFace.CAPIorCAMI
- process mode (some Lunatic output) keeps everything (so for now, same as all)
Since Fo and Xforms keep only one type of Instruction, the InstructionName items
describing the collcetion mode can be deleted
Since Lunatic keeps everything but SelfAdministeredQuestionnaire.Paper, InstructionName
items need to be kept to decide later what to valorize depending on the collection
mode
To allow compatibility with older ddi, an Instruction with no match with an
InstructionName describing a collection mode shall be kept
This template is meant to keep instructions if and only if the StatementItem (BEFORE_QUESTION_TEXT in Pogues) is meant to
be kept for the mode
Rules are as follow :
- all mode (ddi and fodt output) to keep everything
- papi mode (Fo output) only keeps SelfAdministeredQuestionnaire.Paper
- cawi mode (Xforms output and some Lunatic output) only keeps SelfAdministeredQuestionnaire.WebBased
- cati mode (some Lunatic output) keeps Interview.Telephone.CATI
- capi mode (some Lunatic output) keeps Interview.FaceToFace.CAPIorCAMI
- process mode (some Lunatic output) keeps everything (so for now, same as all)
Since Fo and Xforms keep only one type of Instruction, the InstructionName items
describing the collcetion mode can be deleted
Since Lunatic keeps everything but SelfAdministeredQuestionnaire.Paper, InstructionName
items need to be kept to decide later what to valorize depending on the collection
mode
To allow compatibility with older ddi, an Instruction with no match with an
InstructionName describing a collection mode shall be kept
This template is used to NOT copy the InstructionName specifying the mode -> else it makes Eno crash in further treatment of instructions
Later, it might be overloaded to rather keep that information for some cases (all ? process ?) so it might be valorized
Thus the idea now is : the Instruction to keep for the mode specified have been filtered by the previous template
And the template below will delete (for those kept Instruction) the InstructionName in the DDI referring to the mode
This template is used to NOT copy the ConstructName specifying the mode -> else it might make Eno crash in further treatment of instructions
Later, it might be overloaded to rather keep that information for some cases (all ? process ?) so it might be valorized
Not necessary as with InstructionName, but keeps things tidier
© 2015 - 2025 Weber Informatics LLC | Privacy Policy