Monday, October 17, 2016

Morning

Session 1 (plenary):  Introductions, goals of the workshop, and overall introduction to DDI

Introduction of participants

Introduction to DDI

Session 2 (plenary): Presentations from external experts on specific specifications or usage of specifications.

External presentations:

Afternoon

Session 3 (plenary): Presentations from external experts on specific specifications or usage of specifications.

External presentations:

Session 4 (plenary): Discussion of interoperability

Interoperability

Evening:

Possible evening session - Topic to be determined

Tuesday, October 18, 2016

Morning

Session 1 (plenary): Discussion of interoperability

Session 2 (working groups):

Session 2A:  Business scenario:  Situations where we would use different standards together

Session 2B:  Common Aspects of all specifications present during Data Description

Afternoon

Session 3 (working groups):

Session 3A:  Provenance of data, metadata

Outcome: A common definition / understanding of provenance for the purpose of this workshop

Session 3B:  Design patterns 

Outcome:  document outlining:

Session 4 (working groups):

Session 3A continued: Provenance of data, metadata

Session 3B continued:  Design patterns


Evening:

Possible evening session - Topic to be determined


Wednesday, October 19, 2016

Morning

Session 1 (working groups):

Session 1A:  Bindings of DDI, CDISC, HL7/FHIR, SDMX, GSIM, CSV on the Web


Session 1B:  Operations (Protocols)  with specifications, i.e. REST with DDI, CDISC, HL7/FHIR, SDMX, GSIM, CSV on the Web (Part 1)

Outcome:  document contrasting the approaches used to interchange protocols (REST, SPARQL, SOAP, etc..) by the different specifications; Proc and cons of having standard interfaces as part of the specification and the rationale

Session 2 (working groups):

Session 1A continued:  Bindings of DDI, CDISC, HL7/FHIR, SDMX, GSIM, CSV on the Web 

Session 1B continued:  Operations (Protocols)  with specifications, i.e. REST with DDI, CDISC, HL7/FHIR, SDMX, GSIM, CSV on the Web


Session 2 (plenary): 

Discussion – to determine if there is a consensus view of which bindings/protocols should be used; what does this picture look like?  (Current and future perspective - possible developments)

Afternoon

Session 3 (working groups):

Session 3A:  Provenance of data/metadata  (Data production)

How to record provenance; Can PROV-O describe other process models such as GSBPM/GLBPM?  How can the ideas of PROV-O be used in non-RDF bindings? 

 Outcome: 


Session 3B:  Provenance of data/metadata – RDF  (Data publication)

Goal: best practice for using PROV-O with other Specs

 Outcome: 

Session 4 (plenary):

Plenary session for groups to report back to exchange findings and open discussion

 Outcome:  Extension of provenance definition document to include:

Evening:

Possible evening session - Topic to be determined

Thursday, October 20, 2016

Morning

Session 1 (working groups):

Session 1A:  RDF bindings for statistical data and metadata

Outcome: document describing the requirements and best practices for use of RDF vocabularies in statistical applications

Session 1B:  Data description, general mapping table of multiple specifications with equal and similar items 

Outcome: document outlining the relationship of different standards for data description

Session 2 (working groups):

Session 1A continued:  RDF bindings for statistical data and metadata

Session 1B continued:  Data description, general mapping table of multiple specifications with equal and similar items

Afternoon

3rd Session (plenary):

Session 3A:  DD-R package


Session 3B:  RESTful


4th Session (working groups):

Session 4A:  RDF Bindings and Production framework with Elisa Kendall - via remote

Session 3A continued:  DD-R Package

Session 3B continued:  RESTful


Friday, October 21, 2016

Morning

1st Session (working groups):

Session 1A:  Start the conversation for future collaboration – create a small working group to work out the details

Session 1B:  Statement of design principles to be agreed by specs represented (Data Manifesto)

 Outcome:

The outline and draft of agreed design principles (“Data Manifesto”)

2nd Session:


Afternoon

3rd Session (plenary):