Difference between revisions of "MnM Minutes WGM 20080115"
| Line 1: | Line 1: | ||
| + | ==Monday Q1== | ||
| + | ===Hot topic: update mode=== | ||
| + | ''Hot topics/update mode'' | ||
| + | Grahame Grieve (GG) presented concerns related to "Update Mode" when preparing Abstract Data Types Release 2: | ||
| + | #Clarity on terms and definitions | ||
| + | #Clarity where update mode is documented and how much information data types needs to contain? | ||
| + | #:The update mode descriptions in the HDF do not seem to agree with Abstract Data Types R2 Table 59. | ||
| + | |||
| + | The group discussed possible documentation options, and suggests the following: | ||
| + | |||
| + | Prepare a new document in the ballot package in V3 Foundation, before Reference Information Model. Initial title is "Core Properties of V3 Models". An initial outline (below) was discussed but has been superseded by th evolving document found at [[Core_Properties_of_V3_Models]] | ||
| + | *Introduction to how RIM & data types fit together | ||
| + | **principles | ||
| + | **classes | ||
| + | **properties | ||
| + | ***cardinality | ||
| + | ***mandatory / conformance | ||
| + | **attributes | ||
| + | ***vocabulary concepts & coding strength | ||
| + | **associations | ||
| + | *concepts | ||
| + | **nullFlavor | ||
| + | **typing (typeId & flavorId & templates) | ||
| + | **conformance & testing | ||
| + | **update principles | ||
| + | **referencing principles | ||
| + | **updateMode | ||
| + | ***use cases | ||
| + | **data types | ||
| + | |||
| + | '''''Motion: Grieve/McKenzie (9-0-2)''''' | ||
| + | That MnM ballots this document described above for normative track; Woody Beeler and Grahame Grieve will be co-authors for this coming ballot cycle. | ||
| + | “update mode” will be renamed at the abstract level to “usage mode”. | ||
| + | |||
| + | ===Ballot reconciliation on Abstract Data Types=== | ||
| + | MnM took on various data type abstract ballot negatives, referred from InM. Following reference line items from Ballot reconciliation spreadsheet. | ||
| + | |||
| + | Line 141 '''''(Grieve/Coller 11-0-0)''''' | ||
| + | |||
| + | Line 142 '''''(Grieve/Coller 11-0-0)''''' If the item was (or is to be ) added, having not been present immediately before. (If it is already present, this may be treated as an error condition) | ||
| + | |||
| + | Line 143 '''''(Grieve/Beeler 11-0-0)''''' If the item existed previously and has (or is to be) revised. (If an item does not already exist, this may be treated as an error condition) | ||
| + | |||
| + | Line 146 '''''(Grieve/Beeler 11-0-0)''''' It is not specified whether or what kind of change has occurred to the item. | ||
| + | |||
==Tuesday Q1== | ==Tuesday Q1== | ||
''HDF Ballot Reconciliation'' | ''HDF Ballot Reconciliation'' | ||
Revision as of 17:38, 18 January 2008
Contents
Monday Q1
Hot topic: update mode
Hot topics/update mode Grahame Grieve (GG) presented concerns related to "Update Mode" when preparing Abstract Data Types Release 2:
- Clarity on terms and definitions
- Clarity where update mode is documented and how much information data types needs to contain?
- The update mode descriptions in the HDF do not seem to agree with Abstract Data Types R2 Table 59.
The group discussed possible documentation options, and suggests the following:
Prepare a new document in the ballot package in V3 Foundation, before Reference Information Model. Initial title is "Core Properties of V3 Models". An initial outline (below) was discussed but has been superseded by th evolving document found at Core_Properties_of_V3_Models
- Introduction to how RIM & data types fit together
- principles
- classes
- properties
- cardinality
- mandatory / conformance
- attributes
- vocabulary concepts & coding strength
- associations
- concepts
- nullFlavor
- typing (typeId & flavorId & templates)
- conformance & testing
- update principles
- referencing principles
- updateMode
- use cases
- data types
Motion: Grieve/McKenzie (9-0-2) That MnM ballots this document described above for normative track; Woody Beeler and Grahame Grieve will be co-authors for this coming ballot cycle. “update mode” will be renamed at the abstract level to “usage mode”.
Ballot reconciliation on Abstract Data Types
MnM took on various data type abstract ballot negatives, referred from InM. Following reference line items from Ballot reconciliation spreadsheet.
Line 141 (Grieve/Coller 11-0-0)
Line 142 (Grieve/Coller 11-0-0) If the item was (or is to be ) added, having not been present immediately before. (If it is already present, this may be treated as an error condition)
Line 143 (Grieve/Beeler 11-0-0) If the item existed previously and has (or is to be) revised. (If an item does not already exist, this may be treated as an error condition)
Line 146 (Grieve/Beeler 11-0-0) It is not specified whether or what kind of change has occurred to the item.
Tuesday Q1
HDF Ballot Reconciliation
Attendees
- Bernard Jackson (BERNARD@exchange.clemson.edu)
- Susan W. McClacherty (susan.mcclacherty@khpa.ks.gov)
- Scott Robertson (sScott.M.Robertson@kp.org)
- Ioana Singureanu (ioana@eversolve.com)
- Freida Hall (Freida.Hall@va.gov)
The committee reviewed the comments submitted by Kaiser Permanente. Scott Robertson indicated that Kaiser will withdraw the negative assuming that the proposed resolutions are applied in full.
--Ioana13 16:56, 15 January 2008 (CST)
Tuesday Q2
HDF Ballot Reconciliation
Attendees
- Lee Coller (lee.coller@oracle.com)
- Susan W. McClacherty (susan.mcclacherty@khpa.ks.gov)
- Scott Robertson (Scott.M.Robertson@kp.org)
- Sina Mowzoon (Sina.Mowzoon@azahccs.gov)
- Ioana Singureanu (ioana@eversolve.com)
- Freida Hall (Freida.Hall@va.gov)
- Kathleen Connor (Kathleen.Connor@foxsys.com)
The committee reviewed the comments submitted by Virginia Lorenzi, Jane Curry, and VA. The changes resulting from the comments provided by VA will be substantive.
--Ioana13 16:56, 15 January 2008 (CST)
