Skip to content

Commit

Permalink
remove open questions
Browse files Browse the repository at this point in the history
  • Loading branch information
gerlitmcoding committed May 13, 2024
1 parent 4c9762a commit 3d1ffa8
Showing 1 changed file with 0 additions and 17 deletions.
17 changes: 0 additions & 17 deletions docs/arc42/arc42-bpdm.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,6 @@
- [Architecture Decisions](#architecture-decisions)
- [Quality Requirements](#quality-requirements)
- [Risks and Technical Debts](#risks-and-technical-debts)
- [Glossary](#glossary)
- [NOTICE](#notice)

# Introduction and Goals
Expand Down Expand Up @@ -770,17 +769,6 @@ In addition to the Spring standard logs the BPDM applications keep a log of the

# Risks and Technical Debts

**Open EDC Questions**
* What capabilities will be provided in the future?
* How to deal with APIs provided behind an EDC? Swagger documentation cannot be seen by the requesting service?
* How can we authorize and authenticate a User/System with individual permissions after it passes the EDC?
* Will there by a Proxy EDC concept?
* ...


**Semantic Model and SSI Integration of the Golden Record**
* Not in scope.

**Dependency on third party service provider**
* Currently we are not flexible enough to easily change the third party service provider for golden record creation. Therefore the next step will be to introduce an own data persistence layer, getting more independent.
* ✔️Solved via "Simulator Application"
Expand All @@ -794,11 +782,6 @@ In addition to the Spring standard logs the BPDM applications keep a log of the
* Uploading via CSV File. Does it requires an EDC?
* ⚠️Current State: Yes, is needed.

# Glossary

The Glossary is currently under development and will be added below after internal approval ([DRAFT](https://confluence.catena-x.net/display/CORE/BPDM+Glossary+-+Internal+-+DRAFT)).

The current version you can find in the Catena-X Standards.

## NOTICE

Expand Down

0 comments on commit 3d1ffa8

Please sign in to comment.