My experience is that namespaces are useful but far too often used
without a real need. Some people seem to like complexity. I don't.
Unless you want to live by a prefix only, you only need namespaces when
you mix several XML languages, such as in the case of XSLT and XSL-FO
(where you can mix in foreign content, such as SVG).
In cases where I design my own simple XML, I avoid using them, to keep
things simple.
By the way: living by prefix only may be theoretically unsound, but, as
an example, if your root element is xsl:stylesheet, and if it is being
processed by an XSLT processor, then for all practical purposes it's
obvious what the prefix xsl means.
Pieter
On 7/24/20 12:07 PM, Mukul Gandhi gandhi(_dot_)mukul(_at_)gmail(_dot_)com wrote:
On Fri, Jul 24, 2020 at 8:18 AM Debbie Lapeyre
dalapeyre(_at_)mulberrytech(_dot_)com <mailto:dalapeyre(_at_)mulberrytech(_dot_)com>
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com
<mailto:xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>> wrote:
Namespaces are a real problem.
I personally, find XML namespaces functionality useful. At the moment,
the online downside I see for XML namespaces is, that sometimes they
appear verbose.
We can also see, functional analogues of XML namespaces in the other
languages (like packages in java).
--
Regards,
Mukul Gandhi
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/3208261>
(by email <>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--