search

eclipse-tractusx / sig-release

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

Legal Forms concept, Implementation and Standardization #602

Open rybtim opened 8 months ago

rybtim commented 8 months ago

Description

Current legal form list is not sufficient for the first Go-Live of sharing members. GLEIF list does not reflect all countries worldwide. Analysis must be done which countries are missing and which ones, out of them, are required to be reflected with the country specific legal forms in this list.

Recommended to align with the "roll out plan" EU first.

Pool / Gate data model and APIs MUST be adapted to include a way for downloading the legal forms accepted by Catena-X and valid for each country. It MUST be ensured in the sharing process, that only those legal forms are used in the business partners. Legal form list MUST be included as annex in the Pool and Gate API standardization documents, so that it is clear which legal forms are accepted by Catena-X. Portal onboarding and own company data maintenance UIs COULD present this list as a drop-down to select the correct legal form for the business partner.

Impact

Additional information

jjeroch commented 7 months ago

Attention @rybtim : Upcoming PI Planning Preparation

As we gear up for the forthcoming PI Planning session, it is crucial that all features under consideration align with our established Feature Quality Standards and Definition of Done (DoD) guidelines. To ensure your feature is thoroughly prepared and stands a strong chance of being prioritized, please provide comprehensive documentation that includes the following components:

  1. Feature Summary: An executive overview that encapsulates the essence and objectives of the feature.
  2. Change Description:
    • High-Level Overview: A succinct synopsis of the proposed changes and their overarching impact.
    • Detailed Analysis: An in-depth exploration of the specific alterations, including a clear exposition of the anticipated impact on existing systems.
  3. Impacted Components: A list identifying all system components that will be affected by the feature implementation, accompanied by a brief explanation of the nature of the impact.
  4. Acceptance Criteria: A set of clearly defined conditions that must be met for the feature to be considered complete and acceptable.
  5. Test Scenarios: A detailed outline of test cases that cover all functional paths of the feature to ensure robust validation and verification.
  6. Risks/Dependencies

Please note that any feature submissions lacking these essential elements will not be eligible for consideration in the upcoming PI Planning. It is imperative that your documentation is both thorough and precise to facilitate a smooth and effective planning process.

Please let me know in case you have any questions

Grand-Thibault commented 7 months ago

@rybtim please add more content to the description

rybtim commented 7 months ago

No implementation feature for R. 24.08. Handover to Expert Group plannend and moved to Inbox

stephanbcbauer commented 7 months ago

@rybtim added you as assignee because we need a contact person for every feature.

stephanbcbauer commented 7 months ago

Didn't think about it before, but since the feature is still in Inbox, the open decision label is not needed. Opinions?

Sebastian-Wurm commented 5 months ago

Two lists to consider:

  1. Global Legal Identifier Foundation - Legal Forms according to ISO 20275
  2. European Central Bank - Ana Credit Legal Forms -> List of Legal Forms in Annex
Sebastian-Wurm commented 4 months ago

see https://github.com/eclipse-tractusx/bpdm/issues/784

stephanbcbauer commented 1 month ago

@rybtim if this feature is still valid, and we want to have it in the planning for 25.03. Would it be possible for you to also upgrade it to the new feature template

Is the feature already fully refined? If yes, the Backlog status can stay, if not, please set it to Inbox and refine it, with the new template. Thank you very much.

MaximilianHauer commented 2 weeks ago

can you please assign the R25.06 label otherwise we do not know if you still work on this topic

nicoprow commented 5 days ago

@rybtim @Sebastian-Wurm I would like to coin these issues here to be concrete features we can work on. "Legal forms concept" is quite vague and in my opinion does not represent the content of the feature we are trying to work on here. I propose to rename this issue to "Enhance list of supported legal forms".

Also the issue seems to be split into two (which may be the reason for the very generic name). I would like to create a separate feature here "Make supported legal forms selectable in Portal"

Do you agree with this change?

Sebastian-Wurm commented 4 days ago

I agree, that the title is rather on the level of a roadmap item.

BPDM implementation has been done. I am unsure, if Portal wants to implement this. @MaximilianHauer. What do you think?