<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on Eclipse Dataspace Components</title><link>https://eclipse-edc.github.io/documentation/</link><description>Recent content in Documentation on Eclipse Dataspace Components</description><generator>Hugo</generator><language>en</language><atom:link href="https://eclipse-edc.github.io/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Known Friends</title><link>https://eclipse-edc.github.io/documentation/known-friends/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://eclipse-edc.github.io/documentation/known-friends/</guid><description>&lt;p&gt;To get to know how we define &amp;ldquo;adoptions&amp;rdquo; and see how to submit a feature, please take a look at our
&lt;a href="https://eclipse-edc.github.io/documentation/adoption/"&gt;guidelines for submitting adoption requests&lt;/a&gt;.&lt;/p&gt;
&lt;div class="ft" data-ft
 data-ft-title-header="Title"
 data-ft-desc-header="Description"&gt;

 &lt;div class="ft-controls"&gt;
 &lt;label class="ft-label" for="ft-1777973772116924742"&gt;Filter&lt;/label&gt;
 &lt;input
 id="ft-1777973772116924742"
 class="ft-input"
 type="search"
 placeholder="Filter by title or description…"
 autocomplete="off"
 /&gt;
 &lt;div class="ft-status" aria-live="polite"&gt;&lt;/div&gt;
 &lt;/div&gt;

 &lt;div class="ft-content"&gt;
 &lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th style="text-align: left"&gt;Title&lt;/th&gt;
 &lt;th style="text-align: left"&gt;Description&lt;/th&gt;
 &lt;th style="text-align: left"&gt;Links&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;EDC Extension for Asset Administration Shell (AAS)&lt;/td&gt;
 &lt;td style="text-align: left"&gt;Asset Administration Shell (AAS) data can be manually shared over the EDC by linking an EDC Asset to the HTTP endpoint of the specific AAS element. Additionally, contracts and policies have to be defined for each element. In order to minimize configuration effort and prevent errors, this extension is able to link existing AAS services and its elements to the EDC automatically. Furthermore, this extension can also start an AAS service by reading an static AAS model file. A default contract and policy can be chosen to be applied for all elements. For critical elements, additional contracts and policies can be placed. External changes to the structure of an AAS are automatically synchronized by the extension.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/FraunhoferIOSB/EDC-Extension-for-AAS"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;Eclipse Tractus-X EDC&lt;/td&gt;
 &lt;td style="text-align: left"&gt;Extension of the EDC Connector for &amp;ldquo;Manufacturing-X&amp;rdquo; dataspaces that are based on the &lt;a href="https://catena-x.net/"&gt;Catena-X&lt;/a&gt; data ecosystem. The Tractus-X EDC focus in the automatization of the data exchange and contract negotiation withouth human interaction. Additionally it offers a number of optimizations like the &amp;ldquo;Endpoint Data Reference&amp;rdquo; (EDR) interface which simplifies the data negotiation and transfer mechanism, handling token callback for the business applications. It provides also a token refresh handler, an optional BPN-DID resolution service for easier identification of the partners and &amp;ldquo;restricts&amp;rdquo; the usage of &amp;ldquo;odrl&amp;rdquo; policies based on legal requirements, provided by several company lawyers, which stablished the &lt;a href="https://catenax-ev.github.io/docs/regulatory-framework/governance-framework"&gt;goverance/regulatory framework from Catena-X&lt;/a&gt;, enabling the data exchange in a data ecosystem, via this EDC Connector, to be done with legal coverage. Additionally, this EDC Connector offers a deployment configuration via Helm Charts and an extensive architecture documentation from Business/Adoption Level to Development/Operation Level in the &lt;a href="https://eclipse-tractusx.github.io/docs-kits/kits/connector-kit/adoption-view"&gt;Eclipse Tractus-X Connector KIT&lt;/a&gt;.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/eclipse-tractusx/tractusx-edc"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;Data tracking by auditing data&lt;/td&gt;
 &lt;td style="text-align: left"&gt;Proof of concept of how to track data usage by aggregating audit-logs of different components in a single instance: The work presents a first proof of concept of how traceability of data usage can be implemented using the EDC Connector event framework and audit logging. In this PoC, the traceability of data is limited to the AWS dataplane. The EDC Connector logs which exact assets are stored with which key in the AWS bucket. With this information, data usage can be traced from the shared logs of the EDC Connector and the AWS S3 bucket. Elasticsearch was chosen as the instance to merge both logs in this project. A simple Python script takes over the analysis of the log data.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/FraunhoferISST/edc-data-tracebility-app"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;EDC GUI&lt;/td&gt;
 &lt;td style="text-align: left"&gt;Extended EDC Data Dashboard that integrates the open-source EDC Connector interfaces while adding asset properties and form validation, providing design and UX changes, and introducing configuration profiles.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/sovity/edc-ui"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;EDC Connector HTTP client&lt;/td&gt;
 &lt;td style="text-align: left"&gt;An HTTP client to communicate with the EDC Connector for Node.js and the browser.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/Think-iT-Labs/edc-connector-client"&gt;Link to repository&lt;/a&gt; &lt;a href="https://www.npmjs.com/package/@think-it-labs/edc-connector-client"&gt;npm&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;Integration for Microsoft Dynamics 365 and Power Platform&lt;/td&gt;
 &lt;td style="text-align: left"&gt;The prototype demonstrates how to publish product information from a &lt;a href="https://learn.microsoft.com/en-us/power-apps/powerapps-overview"&gt;Microsoft Power App&lt;/a&gt; to a participant in an existing dataspace. The &lt;a href="https://learn.microsoft.com/en-us/connectors/custom-connectors/define-blank"&gt;Microsoft Power Automate custom connector&lt;/a&gt; calls the EDC endpoints from the Nocode/lowcode platform to publish an asset and create a contract. This example shows the integration into the &lt;a href="https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-intro"&gt;Microsoft Dataverse&lt;/a&gt;.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/edc-oneweek/MinimumViableDataspace/blob/2c20b19b2a70b0631818a25112d04e9cc9fad414/dataverse/README.md"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;Silicon Economy EDC&lt;/td&gt;
 &lt;td style="text-align: left"&gt;The Silicon Economy EDC is a configured version from the Connector of the Eclipse Dataspace Components (EDC). It is used and specialized to easily integrate Silicon Economy components with the IDS.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://git.openlogisticsfoundation.org/silicon-economy/base/ids/silicon-economy-edc"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;EDC Extension for IONOS S3 storage&lt;/td&gt;
 &lt;td style="text-align: left"&gt;We are providing an EDC extension to allow the connector to save and to access files kept into an IONOS S3 storage&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/ionos-cloud/edc-ionos-s3"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;EDC metadata extractor extension&lt;/td&gt;
 &lt;td style="text-align: left"&gt;This extension is a PoC to automatically extract metadata of a file that can be used for further processing (e.g., calculating the FAIRness score).&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://gitlab.fit.fraunhofer.de/ameerali.khan/edc-metadata-extractor-extension"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;Huawei Dataspace Components&lt;/td&gt;
 &lt;td style="text-align: left"&gt;Technology repository containing OBS (S3-compatible object storage hosted in the cloud) and GaussDB (a relational database based on Postgres 9.2.4 as data retention backend) extensions&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/eclipse-edc/Technology-HuaweiCloud"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;A Rust client for EDC connector&lt;/td&gt;
 &lt;td style="text-align: left"&gt;A Rust HTTP client to communicate with the EDC Connector.&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/dataspace-rs/edc-rs"&gt;Link to repository&lt;/a&gt; &lt;a href="https://crates.io/crates/edc-connector-client"&gt;Link to crates.io&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;EDC Connector TUI&lt;/td&gt;
 &lt;td style="text-align: left"&gt;A TUI client for EDC Connector written in Rust&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&lt;a href="https://github.com/dataspace-rs/edc-connector-tui"&gt;Link to repository&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style="text-align: left"&gt;&amp;hellip;&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&amp;hellip;&lt;/td&gt;
 &lt;td style="text-align: left"&gt;&amp;hellip;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;

 &lt;/div&gt;
