Content deleted Content added
→Binary: List UAVCAN |
|||
Line 184:
Okay, there are ''a lot'' of formats out there. I open this section to collect and reference them, and if they reach the notability threshold they can be included in the main article. I'm sure there's plenty.
Also there is some discrepancy/overlapping between ''data-serialization formats'', ''[[data exchange]] formats'' and ''[[configuration file]] formats'', I do not make distinction here since - in my opinion - they are mostly the same set with very similar purposes and only slightly specificattributes. --[[user:grin|grin]] [[user talk:grin|✎]] 09:39, 20 February 2020 (UTC)
:{{reply to|grin}} TOML isn't a [[serialization]] format used as a [[configuration file]] format ([[Configuration_file#Serialization_formats|as often happens]]), it's explicitly designed as a configuration file format. To quote the [https://github.com/toml-lang/toml official objectives]: "TOML aims to be a minimal configuration file format that's easy to read due to obvious semantics."
:The same goes for INI files, and HOCON (it's even in the name: Human-Optimized '''Config''' Object Notation). To quote the HOCON [https://github.com/lightbend/config/blob/master/HOCON.md informal specification]: "The primary goal is: keep the semantics (tree structure; set of types; encoding/escaping) from JSON, but make it more convenient as a human-editable config file format.". Thus everything that HOCON can serialize, JSON can serialize. HOCON is entirely superfluous when it comes to serialization (which this article is about).
:This article is crowded as is. If someone wants a table comparing configuration file formats, then why not create the article "Comparison of configuration file formats"? Then this article could link to that, and that article could link to this. Nothing's stopping that, right?
:[[Special:Contributions/193.138.218.217|193.138.218.217]] ([[User talk:193.138.218.217|talk]]) 11:28, 20 June 2020 (UTC)
==== Human readable ====
| |||