CollectionsBackground.zipDDICollections.docx
Tipsection |
---|
Info |
---|
icon | false |
---|
title | Purpose of the Modelling Team |
---|
| Meeting Minutes |
Section |
---|
Column |
---|
| Panel |
---|
title | What does this team do? |
---|
Description: The role of the modelling team is to work with package teams 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 on 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 at lion.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 (in Enterprise Architect), XML, and RDF. The work also includes review of modeling work done by others and creation of the beta packages for review and approval by the DDI Alliance members. Tasksmodel 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. |
Panel |
---|
borderColor | red |
---|
borderWidth | 3 |
---|
borderStyle | solid |
---|
| |
|
Section |
---|
Column |
---|
|
Panel |
---|
borderColor | green |
---|
titleColor | black |
---|
borderWidth | 3 |
---|
titleBGColor | lightgreen |
---|
borderStyle | solid |
---|
title | Current Activities: |
---|
| - Order relationships - abstract pattern, business rules for creating classes, applied usage
- 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]
|
Panel |
---|
borderColor | blue |
---|
titleColor | black |
---|
borderWidth | 3 |
---|
titleBGColor | lightblus |
---|
borderStyle | solid |
---|
title | Final modelling documents |
---|
|
|
Panel |
---|
title | this documents list needs to be sorted into final and discussion and moved accordingly |
---|
|
Documents | Progress so far |
---|
Process Collections | Proposal (Draft) | Communications Document for Content Modellers | Needs Review | Overall advice from TC on items below | Report to Modelers | Relating to other standards | Proposal | Web services | Proposal | Identification | Proposal | Containership and Reference: Rules for defining when an object is contained as a property or referenced and what the reference structure includes | see TC minutes | Grouping: Mechanism for grouping metadata for management purposes | see TC minutes | Administrative metadata: DDI 3.2 administrative metadata (non-payload) | Proposal | Name,Label, Description: Registry based information ISO 11179-5 | Proposal see TC minutes | Summary of Actions Requested by TC as of 2014-10-27 | see Proposal | Collection/Group Proposal from TC 2014-11-11 (modeling issue raised in | EmailChain |
| Column |
---|
| Panel |
---|
| Updated 2014-11-05: Regular meeting time for Modelling team. The meeting will take place at EVERY Wednesday at 0600 Minneapolis, 0700 Ottawa, 1200UK, 1300 CET, 2300 Canberra. Please indicate which day of the week suits you best. Meeting dates: Weekly Instructions to join the meeting: 1. Please join my meeting. https://www3.gotomeeting.com/join/731015190 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United States: +1 (646) 749-3117 Australia: +61 2 8355 1035 Belgium: +32 (0) 42 68 0154 Canada: +1 (647) 497-9373 Denmark: +45 (0) 89 88 04 29 France: +33 (0) 182 880 932 Germany: +49 (0) 811 8899 6930 New Zealand: +64 (0) 9 801 0292 Norway: +47 21 01 89 06 Sweden: +46 (0) 852 500 288 United Kingdom: +44 (0) 20 7151 1816 Access Code: 731-015-190 Audio PIN: Shown after joining the meeting Meeting ID: 731-015-190 Image RemovedPending Decisions (dates in () refer to minutes): - Identification - Structure
- Identification - RDF Serialization strategy
- Properties and Relationships - what defines something as an extended primitive
- Relationship objects - Administrative objects
- Relationship objects - is there a sub-set that are not "managed" but need identifiers
- Relationship objects - support for late binding
- Former Name, Label, Description - Decision
- Collection/Grouping - Structure (TC needs to submit)
- Collection/Grouping - Structure (decision)
- Classification - objects in Conceptual - view is March release
- Rules for naming - document
- Object_Universe_Population - applied usage (07-24)
- Identifying equivilent objects in other namespaces - Drupal (08-20)
- CodeValueType (in binding or not) (09-17)
- What objects do not trigger versioning (administrative)
Action Items: -
Classification issue - pending Hilda's responseJon to review from documentation perspective -
Review conceptual changes from Dagstuhl -
Rules for modeling - communciation document (Barry) -
Documenting use of process model Identification - have John Kunze's response - follow-up -
Namespaces - points of contact in other namespaces -
Implement decisions on identification, properties, and relationship types -
Renaming objects with foreign namespace -
Act on issues for Agent (09-24) -
Act on issues for Discovery View - (10-01) -
Act on issues for Conceptual (09-17) -
Review Process package - identify issues -
Act on issues for Process Paper on process - (07-24) -
Checklist for a prototype (08-20) -
Cross review for consistency (08-20) -
Formalize decision about related standards (08-20) -
Document technical workflow from Drupal to Bindings (08-20) -
Create a game plan (08-27) -
Finalize structure of library (see 09-24) -
Clarify package namespaces in Drupal and consolidate where needed (09-17) -
Review Dagstuhl work on Instance Variable and edges/interfaces between views and packages -
Determine style and document (09-17) -
Instructions for RDF mappings in Drupal (10-01) -
Review consistency of RDF mappings (10-01) -
High level draft of library structure (Jay) -
Obtain input on RDF implementation of identifier from Benjamin Zapilko (Oliver) and Thomas Bosch (Achim) -
Identify proposed extended primitives in individual packages and move to new location (Jay) -
Request a means of generating a listing of where extended primitives and objects in general are used, bring to Jon, Olof, and Johanna (Wendy) -
Review recommendations on administrative objects as available properties on all objects, raise questions for decision 2014-11-12 (ALL)
Issues in JIRA document | see Document | Evolution document | see Document | Process model as revised 2015-10-18 | see Document | Binding model as revised 2015-10-18 | see Document | Binding and Intermediate Framework (Proposal from Minneapolis Sprint on creating PIM and PSM approach to creating bindings) | see Document | An RDF Schema/OWL Binding for the DDI Model v.3.1 (from Richard Cyganiak) | see Document | XML Binding from the DDI Model - link to current version in Bitbucket | See Document |
|
|
Column |
---|
|
Panel |
---|
borderColor | red |
---|
titleColor | black |
---|
borderWidth | 3 |
---|
titleBGColor | lightred |
---|
borderStyle | solid |
---|
title | Links to more information |
---|
| |
|
|