RE: [xliff] proposed solutions for CSPRD 138 (Unique Particle Attribution) - validation

[Yves Savourel <ysavourel@enlaso.com>]

More on this attribute validation issue:

If I use <xs:anyAttribute namespace="##any" processContents="strict"/> the bad attribute fs:badAttr is correctly seen as a bad
attribute. If I use 'lax" no error is reported.

I don't understand why: the definition for "lax" is suppose to be "The XML processor attempts to obtain the schema for the required
namespaces and validate any attribute from those namespaces; however, if the schema cannot be obtained, no errors will occur."

But this is behaving like if the validators cannot find the schema if the name of the attribute is incorrect.

BTW: I've also checked that the problem is not coming from my validator: I get the same behavior in Oxygen when providing the two
same schemas with xsi:schemaLocation.

I'm baffled. Any pointer would be helpful.
-yves


-----Original Message-----
From: Yves Savourel [mailto:ysavourel@enlaso.com] 
Sent: Wednesday, December 4, 2013 6:56 AM
To: 'xliff@lists.oasis-open.org'
Subject: RE: [xliff] proposed solutions for CSPRD 138 (Unique Particle Attribution)

Hi Tom and other schema experts,


I'm trying to implement the validation using a core schema without reference. And I run into a strange issue for FS:

- the core schema has no reference to FS, just (for example in the <pc> element):

<xs:anyAttribute namespace="##any" processContents="lax"/>

I load the core and FS schema in the validator and it looks like the FS schema is used as if I do:

<pc id='1' fs:fs="bad"> I get the expected error about the invalid value.

However if I do:

<pc id='1' fs:badAtt='val'> I don't get an error, while badAttr is not specified in the FS schema.

Any ideas?
-yves