-
Notifications
You must be signed in to change notification settings - Fork 0
SIARD spec interoperability issues handling? #43
Copy link
Copy link
Open
Labels
DILCISQuestions that should be answered by the DILCIS BoardQuestions that should be answered by the DILCIS BoardquestionQuestions to the specificationQuestions to the specificationtools / implementationsIssues that relate to implementations of the SIARD format and not to the standard itselfIssues that relate to implementations of the SIARD format and not to the standard itself
Description
Metadata
Metadata
Assignees
Labels
DILCISQuestions that should be answered by the DILCIS BoardQuestions that should be answered by the DILCIS BoardquestionQuestions to the specificationQuestions to the specificationtools / implementationsIssues that relate to implementations of the SIARD format and not to the standard itselfIssues that relate to implementations of the SIARD format and not to the standard itself
Who is to decide on any interoperability issues?
This is related to #41 (DILCISBoard versus eCH-0165 SIARD-Formatspec).
The different Tool vendors may have divergent interpretation of elements in the latest SIARD spec.
Who is to decise on what is the correct interpretation?
And is this DILCISBoard SIARD the place to settle this?
Our common goal should be to be able to read any SIARD-package produced by any SIARD-tool using any SIARD-tool. But we are always facing chance of differences in interpretation, implementation and not the least that the different tools may not implement full support of all possible little details of the latest SIARD spec.