ABI CellML Meeting Minutes, 31st August, 2011

Present: Andrew Miller, Dougal Cowan, Randall Britten, Caton Little, Tommy Yu

Apologies: David "Andre" Nickerson

Last week's action items:

Action item 1: Andrew to send slides to Andre.

  • Done.

This week's agenda:

1) CellML core specs - update


  • Andrew: updated document based on discussions in meetings and on the tracker. Noticed some unresolved issues - connection directionality and attribute names.
  • Randall: read the uncertainty paper, have some minor feedback for Andrew.

2) CellML API - update


  • Andrew: working on Java and Python, getting the automated testing working. Java automated testing is working on all platforms, Python soon will be. Updated some documentation on how to use the Java and Python.
  • Randall: is it ready for release?
  • Andrew: as soon as automated testing is working for Python, a release candidate can be made.
  • Andrew: zip files of the Win32 API available.

3) Repository contributions - update


  • Dougal: Andre has put up and exposed Steve Niederer's latest ORd human ventricular action potential model. http://models.cellml.org/e/71/. Andre has added SED-ML which runs through the SED-ML web tools to produce an action potential.

4) PMR2 development - update


  • Tommy: staged version of 0.4 had broken push. Took a while to track down the cause of this. 
  • Tommy: core of the OAuth plugin is done. Now need to limit scope f access to Plone site.


  • There was an extensive discussion about OAuth, administrator, user, and consumer access management.
  • There was a discussion about use-cases for OAuth.
  • Randall: need to add use case(s) to the OAuth tracker item.
  • Randall: Tommy now should focus on getting CellML API accessible via read only webservices processing publicly visible models, and defer work on OAuth to later. Specifically this includes meeting requirements from VPH Share for accessing CellML API support for uncertainty.
Action item 1: Randall to try and get more details from VPH Share partners as to how they plan to use the webservices.