Re: Why XML to comunicate Distributed Components?

carofe wrote:

XML has some features as self-described, human-readable, etc..., and
there are many tools for validation and parsing.

XML is the winner of a primordial soup of text-oriented file formats. It didn't win because of pre-eminence in any single one of those features. It won partly due to inertia (the way right-limbed dominance seems to have "won" among tetrapods), and partly because it presented an adequate fix for _all_ of those bullet points, all at the same time.

Those features are very useful for Configuration files and
Descriptions file which could be edited by humans.

That's YAML's spot, thank you!

(Aka JSON!;)

But, Are those features necessaries to communicate two components?

RPC is a self-description layer, without (correct me whether or not I'm wrong) a transport or representation. XML+RPC provides one of many intercommunication systems. None are perfect, or 100% used.

And, of course, XML abuse is rampant, as with any popular technology...

--
Phlip
.