- From: Bethan Tovey-Walsh <accounts@bethan.wales>
- Date: Tue, 25 Jan 2022 11:10:20 +0000
- To: ixml <public-ixml@w3.org>
- Message-Id: <5A354183-5B9C-4331-B32A-51A73B12EF97@bethan.wales>
Hi, all, I accidentally replied to a GitHub issue email, so the original version of this message was lost. Apologies! Attached is an edit of Dave's terminology document. I've proposed some general revisions, and added some terms that I think/hope others may find useful. In particular, I've been finding it hard to work out how to distinguish between the direct XML output of the ixml processor, before any extra processing to turn it into a desired output format. It can't really be an "ixml document", because that risks confusion with the ixml input. And just calling it the "ixml output" was becoming extremely frustrating when I wanted to find a way to distinguish it from the result of post-processing it, e.g. to produce JSON, or a different flavour of XML, or whatever. Then it struck me that "Visible XML" ("vxml") might be a good term for the output of the ixml processor. It picks up Steven's brilliant "invisible" metaphor, and highlights the main aim of ixml: taking the implied structure of the input string and making it explicit, or "visible". I look forward to your comments and criticisms when we meet, and thank you in advance for corrections to any mistakes. Very best wishes, BTW
Attachments
- text/html attachment: stored
- application/octet-stream attachment: terminology.md
- text/html attachment: stored
Received on Tuesday, 25 January 2022 11:10:35 UTC