MnM Minutes WGM 201010 Cambridge

Sunday,Oct 3, 2010 - Q3

Agenda

• Agenda Topics Review
• Hot Topics Triage

Minutes

PRESENT: Woody Beeler, Lorraine Constable, John Koisch, Bruce McKinnon, Austin Kreisler, Mead Walker, Gregg Seppala, Andy Stechishin, Jean Duteau, Kathleen Connor, Brian Pech, Anil Luthra, Kevin Coonan, Rene Spronk, Sarah Gaunt, Grahame Grieve, David O'Driscoll, David Rowed, Michael Steine, Anita Walden

Agenda Discussion

• Hot Topics to discuss
  • MnM Involvement with SAIF, including BF
  • TemplateId on the Query Response
  • Behavioural Framework (Join OO)
  • Versioning
  • Attribute Context Conduction
  • Role Link
  • CMET status + DCM concerns

No Tue Q2 and no Wed Q2.

Action Items

• ACTION: Grahame will update the WGM schedule and email it to the list.

Monday, October 4, 2010 - Q3

Agenda

• MIF2 Reconcilliation

Attendees

NO QUORUM

Monday, October 6, 2010 - Q4

Agenda

• Core Principles Reconcilliation

Attendees

NO QUORUM

Tuesday, October 7, 2010 - Q1

Attendees

• Grahame Grieve, Woody Beeler, Jean Duteau

Agenda

• Core Principles Reconciliation

Minutes

Core Principles Reconciliation

• Worked through the Negatives assigned to Grahame and some of the Negatives assigned to Woody.
• Brought Lloyd in to discuss two comments that needed in-person discussion.

Meeting adjourned

Tuesday, October 7, 2010 - Q3

Agenda

• Hot Topics - "MnM Involvement with SAIF, including BF"

Attendees

• Woody Beeler, Xia Jing, John Koisch, Lorraine Constable, Adri Burggraaff, Li Zhou, Alexander Henket, Patrick Loyd

Tuesday, October 7, 2010 - Q4

Agenda

• Hot Topics - "Query Mechanism which specifies templates for the response"
• Update on MIF-to-UML work at OMG

Attendees

• Woody Beeler, Alexander Henket, Patrick Loyd, Jean Duteau, Brian Pech, Rik Smithies, Robert Worden, Rene Spronk, Lorraine Constable

Minutes

Discussion of Query Mechanism to specify a template for the response

We discussed the use cases for this requirement. We discussed the rejected alternatives. -interaction per query -make the new template ID a parameter

• This is revising a harmonization proposal "Add QuerySpec.responseTemplateid attribute" (also on the Wiki)
  • There was a comment that we do not have a real implementation of "Query By Example" so the argument against ParameterItem due to QBE requirements was not deemed sufficient.
  • The RIM definition of ParameterItem does not preclude sending the templateID as a parameter item.
  • This seems akin to the QueryLimit information.
  • It was deemed that this proposal was the easiest
  • Currently the proposal is suggesting all templates must be satisfied. There appears to be a use case for "one of" the templates to be satisfied.
  • What should the datatype be? In R1, SET<II>, in R2, QSET<II>. ACTION: Determine what the datatype should be.
  • It appears that we could "undeprecate" the ResponseElementGroupId parameter that had been deprecated.

ACTION: InM will advance the harmonization proposal for the next harmonization meeting.

Update on MIF-to-UML work at OMG

Jean presented a summary of his lunchtime conversation with Robert Lario. Robert will be producing a document that summarizes the analysis. He has requested some volunteer hours to help produce the report. The next step after the report appears to be to build a super-profile.

Wednesday, October 6, 2010 - Q1

Agenda

• Hosting Joint with Vocabulary - MIF Reconciliation

Thursday, October 7, 2010 - Q1

Agenda

• Hot Topics - "Versioning"

Thursday, October 7, 2010 - Q2

Agenda

• Hot Topics - "Attribute Conduction"

Attendees

Rik Smithies, Austin Kreisler, Rene Spronk, Jean Duteau, Marc Koehn, Debbie Bogert

Minutes

Discussion of Context Conduction for Attributes

We considered Austin's original proposal. Given Victor's input on the Hot topic, we decided on the following:

• we would create a new "Block All Attribute Conduction" attribute of type BN on ActRelationship
• The "conductible" property part of Austin's proposal would remain the same
• We also need to document in Core Principles that attributes with conductible set to true will effectively conduct as old-style OP, i.e. propagating, override.

Alternatives:

• "Block All Conduction" vs "Block All Attribute Conduction"
  • we already have the ability to block the other things that conduct, so we decided to make this just attributes for consistency
• Attributes do not conduct at all

ACTION: Austin will take this information and craft a new version of the proposal.

Friday, October 8, 2010 - Q1

Agenda

• Hot Topics - "Role Link"
• Planning and Schedule for Sydney
• CMET Status
• DCM Concerns