This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4532 - [UPD] Section 2.4.1 and others: clarify impact of element constructor semantics
Summary: [UPD] Section 2.4.1 and others: clarify impact of element constructor semantics
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Update Facility (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: P2 minor
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords: editorial
Depends on:
Blocks:
 
Reported: 2007-05-04 23:30 UTC by Michael Rys
Modified: 2007-06-15 19:24 UTC (History)
0 users

See Also:

Attachments

Description Michael Rys 2007-05-04 23:30:30 UTC 
"SourceExpr is evaluated as though it were an enclosed expression in an element constructor (see Rule 1e in Section 3.7.1.3 ContentXQ). "
Lot's of semantics hidden behind this sentence. Please provide clearer impact: SourceNodes get copied, what about impact of copy namespace etc?
Comment 1 Don Chamberlin 2007-06-15 19:24:07 UTC 
This editorial item requests that the update specification replicate material that is normatively presented in the Element Constructor section of the XQuery specification, rather than referencing it by a hyperlink. In the editor's opinion, this would be redundant and would introduce possible inconsistencies. Therefore I have closed this editorial item without action.
--Don Chamberlin (for the Query Working Group)