rfcs VS json5

https://github.com/interledger/rfcs/blob/main/0015-ilp-addre...

ILP also specifies settlement; From "Fed expects to launch long-awaited Faster Payments System by 2023" (2022) https://news.ycombinator.com/item?id=32658402 :

> And then you realize you're sharing payment address information over a different but comparably-unsecured channel in a non-stanfardized way; From https://github.com/interledger/rfcs/blob/master/0009-simple-... :

>> Relation to Other Protocols: SPSP is used for exchanging connection information before an ILP payment or data transfer is initiated*

> To do a complete business process, [there's] signaling around transactions, which then necessarily depend upon another - hopefully also cryptographically-secured and HA Highly Available - information system with API version(s) and database schema(s) unless there's something like Interledger SPSP Simple Payment Setup Protocol and Payment Pointers [...]

Clearing (finance) > US: https://en.wikipedia.org/wiki/Clearing_(finance)#United_Stat...

ACH Network:

interledger.org

Joran from TigerBeetle here.

On the contrary, Coil's Interledger [1] project is designing for TigerBeetle, and TigerBeetle will be the core ledger database for Rafiki [2], the open implementation of Interledger.

[1] https://interledger.org

[2] https://github.com/interledger/rafiki

There are a lot of proponents that some or all of the "JSON5" [1] improvements should be standardized by ECMA as well. Especially because there is a mish-mash of support for such things in some but not all parsers. (Writers are a different matter.) Primarily comments and trailing commas, are huge wish list items and the biggest reasons for all of the other "many" variant parsers (JSONC, etc).

[1] https://json5.org/

That is what you get when people reinvent the wheel and lifetimes/ scopes are implicit. Docker could've used something like JSON5 [0] for their configuration format to make the lifetimes explicit. Another time when easy won over simple. [1]

[0] https://json5.org/

JSON5 support

Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.

I think JSON5 is fairly close to this: https://json5.org

I reckon the only thing it's missing to be truly accessible to non-techies is that string values still need to be quoted, i.e. you can't have:

key: this is my value

(I'm definitely not saying it would be a good idea to allow quotes to be dropped, just that that's the only potential stumbling block I see for non-techies.)

I believe that's JSON5.

https://github.com/json5/json5

It's my preferred configuration file format, it fixes all the problems I have with JSON (trailing commas, comments) without turning it into a mess full of gotchas like YAML.