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

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


 * Meeting Agenda:**
 * **Topic** || **Time Allotted** ||
 * Review of LDAP/HPD data mapping process || 90 ||

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 11/17/2011 || Support team will provide Vincent Lewis with most up to date copy of mappings || Support Team || Closed || 12/16/2011 ||

Meeting Notes

 * Karen reviews LDAP, ISO21091, and HPD relationship and extensions
 * ISO21091 is extension to LDAP, HPD is extension to 21091
 * Karen walks through the gaps she has identified for Individual
 * Suffix, DOB, Address Type, Address elements, Most ESI attributes, Digital Certificate ID, Digital Certificate DN
 * All of these will be easy to add except ESI
 * ESI will be difficult to add because some attributes are already supported
 * Adding a whole new element could break things for those already using the existing elements (digital address and URI)
 * Rachel Foerster: Legal Address type may need additional refinement to take care of administrative demands, especially international addresses
 * Karen walks through the gaps she has identified for Organization
 * IHE has not described the address attribute adequately, Karen has mapped address as well as she can given lack of details
 * Rachel Foerster: It should be stated somewhere that //Semantic interoperability is not the goal//.
 * Organization – Organization Relationship
 * Workgroup discussed possible ways to classify relationships but found it to be highly complex and decided not to include type
 * Rachel Foerster: Add a statement to base data model that clarifies that the relationship does not specify type of relationship
 * General Challenges
 * LDAP does not have an inherent object concept
 * When LDAP/HPD already have some amount of the attributes desired, but not all of them, we can’t extend those fields to hold additional values as it will create problems for existing implementations
 * Next Steps
 * Vincent Lewis has an HPD schema created for the original use case
 * Vincent will add the current model elements to the extension schema and Karen will review this version prior to next week’s call to see if it can improve the data mappings