Re: Invisible XML 1.0 spec has been published
John Cowan <[email protected]>
| Newsgroups | gmane.text.xml.devel |
|---|---|
| Message-ID | <CABzTEQApT_LU0P=ern0-3CMoRT3dk0HGhgXWFf0qCW6QnnVzyg@mail.gmail.com> |
On Fri, Jun 10, 2022 at 4:12 PM C. M. Sperberg-McQueen < [email protected]> wrote: > If by "create a parser" you mean write a program, in some programming > language, which can parse sentences of a particular language, then > nothing could be further from the truth. It depends on whether you think of an ixml grammar as a program or not, I suppose. Admittedly it would be a very high-level program. > TL;DR Why, you ask, is the Invisible XML group trying to re-invent the > wheel? Because we think things will work better with the axle in the > center of the wheel. > Well said. As to binary data, however, ixml seems to be defined in terms of Unicode codepoints/characters, so it would need a preprocessor to convert bytes to characters according to some convention such as Latin-1 or ASCII-with-escapes, such as mapping 2B 5C 81 77 to "+\\\x81w" or alternatively "+\x5c\x81w" or even "2b5c8177". Ixml grammars could handle any of these.