9 ms·
Invisible XML is a language for describing the implicit structure of data
- layer8 4y agoSo, this is a grammar format specification, plus a specification of how ASTs parsed using such grammars are output (serialized) as XML, and some requirements on “processors” doing the parsing and serialization if they claim conformance to the ixml specification.
- PaulHoule 4y agoThis looks like a parser generator that makes an object tree in the form of an XML document.
- quesomaster9000 4y agoI was going to say the same, it looks like an (E)BNF to AST parser which outputs XML. My only quandary would be whether the output XML structure could be ambiguous given the parse tree and input (requiring lots of context-dependent if/then logic when interpreting the XML). Perhaps some kind of invisible XML stylesheet could pre-process the AST before outputting the XML. And secondly, can it handle CSV? If so, along with a command-line app like `jq` it could be an extremely useful addition to the general purpose data munging toolkit. Or do I have to pass the input through a 1000+ byte `sed` script first to normalize it.
- sixdimensional 4y agoI too was also about to say the same. I was literally just working on a project with TatSu[1] in Python which contains language elements that are conditional based on patterns in the syntax. I found that the added RegEx matching to EBNF-like syntax was quite powerful. My only issue was the generated parser appeared to parse the entire content into memory rather than stream parsing. I haven’t read enough on ixml yet, but, while it seems like while it would unlock many existing toolkits (I never hated XML but went away from it as the industry did), it seems like parsing through an XML format should be done in a stream mapping fashion, and not persisting data, for the XML to be truly “invisible”. Adding the overhead of XML back into the processing chain… hmm, honestly have to think if the value of accessing the data and XML toolchain is worth it. I’d almost rather see something that can read any input as a stream with a grammar and produce a stream (that can be materialized) of more optimized, yet open format, that can be compressed but handle complex types.. like protobufs, or flatbuffers. I’m not sure that humans need to read raw data files so long as we have great and open tooling to view data in binary formats (iirc, the biggest argument against XML and the added overhead originally). [1] https://tatsu.readthedocs.io/en/stable/index.html https://tatsu.readthedocs.io/en/stable/index.html
- secondcoming 4y ago+1 XML is to data what UML is to software
- ironhaven 4y ago> Invisible XML (ixml) is a method for treating non-XML documents as if they were XML, > enabling authors to write documents and data in a format they prefer while providing XML for processes that are more effective with XML content. Interesting although this seems a little out of date because xml seems to one of the least desirable data formats for modern programming languages. Maybe this is more useful for legacy enterprise use cases that I don’t know about.
- zapperdulchen 4y agoThere are XML workflows in technical documentation outside of software development where something like this could be of interest.
- gavinray 4y agoThe fact that it's XML is not super relevant -- what you're working with in code is a tree structure that may as well be JSON or YAML This is essentially a way to write grammars for things and get the ability to parse them as trees in a common format that is interchangeable with things like JSON. I honestly don't see much of a difference between this, and something like a PEG grammar where you do this: let parsed = peg.parse(input, grammar) let xml = json2xml(parsed)
- tokinonagare 4y agoXML still has few advantages over JSON: comments, namespaces, a canonical form and slightly better extensibility.
- tartoran 4y agoAt the expense of excessive verbosity. I used xml and still do to this day and it is one of my least favorite formats to read and edit.
- mpyne 4y agoJSON either has those (namespaces, extensibility) or the advantage is slight at best (comments, canonical form). There is a real advantage of XML over JSON not mentioned though, which is its usefulness in annotating computer-readable data into an otherwise human-editable document. There's not a lot of these cases, and where they're at you're probably still better off using AsciiDoc, Markdown or even HTML instead, but those use cases are out there and JSON is awful for those.
- tannhaeuser 4y agoHmm, on the one hand this proposal makes XML come full-circle and re-introduce SGML concepts (eg. SHORTREF) that were explicitly omitted from XML as a simplified SGML subset for canonical angle-bracket markup without the need for markup declarations; OTOH, Norm and Steve are fully aware of SGML. I'd really appreciate if whoever wants to re-introduce SGML features to XML would justify and align their proposal with SGML, just as XML has been introduced as a proper, well-aligned subset of SGML.
- pshc 4y agoI see you’re trying to sneak XML into common use again. Haven’t we already suffered enough?
- solardev 4y agoNow you can export your SQL dump to YAML, parse it to XML, convert it to JSON, put it in NoSQL, messagepack it into a key-value store and finally be able to query your customer names!
- tetris11 4y agoIf only things were that easy!
- adamretter 4y agoI think one of the interesting points missed here, is that if you can convert to XML then you can use the large selection of mature tooling around XML to query, transform, and process your data.
- iFire 4y agoSo let's say I have a binary format.. Let's say PMX. https://gist.github.com/felixjones/f8a06bd48f9da9a4539f https://gist.github.com/felixjones/f8a06bd48f9da9a4539f How do I implement a C++ library to parse PMX to XML and from that XML back into PMX?
- mdaniel 4y agoI don't get the impression this is designed for binary formats, merely "non XML" ones. The task you described sounds like a better fit for https://kaitai.io/ https://kaitai.io/
- hyperpallium2 4y agoxsugar is a similar solution (to a different problem): a mapping between a context free grammar and XML grammar, thus between text and XML. https://www.brics.dk/xsugar/ https://www.brics.dk/xsugar/ XSugar makes it possible to manage dual syntax for XML languages. An XSugar specification is built around a context-free grammar that unifies the two syntaxes of a language. Given such a specification, the XSugar tool can translate from alternative syntax to XML and vice versa
- nojvek 4y agoI read some samples, how is this better than good ol JSON?
- mdaniel 4y agoThe mime type handler on https://invisiblexml.org/ixml.ixml https://invisiblexml.org/ixml.ixml link is bogus, causing the browser to download what appears to the normal eye to be a text file. If the authors see this, I'd recommend changing that to point to the GH repo https://github.com/invisibleXML/ixml/blob/master/ixml.ixml https://github.com/invisibleXML/ixml/blob/master/ixml.ixml which allows actually viewing it as well as making folks aware of the GH org
- kaba0 4y agoHow is it different than ANTLR? Like one could quite trivially add an XML serializer to it and get a functionally equivalent program, right?