Re: Why XML to comunicate Distributed Components?
- From: Patrick May <pjm@xxxxxxx>
- Date: Thu, 28 Feb 2008 16:22:36 -0500
ram@xxxxxxxxxxxxxxxxxx (Stefan Ram) writes:
Robert Martin <unclebob@xxxxxxxxxxxxxxxx> writes:
There are better formats out there. Yaml, JSon, etc.
Possibly, the simplest expressive format is S-expressions.
The nice thing about s-expressions is that you can treat them as
data in Java and code in Lisp or Scheme. Plus they are far more
consistent and concise than XML.
But they do not have a commonly accepted unique specification
independent of LISP. I deem them a little bit too simple, because
I would like to have attributes (not an attribute emulation with
list). XML has attributes, but I want attributes to be as
structured as elements.
What are you looking for that can't be handled with keywords?
So, I have decided to specify a variant of S-expression with
unlimited attributes:
http://www.purl.org/stefan_ram/pub/unotal_en
Interesting. I like it better than XML after only two minutes.
Regards,
Patrick
------------------------------------------------------------------------
S P Engineering, Inc. | Large scale, mission-critical, distributed OO
| systems design and implementation.
pjm@xxxxxxx | (C++, Java, Common Lisp, Jini, middleware, SOA)
.
- References:
- Why XML to comunicate Distributed Components?
- From: carofe
- Re: Why XML to comunicate Distributed Components?
- From: Robert Martin
- Why XML to comunicate Distributed Components?
- Prev by Date: Re: Why XML to comunicate Distributed Components?
- Next by Date: Re: Why XML to comunicate Distributed Components?
- Previous by thread: Re: Why XML to comunicate Distributed Components?
- Next by thread: Re: Why XML to comunicate Distributed Components?
- Index(es):
Relevant Pages
|