OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] Re: Identifying the Top 10 xml Issues.. something with leg

[ Lists Home | Date Index | Thread Index ]

On 7/24/06, Rick Jelliffe <rjelliffe@allette.com.au> wrote:
> David Lyon wrote:
> >
> > <Item Information>
> >  PLU&="A256" Name&="Kitchen Veneer" Rate$~=HD321_C
> > </Item Information>
> >
> > decrypted it would read..
> >
> > <Item Information>
> >  PLU&="A256" Name&="Kitchen Veneer" Rate$=402.00
> > </Item Information>
> >
> There is nothing stopping you doing this in real XML,  just moving the
> type tag inside the attribute value. For example (off the top of my
> head, details may be wrong):
>
>     <Item Information PLU="A256" Name="Kitchen Veneer" Rate="$420"/>
>

This make easy to get data from javascript with dom:

var rate = xitem.getAttribute("Rate");

..and maybe he can have that:

 <Item Information id="REF-A256" PLU="A256" Name="Kitchen Veneer" Rate="$420"/>

var xitem =  xmlDoc.getElementById("REF-A256");
var rate = xitem.getAttribute("Rate");

And the whole doc can be:

<?xml...
<sales>
   <item ...
   <item ...
   <item ...
   <item ...
   <item ...
   <item ...
</sales>


JSON can beat that, maybe:

var rate = sales.items["REF-A256"].rate;




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS