xslt.transformations.ddi2xforms.drivers.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
The newest version!
The main Sequence activates the higher driver 'Form'.
The 'module' Sequence activates the 'Module' driver.
The 'submodule' Sequence activates the 'SubModule' driver.
The 'group' Sequence activates the 'Group' driver.
The d:ThenConstructReference elements activate the xf-group driver.
The d:ElseConstructReference elements activate the xf-group driver.
"Other – give details" activate the Clarification driver for "give details" in QuestionItem
"Other – give details" activate the Clarification driver for "give details" in QuestionGrid
A StatementItem activates the xf-output driver.
Most Instruction elements activates the xf-output driver.
The "FlowControl" ExternalAid of a Question is the Instruction for a GoTo leaving from the Question, so it activates the GoTo.
The Computation Item activates the control driver
Those DateTimeDomain elements activate the DurationDomain driver.
Those DateTimeDomainReference elements activate the DurationDomain driver.
Those DateTimeDomain elements (not duration) activate the DateTimeDomain driver.
Those DateTimeDomainReference elements (not duration) activate the DateTimeDomain driver.
The NumericDomain element activates the NumericDomain driver.
The NumericDomainReference element activates the NumericDomain driver.
Those TextDomain (250 chars max excluded) activate the TextDomain driver.
Those TextDomain elements (250 chars min) activate the TextareaDomain driver.
Those CodeDomain elements activate the CodeDomaindriver.
The NominalDomain element activates the BooleanDomain driver.
Those Code elements activate the xf-item driver.
Those Code elements activate the xf-item driver.
Those Code elements activate the TextCell driver.
Those Label elements activate the TextCell driver. It is placed at the top left of the Grid.
Those Label elements activate the TextCell driver. It is used as a header for the l:Code of the CodeList.
First dimension from 2-dimensions grid active the TextCell driver even if they don't have Label.
Those GridResponseDomain elements activate the Cell driver.
Those NoDataByDefinition elements which are not linked to a text activate the EmptyCell driver.
Those NoDataByDefinition elements which are linked to a text activate the FixedCell driver.
The QuestionItem elements with a single response activate the SingleResponseQuestion driver.
The QuestionItem elements with a StructuredMixedResponseDomain activates the MultipleQuestion driver.
Those d:QuestionGrid aren't fixed, it is possible to add rows, they activate the 'TableLoop' driver.
Those d:QuestionGrid aren't fixed, it is possible to add rows. The d:StructuredMixedGridResponseDomain activate a RowLoop driver to do so.
Those d:QuestionGrid are 'fixed', they activate the Table driver.
The d:QuestionGrid corresponding to MultipleChoiceQuestion
The d:Loop element activates the QuestionLoop driver.
Group of Variable (based on an Instrument or a loop until now)
Variable (collected + calculated + external)
A GenerationInstruction activates the CalculatedVariable driver.