Thomas Smith

I think we agree; I'm hair-splitting in my typical way. Just to be maximally clear/explicit: - The examples are different strings. - They are parsed into different serialization trees. The...

@perlpunk Sorry, I think I'm describing what I mean confusingly. The representation graphs are “equal” according to the definition in 3.2.1.3. Node Comparison (which is used for mapping key uniqueness),...

> if I load the same document into two different native data structures I'm not sure what you mean by this, can you clarify? On Thu, Jul 7, 2022, 18:29...

> Do these three deserialize calls logically build different representation graphs (with different tags) from the YAML point of view? In a word, no. *Construction* is the process that turns...

> I consider the change from non-aliased to aliased nodes (or back) a significant edit. Yeah, I think we have a consensus on that. > I'd like to point out,...

https://spec.yaml.io/pr-277/spec/1.3.0/

Off the top of my head, I believe that `a - b` can always be interpreted `[lookahead ≠ b] a`. Of course, in cases where `a` and `b` are both...

The `eval` thing is definitely specific to JSON. It's only an issue because JSON was created as a subset of JS, and originally `eval` was the only built-in way to...

The canonical form of a scalar node with tag `tag:yaml.org,2002:str` is the same as the formatted content of the node. Whether a scalar is double-quoted, single-quoted, plain, or in block...

Registering a MIME type in the standards tree (as opposed to the vendor or personal trees) requires, among other things, that the spec be published as an RFC. This is...