subpath: parsing stops after segments are clear

[jkowalleck]

as proposed via #448 (comment):

the [subpath parsing] process joins on / to produce a final result.

• Joining path segments is not in the domain of PURL.
• I think the spec should stop after the path-segments are clear. Joining segments on FileSystem/OperatingSystem dependent path separators (/, \, >, etc - see https://en.wikipedia.org/wiki/Path_(computing) for more) is out of scope of the spec.
• The same with environment/FileSystem dependent character escapes.

---

is part of #448

[ppkarwasz]

I love the idea of subpath as a list of (Unicode) strings. 💯

[jkowalleck]

dont concat or further handle the segments, similar to qualifiers.
https://github.com/package-url/purl-spec/blob/main/purl-specification.md?plain=1#L515

[mjherzog]

@jkowalleck We need to "move" this PR to update the file:docs/how-to-parse.md because the file: purl-specification.md is generated and not suitable for PRs (as documented in the file header).
We are also applying a 78 character line limit for markdown files to make change tracking easier. (see also #612)
Do you want to make the updates? Or I can ask @johnmhoran to make them.

[jkowalleck]

Do you want to make the updates? Or I can ask @johnmhoran to make them.

please ask @johnmhoran to take this over. I will review their changes afterward.

thanks in advance.

[johnmhoran]

@jkowalleck @mjherzog This PR 449 has been updated and consolidated in #711.

[jkowalleck]

superseded by #711