Project

Profile

Help

Bug #4674

XQuery computed element and attribute constructors using EQNames

Added by Michael Kay about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XQuery conformance
Sprint/Milestone:
-
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.

History

#1 Updated by Michael Kay about 1 year ago

  • Description updated (diff)

#2 Updated by Michael Kay about 1 year ago

  • Status changed from New to Resolved
  • Priority changed from Low to Normal
  • Applies to branch 10, trunk added
  • Fix Committed on Branch 10, trunk added

New tests now passing.

#3 Updated by O'Neil Delpratt about 1 year ago

  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 10.2 added

Bug fix applied in the Saxon 10.2 maintenance release.

#4 Updated by O'Neil Delpratt about 1 year ago

  • Status changed from Resolved to Closed

Please register to edit this issue

Also available in: Atom PDF