Yep. This is a future thing. ----- Original Message ----- From: Assaf Arkin <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 15, 1999 2:18 PM Subject: Re: [Proposal] Printer package
> According to the W3C, additional requirements are to deal with > namespaces, normalize attributes, etc. Namespace handling will require > some SAX filter before the printer layer. Attribute normalization can > only be done if you know the attribute's type, which DOM does not > supply. > > arkin > > > [EMAIL PROTECTED] wrote: > > > > Here's the definition of canonical that we've been using > > > > http://www.jclark.com/xml/canonxml.html > > > > In the future: > > > > http://www.w3.org/TR/xml-c14n > > > > I'm sure Tim or James can tell us more about whether this is ready for use > > yet. > > I haven't had time to read it yet. > > > > For now, Clark's definition works for me. > > > > Ted > > ----- Original Message ----- > > From: Assaf Arkin <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, November 15, 1999 12:37 PM > > Subject: Re: [Proposal] Printer package > > > > > > Also, I'd like to see a printer that can generate "canonical" XML. This > > is > > > > especially handy for testing purposes. > > > > > > Keith just explained to me that canonical XML is a minimal XML document, > > > i.e. one without CDATA sections, indentation or any extra formatting. In > > > the SAX case any document you print without indendation and whitespaces > > > will be canonical. In the DOM case, you also need to print CDATA as > > > standard text nodes. If I'm right about that one, a canonical options > > > should piece of cake. > > > > > > arkin > > > > > > > > > > > > My personal opinion is that the basic printers belong in the parser, > > the > > > > > parser being the more general case of XML usage. I assume most users > > who > > > > > download Xalan also have Xerces installed, or can obtain the > > > > > printer/utility packages separately. In my understanding FOP > > implements > > > > > it's own printer that requires the FOP code base, and Cocoon should > > > > > implement it's own framework for printers to use the default, FOP or > > > > > whatever comes along (application code). > > > > > > > > I like this arrangement (printers in the parser) more than a separate > > > > package. > > > > That means a separate download, which is a bad thing. > > > > > > -- > > > ____________________________________________________________ > > > Assaf Arkin [EMAIL PROTECTED] > > > CTO http://www.exoffice.com > > > Exoffice, The ExoLab Company tel: (650) 259-9796 > > > > > -- > ____________________________________________________________ > Assaf Arkin [EMAIL PROTECTED] > CTO http://www.exoffice.com > Exoffice, The ExoLab Company tel: (650) 259-9796 >
