RE: XSD 1.1: not okay to have an xs:assert at the attribute level?

> <xsd:assert test="QName('http://www.w3.org/2001/XMLSchema',
> string(@name)) eq xsd:QName('xsd:element')"/>

Nice work Mukul. 

You used XERCES, right? 

I tried that with SAXON and got errors.

So either XERCES is accepting as valid something that it shouldn't or SAXON is not accepting as valid something that it should.  

XML Schema Working Group: what is the truth?

/Roger



-----Original Message-----
From: Mukul Gandhi [mailto:[email protected]] 
Sent: Sunday, September 23, 2012 12:59 PM
To: Costello, Roger L.
Cc: [email protected]
Subject: Re: XSD 1.1: not okay to have an xs:assert at the attribute level?

Hi Roger,
    The following <assert>,

<xsd:assert test="QName('http://www.w3.org/2001/XMLSchema',
string(@name)) eq xsd:QName('xsd:element')"/>

seems to give me the result that you want.

On Sun, Sep 23, 2012 at 9:03 PM, Costello, Roger L. <[email protected]> wrote:
> Hello Mukul,
>
>> <xsd:assert test="string(@name) eq 'xsd:element'" />
>
> That's a good idea, but the value of @name is not a string, it is a QName. Thus, I should be able to change the namespace prefix:
>
> <xsd:assert test="string(@name) eq 'xs:element'" />
>
> and the assertion should still work.
>
> /Roger




-- 
Regards,
Mukul Gandhi