Repository Design

From PhUSE Wiki
Jump to: navigation, search

Respository Design

Overview

The RDF/OWL files are going to be stored in a Source Controlled Repository; the question is how we want to store these? Currently the cdisc2rdf repository folder is essentially a dump, including the SDTM schema, Controlled Terminology and Meta Model Schema documents. The question stands; do we want to change this when we add the other content? Are we concerned about multiple teams trying to maintain multiple files in the same folder/repository?

A proposal

I think there could be an argument for a structure resembling the following:

 adam/
   import-files/*.xls
   ontology/*.[owl,rdf]
   doc/*.[doc,md]
 cdash/
   import-files/*.xls
   ontology/*.[owl,rdf]
   doc/*.[doc,md]
 prm/
   import-files/*.xls
   ontology/*.[owl,rdf]
   doc/*.[doc,md]
 send/
   import-files/*.xls
   ontology/*.[owl,rdf]
   doc/*.[doc,md]
 sdtm/
   import-files/*.xls
   ontology/*.[owl,rdf]
   doc/*.[doc,md]

The complicating factor is the shared meta-model-schema - this is shared by all the content; but we don't want to get silo'ed versions of it. Possibly the meta-model-schema could exist in a separate repository and each of the projects reference it, or have a development version in each version that gets merged prior to release.

When we deploy we could copy the relevant files into a common folder for released versions; so then the URL would be something like:

 http://rdf.cdisc.org/mms#
 http://rdf.cdisc.org/cdash-1-1#
 http://rdf.cdisc.org/stdm-3-1-2#

and for development versions (if required)

 http://rdf.cdisc.org/mms/mms#
 http://rdf.cdisc.org/cdash/cdash-1-1#
 http://rdf.cdisc.org/sdtm/stdm-3-1-2#

Anyhow, it was a thought. Feel free to express an opinion on the discussion page.