&lt;/div&gt;</description></item><item><title>Getting adopted</title><link>https://eclipse-edc.github.io/documentation/adoption/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://eclipse-edc.github.io/documentation/adoption/</guid><description>&lt;p&gt;This document is intended as guideline for contributors who either already have implemented a feature, e.g. an
extension, or intend to do so, and are looking for ways to upstream that feature into the EDC.&lt;/p&gt;
&lt;p&gt;There are currently two possible levels of adoption for the EDC project:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;incorporate a feature as core EDC component&lt;/li&gt;
&lt;li&gt;reference a feature as &amp;ldquo;friend&amp;rdquo;&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="get-referenced-as-friend"&gt;Get referenced as &amp;ldquo;friend&amp;rdquo;&lt;a class="td-heading-self-link" href="#get-referenced-as-friend" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;This means we will add a link to our &lt;a href="https://eclipse-edc.github.io/documentation/known-friends/"&gt;known friends&lt;/a&gt; list, where we reference projects and features
that we are aware of. These are repositories that have no direct affiliation with EDC and are hosted outside the
&lt;code&gt;eclipse-edc&lt;/code&gt; GitHub organization. We call this a &amp;ldquo;friend&amp;rdquo; of EDC (derived from the C++ &lt;a href="https://en.cppreference.com/w/cpp/language/friend"&gt;
&lt;code&gt;friend class&lt;/code&gt; concept&lt;/a&gt;).
In order to become a &amp;ldquo;friend&amp;rdquo; of EDC, we do a quick scan of the code base to make sure it does not contain anything
offensive, or that contradicts our code of conduct, ethics or other core OSS values.&lt;/p&gt;</description></item><item><title>Committers</title><link>https://eclipse-edc.github.io/documentation/committers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://eclipse-edc.github.io/documentation/committers/</guid><description>&lt;p&gt;Committers decide what code goes into the code base, they decide how a project builds, and they ultimately decide what
gets delivered to the adopter community. With awesome power, comes awesome responsibility, and
so &lt;a href="https://www.eclipse.org/projects/dev_process/#2_1_Open_Source_Rules_of_Engagement"&gt;the Open Source Rules of Engagement&lt;/a&gt;
described by &lt;a href="https://www.eclipse.org/projects/dev_process/"&gt;the Eclipse Foundation Development Process&lt;/a&gt; puts
meritocracy on equal footing with transparency and openness: becoming a committer isn’t necessarily hard, but it does
require a demonstration of merit:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Operate in an open, transparent, and meritocratic manner;&lt;/li&gt;
&lt;li&gt;Write code (and other project content) and push it directly into the project’s source code repository;&lt;/li&gt;
&lt;li&gt;Review contributions (merge and pull requests) from contributors;&lt;/li&gt;
&lt;li&gt;Engage in the Intellectual Property Due Diligence Process;&lt;/li&gt;
&lt;li&gt;Vote in committer and project lead elections;&lt;/li&gt;
&lt;li&gt;Engage in the project planning process; and&lt;/li&gt;
&lt;li&gt;Otherwise represent the interests of the open source project.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For Eclipse projects (and the open source world in general), committers are the ones who hold the keys. Committers are
either appointed at the time of project creation or elected by the existing project team.&lt;/p&gt;</description></item></channel></rss>