Meeting Date and Time OK?
User Tests and Debugging for Annotation Processor.
Facades for Jobs,JobRunner,NetworkCapabilities allowing development/testing outside Glassfish.
Updated Roadmap to indicate things not accomplished for SPNHC, and expand list of potential next step targets.
Worked on Kurator proposal with rest of team (Saturday).
July 4th is a Wednesday, Canadians have the 1st off, Otherwise OK.
James: Lots of "Can I use this tomorrow?" questions. TODO: Add audio track to video, upload to youtube channel. James to try recording audio track, Paul to add to video, Lei to make channel link available. TODO: Jim to send Paul contact at Smithsonian Center For Astrophysics group, Paul to contact about more elaborate video.
Bob: Bob and Jim working out contacts for Designers. Jim: Need clarification on some of the notes.
Paul to Invite Patrick and Chuck for next week's meeting. Need Software engineering discussion with Ed Gilbert about colaboration in Symbiota.
Confirmed meeting dates in August. Time to book travel.
James: Asked by iDigBio to give (1) 15 minute talk, and (2) be part of a one day workshop (about 30 participants) to give a FP demonstration. Demonstration much like SPNHC. TODO: Get Specify installed on James' laptop, and test MySQL over SSH tunnel from his machine. Paul: A few minor bugs and some minor feature requests from demonstration, will file bugs. Add fillin for highertaxon/rank on mapping. Date issue. Leave oauth error handling to next week when Maureen gets back. TODO: Paul to stop in with Jim this Afternoon to check in authentication. James: Could use further help on UI development.
Delivery of annotations to interests based on related data not found in annotation Requirement20 (Bob working on, evaluating SPARQL Push).
James: Priorities, ApplePie and TCN engagement gives us nice traction, how do we leverage this. We need something that works. Discussion: Lightweight annotation system would be good something to deploy that works. TODO: David and Bob to produce a brief description of VM capability and software requirements (SPARQL Push, Fuseki, etc) to deploy an instance. Paul: How fragile to changes in domain ontologies? Bob: Not fragile. David: Domain ontology removed from Java code, all defined in configuration. Paul: What are the implications of deploying, using, and then changing the vocabulary? Bob: For development, about 2 hours of configuration. For use, makes questions more complex, are questions (interests) to reflect only old interests, or only new, or both? A specific risk is that existing interests would not pick up new annotations. Phrase other way around, when someone expresses an interest (a SPARQL query), they want a notification whenever a new annotation is made that meets that query, plus the first time you subscribe, all existing matches to the query. What do you expect to happen when you register a new interest with respect to things in the old vocabulary (will depend on reasoning linking vocabularies). James: A few higher level suggestions, coming from Maureen. Meetings taking too much time. Good to have specific weekly targets. Paul: Good to tighten up Wednesday meetings, down to 1 hour. Bob: Refactor meetings to put deliverables discussion that programmers need to be involved in first, then research goals later. James: Would be good to have more control of meeting software. Jim: Kansas/Minesota/Arizona team discussions used effective system. Bob: evo.caltech.edu http://evo.caltech.edu/evoGate/ Paul: Will give another try at using roadmap to develop weekly targets.