[dev] [commits] Kolab XML tag order (was: Horde branch master updated. 7290a9af17b8e2cc8dce40972139a8501cd730a5)

Thomas Jarosch thomas.jarosch at intra2net.com
Fri Mar 7 15:11:25 UTC 2014


On Thursday, 6. March 2014 20:13:33 Michael M Slusarz wrote:
> The branch "master" has been updated.
> The following is a summary of the commits.
> 
> from: 6d6bb81241fa8d05694925c9466cf4581d8963bb
> 
> 7290a9a I'm assuming order of XML tags doesn't matter - this fixes failing
> unit test though
> 
> Summary:
> http://github.com/horde/horde/compare/6d6bb81241fa8d05694925c9466cf4581d8
> 963bb...7290a9af17b8e2cc8dce40972139a8501cd730a5

@Jan: I'm not 100% sure if re-sorting the tag order alphabetically is a good 
idea or not. This breaks at least the expected order of the known fields, 
though there is no "hard rule" on that in the format specification.

A client can insert custom XML tags at any position, so parsers should
be pretty relaxed.

Kolab format specification for Kolab 2.0 (which is what we implement):
http://www-old.kolab.org/doc/kolabformat-2.0rc7-html/

Directly link for the contacts:
http://www-old.kolab.org/doc/kolabformat-2.0rc7-html/c270.html

Cheers,
Thomas



More information about the dev mailing list