Merge branch 'main' into feature/include_wsl_documentation

Author: rpietzsch

.github/workflows/pages.yml

@@ -75,12 +75,12 @@ jobs:
         run: task clean build
 
       - name: upload artifact
-        uses: actions/upload-pages-artifact@v1
+        uses: actions/upload-pages-artifact@v3
         with:
           # Upload entire repository
           path: 'site'
 
       - name: deploy to gitHub pages
         id: deployment
-        uses: actions/deploy-pages@v1
+        uses: actions/deploy-pages@v4
 

README.md

@@ -13,7 +13,7 @@ If you consider to contribute to this project, please have a look on [CONTRIBUTI
 
 ## License
 
-Copyright © 2024 [eccenca GmbH](https://eccenca.com)
+Copyright © 2025 [eccenca GmbH](https://eccenca.com)
 
 This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License][cc-by-sa].
 

Taskfile.yml

@@ -5,9 +5,9 @@ version: '3'
 
 vars:
   PUBLIC_BRANCH: published
-  CURRENT_VERSION: 24.3
-  MATERIAL_TAG: 9.5.44
-  MATERIAL_INSIDER_TAG: 9.5.44-insiders-4.53.14
+  CURRENT_VERSION: 25.2
+  MATERIAL_TAG: 9.6.14
+  MATERIAL_INSIDER_TAG: 9.6.14-insiders-4.53.16
 
 tasks:
 
@@ -108,7 +108,7 @@ tasks:
     desc: re-generates the cmemc command reference
     cmds:
       - rm -rf {{.REFERENCE_DIR}}/*
-      - CMEMC_MANUAL_DIR={{.REFERENCE_DIR}} cmemc -q config
+      - cmemc manual --format markdown-multi-page --output-dir {{.REFERENCE_DIR}}
     vars:
       REFERENCE_DIR: docs/automate/cmemc-command-line-interface/command-reference
 

docs/automate/cmemc-command-line-interface/command-reference/admin/index.md

@@ -26,7 +26,7 @@ $ cmemc admin status [OPTIONS]
 
 This command outputs version and health information of the selected deployment. If the version information cannot be retrieved, UNKNOWN is shown.
 
-Additionally, this command informs you in one of these cases: (1) A warning, if the target version of your cmemc client is newer than the version of your backend. (2) A warning, if the ShapeCatalog has a different version than your DataPlatform component. (3) An error, if your Corporate Memory license is expired (grace period). (4) A warning, if your Graph DB license will expire in less than a month.
+Additionally, this command informs you in one of these cases: (1) A warning, if the target version of your cmemc client is newer than the version of your backend. (2) A warning, if the ShapeCatalog has a different version than your Explore component. (3) An error, if your Corporate Memory license is expired (grace period). (4) A warning, if your Graph DB license will expire in less than a month.
 
 To get status information of all configured deployments use this command in combination with parallel.
 

docs/automate/cmemc-command-line-interface/command-reference/admin/metrics/index.md

@@ -1,5 +1,4 @@
 ---
-status: new
 title: "cmemc: Command Group - admin metrics"
 description: "List and get metrics."
 icon: material/chart-line-variant

docs/automate/cmemc-command-line-interface/command-reference/admin/migration/index.md

@@ -1,5 +1,4 @@
 ---
-status: new
 title: "cmemc: Command Group - admin migration"
 description: "List and apply migration recipes."
 icon: material/database-arrow-up-outline
@@ -15,7 +14,7 @@ With this command group, you can check your instance for needed migration activi
 
 Beside an ID and a description, migration recipes have the following metadata: 'First Version' is the first Corporate Memory version, where this recipe is maybe applicable. The recipe will never be applied to a version below this version. 'Tags' is a classification of the recipe with regard to the target data, it migrates.
 
-The following tags are important: 'system' recipes target data structures which are needed to run the most basic functionality properly. These recipes can and should be applied after each version upgrade. 'user' recipes can change user and / or customizing data. 'acl' recipes migrate access condition data. 'shapes' recipes migrate shape data. 'config' recipes migrate configuration data.
+The following tags are important: `system` recipes target data structures which are needed to run the most basic functionality properly. These recipes can and should be applied after each version upgrade. `user` recipes can change user and / or customizing data. `acl` recipes migrate access condition data. `shapes` recipes migrate shape data. `config` recipes migrate configuration data.
 
 
 ## admin migration list
@@ -59,7 +58,7 @@ This command executes one or more migration recipes. Each recipe has a check met
 
 Recipes are executed ordered by first_version.
 
-Here are some argument examples, in order to see how to use this command: `execute `--all` `--test-only`` will list all needed migrations (but not execute them), `execute `--filter` tag system` will apply all migrations which target system data, `execute bootstrap-data` will apply bootstrap-data migration if needed.
+Here are some argument examples, in order to see how to use this command: execute `--all` `--test-only` will list all needed migrations (but not execute them), execute `--filter` tag system will apply all migrations which target system data, execute bootstrap-data will apply bootstrap-data migration if needed.
 
 
 

docs/automate/cmemc-command-line-interface/command-reference/admin/workspace/python/index.md

@@ -11,7 +11,7 @@ tags:
 
 List, install, or uninstall python packages.
 
-Python packages are used to extend the DataIntegration workspace with python plugins. To get a list of installed packages, execute the list command.
+Python packages are used to extend the Build (DataIntegration) workspace with python plugins. To get a list of installed packages, execute the list command.
 
 !!! warning
     Installing packages from unknown sources is not recommended. Plugins are not verified for malicious code.
@@ -133,3 +133,18 @@ With this command, you can open the pypi.org page of a published package in your
 
 
 
+## admin workspace python reload
+
+Reload / Register all installed plugins.
+
+```shell-session title="Usage"
+$ cmemc admin workspace python reload
+```
+
+
+
+
+This command will register all installed plugins into the Build (DataIntegration) workspace. This command is useful, when you are installing packages into the Build Python environment without using the provided cmemc commands (e.g. by mounting a prepared filesystem in the docker container).
+
+
+

docs/automate/cmemc-command-line-interface/command-reference/config/index.md

@@ -12,51 +12,51 @@ tags:
 ```text
 List and edit configs as well as get config values.
 
-    Configurations are identified by the section identifier in the
-    config file. Each configuration represent a Corporate Memory deployment
-    with its specific access method as well as credentials.
-
-    A minimal configuration which uses client credentials has the following
-    entries:
-
-    
-    [example.org]
-    CMEM_BASE_URI=https://cmem.example.org/
-    OAUTH_GRANT_TYPE=client_credentials
-    OAUTH_CLIENT_ID=cmem-service-account
-    OAUTH_CLIENT_SECRET=my-secret-account-pass
-
-    Note that OAUTH_GRANT_TYPE can be either client_credentials, password or
-    prefetched_token.
-
-    In addition to that, the following config parameters can be used as well:
-
-    
-    SSL_VERIFY=False    - for ignoring certificate issues (not recommended)
-    DP_API_ENDPOINT=URL - to point to a non-standard DataPlatform location
-    DI_API_ENDPOINT=URL - to point to a non-standard DataIntegration location
-    OAUTH_TOKEN_URI=URL - to point to an external IdentityProvider location
-    OAUTH_USER=username - only if OAUTH_GRANT_TYPE=password
-    OAUTH_PASSWORD=password - only if OAUTH_GRANT_TYPE=password
-    OAUTH_ACCESS_TOKEN=token - only if OAUTH_GRANT_TYPE=prefetched_token
-
-    In order to get credential information from an external process, you can
-    use the parameter OAUTH_PASSWORD_PROCESS, OAUTH_CLIENT_SECRET_PROCESS and
-    OAUTH_ACCESS_TOKEN_PROCESS to set up an external executable.
-
-    
-    OAUTH_CLIENT_SECRET_PROCESS=/path/to/getpass.sh
-    OAUTH_PASSWORD_PROCESS=["getpass.sh", "parameter1", "parameter2"]
-
-    The credential executable can use the cmemc environment for fetching the
-    credential (e.g. CMEM_BASE_URI and OAUTH_USER).
-    If the credential executable is not given with a full path, cmemc
-    will look into your environment PATH for something which can be executed.
-    The configured process needs to return the credential on the first line
-    of stdout. In addition to that, the process needs to exit with exit
-    code 0 (without failure). There are examples available in the online
-    manual.
-    
+Configurations are identified by the section identifier in the
+config file. Each configuration represent a Corporate Memory deployment
+with its specific access method as well as credentials.
+
+A minimal configuration which uses client credentials has the following
+entries:
+
+
+[example.org]
+CMEM_BASE_URI=https://cmem.example.org/
+OAUTH_GRANT_TYPE=client_credentials
+OAUTH_CLIENT_ID=cmem-service-account
+OAUTH_CLIENT_SECRET=my-secret-account-pass
+
+Note that OAUTH_GRANT_TYPE can be either client_credentials, password or
+prefetched_token.
+
+In addition to that, the following config parameters can be used as well:
+
+
+SSL_VERIFY=False    - for ignoring certificate issues (not recommended)
+DP_API_ENDPOINT=URL - to point to a non-standard Explore backend (DataPlatform) location
+DI_API_ENDPOINT=URL - to point to a non-standard Build (DataIntegration) location
+OAUTH_TOKEN_URI=URL - to point to an external IdentityProvider location
+OAUTH_USER=username - only if OAUTH_GRANT_TYPE=password
+OAUTH_PASSWORD=password - only if OAUTH_GRANT_TYPE=password
+OAUTH_ACCESS_TOKEN=token - only if OAUTH_GRANT_TYPE=prefetched_token
+
+In order to get credential information from an external process, you can
+use the parameter OAUTH_PASSWORD_PROCESS, OAUTH_CLIENT_SECRET_PROCESS and
+OAUTH_ACCESS_TOKEN_PROCESS to set up an external executable.
+
+
+OAUTH_CLIENT_SECRET_PROCESS=/path/to/getpass.sh
+OAUTH_PASSWORD_PROCESS=["getpass.sh", "parameter1", "parameter2"]
+
+The credential executable can use the cmemc environment for fetching the
+credential (e.g. CMEM_BASE_URI and OAUTH_USER).
+If the credential executable is not given with a full path, cmemc
+will look into your environment PATH for something which can be executed.
+The configured process needs to return the credential on the first line
+of stdout. In addition to that, the process needs to exit with exit
+code 0 (without failure). There are examples available in the online
+manual.
+
 ```
 
 ## config list

docs/automate/cmemc-command-line-interface/command-reference/graph/imports/index.md

@@ -0,0 +1,109 @@
+---
+title: "cmemc: Command Group - graph imports"
+description: "List, create, delete and show graph imports."
+icon: material/family-tree
+tags:
+  - KnowledgeGraph
+  - cmemc
+---
+# graph imports Command Group
+<!-- This file was generated - DO NOT CHANGE IT MANUALLY -->
+
+List, create, delete and show graph imports.
+
+Graphs are identified by an IRI. Statement imports are managed by creating owl:imports statements such as "`FROM_GRAPH` owl:imports `TO_GRAPH`" in the `FROM_GRAPH`. All statements in the `TO_GRAPH` are then available in the `FROM_GRAPH`.
+
+!!! note
+    The get a list of existing graphs, execute the `graph list` command or use tab-completion.
+
+
+
+## graph imports tree
+
+Show graph tree(s) of the imports statement hierarchy.
+
+```shell-session title="Usage"
+$ cmemc graph imports tree [OPTIONS] [IRIS]...
+```
+
+
+
+
+You can output one or more trees of the import hierarchy.
+
+Imported graphs which do not exist are shown as `[missing: IRI]`. Imported graphs which will result in an import cycle are shown as `[ignored: IRI]`. Each graph is shown with label and IRI.
+
+
+
+??? info "Options"
+    ```text
+
+    -a, --all   Show tree of all (readable) graphs.
+    --raw       Outputs raw JSON of the graph importTree API response.
+    --id-only   Lists only graph identifier (IRIs) and no labels or other
+                metadata. This is useful for piping the IRIs into other
+                commands. The output with this option is a sorted, flat, de-
+                duplicated list of existing graphs.
+    ```
+
+## graph imports list
+
+List accessible graph imports statements.
+
+```shell-session title="Usage"
+$ cmemc graph imports list [OPTIONS]
+```
+
+
+
+
+Graphs are identified by an IRI. Statement imports are managed by creating owl:imports statements such as "`FROM_GRAPH` owl:imports `TO_GRAPH`" in the `FROM_GRAPH`. All statements in the `TO_GRAPH` are then available in the `FROM_GRAPH`.
+
+
+
+??? info "Options"
+    ```text
+
+    --raw                    Outputs raw JSON response.
+    --filter <TEXT TEXT>...  Filter imports by one of the following filter names
+                             and a corresponding value: from-graph, to-graph.
+    ```
+
+## graph imports create
+
+Add statement to import a TO_GRAPH into a FROM_GRAPH.
+
+```shell-session title="Usage"
+$ cmemc graph imports create FROM_GRAPH TO_GRAPH
+```
+
+
+
+
+Graphs are identified by an IRI. Statement imports are managed by creating owl:imports statements such as "`FROM_GRAPH` owl:imports `TO_GRAPH`" in the `FROM_GRAPH`. All statements in the `TO_GRAPH` are then available in the `FROM_GRAPH`.
+
+!!! note
+    The get a list of existing graphs, execute the `graph list` command or use tab-completion.
+
+
+
+
+## graph imports delete
+
+Delete statement to import a TO_GRAPH into a FROM_GRAPH.
+
+```shell-session title="Usage"
+$ cmemc graph imports delete FROM_GRAPH TO_GRAPH
+```
+
+
+
+
+Graphs are identified by an IRI. Statement imports are managed by creating owl:imports statements such as "`FROM_GRAPH` owl:imports `TO_GRAPH`" in the `FROM_GRAPH`. All statements in the `TO_GRAPH` are then available in the `FROM_GRAPH`.
+
+!!! note
+    The get a list of existing graph imports, execute the `graph imports list` command or use tab-completion.
+
+
+
+

docs/automate/cmemc-command-line-interface/command-reference/graph/index.md

@@ -42,7 +42,7 @@ This command lists graphs with their triple count. Counts do not include importe
 
 ## graph tree
 
-Show graph tree(s) of the owl:imports hierarchy.
+(Hidden) Deprecated: use 'graph imports tree' instead.
 
 ```shell-session title="Usage"
 $ cmemc graph tree [OPTIONS] [IRIS]...
@@ -51,11 +51,6 @@ $ cmemc graph tree [OPTIONS] [IRIS]...
 
 
 
-You can output one or more trees of the import hierarchy.
-
-Imported graphs which do not exist are shown as `[missing: IRI]`. Imported graphs which will result in an import cycle are shown as `[ignored: IRI]`. Each graph is shown with label and IRI.
-
-
 
 ??? info "Options"
     ```text
@@ -117,6 +112,9 @@ In case of file export, data from all selected graphs will be concatenated in on
     --include-imports               Export selected graph(s) and all graphs
                                     which are imported from these selected
                                     graph(s).
+    --include-import-statements     Save graph imports information from other
+                                    graphs to the exported graphs and write
+                                    *.imports files.
     --create-catalog                In addition to the .ttl and .graph files,
                                     cmemc will create an XML catalog file
                                     (catalog-v001.xml) which can be used by
@@ -153,9 +151,11 @@ $ cmemc graph delete [OPTIONS] [IRIS]...
 ??? info "Options"
     ```text
 
-    -a, --all          Delete all writeable graphs.
-    --include-imports  Delete selected graph(s) and all writeable graphs which
-                       are imported from these selected graph(s).
+    -a, --all                    Delete all writeable graphs.
+    --include-imports            Delete selected graph(s) and all writeable
+                                 graphs which are imported from these selected
+                                 graph(s).
+    --include-import-statements  Delete import reference of deleted graphs
     ```
 
 ## graph import
@@ -186,12 +186,16 @@ If the ``--replace`` flag is set, the data in the graphs will be overwritten, if
 ??? info "Options"
     ```text
 
-    --replace        Replace / overwrite the graph(s), instead of just adding
-                     the triples to the graph.
-    --skip-existing  Skip importing a file if the target graph already exists in
-                     the store. Note that the graph list is fetched once at the
-                     beginning of the process, so that you can still add
-                     multiple files to one single graph (if it does not exist).
+    --replace                    Replace / overwrite the graph(s), instead of
+                                 just adding the triples to the graph.
+    --skip-existing              Skip importing a file if the target graph
+                                 already exists in the store. Note that the
+                                 graph list is fetched once at the beginning of
+                                 the process, so that you can still add multiple
+                                 files to one single graph (if it does not
+                                 exist).
+    --include-import-statements  Use *.imports files to re-apply the graph
+                                 imports of the imported graphs.
     ```
 
 ## graph open