Efficient XML Interchange about triplea HOT 6 CLOSED

This seems like something that only applies to the transfer of an XML, and would not change the difficulty of writing it or reading it. I don't think we want this.

from triplea.

This would probably just make the XML smaller so result in smaller network overhead. I don't think network overhead is an issue yet. And if it does become someday we can win bigger by upgrading to YAML. I think we can close this.

from triplea.

This needs to be re-opened (or opened as a different issue) and not summarily dismissed in this manner, please and thank you.

First of all, there is an issue with network overhead. The current problem with posting to axisandallies.org is not only the server. The server seems to be getting backed up on uploads. Many times the error dialog will indicate failure but post the file anyway. Smaller files means less backup.

Next, the files are insanely large. Yes, one file on your drive is not a big deal. Trying thousands upon thousands. It adds up quick. My bill for AWS S3 is increasing my $5/month. Smaller files will help reduce this cost.

After watching a preso on EXI, almost any other binary format is better that gzipped xml. EXI was one idea, there's also Protocol Buffers, Message Pack, and even BSON would help on this front.

from triplea.

The processing power needed to parse the EXI format is far less than standard XML.

YAML would be a very bad idea (sorry I usually don't like to criticize without the research behind it but I really should be working right now so I'll get it later, promise 😉).

The only positive YAML has is that it is more human readable. There are other formats even more readable than YAML. JSON5 or TOML come to mind.

The thing is, these files need to be machine readable only. File size and processing should be the quality attributes for this feature not allowing a human to view the file..

from triplea.

Please note that human readability does help with debugging and enhances
the chances of being open to adding new fields inside it (note newer
versions of TripleA should parse older version save files, doesn't it) ?

Bernát GÁBOR

On Mon, Aug 3, 2015 at 8:27 PM, Dave Jensen [email protected]
wrote:

The processing power needed to parse the EXI format is far less than
standard XML.

YAML would be a very bad idea (sorry I usually don't like to criticize
without the research behind it but I really should be working right now so
I'll get it later, promise [image: 😉]).

The only positive YAML has is that it is more human readable. There are
other formats even more readable than YAML. JSON5 or TOML come to mind.

The thing is, these files need to be machine readable only. File size and
processing should be the quality attributes for this feature not allowing a
human to view the file..

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

from triplea.

Yes this is does read older version. You can do that with a binary format too. I'm not saying to use a custom binary format but something like XML or JSON but just the binary representation of that. EXI in particular works almost exactly like XML. The different for "readability" would be you would have to process it into readable UTF-8 text first or use an XML editor that can read EXI.

Why can't you debug a binary format?

• Just unpack the data into an object and investigate, right?
• How many issues that required debugging were errors in the XML itself? 😉

Note: My previous, deleted, response was missing some things so I updated and reposted since I know a few of you are responding via email.

from triplea.