Merge branch 'main' into docs/schema

.github/workflows/auto-fix-md.yml

@@ -20,6 +20,7 @@ jobs:
         continue-on-error: true
         with:
           args: "**/*.md"
+          ignore: contracts/**/*.md contracts_versioned_docs/**/*.md modules/**/*.md modules_versioned_docs/**/*.md commands/**/*.md commands_versioned_docs/**/*.md
           fix: true
 
       - name: Commit changes

.github/workflows/update-versioned-docs.yml

@@ -72,7 +72,7 @@ jobs:
 
       - name: Search for all modified files that involve the creation of PR or commit to main
         id: changed-files
-        uses: tj-actions/changed-files@v37.5.1
+        uses: tj-actions/changed-files@v38.1.3
         with:
           files: |
             *.json

contracts/okp4-cognitarium.md

@@ -83,8 +83,27 @@ Returns a description of the resource identified by the provided IRI as a set of
 |`describe.format`|**[DataFormat](#dataformat)\|null**. The format in which the triples are serialized. If not provided, the default format is [Turtle](https://www.w3.org/TR/turtle/) format.|
 |`describe.query`|*(Required.) * **[DescribeQuery](#describequery)**. The query to execute.|
 
+### QueryMsg::Construct
+
+Returns the resources matching the criteria defined by the provided query as a set of RDF triples serialized in the provided format.
+
+|parameter|description|
+|----------|-----------|
+|`construct`|*(Required.) * **object**. |
+|`construct.format`|**[DataFormat](#dataformat)\|null**. The format in which the triples are serialized. If not provided, the default format is [Turtle](https://www.w3.org/TR/turtle/) format.|
+|`construct.query`|*(Required.) * **[ConstructQuery](#constructquery)**. The query to execute.|
+
 ## Responses
 
+### construct
+
+Represents the response of a [QueryMsg::Construct] query.
+
+|property|description|
+|----------|-----------|
+|`data`|*(Required.) * **[Binary](#binary)**. The data serialized in the specified format.|
+|`format`|*(Required.) * **[DataFormat](#dataformat)**. The format of the data.|
+
 ### describe
 
 Represents the response of a [QueryMsg::Describe] query.
@@ -143,6 +162,16 @@ An RDF [blank node](https://www.w3.org/TR/rdf11-concepts/#dfn-blank-node).
 |----------|-----------|
 |`blank_node`|*(Required.) * **string**. |
 
+### ConstructQuery
+
+Represents a CONSTRUCT query over the triple store, allowing to retrieve a set of triples serialized in a specific format.
+
+|property|description|
+|----------|-----------|
+|`construct`|*(Required.) * **Array<[TriplePattern](#triplepattern)>**. The triples to construct. If nothing is provided, the patterns from the `where` clause are used for construction.|
+|`prefixes`|*(Required.) * **Array<[Prefix](#prefix)>**. The prefixes used in the query.|
+|`where`|*(Required.) * **Array<[WhereCondition](#wherecondition)>**. The WHERE clause. This clause is used to specify the triples to construct using variable bindings.|
+
 ### DataFormat
 
 Represents the format in which the data are serialized, for example when returned by a query or when inserted in the store.

docs/tutorials/nonos-tuto-3.md

@@ -0,0 +1,11 @@
+---
+sidebar_position: 103
+---
+# Video Tuto #3 - Ontology
+
+🚀 Welcome to the third episode of Nono's Tuto !
+Your tutorial series to become an expert developer on the OKP4 protocol 🔥
+
+📚 In this third episode, we'll dive in the Ontology and do some demonstration!
+
+<iframe width="100%" height="550" src="https://www.youtube.com/embed/39SOwMhdylA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

docs/tutorials/overview.md

@@ -20,3 +20,4 @@ Discover our video tutorials with Arnaud our Blockchain Architect:
 
 * [Introduction to OKP4 Architecture](./nonos-tuto-1)
 * [Governance, you said](./nonos-tuto-2)
+* [Learn more about Ontology](./nonos-tuto-3)

docs/whitepaper/solution.md

@@ -93,14 +93,19 @@ From this perspective, Digital Services serve as the structural and functional u
 
 **STaaS-Storage as a service:**
 The Dataverse is capable of supporting all storage options. These range from local storage options to cloud storage solutions operated by major providers such as Dropbox or Any”Drive”. Additionally, decentralized storage networks like InterPlanetary File System (IPFS), Filecoin, or Arweave can also be integrated into the platform.
+
 **Compute-as-a-Service:**
 Similarly, the Dataverse is adaptable to a range of computation options. While many services will be provided as APIs with their own computational resources, others can be executed on cloud services operated by commercial entities or decentralized compute resources. This flexibility is essential for accommodating different types of computational tasks and workloads. Revelant general purpose compute networks as [Akash](https://akash.network/) can be easily referenced into the protocol.
+
 **Identity Provider:**
 In terms of identity management, the Dataverse can integrate with various identity management services or identity standards, depending on the specific requirements. Whether it's a simple, a decentralized identity management system, or a more complex centralized identity service, OKP4 can support it, providing secure and flexible solutions for identity management;
+
 **Orchestration-as-a-Service:**
 The Orchestration Service is a **crucial service** of the Protocol which orchestrates the invocations of other services. It is a reflex component of the Ecosystem that listens to the transactions of the blockchain and is triggered on command, when a particular transaction of execution request is registered in the blockchain. It's important to note that, given the potential for multiple instances of the service and several types of orchestration services, there is a decentralized mechanism in place that ensures the correct instance of the appropriate type is executed.
+
 **Algorithms and Models:**
 From simple logical rules to sophisticated AI-driven algorithms, machine learning models, data processing scripts, image recognition models, predictive analytics, natural language processing (NLP) models, and even blockchain smart contracts, the Dataverse is designed to accommodate and utilize a diverse range of algorithms and models. Their inclusion is dictated solely by the unique needs and objectives of the tasks at hand.
+
 **Analytic-as-a-Service:**
 In an era of increasing data complexity and volume, effective knowledge representation is pivotal. The Analytics and Business Intelligence services is designed to transform raw data into useful insights, employing tools of B.I and Knowledge Graphs.
 BI tools can be effectively employed to comprehend the data shared within the zones and facilitate the extraction of useful knowledge. Knowledge Graph can facilitate the interpretation of the complex interactions and dependencies within the Dataverse, offering an intuitive view of the knowledge extraction processes.

docusaurus.config.js

@@ -20,6 +20,11 @@ async function createconfig() {
     deploymentBranch: 'gh-pages',
     trailingSlash: false,
 
+    i18n: {
+      defaultLocale: 'en',
+      locales: ['en', 'fr']
+    },
+
     presets: [
       [
         'classic',

i18n/en/code.json

@@ -0,0 +1,6 @@
+{
+  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
+    "message": "Back to main menu →",
+    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
+  }
+}

i18n/fr/code.json

@@ -0,0 +1,6 @@
+{
+  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
+    "message": "Retour au menu principal →",
+    "description": "Le libellé du bouton de retour pour revenir au menu principal, à l'intérieur du menu secondaire de la barre latérale de la barre de navigation mobile (utilisé notamment pour afficher la barre latérale des documents)"
+  }
+}

src/scss/custom.scss

@@ -39,6 +39,7 @@
   --ifm-footer-background-color-main: transparent linear-gradient(212deg, #181c49 0%, #343869 100%)
     0% 0% no-repeat padding-box;
   --ifm-navbar-background-color: #f2f6f9;
+  --ifm-navbar-item-color: linear-gradient(39.81deg, #006796 21.82%, #00b6b7 98.43%);
   --ifm-article-anchor-color: #ff9500;
   --ifm-graph-svg-background-color: #ecf0f1;
   --ifm-knowledge-graph-data-fill-color: #f3a83f;

src/scss/main.scss

@@ -1,3 +1,9 @@
+@mixin with-linear-gradient($background-color) {
+  background: var($background-color);
+  background-clip: text;
+  -webkit-text-fill-color: transparent;
+}
+
 html {
   background: var(--ifm-background-color-main);
   min-height: 100%;
@@ -33,6 +39,12 @@ html {
   .navbar__items--right {
     display: flex;
     flex-direction: row-reverse;
+
+    @media (max-width: 996px) {
+      position: absolute;
+      right: 55px;
+      top: 40px;
+    }
   }
 
   .card-title {
@@ -77,6 +89,18 @@ html {
   .navbar__items {
     font-size: 18px;
 
+    @media (max-width: 996px) {
+      flex-direction: row-reverse;
+
+      .navbar__brand {
+        width: 100%;
+      }
+    }
+
+    .navbar__link {
+      color: inherit;
+    }
+
     .navbar__search {
       input {
         font-family: var(--ifm-font-family-base);
@@ -96,10 +120,26 @@ html {
     color: var(--ifm-color-primary);
   }
 
+  .navbar-sidebar {
+    left: inherit;
+    right: 0;
+    transform: translate3d(100%, 0, 0);
+  }
+
   .navbar__link--active {
+    @include with-linear-gradient(--ifm-navbar-item-color);
+
     font-weight: var(--ifm-font-weight-bold);
   }
 
+  .navbar__link:hover {
+    @include with-linear-gradient(--ifm-navbar-item-color);
+  }
+
+  .dropdown .navbar__link:hover::after {
+    border-color: #00b6b7 transparent;
+  }
+
   .footer {
     background: var(--ifm-footer-background-color-main);