Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Namespace Attributes

From: Joseph Kesselman <keshlam-nospam@-------.--->
To: NULL
Date: 12/4/2007 9:07:00 AM
geoff wrote:
> The snippet below had 'po' in front of 'billTo', 'shipTo', 'order', etc. but
> they say by moving the 'po' namespace definition to the 'po:po' element, the
> child elements fall into that namespace:

If so, they're wrong. However, you could get that effect by using the 
Default Namespace Declaration:

           <po id="43871" submitted="2001-10-05"
              xmlns="http://www.skatestown.com/ns/po">
              <billTo id="addr-1">
                 ...
              </billTo>
              <shipTo href="addr-1"/>
              <order>
                 ...
              </order>
           </po>

Note that the Default Namespace Declaration only affects elements. If 
you want attributes to be in a namespace, they have to use a properly 
declared prefix. (However, it is not uncommon for namespaced nodes to 
expect non-namespaced attributes, so always check your particular schema 
or application spec to see whether this is going to be an issue.)

-- 
Joe Kesselman / Beware the fury of a patient man. -- John Dryden


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent