gmabey

> Maybe @gmabey will give you write access to his fork to make those additions I'm happy to accept and review PR's to my fork

> Examples that are not useful will get the 🧹 In my mind, there is a significant difference between "sample code" (to draw a C++ analogy, code that demonstrates how...

I did move `wav2sigmf.py` to `sigmf/tools/` (utils/ wouldn't work as there's already a `utils.py` in there. I think that this file is unique (in SigMF) in that it's intended to...

Yes, but I think all of what you said is already in the spec, and you didn't address the asymmetry in allowance of top level fields like I'd hoped. I'm...

Sorry let me back up. Both recordings and collections have a canonical set of top-level keys; in the case of recordings, that set is of size 3, whereas for collections...

I agree that it could/should be sharpened, but here's the line that led me to believe that extensions could add new top-level, under `Extension Namespaces`: ``` 4. An extension namespace...

poke @bhilburn

Here's that utility that I threatened to write: https://github.com/gmabey/SigMF/commit/b00567afa553b91bc123c276d8d4d936deb0d867 You have to download the win64-binary from https://www.libarchive.org and surely hafta tweak `build.bat` but other than that it should be good...

> Thanks @gmabey I agree there is a problem here. The N/N.sigmf-* structure was very much intentional. I believe you when you say it was intentional. I'm just asking for...

Hello @mibangah -- Please do review the explanation of what `pip` is to make sure you generally understand what the purpose of that line is, at https://pypi.org/project/pip/ Some basic prerequisites...