W3C home > Mailing lists > Public > xmlschema-dev@w3.org > November 2008

Re: doubt regarding targetNamespace

From: Pete Cordell <petexmldev@codalogic.com>
Date: Thu, 20 Nov 2008 10:44:46 -0000
Message-ID: <BDDCF2E2A27B4C8AA214D4762A7A15AA@Codalogic>
To: <bharathkr@huawei.com>, <xmlschema-dev@w3.org>

Hi Bharath,

targetNamespace should not have the namespace prefix.  The attributes in XML 
schema (and most XML vocabularies) are unqualified.  The XML schema schema 
does allow attributes from other namespaces, but really shouldn't allow 
attributes from the XML schema namespace.  libxml looks to be taking a 
relaxed interpretation here.

HTH,

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using XML C++
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ for more info

----- Original Message ----- 
From: "Bharath Kumar Reddy T" <bharathkr@huawei.com>
To: <xmlschema-dev@w3.org>
Sent: Wednesday, November 19, 2008 12:16 PM
Subject: doubt regarding targetNamespace


>
>
> Hi..
>
> I have a doubt whether we can give prefix for targetNamespace attribute or
> not.
>
> In the following schema we have xsd prefix for targetNamespace. Is it
> correct or not..........
>
> <?xml version="1.0"?>
>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xsd:targetNamespace="http://foobar">
>
> <xsd:element name="foo"/>
>
> </xsd:schema>
>
>
>
> Altova spy says it is wrong but libxml parser has not given any error when
> this schema is parsed.
>
>
>
> Thank you very much,
>
> Bharath.
>
>
>
> htipl
> HUAWEI TECHNOLOGIES CO.,LTD. huawei_logo
>
>
> Address: Huawei Industrial Base
> Bantian Longgang
> Shenzhen 518129, P.R.China
> www.huawei.com
> ----------------------------------------------------------------------------
> ---------------------------------------------------------
> This e-mail and its attachments contain confidential information from
> HUAWEI, which
> is intended only for the person or entity whose address is listed above. 
> Any
> use of the
> information contained herein in any way (including, but not limited to,
> total or partial
> disclosure, reproduction, or dissemination) by persons other than the
> intended
> recipient(s) is prohibited. If you receive this e-mail in error, please
> notify the sender by
> phone or email immediately and delete it!
>
>
> 
Received on Thursday, 20 November 2008 10:45:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:15:09 GMT