IOXIO Dataspace™ overview
Built on the internet best practices §
The trust mechanisms on the IOXIO Dataspace™ architecture are built on a decentralized model based on internet best practices currently in widespread use. There's no hocus pocus, no new cryptography invented, you only need to use open standards and architecture mixed with industry standards with comprehensive ecosystems of implementations and tools.
All the parties host their own public keys using JSON Web Key Sets, which then are used for verifying tokens and messages, as well as encryption, whenever it is needed. Trust in JWKS is brought by the existing mechanisms on the internet, DNSSEC, SSL certificates (incl. Extended Validation), and so on.
JSON Web Tokens, IETF HTTP Message Signatures and JSON Web Signatures, as well as JSON Web Encryption provide a solid set of tools for providing trust on multiple layers, including verifying authentication or consent tokens, to ensuring data hasn't been tampered with, or confidentiality.
You can also read more about our trust architecture.
Standardized data makes products §
When we agree on standard sizes of toast and toasters, selling a competing toaster becomes a lot easier. Similarly we believe that standardizing data products and the ways of transferring them will make it possible to get data moving, and when multiple vendors are providing their own data in standard formats we will empower a new modern data economy, unleashing new kinds of practical applications.
The data vendors and application developers alike can collaborate in the work for defining data products on the Dataspace in the Definitions repository, and the results are published on the Dataspace so everyone can easily follow the agreed standards. You will find the currently available data definitions on the Definitions Viewer, and technical details in the API Docs.
Explore our data definition guide or the Youtube video tutorial for productizing data.
Great tools for application developers §
Application developers on the IOXIO Dataspaces get many tools at their disposal, ranging from easy tools to find and analyze the available Data Products, to technical API documentation, as well as example code.
The application integration can be simplified to just a couple of steps. You start off by finding the data sources you want to use on the dataspace on the Developer Portal, you can then check the Definitions Viewer and API Docs for details on how to use them. Then, you just need to follow the Data Product definition and request the data product from your selected source, the Developer Portal will tell you the API endpoint.
The IOXIO Dataspace™ architecture does not force any specific technology choices, deployment models, etc. onto application developers. You know how your applications should be built, and we step out of your way and provide the capabilities to easily bring data into them.
Explore our application developer guides and open source example application for more information.
Bringing data available is a breeze §
Making your data available has never been easier. Data vendors can participate in the common work to define the data models with other data vendors and application developers, or they can choose to just use the existing Data Definitions and bring their valuable data to others.
The data source integration can be simplified to just a couple of steps. You start off by finding the data definition you want to provide data on the dataspace in the Definitions Viewer, you can then check API Docs and the OpenAPI Specs for details on how to use them. Once your productizer is complete, you register it on the Developer Portal, test it, and publish it.
The IOXIO Dataspace™ architecture does not force any specific technology choices, deployment models, etc. onto data vendors. You know best how to build your HTTP JSON APIs according to the data product spec, and we don't want to step on your toes.
Explore our data integrator guides and open source example productizer for more information.
Configuration and documentation §
Our Dataspaces are built on the assumption that there will be multiple dataspaces, and we want to make it as easy as possible for you to start using a dataspace. There's little need for hard-coded magic, as we provide many public configuration files for the services, starting from our Dataspace configuration file which tells your applications how to talk to the Dataspace and where to discover the various services in it.
All the parties on the Dataspace, including us, the application developers, and data vendors, publish their own Party configuration file, which documents things like where their public keys can be found. The data you share on our Dataspaces is configured via the Data Product Definitions.
All of the information you need is easily available on our Developer Portal, but if you ever have issues or questions, our IOXIO® Community Slack is there for you.
Code examples §
Example productizer
Data productization in short means adapting current data sources into a standardized format, so it can be shared via a dataspace.
We have created an example productizer, which you can use as bases for productizing your own data.
You can check the source from GitHub, and to help you create your own productizer, you can go and check out our guide on how to build a data source.
Example application
A Dataspace allows you to register applications to use the data available from it. By creating an application on top of a Dataspace, we provide you with the ability to use our Data products in your application.
We have created an example application for you to check out, as well as a step-by-step guide on how to create your own application using a Dataspace to get content.
On this page