Task4 up#116
Open
peppelinux wants to merge 2 commits into
Open
Conversation
Contributor
Author
|
this review was brought by @Sebastian-Elfors-IDnow |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the documentation for the Trust Infrastructure and Onboarding APIs to clarify their scope, align descriptions with relevant European Commission technical specifications, and add normative references. The changes ensure that the APIs are clearly mapped to EC and ETSI standards, improving traceability and compliance for implementers.
API Scope and Description Updates:
README.md,task4-trust-infrastructure-api/README.md,task4-trust-infrastructure-api/onboarding-api/README.md,task4-trust-infrastructure-api/trust-infrastructure-api/README.md: Expanded descriptions for the Trust Infrastructure API and Onboarding API to specify the types of endpoints provided, their alignment with EC technical specifications (TS02, TS05, TS06), and upcoming ETSI standards. [1] [2] [3] [4]Normative References and Standards Alignment:
task4-trust-infrastructure-api/README.md,task4-trust-infrastructure-api/onboarding-api/README.md,task4-trust-infrastructure-api/trust-infrastructure-api/README.md: Added detailed lists of normative references, including links to EC TS02, TS05, TS06, and ETSI EN 319 486, and mapped them to relevant ARF topics and requirements. [1] [2] [3]task4-trust-infrastructure-api/README.md,task4-trust-infrastructure-api/onboarding-api/README.md: Referenced related project documents and legal bases (e.g., Regulation (EU) 2025/848) to clarify the regulatory context for the APIs. [1] [2]These updates improve the documentation’s clarity, regulatory alignment, and usefulness for implementers.