OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] targetNamespace and default namespace

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.


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/";>

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.

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

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS