This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "November 2nd, Templates Minutes"

From HL7Wiki
Jump to navigation Jump to search
 
Line 6: Line 6:
 
# Agenda Check  
 
# Agenda Check  
 
## Looks ok.
 
## Looks ok.
# Review of [[Static Model Working Terms]] from Constraints Meeting
+
 
 
##  
 
##  
 
# [["Shallow" vs. "Deep" LIMs (Templates)]]
 
# [["Shallow" vs. "Deep" LIMs (Templates)]]
Line 13: Line 13:
 
## BE - Distinction - Deep seems to be assumed static, shallow are more dynamic.
 
## BE - Distinction - Deep seems to be assumed static, shallow are more dynamic.
 
## BE - Shallow are building blocks, but deep makes it a valid V3 message.  There may be levels of shallow.
 
## BE - Shallow are building blocks, but deep makes it a valid V3 message.  There may be levels of shallow.
 +
 +
# Review of [[Static Model Working Terms]] from Constraints Meeting
 +
 
## Yan - Does a DIM only allow constraints of structure and not vocabulary?
 
## Yan - Does a DIM only allow constraints of structure and not vocabulary?
 
## KR - Templates are equivalent to all static models (not the RIM.)  What differs is the conformance criteria and purpose for use.   
 
## KR - Templates are equivalent to all static models (not the RIM.)  What differs is the conformance criteria and purpose for use.   

Latest revision as of 20:49, 2 November 2005

  1. Roll Call
    1. Ken Rubin (BE)
    2. Russell Hamm (RH)
    3. Yan Heras (YH)
    4. Brett Essler (BE)
  2. Agenda Check
    1. Looks ok.
  1. "Shallow" vs. "Deep" LIMs (Templates)
    1. BE - This is just another useage distinction. A deep definition is costrained to the point where it is static. Shaoow is constrained to the point that specifies the pattern, without getting into serialization. Just the degree of constraint.
    2. KR - Conf Prof are useful here.
    3. BE - Distinction - Deep seems to be assumed static, shallow are more dynamic.
    4. BE - Shallow are building blocks, but deep makes it a valid V3 message. There may be levels of shallow.
  1. Review of Static Model Working Terms from Constraints Meeting
    1. Yan - Does a DIM only allow constraints of structure and not vocabulary?
    2. KR - Templates are equivalent to all static models (not the RIM.) What differs is the conformance criteria and purpose for use.
    3. BE - Agree with Ken. Much of the difference lies in useage, and not a technical distinction. The constraints requirements are technically the same and differ only in useage. 'Templating' is the same (or very similar to) modelling.
    4. RH - A Template is esentially a constraint pattern.
    5. BE - Necessary to separare useage from model technical properties.
    6. KR - The Templates group has been unsucessful at carving out it's technical space due to percieved conflict with other areas. Templates are the whitespace between two nodes. By saying all these things are Templates, we remove the whitespace. The SIG can then define its area, and MnM can define how these models interrelate.
    7. YH - What is an example of useage.
    8. KR - e.g the useage of a CMET.
  1. Continue review of Archetypes Requirements.
  2. Determine the next call time.
  3. Next Week's Agenda (Technical)
  4. Adjourn

http://informatics.mayo.edu/wiki/index.php/November_2nd%2C_Templates_Agenda