Difference between revisions of "MnM Minutes CC 20110302"
(10 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | + | [[Category:2011 MnM Minutes]]__NOTOC__ | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=M&M Conference Call 4:00PM Eastern Time (Date above)= | =M&M Conference Call 4:00PM Eastern Time (Date above)= | ||
− | |||
[[:Category:2011 MnM Minutes|Return to MnM Minutes]] | [[:Category:2011 MnM Minutes|Return to MnM Minutes]] | ||
==Agenda== | ==Agenda== | ||
− | *Approve [[ | + | *Approve [[MnM_Minutes_CC_20110216| Minutes Prior Meeting on 02/16]] |
* Reconcile Core Principles Negative Votes | * Reconcile Core Principles Negative Votes | ||
* Reconcile Core Principles "A*" Votes | * Reconcile Core Principles "A*" Votes | ||
+ | * Plan response to ITS Project Proposal for Data Tapes ITS R2B (Show on GoToMeeting) | ||
+ | * Quick Scan of PSS for Artifact Definition | ||
− | ==Approve Agenda and [[ | + | ==Attendees== |
+ | Beeler, Stechishin, Kreisler, Seppala, McKenzie, Natarajan | ||
+ | ==Approve Agenda and [[MnM_Minutes_CC_20110216| Minutes Prior Meeting on 02/16]]== | ||
+ | :Agenda approval - Andy/Ravi 5-0-0 | ||
+ | :Minutes approval - Gregg/Lloyd 5-0-0 | ||
==Reconcile Core Principles Negative Votes== | ==Reconcile Core Principles Negative Votes== | ||
Proposed actions in [http://www.hl7.org/documentcenter/ballots/2010SEP/reconciliation/recon_v3_cppv3models_r1_n4_2010sep.xls Spread sheet on Ballot Desktop] | Proposed actions in [http://www.hl7.org/documentcenter/ballots/2010SEP/reconciliation/recon_v3_cppv3models_r1_n4_2010sep.xls Spread sheet on Ballot Desktop] | ||
− | |||
− | |||
[http://www.hl7.org/v3ballot2010sep/html/infrastructure/coreprinciples/v3modelcoreprinciples.htm Document Being Reconciled] | [http://www.hl7.org/v3ballot2010sep/html/infrastructure/coreprinciples/v3modelcoreprinciples.htm Document Being Reconciled] | ||
− | + | Changes documented in [http://www.hl7.org/documentcenter/ballots/2010SEP/reconciliation/recon_v3_cppv3models_r1_n4_2010sep.xls spread sheet]. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Items 33, 34, 35, 40 - Lloyd/Robb 5-0-0 | |
− | |||
− | |||
− | |||
− | |||
− | == | + | ==Reconcile Core Principles A-* Votes== |
− | + | Changes documented in [http://www.hl7.org/documentcenter/ballots/2010SEP/reconciliation/recon_v3_cppv3models_r1_n4_2010sep.xls spread sheet]. | |
− | |||
− | |||
− | |||
− | + | Items 1 - 7 Andy/Lloyd 5-0-0 | |
− | |||
− | |||
− | |||
− | + | Remaining items Austin/Ravi 5-0-0 | |
− | |||
− | |||
− | |||
− | |||
− | == | + | ==Review/Update MnM of Project Scope for SAIF Artifact Definition== |
− | + | We reviewed the document that had been updated by Lloyd. This was the version that had been discussed previously in a joint conference call with Project Services. Minor edits were made to the document in clarifying the scope and responsibilities. The [http://gforge.hl7.org/gf/download/docmanfileversion/6174/8092/SAIFArtifactDefinitionProjectScopev03.doc Revised PSS has been posted] and will be forwarded to TSC for its review. | |
− | We | ||
− | |||
− | |||
− | + | The changes were approved: Austin/Andy 5-0-0 | |
− | == | + | ==Plan response to ITS Project Proposal for Data Tapes ITS R2B == |
− | + | ITS Work Group is preparing to advance a Project Scope for a project to: | |
− | + | :"This project will develop ITS specifications for HL7 v3 messages and documents, that are wire-backwards-compatible to existing ITS Structures R1.1, and abstract data types R2 while to the maximum extent possible adopting all changes and new features that are being introduced by semantic and abstract specifications, such as the RIM and abstract data types..." | |
− | |||
− | + | The version reviewed was not believed to be the final version, but it is expected that this may come up for review in the Foundation And Technology SD before the next MnM meeting. There were lively discussions about the project and its intentions. | |
− | |||
− | |||
− | |||
− | |||
− | + | Based on the group's understanding of the proposal, the following major concerns were raised, and the co-chairs were urged to raise them in discussion at the SD: | |
− | |||
− | |||
− | |||
− | |||
+ | *HL7 needs to avoid sponsoring two incompatible "normative" ways to implement data types (DT) R2 (also the ISO data types) in the long term. | ||
+ | * The complete capability of DT R2 should be the only viable target for the future, and relatively soon. The proposed ITS's do '''not''' strive to implement all features of DT R2. | ||
+ | *If this is a bridge specification to allow a smooth transition, it should be sunset at some point. | ||
− | + | *It is our understanding that there are elements of the proposed ITS that will '''not'' be backwards compatible, what are they, and how can one claim this is backwards compatible? | |
− | == | + | * We believe there is a need to '''limit''' this to those circumstances where there is an '''extant, demonstrable implementation of the earlier standard that justifies such backwards compatibility'''. It should never be used for new, unrelated endeavors. |
+ | |||
+ | ==Adjourned after 75 minutes== |
Latest revision as of 00:39, 3 March 2011
M&M Conference Call 4:00PM Eastern Time (Date above)
Agenda
- Approve Minutes Prior Meeting on 02/16
- Reconcile Core Principles Negative Votes
- Reconcile Core Principles "A*" Votes
- Plan response to ITS Project Proposal for Data Tapes ITS R2B (Show on GoToMeeting)
- Quick Scan of PSS for Artifact Definition
Attendees
Beeler, Stechishin, Kreisler, Seppala, McKenzie, Natarajan
Approve Agenda and Minutes Prior Meeting on 02/16
- Agenda approval - Andy/Ravi 5-0-0
- Minutes approval - Gregg/Lloyd 5-0-0
Reconcile Core Principles Negative Votes
Proposed actions in Spread sheet on Ballot Desktop
Changes documented in spread sheet.
Items 33, 34, 35, 40 - Lloyd/Robb 5-0-0
Reconcile Core Principles A-* Votes
Changes documented in spread sheet.
Items 1 - 7 Andy/Lloyd 5-0-0
Remaining items Austin/Ravi 5-0-0
Review/Update MnM of Project Scope for SAIF Artifact Definition
We reviewed the document that had been updated by Lloyd. This was the version that had been discussed previously in a joint conference call with Project Services. Minor edits were made to the document in clarifying the scope and responsibilities. The Revised PSS has been posted and will be forwarded to TSC for its review.
The changes were approved: Austin/Andy 5-0-0
Plan response to ITS Project Proposal for Data Tapes ITS R2B
ITS Work Group is preparing to advance a Project Scope for a project to:
- "This project will develop ITS specifications for HL7 v3 messages and documents, that are wire-backwards-compatible to existing ITS Structures R1.1, and abstract data types R2 while to the maximum extent possible adopting all changes and new features that are being introduced by semantic and abstract specifications, such as the RIM and abstract data types..."
The version reviewed was not believed to be the final version, but it is expected that this may come up for review in the Foundation And Technology SD before the next MnM meeting. There were lively discussions about the project and its intentions.
Based on the group's understanding of the proposal, the following major concerns were raised, and the co-chairs were urged to raise them in discussion at the SD:
- HL7 needs to avoid sponsoring two incompatible "normative" ways to implement data types (DT) R2 (also the ISO data types) in the long term.
- The complete capability of DT R2 should be the only viable target for the future, and relatively soon. The proposed ITS's do not strive to implement all features of DT R2.
- If this is a bridge specification to allow a smooth transition, it should be sunset at some point.
- It is our understanding that there are elements of the proposed ITS that will 'not be backwards compatible, what are they, and how can one claim this is backwards compatible?
- We believe there is a need to limit this to those circumstances where there is an extant, demonstrable implementation of the earlier standard that justifies such backwards compatibility. It should never be used for new, unrelated endeavors.