2343 2005-10-14 22:19:29 +0000 Syntax for @mode and @exclude-result-prefixes ins't alligned 2007-02-25 23:56:28 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 2.0 Working drafts PC Windows XP CLOSED LATER P3 normal --- 1 sdubinets mike public-qt-comments oldest_to_newest 6702 0 sdubinets 2005-10-14 22:19:30 +0000 Value space of both attributes is the same (with the difference that missing mode means #default). But: mode=” #all ” – Valid mode=” ” – Invalid while exclude-result-prefixes=” #all ” – Invalid exclude-result-prefixes=” ” – Valid It'd be better to have compatible behavior and simular wording. Relative topics: extension-element-prefixes and xsl:strip-space 6703 1 sdubinets 2005-10-14 22:29:14 +0000 Duplicate in @mode is and error Duplicate in @exclude-result-prefixes is not 6704 2 mike 2005-10-15 09:04:53 +0000 Thanks for the comment. The last call period is over, but the comment will be held over and considered during the next phase. However, we're now applying very strict criteria, and only making changes to fix errors and inconsistencies, not simply because someone has identified a way of improving the language. It's probably true that these two attributes could have been made more consistent. However, their value space isn't the same (one is a list of QNames, the other a list of NCNames), and they serve very different purposes. And as you point out in your final remark, once we start hunting for opportunities to make disparate things more consistent, there are a lot of places to look. At this stage, we're all keen to get finished. Michael Kay personal response 14181 3 jim.melton 2007-02-25 23:56:28 +0000 Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.