Re: [xml-dev] XML mantra

For many the affinity is for the affordabilities of the ecosystem not the suitability format, so the point of 1 and 2 is so that you can use 3 to do stuff instead of trying to reinvent the same ecosystem for JSON.

The approach is becoming more difficult to apply because environments like AWS pretend that XML doesn't exist and are not supportive of it's tooling.

On Sun, Jan 27, 2019 at 6:27 PM Rick Jelliffe <rjelliffe@allette.com.au> wrote:

Hmmm. s/data/document/g

I don't see that it has ever been shown that XML is generally great for non-document data, such as relational data. And the rise of JSON suggests it is not so congenial for non-pipeline uses too, doesn't it?

Non document data tends to be XML only when there are other requirements or factors, such as longevity, validation, standardization, surrounding architecture, use of framework or library, team exposure, lack of datatypes, where the data firms a natural hierarchy, and so on.

Regards
Rick

On Sat, 26 Jan. 2019, 23:23 Costello, Roger L. <costello@mitre.org wrote:

Still worth repeating …..

XML mantra:

          1. Get data into XML as quickly as possible

          2. Keep it in XML until the last possible minute

          3. Bring all your XML tools to bear on solving the data processing problem

                      -- Sean McGrath

See slide 12 of "Performing impossible feats of XML processing with pipelining"