PD+Electronic+Service+Information+SWG+Meeting+Session+22

**Time:** 11:00PM - 12:00PM EDT
 * Electronic Service Information Discovery Workgroup Call **
 * Date **:11/1/2011


 * Meeting Agenda:**
 * **Topic** || **Time Allotted** ||
 * ESI Discussion || 60 ||

Attendance
Lin Wan, Karen Witting, Ernest Grove, Tynisha Carter, Peter Bachman, John Moehrke, Robert Dieterle, Zeshan Rajput, Naveen Amiruddin

Meeting Notes

 * ESI object is only a few objects, two of those objects are lists of codes with more complexity behind those codes
 * Coded field 1 (IntegrationProfile) maps to clearly defined documentation on transport and contents
 * Coded field 2 (Content) maps to clearly defined documentation on content supported by the service
 * Does not include detailed protocol, content, or wrapper issues in ESI object
 * Some transport and content combinations demand content wrappers, some do not, and for some it is difficult to say if content and wrapper are separate or combined
 * IntegrationProfile covers everything but wrapper. Need to decide how to handle wrappers.
 * Defining coded values would be an external documentation exercise
 * S&I could provide a base set for Direct and other S&I projects that could be extended by anyone to include additional types
 * Bob recommends adding additional elements
 * Security Profile will be a coded value
 * Digital Certificate will contain the certificate required by the integration profile
 * Does it make sense to include digital certificate here? Should use case 2 only provide an email address which can then be used to discover a digital certificate via use case 1 approach?

Next Meeting
**Workgroup Recurring Meetings:** Thursdays, 12:00-1:30pm ET **WebEx:** [|siframework2.webex.com] **Dial-in:** 1-408-600-3600 **| Passcode: ** 662 186 665 (Meeting on 11/3)