| ONTOCHAIN.NGI.EU ▪ Semantic Web as well as Blockchain are all about trust! ▪ Ontology is a shared conceptualisation ▪ Blockchain is a shared ledger ONTOCHAIN- Where Semantic Web and Blockchain meet
| ONTOCHAIN.NGI.EU ▪ Application oriented ▪ Marketplace(s) setup and operation ▪ Fact checking against fake information ▪ Self-sovereign identity ▪ Trusted and secure data management ▪ Asset ownership management ▪ Secure and transparent copyright management and verification ▪ Technology oriented ▪ Trusted and secure third-party data integration in Blockchain logic ▪ Blockchain based database access management to preserve and maintain integrity and reliability of data ▪ Trust based on transparent, secure, decentralised reputation models ▪ Decentralised Blockchain Database concept ▪ Intraledger transaction execution and data exchange ▪ Semantic annotation of Big Data pipelines Orthogonalviewpoints considered for the 1st Call
| ONTOCHAIN.NGI.EU ▪ eCommerce ▪ Transparent and secure asset management ▪ Supply chain management ▪ Education ▪ Trusted and transparent learning platforms ▪ eGovernment/Public Services ▪ Smart city scenarios ▪ Identity and access management to computing resources/storage/IoT sensor/software components ▪ Shared mobility ▪ Digital identity ▪ Trusted identification and authentication ▪ Individual control of identity without the intervening administrative authorities ▪ Digital insurance policies ▪ eContent ▪ Trusted crowd-source journalism (reputation and blockchain models to validate information and identify participants) ▪ Preserve data integrity and security (verify data from large, trusted ontology models) ▪ Copyright management ▪ Social network privacy control ▪ eHealth ▪ Medical supply chain to prevent fake/counterfeit drugs ▪ Secure management of electronic health records (EHRs) ▪ Patient consent management ▪ Basis for the 1st Call; User story examples to be included. Some application domains
| ONTOCHAIN.NGI.EU Motivation: Propose a new architecture of ONTOCHAIN applications ▪ Multitier and scalable design – the anatomy of ONTOCHAIN applications (to be designed) ▪ Presentation tier (GUI) design for applications built by using the ONTOCHAIN software ecosystem ▪ Logic tier (Backend logic + blockchain services) ▪ Security tier (Firewall, security protocols, encryption) ▪ Data tier (Ontologies) ▪ Explain how applications can be built by using the software ecosystem ▪ Ontologies and workflows for the application design, data, metadata exchange formats between application components ▪ Communication protocols between components ▪ Interoperability between the platform and the applications ▪ Application requirements analysis for trusted knowledge management; design of typical ONTOCHAIN applications, designs for various application domains, innovative use cases. ONTOCHAIN system and applications FR, NFR, SR in order to design an architecture, component implementation and integration strategy. ▪ Generic use cases identification. ▪ Good coverage of application areas by the system. Applications
| ONTOCHAIN.NGI.EU ▪ Functional requirements: describe a particular system/component behavior ▪ Trustworthy content handling, trustworthy information exchange ▪ Trustworthy Web and Social Media, Trustworthy Crowdsensing, Trustworthy Social Networks, Trustworthy Service Orchestration ▪ Prepare detailed designs of use cases across all subject domains ▪ Non-functional requirements: define criteria that judge the system operation ▪ Secure and safe operations over ontology data ▪ Ensure privacy of information ▪ Ensure transparency of operations, and etc. ▪ … ▪ System requirements: define configuration that a system must have to run smoothly ▪ Integration between applications of the OntoChain ecosystem ▪ Interoperability between applications of the OntoChain ecosystem ▪ … Applications
| ONTOCHAIN.NGI.EU ▪ Motivation: Transparent, secure and traceable approach to manage access and operations over the ontologies in the ecosystem. ▪ The potential use of Linked Data ▪ Blockchain based semantic agreement process, ontology agreement ▪ New ideas for onchain and offchain ontology management with trade-offs analysis ▪ Blockchain ontology integration with database and knowledge base technologies ▪ Provide solutions for validation that ontology and onchain and offchain knowledge is logically consistent ▪ Reasoning approaches for onchain ontologies ▪ Realisation of permissioned blockchains with blockchain ontology management ▪ Ontology types ▪ Development of specific ontologies to be used for the project use cases for each application domain ▪ Additional ontologies for reputation models, resource models (e.g. computing clusters, Service-Level Agreements, monitoring, certification, etc.) Semantic interoperability
| ONTOCHAIN.NGI.EU ▪ Functional requirements ▪ Develop specific domain ontologies and populate them with related domain data ▪ Develop and integrate additional ontologies for resource models, reputation models ▪ Manage ontology relation as in clusters, hierarchies or similar ▪ Manage ontologies’ operations (CRUD) through blockchain smart contracts ▪ Validate the correctness of ontology data instance via blockchain ▪ Compliance with W3C and other standards ▪ Functional constraints ▪ Current solutions are mostly simulations or prototypes ▪ Missing less-costly, trustworthy & secure semantics and reasoning mechanisms ▪ Knowledge bases have low implementation in the industry, integration and performance challenges can appear Semantic interoperability
| ONTOCHAIN.NGI.EU ▪ Motivation: ▪ Novel ideas for implementation of on-chain data management methods ▪ Suitable consensus protocols identification for implementation ▪ Blockchain controlled storage for semantic formats (e.g. OWL Lite) ▪ Trusted and transparent data sharing among organizations within the same domain of interest ▪ Functional requirements: ▪ Identification, authorization and role management of enrolled entities ▪ Verify data integrity on blockchain (e.g. hash comparison) ▪ Securely store encrypted ontology instances on the blockchain ▪ Keep track of ontology history on the blockchain (Data provenance) ▪ Keep track of what has been modified in the ontology by whom ▪ Facilitate intraledger transactions On-chain data management
| ONTOCHAIN.NGI.EU ▪ Functional constraints: ▪ Limited amount of data that can be stored on the blockchain ▪ Limitations with execution time and cost of execution ▪ Limitations when feeding smart contracts with off-chain data ▪ Smart contract limitations in the context of legal aspects of their application* *Hansen, J. D., Rosini, L., & Reyes, C. (2018). More legal aspects of smart contract applications. Perkins Coie LLP, March. On-chain data management
| ONTOCHAIN.NGI.EU ▪ Motivations: Improve existing and propose new approaches for off-chain knowledge management. Suitable protocols for implementation of the initial ONTOCHAIN architecture. ▪ Functional requirements: ▪ Feed Smart Contracts with off-chain data by using Smart Oracles ▪ Build reputation models and integrate them with data provenance and authorization/identification components ▪ Integrate trustless structured and other knowledge base technologies ▪ Apply decentralised computing technologies for storing and accessing data (e.g. OAI-PMH) ▪ Trusted execution environments ▪ Proof of executions, code signatures ▪ Governance – the rules that one has to abide in order to push data to Smart Contracts ▪ Functional constraints: ▪ Operational expenses when using Decentralised Oracles ▪ Security protocols for trusted/trustless operations ▪ Reputation-based algorithms’ computational complexity Off-chain knowledge management
| ONTOCHAIN.NGI.EU ▪ Motivation: New business ecosystem based on semantically complex, dynamic and decentralized trusted knowledge management. Market framework, business models for trusted knowledge management ▪ Functional requirements: ▪ Facilitate asset management ▪ Sell/Buy/Share/Rent ontology data ▪ Business models: prepaid, postpaid, time-limited and etc. ▪ Define and compare business processes ▪ Data encryption, validation, verification ▪ Analyze and compare different ledger technologies (Hyperledger Fabric, Ethereum) and protocols (ERC-20, ERC-721) ▪ Design new ways of accessing expertise, knowledge, data ▪ Trustworthy approaches ▪ Maintaining privacy and security ▪ Secure data pipelines Ecosystem economy
| ONTOCHAIN.NGI.EU ▪ Integration strategies ▪ Following integration standards and data formats (e.g. FHIR, EHR for telemedicine) ▪ Ecosystem setup and enlargement ▪ Testbed design ▪ Like in https://dappnode.io/ ▪ Incentives design for participation ▪ Joining kit ▪ Resolution of scalability requirements including ▪ High QoS ▪ Low operational costs ▪ Low energy consumption ▪ Large-scale simulation Ecosystem scalability and integration
| ONTOCHAIN.NGI.EU KPIs currently being considered KPI Target New innovative ONTOCHAIN use cases 20 New innovative OntoChain reasoning technologies 5 New ways to serialise ontologies and semantics on blockchain 5 Other (unimaginable) new approaches to implementing “ b ” 10
| ONTOCHAIN.NGI.EU KPIs currently being considered (also for subsequent calls) KPI Target Accepted proposals for framework design 10 Awards and challenges for conferences funded 18 Prototypes 25 Applications (use-cases) running 15
| ONTOCHAIN.NGI.EU KPIs currently being considered KPI Target Application domains 10 Specific SOTA review documents 6-12 Specific technology testing documents 6-12 Joint market assessment 2-3
| ONTOCHAIN.NGI.EU KPIs currently being considered KPI Target Psychology and societal study on the requirements of the society towards trusted knowledge management 1 Contributors and users of the joint ONTOCHAIN Open Source (preferably Apache License V2.0) software repository 30+ entities Design/experimental articles in high impact journals and conferences 18+ … …
ontochain
irof
okada_fuutass
tacck
miyake
marikashiotsuki
fujiwara3
junkifurukawa
mode86
interu
moritama1515
nabedge
yuya4
chrislema
skipperchong
eileencodes
bryan
keithpitt
marktimemedia
geeforr
bermonpainter
robhawkes
holman
yeseniaperezcruz
akosma