You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KA-EDC is a product of the [Catena-X Knowledge Agents Kit (about to move to: Tractus-X Knowledge Agents Kit)](https://bit.ly/tractusx-agents) implementing the core "dataspace" modules of the CX-0084 standard (Federated Queries in Dataspaces).
28
+
KA-EDC is a product of the [Tractus-X Knowledge Agents Kit](https://eclipse-tractusx.github.io/docs-kits/kits/knowledge-agents/adoption-view/intro) implementing the core "dataspace" modules of the CX-0084 standard (Federated Queries in Dataspaces).
29
29
30
30
* See the [User Documentation](docs/README.md)
31
+
* See the [Architecture](docs/architecture/Arc42.md)
32
+
* See the [OpenAPI definition](https://github.com/eclipse-tractusx/knowledge-agents/blob/main/docs/api/openAPI.yaml)
33
+
* See the [Administration Guide](docs/admin/README.md)
Copy file name to clipboardExpand all lines: docs/README.md
+6-160Lines changed: 6 additions & 160 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,14 @@
19
19
20
20
# Tractus-X Knowledge Agents EDC Extensions (KA-EDC) Documentation
21
21
22
-
In the Knowledge Agent Architecture, an Agent is any component which speaks and/or enacts a Semantic Web protocol, such as SPARQL.
22
+
In the [Knowledge Agent Architecture](architecture/Arc42.md), an Agent is any component which speaks and/or enacts a Semantic Web protocol, such as SPARQL.
23
23
24
24
The Tractus-X Knowledge Agents EDC Extensions (KA-EDC) introduces support for these protocols (and runnable applications) into the [Eclipse DataSpace Connector](https://github.com/eclipse-edc/Connector) and [Tractus-X EDC](https://github.com/eclipse-tractusx/tractusx-edc).
25
25
26
26
In particular, KA-EDC implements the so-called Matchmaking Agent endpoint that is able to discover and delegate to business data & functions provided by Binding Agents such as provided by [Knowledge Agents Reference Implementations (KA-RI)](https://github.com/eclipse-tractusx/knowledge-agents).
27
27
28
+
See the [Knowledge Agents OpenAPI](https://github.com/eclipse-tractusx/knowledge-agents/blob/main/docs/api/openAPI.yaml) for a detailed description of this protocol.
29
+
28
30
In contrast to the Binding Agents which are restricted to a subset of the full SPARQL protocol called the KA-BIND profile, KA-EDC implements the KA-MATCH and KA-TRANSFER profiles. The data upon which KA-EDC operates however consists of ontology information and the data catalogue of the respective dataspace tenant.
29
31
30
32
## How it works
@@ -47,165 +49,9 @@ using different extensions for
The configuration in your values.yaml follows the [Tractux-X EDC Helm Chart](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/charts/tractusx-connector/README.md).
98
-
A few sections can be copied over 1-1 to the agent-plane which we demonstrate in the following.
99
-
The agent-plane chart is documented [here](charts/agent-plane/README.md).
100
-
The agent-plane-azure-vault chart is documented [here](charts/agent-plane-azure-vault/README.md).
The configuration in your values.yaml follows the [Tractux-X EDC Helm Chart](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/charts/tractusx-connector/README.md).
77
+
A few sections can be copied over 1-1 to the agent-plane which we demonstrate in the following.
78
+
The agent-plane chart is documented [here](charts/agent-plane/README.md).
79
+
The agent-plane-azure-vault chart is documented [here](charts/agent-plane-azure-vault/README.md).
0 commit comments