[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-dev
Subject:    Re: [xml-dev] Bad Design? An XML Schema that forces applications to maintain state
From:       Norm Tovey-Walsh <ndw () nwalsh ! com>
Date:       2023-02-07 8:39:48
Message-ID: m2pmalyibw.fsf () nwalsh ! com
[Download RAW message or body]


Roger L Costello <costello@mitre.org> writes:
> In other words, the XML Schema forces applications to maintain state. 
>
> Isn't that really, really bad?
>
> Imagine trying to map this battlefield message data format to some
> other battlefield data format. You would have to do state-dependent
> mapping. Ugh! That's awful! Right?

Maybe. It really depends on the context. If this is a format used by
historians to describe battles and the expectation is that entire
campaigns will be in a single file then not forcing the user to repeat
something is possibly a useful feature. The value you want is always on
a preceding sibling anyway.

Even in a modern context where the messages are being used to describe
an ongoing conflict, if they're routinely sent in small batches, it
might be advantageous to save space by allowing later messages in the
same batch have state implicit from earlier messages.

If they're being sent wholly independently over UDP then, yeah, that
seems bad.

                                        Be seeing you,
                                          norm

--
Norman Tovey-Walsh <ndw@nwalsh.com>
https://nwalsh.com/

> Our years, our debts, and our enemies are always more numerous than we
> imagine.--Charles Nodier

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]