W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2010

[Bug 9302] [XQuery11] How are output declarations processed?

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 May 2010 23:26:07 +0000
To: public-qt-comments@w3.org
Message-Id: <E1OBypz-0007ml-Kk@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9302


Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




--- Comment #5 from Michael Kay <mike@saxonica.com>  2010-05-11 23:26:07 ---
I'm reopening this because the resolution in comment #4 still leaves some
detail to be defined. Saying that character maps should use "the same format as
XSLT" isn't really a full specification. The XSLT rules allow character maps to
appear in stylesheet modules and there are complex rules for dealing with
duplicate mappings based on import precedence and the like; character maps can
also be built up hierarchically from smaller character maps. This seems
over-engineered for XQuery (which doesn't have facilities for overriding other
rather more important things, such as functions). I think a simple map of the
form:

<x:character-map>
  <x:output-character character="char" string="string"/>
  ...
</x:character-map>

would do the job just fine. Since this syntax isn't identical to the XSLT
syntax (character maps are not named and there is no use-character-maps
attribute), I would think that a namespace other than the XSLT namespace should
be used.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 11 May 2010 23:26:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:42 UTC