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 5326 - [UPD] Terminology - "transform expression"
Summary: [UPD] Terminology - "transform expression"
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Update Facility (show other bugs)
Version: Recommendation
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:
Depends on:
Blocks:
 
Reported: 2007-12-19 17:34 UTC by Michael Kay
Modified: 2011-01-07 11:14 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2007-12-19 17:34:51 UTC
It's confusing to have an expression called a "transform expression" (with non-terminal symbol TransformExpr) that does not use the keyword "transform" in its syntax. Members of the WG will be able to relate to this because they know the history, but it's illogical when seen without this knowledge.

For implementors, it makes it difficult to decide whether to use the term "transform expression" in error messages - will users know what this term is referring to? It's better for names of expressions to bear some relationship to the keywords that characterize them.

I suggest renaming it to a "copy-modify" expression, with the non-terminal CopyModifyExpr.
Comment 1 Don Chamberlin 2008-04-15 21:39:24 UTC
Michael,
The Query Working Group considered this bug report on 15 April 2008. The working group agrees that a "transform expression" no longer contains the keyword "transform". However, the group feels that "transform expression" is a reasonably descriptive name, just as "conditional expression" is a descriptive name for an expression that does not contain the keyword "conditional". The benefit to be gained by changing the descriptive name of this expression does not seem to justify the work involved in changing nonterminal symbols in the grammar, error messages, XQueryX syntax, etc. Therefore the consensus of the working group was to close this bug report with no changes to the specification. If you are satisfied with this resolution, please mark this bug report as "Closed".
Regards,
Don Chamberlin (for the Query Working Group) 
Comment 2 Michael Kay 2011-01-07 11:14:55 UTC
Accepted with reluctance.