Differences between current version and previous revision of Serialisation.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 5 | Last edited on Friday, May 5, 2006 5:48:18 pm | by LawrenceDoliveiro | |
Older page: | version 4 | Last edited on Friday, May 5, 2006 5:34:28 pm | by LawrenceDoliveiro | Revert |
@@ -22,7 +22,7 @@
In recent times, it has become fashionable to use [XML] as a [Serialisation] format for [RPC], as seen in [SOAP], which is mostly pursued by [IBM] and MicrosoftCorporation, and in [XMLRPC]. This is a consequence of the challenge that language neutral [Serialisation] has always posed. [XML]'s verbosity is beneficial for debugging but a pig on bandwidth.
[YAML] is another text based serialisation format designed to be language agnostic and easily human-readable and -writable. Implementations are available for most "agile" languages. It has been designed with an eye on use for configuration files, but is not restricted to that purpose.
-Another such format is [JavaScript Object Notation (
JSON)|http://www.json.org/
].
+Another such format is [JSON].
----
CategoryProgramming