Re:New better alterative to XML, JSON and YAML
by GeneThomas on Sunday November 03, 2024 @11:48PM
(#42038545)
The example you give is valid xᴇɴᴏɴ. The key and value may contain whitespace and must be delineated? <>s are that that made XML and HTML good.
Re:New better alterative to XML, JSON and YAML
by eviks on Monday November 04, 2024 @12:07AM
(#42038665)
So delineate them when they contain whitespace, for example "quotes serve exactly that purpose". There is no point in delineation when there is nothing to delineate, it's just needless verbosity in a language that aims to be "terse"
What exactly is good about <>s that you think it's the good in the bad XML?
Re:New better alterative to XML, JSON and YAML
by lifthrasiir on Monday November 04, 2024 @12:25AM
(#42038756)
There is a widespread agreement that XML is generally bad for the data serialization, while HTML is not much questioned as such. You can't carelessly adopt angle brackets without why such difference exists in the first place [1].
[1] Hint: "semi-structured data"
Re:New better alterative to XML, JSON and YAML
by GeneThomas on Wednesday November 06, 2024 @08:54PM
(#42072437)
You mean ʜᴛᴍʟ is not used a such.
Re:New better alterative to XML, JSON and YAML
by lifthrasiir on Wednesday November 06, 2024 @09:59PM
(#42072905)
If you figured that out yourself, you should have also realized that angle brackets are generally considered bad for the data serialization. Cherry-picking my words without answering my whole point is not a good move.
Re:New better alterative to XML, JSON and YAML
by GeneThomas on Thursday November 07, 2024 @08:31PM
(#42083210)
> angle brackets are generally considered bad for the data serialization.
Not a point.
The best would be to remove all the unneeded unergonomic shift-requiring <characters> from here, you already have = symbol with whitespace and $ that separate all you need
<Person> <Name=Fred> <Height=1.67> <$>