--=-kAwzVBRLIp+bmVekKMbr Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2003-05-29 at 16:19, seth vidal wrote: > documenting syntax on xml files can be tricky sometimes. > That's really all. yeah, but there's a formal spec. for it if you need that - xml schema. i will grant that an xml format may be difficult to describe to an xml-unfamiliar audience, but simple xml is not a very hard thing to get the program for and is applicable to other programs later. > and it's useful to remember that there are end-users editing this config > file, not always admins/more advanced unix users. honestly, i expect most people just cut'n'paste the examples and modify key words. copious example creation is perhaps one way to deal. again, i don't think something like=20 cachedir=3D/var/cache/yum is much harder to understand than <cachedir>/var/cache/yum</cachedir> but that's highly subjective. > and not as useful for a format for users to edit. Especially when > compared to the configParser format which is dead-simple. yeah, but that would make for dead-simple xml too imo. > but you have to determine the attribute names and the entities. Those > don't magically appear. true - but this is no different from the current syntax in that respect, if i understand you correctly > and you have to keep up with the xml parsers and their bugs. not with something this simple. most xml parsers are at the stage now where they must deal with corner cases in the specification; i doubt you'll be doing anything that will call those into play here. --=-kAwzVBRLIp+bmVekKMbr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+1nO/qtG3xorrQfMRAsGTAJsGJ+0k70VGFvSmLzoeQNy9KdI4WQCg3xjN NaNcrjfMODzgAKhQoeeEv/8= =cWjt -----END PGP SIGNATURE----- --=-kAwzVBRLIp+bmVekKMbr--
