xom-interest AT lists.ibiblio.org
Subject: XOM API for Processing XML with Java
List archive
- From: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
- To: Wolfgang Hoschek <whoschek AT lbl.gov>
- Cc: xom-interest AT lists.ibiblio.org
- Subject: [XOM-interest] Canonical XML in core?
- Date: Mon, 10 Nov 2003 07:35:19 -0500
At 11:43 PM -0800 11/9/03, Wolfgang Hoschek wrote:
- Suggestion: A package that contains a single public class only seems to me a little like overkill: increases complexity with little gain in modularity. Hence, move nu.xom.canonical.* --> nu.xom.*
This would make it easier to learn (less packages) and not significantly less modular (affects one class only).
I look at it from the other direction. Keeping CanonicalXMLSerializer out of nu.xom makes the core package API simpler. It makes it obvious that you don't need to understand this class unless you have a specific need for it.
--
Elliotte Rusty Harold
elharo AT metalab.unc.edu
Effective XML (Addison-Wesley, 2003)
http://www.cafeconleche.org/books/effectivexml
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
-
Re: [XOM-interest] Make DOMConverter methods public?,
Elliotte Rusty Harold, 11/09/2003
- Re: [XOM-interest] Make DOMConverter methods public?, John Cowan, 11/09/2003
-
Re: [XOM-interest] Make DOMConverter methods public?,
Wolfgang Hoschek, 11/10/2003
- [XOM-interest] Canonical XML in core?, Elliotte Rusty Harold, 11/10/2003
- Re: [XOM-interest] Make DOMConverter methods public?, Elliotte Rusty Harold, 11/10/2003
- Re: [XOM-interest] Make DOMConverter methods public?, Elliotte Rusty Harold, 11/10/2003
Archive powered by MHonArc 2.6.24.