A new twist on attributes vs elements

Melvyn, 

The one major problem I forsee is the instance when your database 
field contains both single and double quotes.  Your xml parser will 
choke when attempting to add that as an attribute.  I'm sure there is 
some means to escape quotes, but that is an added annoyance that is avoided
by simply using child nodes.

I agree though, attributes attacched to a row element seem cleaner to me 
as well.

-matt


------------------------------

>Date: Sun, 12 Nov 2000 19:28:29 -0500
>From: "Melvyn Rosengarden" <melrose@xxxxxxxxxxxxxxxx>
>Subject: A new twist on attributes vs elements

>I have seen a great deal of discussion recently about converting return sets
>from SQL ( cursors, recorsets, datawindows) into XML strings. All of the
>examples extract the column names of the return set and create XML with
>them. While this method is probably more efficient for storing and
>retrieving XML data in a relational database it is inferior when it comes to
>navigating the DOM.  I would much prefer to work with attributes (when they
>make sense) than a myriad of embeded elememts. Has anyone else recognized
>this as an issue and if so how did you resolve it...TIA


>"You already have zero privacy -- get over it !!
>Melvyn Rosengarden
>melrose@xxxxxxxxxxxxxxxx


> XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

> ------------------------------


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list