From ba7027ada7a3ed4bc92d4ae1d133b396f6342ea8 Mon Sep 17 00:00:00 2001 From: Stephan Bauer Date: Tue, 31 Oct 2023 10:14:36 +0100 Subject: [PATCH] Delete unused files and content --- .../kit/adoption-view/page_domain_model.md | 64 ------------------- sidebarsDocsKits.js | 1 - 2 files changed, 65 deletions(-) delete mode 100644 docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_domain_model.md diff --git a/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_domain_model.md b/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_domain_model.md deleted file mode 100644 index 5143889f9e9..00000000000 --- a/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_domain_model.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -id: Domain Model -title: Domain Model -description: 'Connector Kit' -sidebar_position: 2 ---- - -![domain-model](images/domain-model.png) - -> The shown picture illustrates only a generic view of the Domain Model and is not intended to show all aspects of the project. - -## Asset - -An asset represents data (databases, files, cache information, etc.) which should be published and shared between -organizations. For each asset, a [`DataAddress`](#data-address) needs to be resolvable. - -## Data address - -A data address is a pointer into the physical storage location where an asset will be stored. - -## Contract - -A contract always contains one or more [`Assets`](#asset) and a single [`Policy`](#policy). The contract construct is -used to define the arrangement between two parties ("consumer" and "provider"). Regarding this arrangement, the contract -passes several stages which are explained below: - -### Contract definition - - Contract definitions associate a policy with assets. A `ContractDefinition` object contains an access policy, a contract - policy, and an asset selector which links the contract to one or more assets. - -### Contract offer - - The contract offer is a dynamic representation of the [`ContractDefinition`](#contract-definition) - for a specific consumer and serves as protocol's data transfer object (DTO) for a particular contract negotiation. - Contract offers are not persisted and will be regenerated on every request. The connector acting as data provider will - generate contract offers only for contract definitions dedicated to the organization or data space participant - operating the requesting connector acting as data consumer. A contract offer is always related to a single asset of - the `ContractDefinition` object (e.g. for a `ContractDefinition` containing three `Asset` objects, the connector will - generate three `ContractOffer` objects). - -### Contract negotiation - - A `ContractNegotiation` captures the current state of the negotiation of a contract (`ContractOffer` -> - `ContractAgreement`) between two parties. This process is inherently asynchronous. - -### Contract agreement - - A contract agreement represents the agreed-upon terms of access and usage of an asset's data between two data space - participants, including a start and an end date and further relevant information. - -## Policy - -Contract policies represent permitted and prohibited actions over a certain asset. These actions can be limited further -by constraints (temporal or spatial) and duties ("e.g. deletion of the data after 30 days"). - -## Transfer process - -After a successful contract negotiation, a `DataRequest` is sent from a consumer connector to a provider connector to -initiate the data transfer. It references the requested [`Asset`](#asset) and [`ContractAgreement`](#contract-agreement) -as well as information about the [data destination](#data-address). - -Similar to the `ContractNegotiation`, this object captures the current state of a data transfer. This process is -inherently asynchronous, so the `TransferProcess` objects are stored in a backing data store (`TransferProcessStore`). diff --git a/sidebarsDocsKits.js b/sidebarsDocsKits.js index 0d291b51edd..6bd157f3ef7 100644 --- a/sidebarsDocsKits.js +++ b/sidebarsDocsKits.js @@ -108,7 +108,6 @@ const sidebars = { collapsed: true, items: [ 'kits/tractusx-edc/docs/README', - 'kits/tractusx-edc/docs/kit/adoption-view/Domain Model', { type: 'category', label: 'openAPI',