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] Namespace problem

[ Lists Home | Date Index | Thread Index ]

Title: RE: [xml-dev] Namespace problem

Depends if you believe in namespaces or not. Changing name under customer to customerName is not too much different from using a namespace. Except that using a namespace gives (IMHO) better modularization abilities and gives a nice handle for extra semantics (duck and wait for the syntax vs semantics argument to start again).

Think of the URI as part of the element name. {http://mycompany.com/customers}:Name is a "different" element from {http://yourcompany.com/customers}:Name, even if they are to be handled in the same way. It makes sense to put it in a common namespace, not least because it potentially helps resolving version identification.

You do not *have to* agree on the URI - if you each supply a schema for the documents and you use youyr business partner's schema to validate messages from him, then your XML validation will work anyway. Assuming that the elements should have the same meaning, this would not be a good approach.

So yes, agree on a URI, and only change it in future versions of the schema (by mutual consent) if there is a structural change to objects in that namespace.

If agreeing on a URI is a stumbling block, then you have more serious issues to resolve before the partnership succeeds.


-----Original Message-----
From: pradeep bhat [mailto:pradeepbhat@slk-soft.com]
Sent: 05 June 2002 13:49
To: xml-dev@lists.xml.org
Subject: [xml-dev] Namespace problem

Hi All,

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. The way to distinguish between the 2 <name> tags is with 2
different URI. 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)?

Please help me. Thanks in advance.
pradeep bhat


The information contained and transmitted by this e-mail is proprietary to
SLK Software Services Private Limited and is intended solely for the use of
the individual or entity to whom it is addressed and others authorized to
receive it. It may contain privileged or confidential information or
information exempt from disclosure as per applicable law. If you are not the
intended recipient or responsible for delivery to the intended recipient,
you may not copy, deliver, distribute or print this message. If it is a
forwarded message it may not have been sent with the authority of the
company. Any views or opinions are individual to the sender and are not the
opinion of or endorsed by the company. The attachments to this message have
been virus checked. However, the recipients may conduct their own virus
checks. SLK Software Services Pvt. Ltd. will not accept any claims for loss
or damages arising out of viruses.

The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>

The information transmitted by this e-mail message is intended solely for the use of the person to whom or entity to which it is addressed. The message may contain information that is privileged and confidential.  Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please do not disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail (including the original message with your reply) and then delete and discard all copies of the message.

Although we have taken precautions to minimize the risk of transmitting viruses we nevertheless advise you to carry out your own virus checks on any attachment to this message. We accept no liability for any loss or damage caused by viruses.


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

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