Altova Mailing List Archives

Re: [xml-dev] To namespace or not to Namespace ....

From: Mukul Gandhi <gandhi.mukul@-----.--->
To: xml-dev@-----.---.---
Date: 4/8/2010 3:25:00 AM
On Wed, Apr 7, 2010 at 8:53 PM, John L. Clark <jlc6@p...> wrote:
> To a namespace-aware XML processor, the existence of prefixes (or lack thereof) in the
> source is irrelevant.  I don't feel any pressure to use namespace prefixes until
> multiple dialects get combined, and then I tend to award the majority
> dialect with prefix-freedom.  (A notable exception is XSLT, where I
> like to emphasize the majority *output* dialect by placing it in the
> default namespace.)

I think, there could be some design considerations specific to a given
problem, whether we should use namespace prefixs or not.

For example, my application could use namespace prefixes to check for
equality of namespaces (orcourse, this is not as reliable as using
namespace-uri for namespace equality, but again this is perhaps
problem specific).

Also I think, prefixes serve as a good annotation for namespaces in a
XML document :)

I agree though, that using prefixes is good when we are combining
multiple XML vocabularies.

Mukul Gandhi


XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address:
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive:
List Guidelines:


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 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.