Shawn Silverman

Ah, so it's the validator spec that describes this better. If the validation vocabulary is optional, that would explain why the `zeroTerminatedFloats.json` test is optional.

> > 1. Can we JSON-encode the int 1 as "a_number": 1.0? > > This is the case the spec is trying to discourage. This is the problematic thing for...

> Most of the point of JSON Schema is portability :) > > If it didn't acknowledge the existence of languages like JS it's just excluding its ability to be...

> > Ah, so it's the validator spec that describes this better. If the validation vocabulary is optional, that would explain why the `zeroTerminatedFloats.json` test is optional. > > the...

You're right, this is off into the weeds... (But to summarize and explain: I was giving an illustrative example of JavaScript's restrictions influencing specifications. I also don't agree that "1.0"...

This code update is just a suggestion. No worries if you decide not to use it.

Thanks for the information. (Side note: I've been maintaining a separate IEEE 1588 branch locally that is far ahead of this one because it's rebased on top of the latest...

I haven't forgotten about this. When I next have a chance, I'll have a look.

It turns out that without the fix, the transmit properly sends 7-bit data, but receive still sometimes sets the 8th bit high. I need to explore more...

On my journey to understanding this better — It's been a while since I've explored this in depth (for TeensyDMX) — I think I'm re-discovering that the "data" includes everything...