In article <IpX4j.54803$MU5.2215@f...>,
geoff <nospam@n...> wrote:

>In the following fragment, elements like 'item' and 'description' would be 
>in the 'po' namespace but the attribute 'p:priority="high" ' would be in the 
>'p' namespace?
>
>    <po:po id="43871"
>         submitted="2004-01-05"
>         customerId="73852"
>         xmlns:po="http://www.skatestown.com/ns/po"
>         xmlns:p="http://www.skatestown.com/ns/priority">
>                . . .
>         <po:order>
>              <item sku="318-BP" quantity="5" p:priority="high">
>                   <description>Skateboard backpack; five 
>pockets</description>

No, item and description are in no namespace.

>. . . so, if an order processor could handle this xml and later on, 
>'priority' was added, this would not break the processor since priority is 
>in its own namespace?

Using namespaced attributes is certainly a way to add attributes whose
interpretation does not come from the element they're on, provided
that your schema (or whatever) allows such other-namespace attributes.

-- Richard
-- 
"Consideration shall be given to the need for as many as 32 characters
in some alphabets" - X3.4, 1963.