Import validation Sample Clauses

Import validation. The third level of conformance is less straightforward to define: the package must be imported by an eViP-compliant system in a meaningful way. It is best described in a set of desiderata. The bottomline is that an author has a clear profit from importing the package into the system. • After import, enough data must be available to the target author in order to start repurposing of the case in the new system. • Main sections of the VP package are recognised by the target VP system. After importing there is a clear separation of narrative/clinical data describing the case from data defining the activity model. • As a threshold for level 3 conformance will hold: it takes less time to import the case automatically than create it anew. • The package should not contain non-referenced items • Optional: selected fragments from the package can be automatically imported into the target proprietary VP model. The import process may be customised and controlled by the user allowing a pragmatic conversion between different system models (e.g while converting from a branched to linear model the system may display all available state nodes and the user selects manually the preferred path). Manual extensions are usually required to make the case logically consistent. It means that, for example, a simple import function written as an XSLT transformation that changes all text available in MVP XMLs elements into a long text string regardless of the semantics of elements would not fulfil those criteria. This third level of conformance does not only concern the exported VP packages but also states what eViP compliant systems should be able to do. This could result in a circular definition: a VP package is level-3 conform (meaning: is imported meaningfully) if an eViP- complaint system can import it meaningfully. To break the circle, eViP compliance has been defined as being able to import a set of standardised VP packages (i.e. the test suite) in a meaningful way.

Import validation. The bottom-line for the third level of conformance is that the author has a clear profit from importing the package into the system. It implies that the target VP player or authoring system extracts and imports the content in a relatively meaningful way.

Import validation. Tests on the third and fourth conformance level need to be verified in the context of the source and target VP system (in our case adequately OpenLabyrinth and CASUS). Guided by the checklist from the previous chapter we validate the imported package. Since we have already verified and corrected the package on the 1st and 2nd conformance level the import is accomplished without any errors or warnings. Nodes from OpenLabyrinth are imported as CASUS cards. After opening a card its content becomes visible and is legible and well positioned (Fig. 9).