From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftables PATCH] change XML output format to element better than attributes
Date: Thu, 14 Feb 2013 09:34:13 +0100 [thread overview]
Message-ID: <20130214083413.GB3343@localhost> (raw)
In-Reply-To: <20130213221513.11611.54603.stgit@nfdev.cica.es>
On Wed, Feb 13, 2013 at 11:15:13PM +0100, Arturo Borrero wrote:
> Some of the problems with attributes are:
>
> * attributes cannot contain multiple values (child elements can)
> * attributes are not easily expandable (for future changes)
> * attributes cannot describe structures (child elements can)
> * attributes are more difficult to manipulate by program code
> * attribute values are not easy to test against a DTD
>
> Examples of this question at: http://www.w3schools.com/dtd/dtd_el_vs_attr.asp
Applied, thanks.
prev parent reply other threads:[~2013-02-14 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 22:15 [libnftables PATCH] change XML output format to element better than attributes Arturo Borrero
2013-02-14 8:34 ` Pablo Neira Ayuso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130214083413.GB3343@localhost \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).