Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »


Use Case:  Bicycle Supply Chain structure - Use Case [DRAFT]

Full-Text Bicycle Use Case Article

Action Items - 25 March conversation with Sofia and Kelly

  • Keep everything in the context of blockchain smart contracts
  • Related concepts are sub-areas and added if they help the reader to understand interoperability in blockchain smart contracts. 
  • Add References from other wiki pages such as Annotated Bibliography that are referred to in the paper or that informed work in the paper
  • Add ideas and BPMN for the bicycle use case
  • Add others' research ideas to define, set the context, or support argument in the white paper



  1. Week 1 (2 March) - Start
    • Introducing the problem
    • Annotated bibliography (minimum 1 per person)
      • Papers regarding Interoperability on private or/and permissioned Blockchains (i.e. BPMN CAWEMO.com and DAML etc)
  2. Week 2 (9 March)
    • Outlining the Introduction and Interoperability chapters of the paper ( ++ anything else relevant)
    • Annotated bibliography (minimum 1 per person)
      • papers regarding Smart Contracts on blockchain
  3. Week 3 (16 March)
    • Outlining the Smart Contracts and BPMN chapters of the paper ( ++ anything else relevant)
    • Annotated bibliography (minimum 1 per person)
      • Papers regarding Interoperability Challenges on blockchain (i.e. Security, GDPR, data standards, legacy database etc)
  4. Week 4 (23 March)
    • Outlining the Interoperability Challenges and Recommendations chapters of the paper ( ++ anything else relevant)
    • Annotated bibliography (minimum 1 per person)
      • Papers regarding interoperability recommendations and identifying gaps in interoperability on blockchain (i.e. research that supports the paper's recommendations)
  5. Week 5 (30 March)
    • Outlining the interoperability recommendations and identified gaps
    • Final Draft of the full paper (Abstract + everything else above + Conclusions)
  6. Week 6 (6 April)
    • Finalize the paper and create a draft blog post (using the template)
    • Request peer review
  7. Week 7 (13 April)
    • Peer review / edits
    • Finalize the blog post
  8. Week 8 (20 April) - End (Publishing)


  • No labels