[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Namespace problem

• To: <pradeepbhat@s...>
• Subject: RE: Namespace problem
• From: "Manos Batsis" <m.batsis@b...>
• Date: Wed, 5 Jun 2002 15:00:01 +0300
• Cc: <xml-dev@l...>
• Thread-index: AcIMhyRr9balWKNLSI282qNWngU2kQAABaDw
• Thread-topic: Namespace problem

Ah, at last a simple,  non philosophical, xml-development question.

> -----Original Message-----
> From: pradeep bhat [mailto:pradeepbhat@s...] 

> Namespaces was introduced to distinguish duplicate attributes 
> and elements.
> We associate URI with elements and attributes to distinguish duplicate
> elements and attributes.
> 
> I have an element <Name> under <Customer>  and <product> in 
> the same xml
> file.The problem here is that I receive the file from my 
> business partner.We
> have decided to use namespace to distinguish duplicate elements and
> attributes.

If the hierarchical structure means that the <Name> under <Customer> is
the customer name, then your partner should probably change it in
<customerName> and the one below <Product> in <productName>. That will
serve  as self-describing markup. Namespaces where introduced to resolve
conflicts between same nodeNames in different vocabularies when
different XML files are merged etc. Your problem is wrong design as far
as I understand.


>  The way to distinguish between the 2 <name> tags is with 2
> different URI. 

See above.

>Does this mean we have to agree upon the URI 
> for Customer and
> product tags??
> I want to know whether this means that the 2 URI are fixed(they do not
> change unless we both agree for  a change)?

There is no standard procedure for the above, only best practices
(unless you have a formal agreement with your partner). Besides, you
don't need it.

Cheers, 

Manos

• Prev by Date: Namespace problem
• Next by Date: RE: Namespace problem
• Previous by thread: Namespace problem
• Next by thread: RE: Namespace problem
• Index(es):
  • Date
  • Thread