base on EDC core services including data plane and control plane # EDC Connector [](https://eclipse-edc.github.io) [](https://discord.gg/n4sD9qtjMQ) [](https://search.maven.org/artifact/org.eclipse.edc/boot) [](https://www.apache.org/licenses/LICENSE-2.0) <br> [](https://github.com/eclipse-edc/Connector/actions/workflows/verify.yaml?query=branch%3Amain) [](https://github.com/eclipse-edc/Connector/actions/workflows/trigger_snapshot.yml) [](https://github.com/eclipse-edc/Release/actions/workflows/nightly.yaml) --- ## Documentation Base documentation can be found on the [documentation website](https://eclipse-edc.github.io). \ Developer documentation can be found under [docs/developer](docs/developer/README.md), \ where the main concepts and decisions are captured as [decision records](docs/developer/decision-records/README.md). ## Directory structure ### `spi` This is the primary extension point for the connector. It contains all necessary interfaces that need to be implemented as well as essential model classes and enums. Basically, the `spi` modules defines the extent to what users can customize and extend the code. ### `core` Contains all absolutely essential building that is necessary to run a connector such as `TransferProcessManager`, `ProvisionManager`, `DataFlowManager`, various model classes, the protocol engine and the policy piece. While it is possible to build a connector with just the code from the `core` module, it will have very limited capabilities to communicate and to interact with a data space. ### `extensions` This contains code that extends the connector's core functionality with technology- or cloud-provider-specific code. For example a transfer process store based on Azure CosmosDB, a secure vault based on Azure KeyVault, etc. This is where technology- and cloud-specific implementations should go. If someone were to create a configuration service based on Postgres, then the implementation should go into the `extensions/database/configuration-postgres` module. ### `launchers` Launchers are essentially connector packages that are runnable. What modules get included in the build (and thus: what capabilities a connector has) is defined by the `build.gradle.kts` file inside the launcher subdirectory. That's also where a Java class containing a `main` method should go. We will call that class a "runtime" and in order for the connector to become operational the `runtime` needs to perform several important tasks (="bootstrapping"). For an example take a look at [this runtime](https://github.com/eclipse-edc/Samples/tree/main/basic/basic-01-basic-connector). ### `data-protocols` Contains implementations for communication protocols a connector might use, such as DSP. ## Contributing See [how to contribute](https://github.com/eclipse-edc/eclipse-edc.github.io/blob/main/CONTRIBUTING.md). ", Assign "at most 3 tags" to the expected json: {"id":"10533","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"