GeneThomas

5 ms·

1.
by GeneThomas 2y ago
I have silenced all criticism. The new Xenon Design Rationale shows how Xenon is the best data description language. https://xenondata.org/xenon-design-rationale.html Comment at https://news.ycombinator.com/
2.
by GeneThomas 2y ago
I have silenced all criticism. The new Xenon Design Rationale shows how Xenon is the best data description language. https://xenondata.org/xenon-design-rationale.html Comment at https://news.ycombinator.com/
3.
by GeneThomas 2y ago
Thanks. The linked document justifies all design decisions. Please try to make valid criticism.
4.
by GeneThomas 2y ago
They are for less than and greater than in mathematics!? They are good in markup for a number of reasons including that they stand out.
5.
Xenon Design Rationale: Why it is a better alternative to XML, JSON and YAML(xenondata.org)
2 points by GeneThomas 2y ago|4 comments
6.
by GeneThomas 2y ago
I believe it is readable, what else could that mean but a Book object with the given name, the author details and an array of three one-line reviews. <Book> <Name=A Plan> <Author> <Name=Eric Ha
7.
by GeneThomas 2y ago
See https://news.ycombinator.com/item?id=42038004#42083249
8.
by GeneThomas 2y ago
> * Native support for arrays. I mentioned a few above. `<<Faults$$>>` and `<<$$>>` -- guess what these two mean if you see this first time? You would never guess. It's an empty array and an empty element, yo
9.
by GeneThomas 2y ago
I emboldened the <code> blocks a little. Looks good on Chrome on iPhone but not Edge nor Safari. :o| Thanks.
10.
by GeneThomas 2y ago
> I guess Xenon is designed to be not comfortable for the vast majority of people including me then? You seem fairly comfortable with the rest of English. Korean numbers do not seem to scale well. > allow `$` or not requires a single
11.
by GeneThomas 2y ago
The point is one can apply the xᴇɴᴏɴ library to arbitrary data and generate representative markup. For “Egyptian hieroglyphs not encoded in Unicode” 𓀠 one can write plug-ins.
12.
by GeneThomas 2y ago
There is the concept of “well formed xᴇɴᴏɴ” as outputted by the ᴅᴏᴍ and serializer which is deterministic as will suffice for canonicalization.
13.
by GeneThomas 2y ago
Specific points would be a contribution to the discussion.
14.
by GeneThomas 2y ago
The charset is not published, when it does eventuate byte order marks safeguard the interpretation of documents.
15.
by GeneThomas 2y ago
See https://news.ycombinator.com/item?id=42038004#42082571 Xᴇɴᴏɴ provides semantics around common data types.
16.
by GeneThomas 2y ago
> angle brackets are generally considered bad for the data serialization. Not a point.
17.
by GeneThomas 2y ago
Thanks
18.
by GeneThomas 2y ago
That is the only place that I have stated xᴇɴᴏɴ’s applicability to configuration and data.
19.
by GeneThomas 2y ago
Appears to be a bug in your browser. See the embedded css, the <code> block are the same font size just Courier New or a monospace font.
20.
by GeneThomas 2y ago
> You're about to introduce node attributes. Yes, but limited to #id and :type. > tabular data that is very common as well? Xᴇɴᴏɴ has first class arrays also so tabular data could be stored as such. > explain what makes the
21.
by GeneThomas 2y ago
Have you? And they are quite different!
22.
by GeneThomas 2y ago
Made them lighter so more legible.
23.
by GeneThomas 2y ago
No; I don’t believe so.
24.
by GeneThomas 2y ago
Make a point.
25.
by GeneThomas 2y ago
Odd
26.
by GeneThomas 2y ago
I conject that with programming languages that do not crash schemas used for validation are relatively unimportant. xᴍʟ schemas suffer from the fact that one can not specify that an element may only appear once.
27.
by GeneThomas 2y ago
Make a point
28.
by GeneThomas 2y ago
Xᴇɴᴏɴ excels at both.
29.
by GeneThomas 2y ago
irrelevant
30.
by GeneThomas 2y ago
You mean ʜᴛᴍʟ is not used a such.

More ›