funding and mentoring program with best international experts in Semantic Web, Linked Data, Ontology engineering, Blockchain interoperability, knowledge management, distributed and decentralised computing, business models for trusted knowledge… 3 ONTOCHAIN empowers innovators and end users to develop blockchain-based knowledge management solutions that will be part of its novel protocol suite & software ecosystem for a better share of knowledge and value.
Resilient Internet With protection of privacy, user empowerment, inclusivness openness A Trustworthy Internet With trustworthy Content, Information exchange, Identities A Sustainable Internet With Interoperable services, Data traceability Develop block(s) of a software ecosystem that will serve the trusted knowledge and information needs of HUMANITY! Contribute to : Yourmission
Promotion Community Building With Innovators, Industry, Investor Media Promotiom Access to Top Events Software technologies IEXEC platform MyIntelliPatent Up to 200 000 € Per sub-grantee For scaling up innovative business Webinars Access to various expertise What’s in it for you?
phases Phase 2 – Protocol Suite & Software Ecosystem Foundations You will : Establish the Ontochain framework as human centric decentralised & trustworthy solution based on the available technologies. With coaching support You will : Build the Ontochain concept for the creation of a trustworthy information exchange process & a more transactional content handling. Create the Ontochain Framework prototypes. With coaching support You will : Exploit the Ontochain solution to real life use cases. With coaching support Call budget: 1,14M€ Call budget: 1,32M€ Call budget: 1,75M€ Phase 1 - Research Phase 3 - Applications & Experimentation
open to an unexpected visitor? ▪ Should I borrow my car to my neighbour? ▪ Who will gain access to my video stream for processing? ▪ Can we trust the sensors and the traffic lights on the smart crossing? ▪ Can we trust the documents in the archive? ▪ When I move my smart car from Ljubljana to Vienna what happens with my transactions? ▪ Who can access my files? ▪ … many scenarios … and many scenarios have already been explained… ▪ #ICT2018 e-SIDES project: ▪ Fog Computing and the Problem of Trust Trust-critical use cases
replication based on security needs ▪ Possibility for split and join operations with ONTOBLOCKs ▪ Quality of Service managements with trade-offs for ONTOBLOCKs: in memory, temporary usage of blocks, storage for indefinite time, number of replicas versus storage cost etc. ▪ Trusted approaches for ontologies and metadata management ▪ Trusted approaches for data management ONTOBL OCK TRUS T ❑ People, resources ❑ Data, Metadata, Knowledge, Information ❑ Internet of Things ❑ Microservice containers ❑ Edge-to-Cloud infrastructures ❑ Artificial Intelligence algorithms ❑ Digital Twins ONTOBLOCK
Block Forest ▪ Designed for indefinite usage ▪ Supporting services for continuous Knowledge Block Forest operation: ▪ ONTOBLOCKS split & join ▪ ONTOBLOCKs archiving ▪ ONTOBLOCKs defragmentation ▪ In memory ONTOBLOCKs ▪ High security ONTOBLOCKs ▪ Moving blocks vertically or horizontally ▪ Local versus Global decision making ▪ Geographic mapping of ONTOBLOCKs ▪ Top blocks have much higher security, are kept in memory, regularly copied between countries ▪ Trust in the provided information! ONT OBLO CK ONT OBLO CK ONT OBLO CK ONT OBLO CK ONT OBLO CK ONT OBLO CK The Knowledge Block Tree and Forest
▪ 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 Orthogonal viewpoints considered for the 1st Call
▪ 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
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. ▪ Functional requirements: describe a particular system/component behavior ▪ CRUD operations over ontology data ▪ Verify data on the blockchain ▪ Authenticate, Authorize participants in the ecosystem ▪ Build semantic models for data analysis, visualization and decision-making ▪ Implement reputation models for decision-making ▪ Implement data provenance ▪ 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 ▪ Public, Private, Consortia blockchain ▪ Interoperability and integration between applications of the OntoChain ecosystem ▪ … ▪ Prepare detailed designs of use cases across all subject domains Applications’ requirements analysis for trusted knowledge management
manage access and operations over the ontologies in the ecosystem. ▪ 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 ▪ Information retrieval based on onchain and offchain knowledge management ▪ Ontology related proof-of-* ▪ Data interoperability and ontological clustering ▪ 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.) Blockchain 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 ▪ 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 Blockchain Ontologies
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 asset management ▪ Sell/Buy/Share/Rent ontology data ▪ Business models: prepaid, postpaid, time-limited and etc. ▪ Facilitate intraledger transactions On-chain data management
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
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 semantic models ▪ 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) ▪ Functional constraints: ▪ Operational expenses when using Smart Oracles ▪ Security protocols for trusted/trustless operations ▪ Reputation-based algorithms’ computational complexity Off-chain knowledge management
complex, dynamic and decentralized trusted knowledge management ▪ Functional requirements: ▪ 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 Business approaches for decentralised knowledge and information economy
▪ 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 actually 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 ▪ Integration strategies ▪ Following integration standards and data formats (e.g. FHIR, EHR for telemedicine) Interoperability and integration aspects
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
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
rvirus0817
shujisado
bgpat
mochizuki875
nagisa53
oracle4engineer
kniino
naoki_0531
fujisawaryohei
yuj1osm
sat
.png){kind=icon}
pharma_x_tech
afnizarnur
keavy
swwweet
ufuk
samanthasiow
lara
morganepeng
eileencodes
davidbonilla
kneath
scottboms
sugarenia
