ITI CPs 2014-04-04

From IHE Wiki
Jump to navigation Jump to search

ITI domain CPs for 2013-2014 are managed here: http://wiki.ihe.net/index.php?title=ITI_Change_Proposals_2014

This page contains the agenda and minutes for the April 4, 2014 meeting.

Apr-4-2014

Fri 9-11am Central US

Agenda

The current status spreadsheet dated 2014-03-27 is here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/Status/

(1) Discuss assigned CPs ready for review: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/1_Assigned/

  • CP-ITI-672-03 - Clarify mustUnderstand (Elliott L. & Vassil)
  • CP-ITI-763-01 - Enable NetworkAccessPoint for Humans (Elliott L.)
  • CP-ITI-581-03 - DSUB correction for eventId in audit message (John M)
    • Note this is assigned to John, but Stephan Schroeder from ICW did these most recent updates to address the following public comments (this CP failed ballot 19 with these comment)s:
      • For those lines where ParticipantObjectName has been changed to "not specialized", the "mandatory" column should be changed to "U".
      • The strikeouts should be bolded.
      • As far as I can tell, ITI-52 and ITI-54 do not reference RepositoryUniqueId or HomeCommunityId, and ITI-53 only references them for Minimal Notification messages. As such, the changes from this CP are not appropriate (nor is the original). A more appropriate value should be substituted, but I would contend that a new ballot would be required for such a modification.
      • For ITI-53, I think the wording is bad. (I know it was copied from another transaction, but it's bad there, too.) Recommend the wording below. (Note that I used a lower-case "D" in UniqueId to be consistent with the element names. The use of an upper-case "D" in the other transaction(s) is incorrect.)
      • The ParticipantObjectDetail element may occur more than once.
      • (THIS COMMENT MAY NOT BE INCLUDED IN THIS UPDATE) For a Minimal Notification message, one element shall exist with the "type" attribute populated with the string "ihe:RepositoryUniqueId" and the "value" attribute populated with the value of the <xds:RepositoryUniqueID> element. Furthermore, if the homeCommunityId is known, another element shall exist with the "type" attributed populated with the string "ihe:homeCommunityId" and the "value" attribute populated with the value of the <xds:HomeCommunityId> element.
  • ..

(2) Progress on CPs against Vol 3

  • Review of analysis of Vol 3 CPs by Karen, Mark, and Walco. Refer to 'Vol3-CP-cleanup' tab in the status spreadsheet.

(3) Incoming CP review: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/0_Incoming/

  • CP-ITI-LF-errorInReferenceIdListExample.doc
  • CP-ITI-LF-SVS-ITI60RqdOrOptional.doc
  • CP-ITI-LF-FixXUASubjectRoleAttribute.doc
  • CP-ITI-LF_HPD-attribute-typos.doc
  • ...

(4) Next in CPs:

  • The next CP processing call is Thursday, April 17, 9-11am CDT.
  • Reminder: comments/votes on ballot 21 are due Fri Apr 25. The next CP discussions will be during the Apr 28- May 2 ITI Tech Cmte F2F meeting in Oak Brook, precise times TBA.

Minutes

Attendees: Elliott Lavy, Vassil Peytechev, Walco van Loon, Karen Witting (chair)

Status: updated status spreadsheet, dated 2014-04-05 is here - ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/Status/

(1) Discuss assigned CPs ready for review:

  • CP-672-03 - Clarify mustUnderstand (Elliott L. & Vassil) -- No agreement on the changes here:
    • a) regarding guidance to not specify mustUnderstand on replyTo - Karen/Vassil feel that that kind of guidance is not appropriate in the TF. Walco/Elliot feel it is important.
    • b) regarding removal of the requirement to specify replytoon sync calls - Vassil sees this as valuable, Karen/Walco/Elliot see as harmful.
    • Next steps: Walco will gather informal data at connectathon in terms of what vendors would like to see and are able to support. With that data, plan to discuss at f2f with Vassil/Bill/Walco/Elliot all present at once and other voices as well to hear the arguments. Vassil expects to be available Tu-Th of that week.
  • CP-ITI-763-01 - Enable NetworkAccessPoint for Humans (Elliott L.) -- agreed this is ready for ballot.
  • CP-ITI-581-03 - DSUB correction for eventId in audit message (John M)
    • reviewed this CP, comparing against 02. some updates to the messages for transactions 52&54 were put in 04.
    • Next steps: Walco will finish transaction 53, communicating with Elliot. Karen to send -04 to Walco as a starting point. -04 is also on ftp site in 'Assigned'

(2) Progress on Vol 3 CPs

  • topic deferred to next meeting

(3) Incoming CP review:

  • topic deferred to next meeting

(4) Next in CPs:

  • The next CP processing call is Thursday, April 17, 9-11am CDT.
  • Reminder: comments/votes on ballot 21 are due Fri Apr 25. The next CP discussions will be during the Apr 28- May 2 ITI Tech Cmte F2F meeting in Oak Brook, precise times TBA.
Retrieved from "http://wiki.ihe.net/index.php?title=ITI_CPs_2014-04-04&oldid=75862"