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
maven/mavencentral/jakarta.activation/jakarta.activation-api/2.1.0, EPL-2.0 OR BSD-3-Clause OR GPL-2.0-only with Classpath-exception-2.0, approved, ee4j.jaf
99
99
maven/mavencentral/jakarta.annotation/jakarta.annotation-api/2.1.1, EPL-2.0 OR GPL-2.0-only with Classpath-exception-2.0, approved, ee4j.ca
Copy file name to clipboardExpand all lines: agent-plane/agent-plane-protocol/README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,11 +23,12 @@ This folder hosts the [Agent Data Protocols Extension for the Eclipse Dataspace
23
23
## Architecture
24
24
25
25
This extension
26
-
- introduces a tenant-internal endpoint (Matchmaking Agent) for submitting possibly federated queries (called Skills) in the supported inference languages (currently: SparQL)
26
+
- introduces or interfaces to a tenant-internal endpoint (Matchmaking Agent) for submitting possibly federated queries (called Skills) in the supported inference languages (currently: SparQL)
27
+
- hosts a synchronisation schedule which regulary requests the catalogue from configured partner connectors and includes them into the default graph
27
28
- may negotiate further agreements for delegating sub-queries on the fly, for which purpose it also operates as an EDR callback for the control plane
28
29
- may operate as a validation proxy in case that this data plane is attached to several control planes (e.g. a consuming and a providing control plane)
29
30
- implements special Sources for dealing with http-based transfer protocols, such as SparQL-Over-Http and Skill-Over-Http
30
-
- hosts a synchronisation schedule which regulary requests the catalogue from configured partner connectors and includes them into the default graph
31
+
31
32
The SparQL implementation currently relies on Apache Jena Fuseki as the SparQL engine.
32
33
33
34
see the [Overall Source Code Layout](../../README.md#source-code-layout--runtime-collaboration)
@@ -63,7 +64,7 @@ Add the following dependency to your data-plane artifact pom:
| cx.agent.matchmaking ||http://matchmaking-agent.internal| URL of the matchmaking agent (use internal one if null) ||
92
94
| cx.agent.asset.default || urn:x-arq:DefaultGraph| IRI of the default graph (federated data catalogue) ||
93
95
| cx.agent.asset.file ||https://www.w3id.org/catenax/ontology,dataspace.ttl| Initial triples for the default graph (federated data catalogue) | L |
94
96
| cx.agent.accesspoint.name || api | Matchmaking agent endpoint name (internal) ||
@@ -109,7 +111,7 @@ See [this sample configuration file](resources/dataplane.properties)
109
111
| cx.agent.service.deny || ^$ | Regular expression for determining which IRIs are denied in SERVICE calls (on top level/federated data catalogue) |||
110
112
| cx.agent.service.asset.allow || (http|edc)s://.*| Regular expression for determining which IRIs are allowed in delegated SERVICE calls (if not overriden by the cx-common:allowServicePattern address property) ||
111
113
| cx.agent.service.asset.deny || ^$ | Regular expression for determining which IRIs are denied in delegated SERVICE calls (it not overridden by the cx-common:denyServicePattern address property) |||
112
-
| cx.agent.dataspace.remotes ||http://consumer-edc-control:8282,http://tiera-edc-control:8282| business partner control plane protocol urls to synchronize with | L |
114
+
| cx.agent.dataspace.remotes ||http://consumer-edc-control:8282,http://tiera-edc-control:8282| business partner control plane protocol urls to synchronize with (if using internal matchmaking) | L |
113
115
| cx.agent.sparql.verbose || false | Controls the verbosity of the SparQL Engine ||
114
116
| cx.agent.threadpool.size || 4 | Number of threads pooled for any concurrent batch calls and synchronisation actions ||
115
117
| cx.agent.federation.batch.max || 9223372036854775807 / 8 | Maximal number of tuples to send in one query ||
0 commit comments