Actions
Bug #4674
closedXQuery computed element and attribute constructors using EQNames
Start date:
2020-08-09
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
10, trunk
Fix Committed on Branch:
10, trunk
Fixed in Maintenance Release:
Platforms:
Description
It is not entirely clear whether XQuery 3.1 allows the computed name in a computed element or attribute constructor to be an EQName in the form Q{uri}local. We are allowing it, but new tests from Christian GrĂ¼n show that we're getting some of the detail wrong:
(a) the URI part needs to be whitespace-collapsed
(b) for attributes, we need to allocate a prefix, and we're doing this incorrectly
(c) we probably shouldn't expand entity/character references (there's nothing in the spec either way on this in the spec, but it seems an inappropriate thing to do at run-time)
(d) we should reject an opening brace in the URI - the grammar doesn't allow it.
Please register to edit this issue
Actions