Semantic Container

Status of this document

This specification is not a W3C Standard nor is it on the W3C Standards Track. Learn more about W3C Community and Business Groups. GitHub Issues are preferred for discussion of this specification.

History

Version 0.1: 17 May 2023 (initial public release, current version)

1. Introduction

tbd

1.1. Terminology

This document uses the following terms as defined in external specifications and defines terms specific to Semantic Container.

DRI: A Decentralized Resource Identifier represents a content based address for a dataset. Within SemCon Multihash [MULTIHASH] (default: sha2-256) is used for hashing a JSON object and Multibase [MULTIBASE] (default: base58-btc) for encoding the hash value.

1.2. Design Goals and Rationale

SemCon satisfies the following design goals:

Open: all components are open source, free to use (incl. commercially), and publicly accessible (Github, public Repository)
Extensible: design is inherently supposed to be extended through own definitions, extensions, concepts
Compatible: allow seamlessly switching between data formats to use the best technology for the given use case
Ease of use: make it as simple as possible (but not simpler!) through documentation (e.g., tutorials, examples) and UI components (databud)
Focus on Semantic Web: build on top of and make use of the Semantic Web Stack
Decentralised: avoid any centralized components or addressing (i.e., use decentralized resource identifiers - DRIs - where possible)

1.3. Motivation

tbd

2. Features

tbd

3. Tools

3.1. Repository

tbd

3.2. Command Line Tool

tbd

4. Reference Implementation

tbd

This project has received funding from the European Union’s Horizon 2020 research and innovation program through the NGI ONTOCHAIN program under cascade funding agreement No 957338.

Conformance

Document conventions

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.