SeriousBusiness101

Comparing SPDX-ID fields is ad-hoc and inflexible. Also prone to forgery, misrepresentation, and compliance depreciation. Competent and reliable license management is infeasible. There's better pluralistic schemes to index legal particulars.

I abridged. This proposal would encourage using SPDX identifiers in a context which, again: is prone to forgery, misrepresentation, and depreciation of compliance. * The ***only*** appropriate use for a...

Tangental anecdote: The manifest rigmarole for [Rust](https://doc.rust-lang.org/cargo/reference/manifest.html) and [Julia](https://pkgdocs.julialang.org/v1/toml-files/) is an insert of the instant-sharing style of their respective centralized package managers. It's never fully thought out, but particularly unnecessary...

If this plus solutions #17385 and #14534 are accepted, we can achieve this representation in ZON: ```js .{ .@"\{ ff\ 0\ 0}" = "red", .@"\{ 0\ ff\ 0}" = "green",...

While this proposal, motivated by use cases in declarative ZON, erstwhile covered also binary/octal/decimal escapes, that's likely excessive for scenarios where plaintext ZON is exchanged, and there isn't much demand...

@castholm The motivation as in my other issues is foremostly object notation. The desire is 8-bit cleanness, in situations where you're reaching outside of a vacuum. I don't think it...

Actually this form of canonicalization isn't a measure that helps with searchability, most certainly not in the example I presented here @silversquirl. Andrew knows a crime when he sees one.

@silversquirl It's not a non-textual use case. It's disengaged from an exclusive canonicalization for a specific encoding, in what is essentially it's own interchange format. This makes sense in `extern`...

This doesn't call for an extensible parser per se, ultimately comment form tooling to leverage the AST declaratively should be viable with common components (i.e. no forks or unnecessary propagations...

Modularizing this is an emender. This would be a significant redundancy in colossal codebases.