Re: [xml-dev] HTML5 and almost no namespaces
Like others are saying, it is usually some other factor which
causes you to associate the markup with the domain; not
the namespace. Even if you use a namespace, this is still
probably true - that your software determines the markup-
to-domain association by some means other than namespace
(or at least, not the namespace alone).
----
Stephen D Green
On 2 June 2011 11:44, Mukul Gandhi <[email protected]> wrote:
With due respects to people who dislike XML namespaces,
Consider the following example:
The element "name" here represents an organization name.
<name xmlns="http://organization-ns">ABC corp</name>
The element "name" here represents a person name.
<name xmlns="http://person-ns">Jill Doe</name>
If I'm presented with either (or both) of these documents, the
namespace binding helps me (and my XML application) to make a logical
association between the XML markup and to the domain with which it is
related to.
And we all say that, XML namespaces helps us to avoid name collisions
(one of the example of this is given above).
I (therefore) personally like XML namespaces. It's an optional
feature. If someone doesn't need XML namespaces in an application, the
XML software stack allows implementing such a design decision.
--
On Thu, Jun 2, 2011 at 2:55 PM, Stephen D Green
<[email protected]> wrote:
> Isn't it merely that the HTML5 (WHATWG) people were among the many
> who found Namespaces more easily ignored than implemented? Life is
> too short! Roll on 'MicroXML'! :-)
>
> Still, there may be many who get some value using namespaces in XML.
> ----
> Stephen D Green
Regards,
Mukul Gandhi