minutes 23 January 2009 TC meeting

[bill parducci <bill@parducci.net>]

1. Roll Call
    Hal Lockhart (Chair)
    Bill Parducci (Co-Chair, minutes)
    Erik Rissanen
    Anthony Nadalin
    Rich Levinson
    Darran Rolls
    Seth Proctor
    John Tolbert
    Anil Saldhana

   Voting Members: 8 of 11 (72%) (used for quorum calculation)

2. Administrivia
     The TC discussed a clarification on the minutes from the 15 January
     TC meeting. The minutes will be updated to clarify the text. A vote
     upon the minutes has been deferred to next week.

3. Issues Hierarchical Profile
     Rich will present the results of his analysis on the Profile on the
     list.

    Multiple Decision
     Hal reviewed the current proposal and discussion on the list. There
     is general consensus in the TC in support of the proposal. Hal will
     develop the respective schema and text to complete the proposal,
     beginning with a summary to the list. There is still some  
discussion
     on how correlation will be dealt with on the response.

     There was clarification that the syntax will be described in the  
Core
     Schema and the semantics ("boxcaring", etc.) in the Profile text.

    Combining Algorithms
     Tony voiced concern that the old algorithms not removed. There is
     general consensus that both existing and new combining algorithms
     will be mandatory. The TC will likely add text indicating a
     preference in favor of the new algorithms, but all shall remain
     valid in v3.0.

     RBAC Profile
      Darran asked about the state of the RBAC Profile with respect to
      V3. He also reviewed use cases he believes may be pertinent to  
this
      Profile. Darran volunteered to create a proposal to address these
      cases within the Profile.

     XSPA (Comment List)
      There was a comment on the list that some of the links in the XSPA
      Profile that pointed to a private list. Since the references are
      directed at HL7 specification content but link to the TC Demo  
list.
      Hal suggested that there is a better source for this reference.

     Schema Checking (Comment List)
      Hal reviewed a thread from the Comment list that discussed the
      role of schema checking. Schema validity is necessary to be a  
valid
      Policy, but Seth pointed out that how it is done is an
      implementation choice.

meeting adjourned.