I think we have 2 issues here. Packaging and internalization (in particular
collation) specs.
I would go with org.apache.xalan.common.internalization for the common
code.
Internalization  (in particular collation) specs have a lot of
implementation
defined freedom.  I understood that the specs just cannot be that specific
because  of dependences on underline implementations. After a lot of
discussions  we came with a specific spec
(See attached file: collation.doc)

which I think we should  implement for all (xalan interpretive, XSLTC,
xalan C++) our processors. (Actually I wrote a draft implementation  of the
specs for XSLTC). The specs  could be changed in future if XSLT 2.0 would
became less ambiguous (e.g. with respect to default collation. ).
I also think that not only collation, but also lang attribute could be more
specific and has common rules for different xsl elements.

Actually our specs are in a draft form and  obviously not perfect.
Discussions would be appreciated.


Igor Hersht
XSLT Development
IBM Canada Ltd., 8200 Warden Avenue, Markham, Ontario L6G 1C7
Office D2-260, Phone (905)413-3240 ; FAX  (905)413-4839


                                                                                       
                
                      [EMAIL PROTECTED]                                                
                
                      ibm.com                  To:       [EMAIL PROTECTED]             
         
                                               cc:                                     
                
                      11/10/2003 02:34         Subject:  Re: A package for code common 
for XSLTC,      
                      PM                        xalan interpretive and XQuery.         
                
                      Please respond to                                                
                
                      xalan-dev                                                        
                
                                                                                       
                
                                                                                       
                



Igor Hersht wrote:
>Maybe it could be good idea to have package
>(e.g. org.apache.xalan.common) where we could have such code
[for internationalization]
>as well as any code which is common for
>XSLT2.0, XPath 2.0, XQuery 1.0 and XPath 2.0 Functions and Operators.

Given that all the above specs treat collating as a special module,
I like the idea of isolating collators. We might even want to make it
easy for others to write special-purpose collators. With the proper
naming conventions, they could use their own collators in the F&O
functions that allow reference to a collator by "name" (actually by
URI). We also need to define the URIs for Xalan collators.
.................David Marston

Attachment: collation.doc
Description: MS-Word document

Reply via email to