RFC: Attributes and XML-RPC

[Marcus Carr]

Mark Nutter wrote:

> Whether you evaluate the security level first because it's an attribute or
> whether you evaluate it first because it's the first child element, you're
> still going to evaluate it before you evaluate the (other) child
> elements.  Why/how is it worse to deal with it first as a child element
> rather than dealing with it first as an attribute?

If you deal with it as an attribute, it's reasonable to believe that the condition specified
by the attribute persists for everything between the start and end tags of the element, as it
was established before the contents of the element was processed. If you deal with it as the
first child element, there is an ambiguity as to whether the condition should be applied in
the same way as for an attribute, for everything from that point on or just for all child
elements. As you may not be able to relay the handling that you desire, different applications
may be expected to behave differently.


--
Regards,

Marcus Carr                      email:  mrc at allette.com.au
___________________________________________________________________
Allette Systems (Australia)      www:    http://www.allette.com.au
___________________________________________________________________
"Everything should be made as simple as possible, but not simpler."
       - Einstein



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)