(#3syipzq) @lyse its a hierarchy key value format. I designed it for the network peering tools i use.. I can grant access to different parts of the tree to other users.. kinda like directory permissions. a basic example of the format is: ``` @namespace # multi # line # comment root :value # example space comment @namespace.name space-tag # attribute comments attribute attr-tag :value for attribute # attribute with multiple # lines of values foo :bar :bin :baz repeated :value1 repeated :value2 ``` each `@` starts the definition of a namespace kinda like `[name]` in ini format. It can have comments that show up before. then each attribute is `key :value` and can have their own `#` comment lines. Values can be multi line.. and also repeated.. the namespaces and values can also have little meta data tags added to them. the service can define webhooks/mqtt topics to be notified when the configs are updated. That way it can deploy the changes out when they are updated.

(#3syipzq) I can query the configurations a few different ways. i can request the specific name `foo.bar` or a glob like `foo.*` or trace the hierarchy `trace:some.deep.name.space` which will give me the namespaces `some`, `some.deep`, `some.deep.name`, and `some.deep.name.space`. These can be combined.

(#3syipzq) and then i have a compact version that makes things more grep'able in scripts.

(#3syipzq) @xuu Cool! I particularly like the idea of converting it into a `grep`-able version, that's very neat. Interesting choice of aligning the colons at the values and not the keys, I think I never came across this.

(#3syipzq) well, at work we use JSONC which basically is JSON + // and /* */ Its syntax is supported by vs code, and we wrote a few scripts to remove the comments so it's practically compatible with anything It's day and night not only for configuration but for testing and development.