Altova Mailing List Archives


Re: Use Attributes vs Elements???

From: "Roland Hall" <nobody@------->
To: NULL
Date: 1/28/2005 12:59:00 PM
"rdcpro" wrote in message 
news:6D2714E4-61F2-45AC-83C1-8CE5E6F5EAB7@m......
: There are few simple rules of thumb that may help.  These are some that 
come
: to mind:
:
: 1.  Attributes must have unique names.  So if you have a structure that 
can
: have more than one "child" of the same name, use elements.
:
: <foo>
: <bar>1</bar>
: <bar>2</bar>
: <bar>3</bar>
: </foo>

You're saying this won't work?

<base>
  <ball>
    <swing strike="one">1</swing>
    <swing strike="two">2</swing>
    <swing strike="three">3</swing>
  </ball>
</base>


-- 
Roland Hall
/* This information is distributed in the hope that it will be useful, but 
without any warranty; without even the implied warranty of merchantability 
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation - http://msdn.microsoft.com/downloads/list/webdev.asp
MSDN Library - http://msdn.microsoft.com/library/default.asp


Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.