Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47)

Hmmm... I would state that the purpose of specifying `xmlns=""` allows me as a web author to have an 'escape' mechanism to prevent that element (and any descendants that don't provide their own namespace) from being in the default namespace.

These two are quite different:

```
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <people xmlns="">
    </people>
  </head>
  <body>
  </body>
</html>
```
and
```
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <people>
    </people>
  </head>
  <body>
  </body>
</html>
```

In the first case, `<people xmlns="">` and its descendants have **no** namespace, whereas in the second case `<people>` and its descendants are in the XHTML namespace.

This is the only authoring mechanism available to me as a web author to specify that a chunk of markup should have no namespace (i.e. be escaped from "inheriting" it's parent namespace).

Therefore, I'm concerned with your use of the term "redundant". The `xmlns=""` is not a redundant construct here.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/DOM-Parsing/issues/47#issuecomment-471883917

Received on Tuesday, 12 March 2019 07:15:40 UTC