Skip to end of metadata
Go to start of metadata

In this page we maintain the roadmap for the project for M20 (end of July 2012), taking into account that this is a key milestone for the project, when the first versions of all software deliverables from WP3-WP5 are delivered, integrated in the Wf4Ever sandbox (WP1).

Roadmap Item

Showcases

Steps (as identified in Granada, Jan2012)
COULD, SHOULD, MUS

RO Demonstrators (in D2.2)
    RO Specification
    RO Primer
    An RO minimal information model
    RO Guidelines

Sprint 2  
   14. RO Primer
   17. Create final RO spec
Sprint 3
   12. Visualisation of ROs (Piotr) 
Sprint 5
   68. Improving the Wf4Ever APIs (Graham)
Later sprints
   5. UI: Traffic lights and Stars (Piotr)
   18. Next version of RO Model (RO model 1.0)
   24. In line RO Annotations (Marco)
   35. RO Guidelines / RO Primer for users
   43b. Follow-up of best practices for users
   33. Structuring research in ROs in local organisations (Marco)
   41. Browsing and Querying ROs
   53. Nanopublications and Research Objects
   55. The RO model can do with another iteration
   71. Categories upper layer for RO Model

Documentation 
    One or two user-stories to guide the project development
    Provenance/evolution of workflow
    What is evolution - need clarification
    What does it mean to repair an RO?
    What breaking and decaying means
    Clarify variety and uses of provenance
    Terminology and glossary
    RO primer for 3rd parties to understand beyond spec
    Improved RO spec
Annotation
    "Breakable component" annotation
    Structured annotations, specially for dependencies
    Dependencies on other tools/services
    Keep provenance of annotations
    Bridging human vs machine-generated/consumed annotations
    Minimal information model for an RO

RO Content (in D2.2)
    Generates 1000s of ROs.
    Convert all content of myExperiment to ROs

Sprint 2 
   9. Astro-Taverna wishlist (Susana)
   15. Creation of concrete RO examples
Sprint 3-4-5
   9. Astro-Taverna wishlist (Susana)
Later sprints
   9. Astro-Taverna wishlist (Susana)
   0. Automated Workflow execution (Stian) - unfinished in sprint 5
  

RO golden examples
Metabolic syndrome use-case publication with RO as additional material
100s of ROs
10s of ROs 
Implement Astro wishlist for Taverna 
myExperiment pack to RO converter

Catalogues/Test libraries (synthetic suite
of workflows and research objects)
(in D2.2, D3.2, D4.2)
    RO model (in D2.2)
        RO examples in (a) Genomics and (b) Astronomy
         RO examples from (a) Taverna, (b) Kepler
           (c) WINGS (d) VisTrails, etc. 
    Of workflow decay (in D2.2)
        Presume that components are scattered and
        independent of the RO owner, without their control. 
        Build a synthetic suite of ROs representing 
            decay in all dimensions so as to validate
            models and simulate with services
    Of RO evolution (in D3.2)
    Of RO stability (in D4.2)

Sprint 3
   21. RO testbed (Dani)
   56. Generate a corpus of provenance (Dani)

Benchmark of tooling
Integration with service catalogues

Integration of Wf4Ever and myExperiment (in D1.2 and D1.4)

Sprint 4
       48. Round-trip myExperiment-Taverna-RODL
Sprint 5
        58. RO-Enabled myExperiment mock-up
        48. Round-trip myExperiment-Taverna-RODL 
Later sprints
        20. myExperiment offer a RO API or export
        59. Grounded RO-enabled myExperiment case studies from ADS, Galaxy and Biovel
        60. RO-Enabled myExperiment hackathon
        52. Initial integration of recommender subsystem with myExperiment (Rafa)
        67. Integration Prerequisites Showcase (Rafa, not finished in sprint 5)

 

