We have a number of open issues and PRs that involve character encoding, which could be handled one-by-one or as a group, in any event likely including an update/clarification of the core spec encoding section. (Encoding is also discussed in other sections of that file as well as for various defined types.)
Please share your views on how we can best address this set of encoding-related issues/PRs.
PR #52 (asks about encoding of ":", "/" and other characters)
PR #150 (concerns encoding of the repository_url value)
PR #176 (asks about encoding "/" in a namespace)
PR #184 (involves percent-encoding of the "/" in an example repository_url value) -- this was merged by sschuberth on 2024-11-21
PR #207 (has a test with a download_url qualifier containing multiple unencoded "/")
PR #261 (involves encoding for qualifiers (here it's space ' ' and plus sign '+'))
issue #35: (character encoding)
issue #39 (asks when ':' and '/' should/should not be encoded)
issue #52: (encoding of ":" in test object version)
issue #58: (encoding of "+" and " ")
issue #73 (asks when a checksum qualifier should be encoded including ":")
issue #204 (encoding, or not, of slashes in a namespace)
We have a number of open issues and PRs that involve character encoding, which could be handled one-by-one or as a group, in any event likely including an update/clarification of the core spec encoding section. (Encoding is also discussed in other sections of that file as well as for various defined types.)
Please share your views on how we can best address this set of encoding-related issues/PRs.