subpath: serializing uses segments

[jkowalleck]

path segments are environment-dependent, and therefore, the splitting is not really in our domain.
Anyway, we can improve our process in the correct direction, by using "path delimiter" instead of '/'.

---

• see also subpath: parsing stops after segments are clear #449

---

this is the serialization-part implied as proposed via #448 (comment):

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

• [...]
• 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.
• [...]

---

is part of #448

[matt-phylum]

PURLs are not bound to the operating system they are created on, and their interpretation must not change when used on a different operating system.

[jkowalleck]

please read the ticket's description: #458 (comment)

[mjherzog]

@jkowalleck We need to "move" this PR to update the file:docs/how-to-build.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.
thanks in advance.

[johnmhoran]

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

[jkowalleck]

superseded by #711