Process content for attributes

[Graham Mann]

Hi,

I've been using the example DOMCount (with switches -n -s -v=always) from Xerces 2.1.0 to validate a document against a schema.
I believe I've uncovered a problem with wildcard attributes and the processContents setting:

So for an element which has an attributes declared like

<xs:attribute name="Good" type="xs:NMTOKEN"/>

<xs:anyAttribute namespace="##other" processContents="strict"/>

Changing the schema setting for  processContents setting and validating a document like

<TESTELEMENT Good="OK" Bad="AlsoOK" OTHER_NS:WhatEver="49" />

Note there is no schema for the OTHER_NS

This is what I've found

ProcessContents         local good attribute    local bad attribute             other attribute
skip                            OK                      OK                              OK
lax                             OK                      OK                              OK
strict                          OK                      {}Bad not declared for element  {OTHER_NS}WhatEver not declared

Of these 'strict' is the only one I belive to be correct.
Without a schema for the OTHER_NS I would expect skip and lax to behave like
ProcessContents         local good attribute    local bad attribute             other attribute
skip                            OK                      {}Bad not declared for element  OK
lax                             OK                      {}Bad not declared for element  OK

With a schema for OTHER_NS (and I've not got this far yet) I would expect the results for the other attribute for lax to depend upon that schema

Graham Mann

Adobe Systems Europe Ltd.

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]