Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PCF Exchange Kit] Kit Update Rel. 24.08 #967

Merged

Conversation

wern
Copy link
Contributor

@wern wern commented Jul 5, 2024

Description

Update of PCF Exchange Kit for Rel. 24.08.

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

wern and others added 30 commits June 6, 2024 09:25
…latest CX Rel. 24.08 standards (e.g. references to PCF Rulebook and PCF Data Model)
…8 standards (e.g. references to PCF Rulebook and PCF Data Model)
Date and version for Rel. 24.08 still need to be revised.
@wern
Copy link
Contributor Author

wern commented Jul 8, 2024

@stephanbcbauer This is the PR I mentioned. Who would be responsible to review it?

@wern
Copy link
Contributor Author

wern commented Jul 10, 2024

@danielmiehle @jSchuetz88 Anyone volunteering for a review? Would be highly appreciated ;)
Release Check ticket: eclipse-tractusx/sig-release#749

Copy link
Member

@jSchuetz88 jSchuetz88 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution and overall great update of the PCF KIT.


My findings refer to more "external" dependencies, that unfortunately needs to be resolved.

@@ -9,14 +9,14 @@ sidebar_position: 3

## Introduction

The developer view provides a detailed guide on how to utilize the PCF exchange KIT effectively. Developer will learn how to integrate the kit into there applications and make use of the feature of exchanging PCF values via the Catena-X network.
IT-Administrators will learn how they need to provide PCF data and which components are needed therefore.
The developer view provides a detailed guide on how to utilize the PCF exchange KIT effectively. Developers will learn how to integrate the kit into their applications and make use of the feature of exchanging PCF values via the Catena-X network.

This comment was marked as resolved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed :)

Comment on lines +58 to +63
| [001](https://eclipse-tractusx.github.io/docs-kits/next/kits/Digital%20Twin%20Kit/Software%20Development%20View/API%20EDC%20Discovery/post-list-of-bpns-or-an-empty-array-to-retrieve-available-company-connector-authorization-required-roles-view-connectors) (Lookup EDC endpoints) | POST | /api/administration/Connectors/discovery/ | `[<Company's BPNL>]` |
| [002](https://eclipse-tractusx.github.io/docs-kits/next/kits/tractusx-edc/docs/samples/management-api-v2-walkthrough/catalog) (Look up dDTR) | POST | /v2/catalog/request | --> Lookup Asset in the EDC catalog (EDC asset type data.core.digitalTwinRegistry) |
| [003](https://eclipse-tractusx.github.io/docs-kits/next/kits/Digital%20Twin%20Kit/Software%20Development%20View/API%20AAS%20Discovery/get-all-asset-administration-shell-ids-by-asset-link) (Lookup Twin ID) | GET | /lookup/shells | `assetIds= [{"key": "manufacturerPartId", "value":"mat345",{"key":"digitalTwinType", "value": "PartType"}}]` |
| [004](https://eclipse-tractusx.github.io/docs-kits/next/kits/Digital%20Twin%20Kit/Software%20Development%20View/API%20AAS%20Registry/get-all-asset-administration-shell-descriptors) (Look Up PCF Submodel/EDC Asset ID) | GET | /shell-descriptors | `{DIGITAL TWIN ID}` |
| [005](../resources/development-view/catena-x-pcf-endpoint-1_1_0.yaml) (Requesting PCF Value) | GET | /productIds | {productId} |
| [006](../resources/development-view/catena-x-pcf-endpoint-1_1_0.yaml) (Sending PCF Value) | PUT | /productIds | {productId} |
| [004](https://eclipse-tractusx.github.io/docs-kits/next/kits/Digital%20Twin%20Kit/Software%20Development%20View/API%20AAS%20Registry/get-all-asset-administration-shell-descriptors) (Lookup PCF submodel/EDC asset ID) | GET | /shell-descriptors | `{DIGITAL TWIN ID}` |
| [005](../resources/development-view/catena-x-pcf-endpoint-1_1_1.yaml) (Requesting PCF value) | GET | /productIds | {productId} |
| [006](../resources/development-view/catena-x-pcf-endpoint-1_1_1.yaml) (Sending PCF value) | PUT | /productIds | {productId} |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the API plugin within Docusaurus will be discontinued in the near future and, thus, the links will stop working, please remove or update the references where possible. See: #970

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the MDX files, but kept an empty sidebar.js so build does not break. To also remove this file, I would have to change the top level sidebar.js. Didn't want to change on top level without agreement up front. ;-)

In addition: Is there a break save way to link to the openAPI folder? Did not want to do this relatively and an absolute link did not work.

Copy link
Member

@jSchuetz88 jSchuetz88 Jul 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately I think, for now you should stick with the relative paths. In my understanding, these files will eventually be automatically copied and rendered with swagger. But for now I'm not sure whether it is already automated or not. Hence, we may need to fix the links later on.

Example link: https://eclipse-tractusx.github.io/api-hub/puris/1.0.0/swagger-ui/
In this case the final link should look like: https://eclipse-tractusx.github.io/api-hub/pcf/1.1.1/swagger-ui/

In addition an *optional* constraint for an existing tenant-specific bilateral contract can be added. It should reference the contract number and is NOT backed up by verifiable credentials. Nevertheless it will be checked on a syntactical level during contract negotiation. If such a contract refererence should be used, a specific usage policy per tenant is needed, as constraint concatenation via OR is not recommended.

>**Note**
>More informations can be found in the official [ODRL Profile Definition](https://github.com/catenax-eV/cx-odrl-profile/blob/main/profile.md).

This comment was marked as resolved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It meant to be a general note that this is a source of information. No specific version required.

@wern
Copy link
Contributor Author

wern commented Jul 11, 2024

Thank you for your contribution and overall great update of the PCF KIT.

My findings refer to more "external" dependencies, that unfortunately needs to be resolved.

@jSchuetz88 Do you have specific images in mind? I tested sequence charts and diagrams and could perfectly zoom in (even on a bigger screen). We should be able to provide SVGs for most images, but wanted to check up front if we need it for some specific ones.

@jSchuetz88
Copy link
Member

Thank you for your contribution and overall great update of the PCF KIT.
My findings refer to more "external" dependencies, that unfortunately needs to be resolved.

@jSchuetz88 Do you have specific images in mind? I tested sequence charts and diagrams and could perfectly zoom in (even on a bigger screen). We should be able to provide SVGs for most images, but wanted to check up front if we need it for some specific ones.

Sorry, I double checked. It seems it was an issue on my side with the zoom. Personally I would sill prefer SVGs, but all of the images are perfectly readable.

Copy link
Contributor

@danielmiehle danielmiehle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@danielmiehle
Copy link
Contributor

@maximilianong please add your review.


![EDCDiscoveryAndDTRAccess](../resources/development-view/EDCDiscoveryanddDTRAccess.png)

### PCF Request

To actual request PCF values via the PCF API endpoint first of all the EDC PCF asset needs to be identified. Therefore the decentralized Digital Twin Registry (dDTR) is used. Data provider must register their dDTR(s) as EDC assets following the CX-0002 standard. After identifying the dDTR the Digital Twin with the related PCF submodel can be looked up (see [API calls [0003 +0004]](#api-calls)). An example is documented [here](#payload-for-requesting-pcf-sub-model).
In order to request PCF values via the PCF API endpoint first of all the EDC PCF asset needs to be identified. Therefor, the decentralized Digital Twin Registry (dDTR) is used. Data providers must register their dDTR(s) as EDC assets following the [CX-0002](https://catenax-ev.github.io/docs/next/standards/CX-0002-DigitalTwinsInCatenaX) Digital Twins in Catena-X standard. After identifying the dDTR, the digital twin with the related PCF submodel can be looked up (see [API calls [0003 +0004]](#api-calls)). An example is documented [here](#payload-for-requesting-pcf-sub-model).

This comment was marked as resolved.

Copy link
Member

@jSchuetz88 jSchuetz88 Jul 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is unclear to me, why the same openAPI has been uploaded twice? Within the Kit and within the openAPI-folder?
Removing this one, would also prevent the requirement for an IP-clearance check.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unclear to me, why was the overall CHANGELOG deleted?

Copy link
Member

@jSchuetz88 jSchuetz88 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the updates. Although I have a few last minor remarks, that should be considered, there is nothing left which prevents an approval from my side.

@maximilianong maximilianong merged commit eaea65e into eclipse-tractusx:main Jul 26, 2024
5 checks passed
@jSchuetz88
Copy link
Member

@wern The PR had to been reverted, as its deleted the overall Changelog. Please re-open a new PR without the Deletion of the src/pages/CHANGELOG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants