Description: The role of the modelling team is to work with package teams and their leaders in order to instantiate DDI objects described on lion.ddialliance.org as 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.

Updated 2015-01-07: Regular meeting time for Modelling team. The meeting will take place at EVERY Wednesday at 0800 Minneapolis, 0900 Ottawa, 1400UK, 1500 CET, 0100 Canberra.

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

Pending 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)

• Update Communication Document with information on Identifier and Name, Label, Description content (Arofan)

• Add "Ask a Question" page to Modelers page and inform content groups