Concrete Implementation Agenda & Notes from 05182010 Meeting

Notes from the Concrete Implementation Workgroup

Status of Notes: DRAFT
Date: May 18, 2010
Time: 12pm-1pm
Attendees: Sean Nolan, Brian Behlendorf, Honora Burnett, Ravi Madduri, Rob Wilmont’s Representative, David Kibbe, John Moehrke, Jason Colquitt, Nageshwara Bashyam, Karen Witting, Mark Stine & team, Brett Peterson, Adeola Odunlami, Rich Kernan, Kevin Puscas, Vassil Peytchev & Arien Malec
Actions from this Week:

#	Date	Action	Status	Owner	Due Date
18	5/18/10	Sean Nolan is going to take input from the call edit the capability worksheet.	Open	Sean	5/25/10
19	5/18/10	If WG has additional comments, email Sean by EOD tomorrow.	Open	Sean & WG	5/25/10
20	5/18/10	WG will then be asked to give feedback on the Capability Worksheet	Open	WG	5/25/10

Actions from Last Week:

#	Date	Action	Status	Owner	Due Date
13	5/11/10	Sean will build a wiki page next to current minimal threshold and WG should contribute	Complete	Sean & WG	5/17/10
14	5/11/10	Brian will arrange that we can track each Concrete Implementation Group’s status reports on the Wiki	Complete	Brian	5/17/10
15	5/11/10	Each Concrete Implementation Group will provide weekly status reports by Tuesday at noon	Ongoing	Each Concrete Implementation Group	Ongoing
16	5/11/10	WG will have a “demo day” on the 25th which will be a LiveMeeting	Planned	WG	5/25/10
17	5/11/10	WG will update the specification documents along with the concrete implementations	Ongoing	WG	Ongoing

Agenda

1. Review Capability Worksheet (Implementation Capability Worksheet)
   • Quickly review existing text
   • Karen: clarify "directory" question
   • Brett et al: Add "vendor integration costs"
   • Arien: Document technology dependencies and availability
   • Roundtable to solicit any other contributions
   • Roundtable: Workgroup-level consensus
2. Discuss milestones
   • 5/25 (Tuesday): implementation groups to publish draft capability worksheets
   • 6/6 (Sunday): implementation groups to publish "final" worksheets
   • 6/8 (Tuesday): workgroup attempts to generate consensus
   • 6/10-11 (Thu-Fri): face-to-face, formal call for IG consensus
3. Status from groups if time (not likely)

Notes
Review Capability Worksheet (**Implementation Capability Worksheet**)
· Looking for on the 25th, being able to fill out draft capability worksheets
· This can’t wait until next week

Comment from Karen Witting
· As a group, are we committed to the timeline that we’ve agreed to

Comment from Rich Kernan
· State grantee level confusion
· NHIN CONNECT isn’t a term anymore – it is CONNECT
· Separate and competing initiatives
· Avoid “old vs. new”
· NHIN Exchange
· Continue this conversation off line (Language) in relation to #8
· Remove #2

Karen’s conversation about Directories
· Question for the room:
o Point is vague about whether this is a “white pages directory” or “using a directory to find endpoints within the system”
o Take out the addressing work, let the addressing WG process this
o Eliminate the directories
o Add bullet – describe how each component is implemented
o Five components – make sure addressing is not overlooked
o Add bullet to define all components (put five elements that are currently there)
o Terms as listed in the abstract model
o Glossary
o Clarify each term in the implementation
o Sean Nolan is going to take input from the call edit the capability worksheet. If WG has additional comments, email Sean by EOD tomorrow. WG will then be asked to give feedback.
o Testing scenarios
o Consensus is that this is the right format/document to put in front of the directory teams
o Not a novel, but want enough to compare to the others

Discuss milestones

• 5/25 (Tuesday): implementation groups to publish draft capability worksheets
• 6/6 (Sunday): implementation groups to publish "final" worksheets
• 6/8 (Tuesday): workgroup attempts to generate consensus
• 6/10-11 (Thu-Fri): face-to-face, formal call for IG consensus

Comment from Karen Witting

• Many different technologies are being presented here
• Tight timeline is not working for Karen
• Schedule longer conference time before the 8th
• Now two weeks into this model with four teams in parallel
• Now we need to sit down and look at these side by side

Comment from Vassil Peytchev

• What are we looking at?
• Compare and prioritize
• Teams who are working on worksheets should have Wiki pages, begin fleshing them out as soon as they can
• Ensure that they aren’t glossing anything over – keep a fair, honest, perspective
• Time bound and have to have these ready for the

Comment from John Moehrke
· Deadline that we need to “march towards”

Comment from Dragon
· Demonstrations to evaluate the products

Comment from Brett Peterson & Adeola Odunlami
· REST group is committed to the schedule and reading

Comment from Arien Malec
· 'Important to stay focused and drive towards this
· 'Process is about getting real and also driving to a good decision that we can all live with and do I have enough information to make this decision?

Update from groups
» SMTP: http://nhindirect.org/SMTP+Implementation+Development+Team
• Currently have an implementation of the security level working in .net and also have a Java version as well
• SMTP Gateway has been enabled and also will be able to plug into existing mail clients
» REST: http://nhindirect.org/REST+Implementation+Development+Team
• Two working REST implementations (one Java, one Ruby on Rails).
» Status is feature complete for both with respect to a one HISP model.
» Experimenting with different security models for HISP-HISP security, and both implementations provide slightly different approaches
• Code:
» RoR code has full working test cases, both internal integration, some unit, and an external client driver with full test tools.
» Java code has some basic unit tests and a Python client driver.
» Neither are production ready, but neither are throwaway code either -- both handle edge cases, implement security, etc.
» Java code has multiple active committers. Rails code is an army of one...
• Advantages are documented in recent mailing list post on the benefits of REST
» IHE / SOAP: http://nhindirect.org/IHE+Implementation+Development+Team
• Decided how to approach
» With existing code & implementations with some -___ writing
» XMPP: [1]
• Documentation Status:
» 1. Updated the Software Map portion of the XMPP Implementation Development Team.
» 2. Gathering feedback on items to enhance the documentation on the XMPP Development Team page.
• Technical Implementation Status:
» 1. Working version of the code per the software map has been created.
» 2. Currently working on Content Specification implementation. (Converting custom message content to fit the MIME Format).
» 3. Need to work on TLS and Security specifications next.
» 4. Trying to resolve SVN Access to Google code to check-in software. (Having a little trouble with my tortoise client).
• Community Activities Status:
» 1. Scheduling an XMPP Implementation Overview between 1pm and 3pm EST on Thursday 5/20/2010 to on-ramp new members of the team.
» 2. Share the information about the cloud instance, source code and other artifacts