Re: targetNamespace and default namespace

Cart

XML Editor - Download a Free Trial >

See What's New >

Buy Now >

[Home] [By Thread] [By Date] [Recent Entries]

From: Thomas Passin <list1@t...>
To: XML Developers List <xml-dev@l...>
Date: Thu, 29 Sep 2016 13:32:17 -0400

I seem to remember from way back a lot of discussion about how you would be able to use elements from another namespace or schema, if they weren't qualified somehow. That might have been mostly about inserting XML fragments from one document into another, I don't remember too clearly. It would have lead to not wanting to default namespaces to that of the parent element.

TomP

On 9/29/2016 11:26 AM, Michael Kay wrote:

omeone, I think, had the bright idea that if a container element is
in a namespace

<svg:svg xmlns:svg="http://svg.com/">
     <rectangle/>
     <circle/>
</svg:svg>

then there is no good reason why its children need to be in a
namespace: like attributes, they are scoped by the container. The
idea didn't catch on, but the schema spec was written in the belief
that this was the way forwards.

Follow-Ups:
- Re: targetNamespace and default namespace
  - From: Elliotte Rusty Harold <elharo@i...>

References:
- targetNamespace and default namespace
  - From: Elliotte Rusty Harold <elharo@i...>
- Re: targetNamespace and default namespace
  - From: Thomas Passin <list1@t...>
- Re: targetNamespace and default namespace
  - From: Elliotte Rusty Harold <elharo@i...>
- Re: targetNamespace and default namespace
  - From: Thomas Passin <list1@t...>
- Re: targetNamespace and default namespace
  - From: Michael Kay <mike@s...>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

XML Editor - Download a 15 Day Free Trial Now >

See What's New in Stylus Studio >

Buy Stylus Studio - XML Editor - Now >