This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Constr-attr-content-1 is marked in the catalog as runtime-error but it looks OK to me (and saxon parses and evaluates it without error) Constr-attr-content-3 is marked in the catalog as runtime-error but { and } are treated symmetrically by the EBNF, so I believe this should be a parse-error (like Constr-attr-content-2) (even though the test applet does parse -3 but not -2) Constr-attr-content-4 as for -3, the EBNF treats < similarly to {} [152] QuotAttrContentChar ::= Char - ["{}<&] so I believe this unquoted < should be a parse error. Constr-attr-content-5 as for -3, the EBNF treats & similarly to {} so I believe this unquoted & should be a parse-error. (while converting to XqueryX, tests that are marked as runtime-error should have a valid xqueryx translation, but typically tests marked as parse-error do not. The above were flagged as I had an unexpected failure to convert these tests as they were marked as runtime-error rather than parse-error.) David
fixed the scenario attribute as suggested.
confirmed fixed in 0.8.2
Constr-attr-content-4 is actually still incorrect in my opinion. An escaped < sign (<) is completely valid in XML - find me an XSLT document which doesn't contain at least one of them. http://www.w3.org/TR/2004/REC-xml-20040204/#sec-starttags (referred from http://www.w3.org/TR/xquery/#id-attributes) states that the replacement text of an entity may not contain a '<'. However http://www.w3.org/TR/2004/REC-xml-20040204/#sec-predefined-ent says that the replacement text for '<' is not '<', but '&#60;', which is the character reference for '<'. So, while it's really obscured in the spec, '<' is legal in attribute values.
(In reply to comment #3) Martin, I don't understand your comment. > An escaped < sign (<) is completely valid in XML This is true but the < in this test is unescaped, it's just a < and this isn't legal in XML or in XQuery, you have to code it as < or something equivalent, surely? QuotAttrContentChar ::= Char - ["{}<&] forces you to escape < in attribute constructors.
Sorry, I've been fooled by my testmachinerie which generates XML, which escapes the < just to de-escape it later.