Slash encoding in qualifiers #293
Replies: 1 comment 3 replies
-
The official test suite makes it clear that slashes are expected not to be escaped. For example (ironically for Java packages, even though the Java implementation does escape them): purl-spec/test-suite-data.json Lines 110 to 121 in 3465898 But I have noticed the following reasons for implementations to fail the official test suite:
I made https://github.com/phylum-dev/purl-survey to be able to compare implementations and it can run the same test suite consistently for all implementations. I entered GitHub issues for some egregious implementation errors, but there are still serious problems which are not covered by the test suite and can cause PURLs to change meanings. |
Beta Was this translation helpful? Give feedback.
-
Continuing the discussion that started in package-url/packageurl-python#121 (comment)
It appears different implementations under https://github.com/package-url implement encoding of slashes (among other things) differently. It'd be good to clarify whether some of them should be fixed to have a consistent encoding across different implementations.
For example, the Python implementation
results in
While the Java one
results in
Would it be worth it creating an issue to align implementations of the encoding rules? Thanks.
FYI @tichavskym
Beta Was this translation helpful? Give feedback.
All reactions