Dear All Thanks so much for your time today at the TOKEN Meeting, I think there were a lot of good points and a lot of work ahead to close the year well with TOKEN https://docs.google.com/document/d/1aIJzPqCzsW13-j1AeOYPu9Hd27nggQBzdbGBBjwh2ow/edit#heading=h.48bkna3m7a25 Here is the link to the minutes and the wrap up conclusions are highlighted in this email. Feel free to add any other relevant points for the TOKEN community Kindest regards K Wrap-up and conclusions 1. Reminder on Business Model Survey if it can be done by tomorrow COB 14 October 2022 , what components are we using or not using and why : this is very important to be answered. Business Model Deliverable is in draft so FBR waiting for this input 2. KPIs to be completed please by October 21st. Hard deadline 30 October 2022. UC needs this soonest. 3. We haven't gotten at least 10 Early adopters so far so that is not good news. NET Service, Federico Caiulo is working on the road map with input from IMEC. Dont miss the upcoming email please react when it comes out. 4. The question is : what are they going to adopt if many things are not going to continue? Option from Adnan, INFRACHAIN : Not all is adopted but the codes and best practices kind of services from the municipalities this would be a good solution to reach the result and have something as early adopters Another new point ( mentioned outside meeting to WP6 via email) 1. Important to highlight that for example FIWARE technology related to Blockchain, Digital Identity, Verifiable Credentials, Wallet and so on is aligned with EBSI. So any application using Canis Major ( a component from FIWARE) is already blockchain-enabled in an EBSI-compatible way. FIWARE has also put them in line with the European Strategy as key for sustainability. 2. Suggestion If other components are not compatible and will not be compatible with EBSI , WP6 could create a section so that Consortium partners can mention their position regarding EBSI compatibility. If they are not compatible they can argue the value of non-compatibility with EBSI which of course can have good reasons. This would help deal with sustainability. Action point INFRACHIAN, Adnan help us include a section on the draft and circulate for completion. Thanks 3. Deliverables on WP3 have been sent to FF for revision , they have not input the questions from the revision of privacy and security done by Uwe from LIST (Luxembourg Institute of Science and Technology) We discussed that this will be included on the update of this same deliverables needed by December of course you could already work on those. 4. Request of one month delay for the Communications deliverable from WP5 Angeles FF on the basis of the upcoming important events on Dissemination in November ( German national event -please send us advertising material to circulate to german public-, Barcelona) 5. Governance Deliverable is in draft questions raised about ISO will be followed up by INFRACHAIN, Adnan 6. Dates for the Berlin final Project meeting will be confirmed by Monday, latest Tuesday COB , the date that was most voted was December 19,20 for a workshop meeting, TBD if the meeting with our TOKEN results with audience will also be included there or done separately. Kindest regards, Karen -- Karen Vega, MPP Senior Manager karen.vega at fiware.org www.fiware.org <https://www.linkedin.com/in/karenvega/> Linked-In/Karen Vega <https://www.linkedin.com/in/karenvega/> "The best preparation for tomorrow is doing your best today." H. Jackson Brown, Jr. American Author <https://nexus.lab.fiware.org/fiware.signature> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/token-all/attachments/20221013/27912650/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy