search

eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release
Apache License 2.0
8 stars 8 forks source link

Ensure that Sites (BPNS) can only be shared by Site owner #403

Open rybtim opened 7 months ago

rybtim commented 7 months ago

User Journey

As Catena-X I want to ensure that Sites (BPNS) can only be created/updated by its owner. This is necessary as sites combine several BPNAs and cannot be checked against official registers. If there is no restriction there might be a data quality problem. I as a sharing member want that site information about a sharing member can only be updated by the respective sharing member to ensure data quality. If it is not possible to technologically or procedurally (idea: community site acknowlegement process) verify that a BPNS belongs to a BPNL, it needs to be evaluated which impact possible error cases or malicious intent have. How is it ensured that a claimed BPNS is verified? Description potential Site acknoledgement process: Another member can confirm that a sharing member is the data owner and thus is allowed to create or upload this data. See LinkedIn skill endorsement process. (buzz words: decentral, community approach)

Impact

If possible, please provide insight in what and how many components and teams might be affected or give a hint, if the feature implementation might result in breaking changes. If there are dependencies to other features please name it.

Additional information

stephanbcbauer commented 7 months ago

Discussed in open refinement -> ready for planning (status Backlog)