The Modelling Team is responsible for clarifying the design rules, standard formats and features, and general purpose content for the DDI UML model. The Team works with business content teams and their leaders in order to instantiate DDI objects described in lion.ddialliance.org as UML classes and Functional Views. A subsidiary group within the Modelling Team is the Production Process and Tools Support group who are responsible for maintaining the Drupal tool atlion.ddialliance.org, supporting the capture of high level documentation as managed text and images, and creating the programing required to move content from the UML model expressed as XMI to the binding implementations (currently XML and RDF). The Modelling Team provides the completed package of output for development draft review and passes it to the DDI Technical Committee for release for review. The work of the Documentation Working Group is of major interest to this team.
Order relationships - abstract pattern, business rules for creating classes, applied usage
Provide Provide contents of Q2 2016 release to TC (2016-04 MT)[DMT-40, DMT-54]
Usage guide to modelers for Lion - packages, views, applying patterns, RDF equality, naming designation, related DDI elements, related GSIM objects (2016-04 WT, JJ, FR) [DMT-28, DMT-34, DMT-49]
Usage guides for creating metadata instances for each binding type (send to TC for completion 2016-04) - overlapping usage and binding specific usage patterns (commonalities and differences) (2015-12 WT)
High level documentation on production process - what happens during transformation steps and how this informs how this is effected by the model - differences in bindings (2016-06 OH)[DMT-23, DMT-45, DMT-50]
More specific documentation on the bindings - building on the documents from Copenhagen Sprint with a high level description (2016-04 OH)[DMT-51]
Metadata instances being able to roundtrip between bindings - rules need to be defined in both directions (2016-12 JW)[DMT-52]
Decide if round-tripping needs to involve the PIM or just the PSM/Bindings; determine what needs to get specified prior to Q2-2016 release - include used defined subset of UML document (Copenhagen) as input to discussion (2016-01 JW)
Design patterns - review of current and possible additional patterns (2016-09 JW, FR, WT)[DMT-32]
Codebook special release - requires working closely with the codebook team (2016-06 OH, WT, DG) [DMT-55]