DDI 4 Sprint in Toronto, June 2014

Introduction

We started with the concept for a production workflow as designed in the previous sprint in Vancouver (figure 1) and identified a couple of issues (documented in the Wiki: IASSIST sprint, technical group). Because we were able to solve most of these issues during the sprint, this document focuses on only a subset of issues where the solution is important to document for subsequent work.

Out of our 11 issues, we selected one as our overall goal for this sprint: to produce a working prototype for the production workflow to prove the overall concept.

Figure 1: Production system as designed in Vancouver (deprecated)

Issues discussed

Identifiers

...

Formats other than XSD and OWL will not be part of the official standard specification. Nevertheless, we like to provide basic support for other formats (e.g. SQL, Java, C#, JSON). There will be a discussion within the DDI developers group to prioritize possible formats.

Some work on the combined use of SQL and Java has already been done.

Single source of information

...

After substantial discussion of the production workflow (Vancouver version) we did some modifications to the design, documented in figure 2.

Figure 2: Production system as designed in Toronto

Handling updates in Drupal and EA

...

EA can version per package. XMI is used as transport format between EA and version control repository.

Figure 3: Using Drupal and EA with one central repository

Drupal could use the version control repository as source for the own data base tables.

...