Attendees
- Donal Fellows (UNIMAN)
- Finn Bacall (UNIMAN)
- Markus Plangg (TUW)
- Rui Castro (KEEPS)
- Carl Wilson (OPF)
- Alan Williams (UNIMAN)
Notes
- Will people be careful when updating ontologies (or profiles) in non-extensive fashions, as this can cause existing published components to cease to be valid. (The Taverna component plugin is now better armoured against this.)
- Care required with licenses, as they can be on tools and (independently) on components. Components can support annotations on tool processors, so can support differentiating between complex cases. Query not yet capable of expressing this subtlety.
- Licenses are an effectively-closed set, with URLs to major public open source licenses already existing.
- Tool names, tool versions, MIME types are fully open sets; probably have to represent using literal text nodes in the RDF.
- For dependencies in KEEP/OPF debian repository, should we create individuals to select from? If so where to get the licenses of used command line tools? (Create from toolspec?)
Actions
From last time
ACT.130307.01 Finn: Give estimate for how long it will take to improve querying over RDF in myExp. (Key Q: In time for us to demo at review or not?)
DONE: Not by review.
ACT.130307.02 Finn: Check whether myExp supports OR queries (needed for component license checks given that there's no ontology support)
DONE: Does not.
ACT.130307.03 Finn: Check timeline for updates to myExp; when will things go live?
DONE: Should be live now.
ACT.130307.04 Finn: Allow myExp to tolerate anonymous nodes; mustn't crash!
ONGOING
ACT.130307.05 Finn: Solution for how to do SCAPE-specific queries for review.
ONGOING
ACT.130307.06 Carl: Review wiki changes properly (also Markus)
DONE: Seem largely reasonable, reviewed by Bolette
ACT.130307.07 Carl: Ask Asger about his changes
DONE: Asked, no response
ACT.130307.08 Markus: Check if Bolette's changes make sense in detail
DONE: Seem to be fine.
ACT.130307.09 Markus: Create characterization example
DONE: using jplyzer
ACT.130307.10 Markus: Use jplyzer as example (coordinate with Carl, Johann, TUW)
ONGOING: Created small example to show all annotations, but no comprehensive use of jpylyzer.
ACT.130307.11 Alan: Update plugin (0.9?)
ONGOING: Some issues still to fix
ACT.130307.12 Alan: SCAPE-specific GUI for migration path & parameters
ONGOING
New
ACT.130314.01 Donal: Ask Sean for assistance with ontology writing
ACT.130314.02 Finn: Create brief feature list of myExperiments
ACT.130314.03 Markus: Create QA component example
ACT.130314.04 KEEP: Add commandline tool license to toolspec
Current Open Actions
ACT.130307.04 Finn: Allow myExp to tolerate anonymous nodes; mustn't crash!
ACT.130307.05 Finn: Solution for how to do SCAPE-specific queries for review.
ACT.130307.07 Markus: Use jplyzer as example to create comprehensive CC component. (coordinate with Carl, Johann, TUW)
ACT.130307.11 Alan: Update plugin (0.9?)
ACT.130307.12 Alan: SCAPE-specific GUI for migration path & parameters
ACT.130314.01 Donal: Ask Sean for assistance with ontology writing
ACT.130314.02 Finn: Create brief feature list of myExperiments regarding components
ACT.130314.03 Markus: Create QA component example
ACT.130314.04 KEEP: Add commandline tool license to toolspec
1 Comment
comments.show.hideMar 14, 2013
Carl Wilson
Is it fair to note that the estimate for RDF SPARQL queries was "about 2 weeks effort", I'm sure that the issue was that Finn doesn't have the available time before the review. An ongoing could be to make sure that there is a plan as to when this might happen.