Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use "hierarchical" form of RFC 2396 syntax #402

Open
ppkarwasz opened this issue Mar 2, 2025 · 0 comments
Open

Use "hierarchical" form of RFC 2396 syntax #402

ppkarwasz opened this issue Mar 2, 2025 · 0 comments
Labels
Ecma specification Work on the core specification PURL core specification Format and syntax that define PURL (excludes PURL type definitions)

Comments

@ppkarwasz
Copy link

The current specification:

  • defines the canonical representation of a PURL as pkg:<opaque_part> (using RFC 2396 syntax).
  • instructs parsers to ignore all solid / characters between pkg: and the start of a namespace.

For languages like Java that don't have an RFC 3986 implementation this means that it is up to the parser to split <opaque_part> into a path, query and fragment.

Would it be possible to change the spec to use pkg:/<hierarchical_part> as canonical representation? This would simplify the reusage of existing language parsers.

Note: I am aware that PURL is defined in terms of RFC 3986, for which the leading solid / does not have any influence on the syntax, but it has an influence for RFC 2396.

@johnmhoran johnmhoran added PURL core specification Format and syntax that define PURL (excludes PURL type definitions) Ecma specification Work on the core specification labels Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ecma specification Work on the core specification PURL core specification Format and syntax that define PURL (excludes PURL type definitions)
Projects
None yet
Development

No branches or pull requests

2 participants