RE: [xacml] XACML Core Spec

[Seth Proctor <Seth.Proctor@Sun.COM>]

On Wed, 2004-04-07 at 14:24, Polar Humenn wrote:
> On Wed, 7 Apr 2004, Tim Moses wrote:
> > [...]
> > 3. Excluding the <xs:string> tags around the <AttributeValue> contents is
> > invalid.  I'm not sure why.  Seth is looking into it.
> 
> Really? That seems odd. I haven't run into that problem. (I think).

More accurately, this should not be the correct behavior, but some
schema validators (at least XMLSpy) seem to reject values of the form

  <AttributeValue DataType="...string">foo</AttributeValue>

using our latest schema. The schema validator that I use (from Netbeans)
is perfectly ok with this. Clearly one of these tools is wrong :)

My hunch is that with the new expression construct in the schema, we've
introduced a problem with attribute value elements. Specifically, they
are expressions, and all expressions are of complex content. I _think_
this is what's going on, but I haven't had a chance to see a) if this is
correct, and b) which tool is doing the right thing. I'm working on this
as quickly as possible, and will get an answer soon.

In the meantime, no one panic! The form I gave above is still correct.
The form that XMLSpy seems to allow

  <AttributeValue DataType="...string">
    <xs:string>foo</xs:string>
  </AttributeValue>

is definately _not_ what we want, it's "just" a matter of getting the
schema correct.


seth