Broken DPV link removed #311
Open
Conversation
This file contains 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
DPV link removed
rartych
requested review from
shilpa-padgaonkar,
patrice-conil,
RubenBG7 and
PedroDiez
as code owners
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.
What type of PR is this?
What this PR does / why we need it:
To avoid maintenance problems in 2 documents: Commonalities and ICM, the external link to W3C DPV is kept in the ICM doc.
Paragraph in 11.6 API Design Guidelines was modified.
Additionally space character was added in line 1469 for better readability.
Which issue(s) this PR fixes:
Fixes #301
Special notes for reviewers:
This PR provides correction to 0.4.0 version and introduces changes into maintenance branch according to Release Management guidelines:
camaraproject/ReleaseManagement#93
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14559630/API+Release+Process#PATCH-update
When approved the changes should be merged into main branch as valid for the next release.
The patch release (v0.4.1) should be prepared if no other corrections are needed.
Changelog input