Create or view a Document
Guideline for developing and displaying content on the Internet of Impact
Document standards
The purpose of documents in the Internet of Impact is to record information in a stateful way. The ixo protocol standard is that a document must be:
Verifiable
Attributable
Semantically interoperable
Universal addressable
Human-readable
Machine-readable
Non-repudiable
Tamper-resistant
Persistently available
Private by design
Document types
The ixo protocol defines a set of standard document types, which are used as building-blocks.
1. DID Document
Each identifiable subject in the Internet of Impact has a Decentralised Identifier (DID). A specifically formatted document is associated with a DID, the DID Document (DDO), which is based on the W3C specification.
The W3C describes a DID Document as "A set of data describing the DID subject, including mechanisms, such as public keys and pseudonymous biometrics, that the DID subject can use to authenticate itself and prove their association with the DID.
A DID document might also contain other attributes or claims describing the subject. These documents are graph-based data structures that are typically expressed using [JSON-LD], but can be expressed using other compatible graph-based data formats.
The following DDO document subjects are defined in the ixo context:
Cell document
Project document
Oracle document
Bond document
Data Asset document
A generic template (in JSON Template standard format) for each of these documents is currently maintained in Github under custodianship of the ixo Foundation.
The generic structure of an ixo protocol DID Document is illustrated below.
[insert illustration]
Document Page is the information which is displayed to an end-user. This uses standard Markdown Format for styling and to embed media into the page. See the Page Formatting guide.
2. Claims document type
Claims are high-definition data objects which encode information in a way that is portable, self-declarative and verifiable. Claims comply with the document standards by implementing the following features:
Subjects are identified in a way that can be authenticated, using a DID.
A schema context is declared, which resolves the claim data to a set of standard semantic definitions.
An issuer is identified and authenticated, using a DID.
The claim is cryptographically verifiable by its hash value and signatures.
The claim object is content-addressable by its hash value (using the IPLD specification).
The following claims categories are defined in the ixo context:
Identity claim (credential)
Impact claim
Evaluation claim
Dispute claim
Transaction claim
A generic template (in JSON Template standard format) for each category of claims is currently maintained in Github under custodianship of the ixo Foundation.
The basic structure of an ixo protocol Claim is illustrated below.
[insert illustration]
Viewing documents
Verifiable displays
Last updated