Jeremy Whitlock

Don't think of it in terms of conflicts in how a format is handled but in terms of different validators (dis)allowing different formats. Maybe I'm just writing tests that are...

I'll get started.

What if it just followed the FIT spec? A FIT file has a _header_, an array/list or _record_ objects and a _CRC_. I've just started writing a parser in Go...

From what I see, it looks good. I'll give it a spin soon. If you don't hear from me, feel free to ping me.

While the _"JSON"_ in _"JSON Reference"_ implies that it would only work for JSON-stored data, that's not actually true as it could very easily be used to reference data in...

I guess I could see where writing a library that was content-aware to swap between resolving in structured language X to structured language Y could be difficult. But I could...

> It does not define the resolution behavior of non-JSON data I'm not sure JSON Reference cares about the data being resolved, and in my opinion it shouldn't care. Resolution...

I've actually thought of enabling support for this in [json-refs](https://github.com/whitlockjc/json-refs) via an option, like an experimental feature.

JSON References are really just a specialized structure, an object containing a sole `$ref` property whose value is a [URI](https://datatracker.ietf.org/doc/html/rfc3986). URIs are pretty dang good at pointing to where something...

I realize the _"JSON_" in _"JSON Pointer"_ and _"JSON Reference"_ implies that the containing document is JSON and the referrant document is JSON. But the structure and syntax of these...