Validate models, architectures and software in practice 
    Stable releases of models and software
        Individual components (in D2.2, D3.2, D4.2)
        Reference implementation (Wf4Ever toolkit)
                  (in D1.2 and D1.4)
    User management: access/Security
        Review approach to include SCATTERED
            components with different access/security
            arrangements

Sprint 2
   26. Recommender: Explainability

Later sprints
   25. User Feedback Handling Showcase
   34. Access Control
   42. RO Scalability
   39. Annotation Notebooklet
   40. Epigenetics ... RO
   46. Continuation of checklist evaluation
   47. I&A evaluation and integration

Architecture
    What is the RO server? An architecture of RO microservices + RO manager
    Focus on services e.g. service details in RO model
    Identify the citation services for an RO
    Link data publications of ROs - how/why/examples/linkage to othet data sets
    Finetune demo
    Develop ideas around RO as context to workflow execution ->
                   role of RO management for project 

User experience
    Recommendation system explainability
    UI - user role mapping - when, who does what
    Include feedback on recommended items
    User feedback handling recommendation system
    Round with acquaintances for feedback on what to show in interface
               - I like it/don't like it, how to present buttons, runnable, etc
    Traffic lights and stars
    Show dependencies

Emphasis on

  • Evolution and decay monitoring and notification
                (why my wf is no longer stable) and reacting
                to decay (in D2.2, and a bit of D3.2)
  • Social aspects of collaboration (in D3.2)
                 Attribution and credit support beyond recommendation
  • Proper use of provenance (where is it and where is it
      not needed, define clear boundaries) (in D4.2)

RO Evolution 
   6. Workflow Evolution (Pinar, WF-258)
   7. Taxonomy of diagnosis (Jose Manuel)
   50. Visualization of RO evolution 
   8. Service substitution (Khalid)  
   3. Mining Decay from myExp (Stian) 
 RO Social aspects
   27.A Social Recommender Showcase
   27.B Scientific Content Recommender
   10. Reviewing an RO (Graham) 
   11. Training with an RO (Pique) 
   44. Workflow processes recommender (Esteban)
   51. Collaboration Spheres Visualisation
Provenance showcases
   22. Querying workflow execution provenance
   74. PROVO export
   28. Workflow reuse
   29. User's view on provenance
   30. RO citation
   31. Reproducibility
   32. User view (Marco)
   38. Provenance interplay
   54. Align RO Provenance Models with W3C PROV Ontology
   64. Integration of the checklist service into the Wf4Ever portal
   65. Linking taxonomy of decay with minim models
   66. Integration of the stability service into the Wf4Ever portal
   70. Workflow decay actions

Evolution/Decay
   Diff tool , detection of changes - RO/data/wfs/services/provenance
   Holistic view of I&A, alignment with "break" and "no brea"
   Dimensions transparant to users
   Substitutability of services/tools
   Service/tool identity - same service
   Change/decay model (both positive and negative)
   Include notion of breaking things and recording
   Using the provenance to feed the decay manager
   What are the things that may break in an RO, and what
            annotations needed to repair RO
   Detection of service changes by provenance changes / overlay
            of multiple ROs
   What is "breakage" e.g. wrong vs. no result. Can we detect these?
   Dimensions of instability vocab (chocolate workflow decay) 
Provenance
   Extract provenance from existing metadata
   Attach RO provenance blob to RO
   Connect workflow provenance with RO provenance -
            file X came from workflow output Y
   Depth of provenance abstraction
   Integration of workflow with abstract workflow model
   Abstract provenance of workflow trace as agent
   Development of structures of workflow analysis
Fragility
   RO provenance for I&A
   What are the IQ dimensions we want to implement?
   RO provenance as a motto for I&A
   Visualisation helps to assess fragility evaluation
   Develop uses of provenance as evidence of quality
   "Critical" annotation flag
Social aspects

Miscellanous

23. Integration with DataFlow
49. Website content updates (ongoing)
69. Video Generation for Demos (Oscar)

Workflow design recommendation
Annotation user role mapping  ????

  • No labels