OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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


This seems to contradict the XSD specification. With anyAttribute set to
"lax", a bad attribute should throw an error when a schema for the
containing namespace has been found. But as you note, it doesn't.

The common interpretation of "lax" is that it throws no error when the
schema for the namespace is not found, nor when the schema is found but a
definition of the attribute is not part of that schema. It seems to be
commonly accepted (and commonly implemented, as you've seen). If anyone
knows where that detail is hidden in the W3C spec for XSD, I'd like to know.


-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On
Behalf Of Yves Savourel
Sent: Wednesday, December 04, 2013 02:49 PM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] proposed solutions for CSPRD 138 (Unique Particle
Attribution) - validation

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

I'm baffled. Any pointer would be helpful.

-----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

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>

<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?

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]