You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Martin Stricker <sh...@gmx.de> on 2001/12/12 23:40:03 UTC

Re: xml-commons charter

Shane Curcuru wrote:

> Let's work on this discussion for a bit and get more participants.  If
> needed we might cross-post once to general@xml to get more folks to
> come look over here (I was impressed you all actually subscribed! I
> thought it was still edwin and sam and me!)  I'm glad there's interest
> here, it will remind me to come back to visit more from the many
> emergencies at work...

I concur mostly with you, Shane: xml-commons shouldn't become a
repository of useful pieces of code (but another subproject like
"xml-tools" might, that's not a bad idea) but more of "glue code"
between the different xml.apache.org subprojects. xml-commons should
prevent subprojects to reinvent the wheel and provide a common
repository of shared code (hence the name). This should, as you
mentioned, help the individual subprojects to interact more closely.
IMHO all subprojects should search for pieces of code that can be
"outsourced" to xml-commons.

A repository of XML and XSL tools, maybe called "xml-tools", should be
kept separate from xml-commons. I see xml-commons as a
inter-xml.apache.org project, and a tool collection definitely would
target more on users than on xml.apache.org subprojects. And if
something from xml-tools becomes used by some xml.apache.org subprojects
it always can be moved over to xml-commons.

Since I kind of propose another xml.apache.org subproject I crosspost
this to general@xml.apache.org *ducks and runs*

> <eof aka="mailto:shane_curcuru@lotus.com"
>  BartSays="Nobody reads these anymore."/>

So, why are you Reply-To-ing there? ;=D

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


how to add comment in the head of xml file

Posted by Li Zongliang <le...@gxlu.com.cn>.
Hi all,

I write out XML file using DOM (and xalan ) from my java application, I want to add some comment text in the head of the output file. such as:

<?xml version="1.0" encoding="UTF-8"?>

<!-- this is the comment before the root element -->

<domain name="netguard">
  <server name="server1" host="lee"/>
  <server name="server2" home="panda">
    <service code="gxlu.Loger" name="Test"/>
  </server>
</domain> 

please tell me how to do.

Re: xml-commons charter

Posted by Martin Stricker <sh...@gmx.de>.
Stefano Mazzocchi wrote:

> This is also why I don't like the idea of 'xml-tools': it's too
> general.
> 'commons' is appropriate for stuff that are so common that could be
> placed in almost any other project. Sort of common denominator between
> projects.
> 
> This is what I'd like to have.

I do fully agree with you here. I invented "xml-tools" to respond to a
suggestion made on xml-commons-dev to include useful tools which are not
shared between xml.apache.org subprojects into xml-commons (that would
be the way jakarta-commons is used). I wanted to keep these tools out of
xml-commons, so I made up a suggestion where these tools could be stored
- that is, if the xml.apache.org community wants them at all.

I want xml-commons to stay as it is: A repository for cross-subproject
code so this code has to be stored and maintained only once. I guess
glue code wasn't a good wording, sorry.

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

Re: xml-commons charter

Posted by Martin Stricker <sh...@gmx.de>.
Stefano Mazzocchi wrote:

> This is also why I don't like the idea of 'xml-tools': it's too
> general.
> 'commons' is appropriate for stuff that are so common that could be
> placed in almost any other project. Sort of common denominator between
> projects.
> 
> This is what I'd like to have.

I do fully agree with you here. I invented "xml-tools" to respond to a
suggestion made on xml-commons-dev to include useful tools which are not
shared between xml.apache.org subprojects into xml-commons (that would
be the way jakarta-commons is used). I wanted to keep these tools out of
xml-commons, so I made up a suggestion where these tools could be stored
- that is, if the xml.apache.org community wants them at all.

I want xml-commons to stay as it is: A repository for cross-subproject
code so this code has to be stored and maintained only once. I guess
glue code wasn't a good wording, sorry.

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Re: xml-commons charter

Posted by Stefano Mazzocchi <st...@apache.org>.
Martin Stricker wrote:
> 
> Shane Curcuru wrote:
> 
> > Let's work on this discussion for a bit and get more participants.  If
> > needed we might cross-post once to general@xml to get more folks to
> > come look over here (I was impressed you all actually subscribed! I
> > thought it was still edwin and sam and me!)  I'm glad there's interest
> > here, it will remind me to come back to visit more from the many
> > emergencies at work...
> 
> I concur mostly with you, Shane: xml-commons shouldn't become a
> repository of useful pieces of code (but another subproject like
> "xml-tools" might, that's not a bad idea) but more of "glue code"
> between the different xml.apache.org subprojects. 

Sorry but I'm not sure of what you mean by 'glue code': for example,
Cocoon 'glues' together Xerces, Xalan, Fop, Batik, XIndice and Soap.
What more 'glue code' do you need?

> xml-commons should
> prevent subprojects to reinvent the wheel and provide a common
> repository of shared code (hence the name).

Yes, I share this vision, but "shared code" is very different from "glue
code" in my vision of software architectures.

For example, Norman's entity resolver is such a code that is very likely
to be shared across different projects (just like SAX, DOM, JAXP and all
the 'very basic' XML stuff)

This is also why I don't like the idea of 'xml-tools': it's too general.
'commons' is appropriate for stuff that are so common that could be
placed in almost any other project. Sort of common denominator between
projects.

This is what I'd like to have.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<st...@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



Re: xml-commons charter

Posted by Martin Stricker <sh...@gmx.de>.
Tom Bradford wrote:
> 
> Martin Stricker wrote:
> > A repository of XML and XSL tools, maybe called "xml-tools", should
> > be kept separate from xml-commons. I see xml-commons as a
> > inter-xml.apache.org project, and a tool collection definitely would
> > target more on users than on xml.apache.org subprojects. And if
> > something from xml-tools becomes used by some xml.apache.org
> > subprojects it always can be moved over to xml-commons.
> 
> I agree with this.  The reason we're using the xml-commons stuff is to
> be sure that our DOM, SAX, and JAXP classes/interfaces will
> interoperate smoothly with other projects.  Anything beyond that may
> be something that we've duplicated or that we don't need, and should
> be kept part of a separate project... Though, it would be nice if some
> of those common utils could become part of an xml-tools project.

This would of course work nicely: xml-tools would just as any other
xml.apache.org subproject be *encouraged* to use anything useful from
xml-commons. To ease development no xml.apache.org subproject should use
code from anywhere but it's own repository and xml-commons. If any code
is in use by more than one subproject this is the clear sign this code
has to be moved to xml-commons asap.

One *could* put stuff in xml-commons which is *expected* to be used in
more than one subproject, but from my personal experience (both
programmer and project manager) I found this usually leads cluttering up
the common repository with maybe useful stuff so no one dares to dig in
that mess, making the common useless. OTOH it's quite easy to move stuff
from one project's repository to common and get it at build time.

Another idea which has proven itself useful is a "providing" and a
"searching" document for each subproject where possibly reusable code
can be advertised. Looking through these documents provides easy
detection of possible synergies for the project manager or anyone in one
of the subprojects.

Just some assorted thoughts...

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Re: xml-commons charter

Posted by Martin Stricker <sh...@gmx.de>.
Tom Bradford wrote:
> 
> Martin Stricker wrote:
> > A repository of XML and XSL tools, maybe called "xml-tools", should
> > be kept separate from xml-commons. I see xml-commons as a
> > inter-xml.apache.org project, and a tool collection definitely would
> > target more on users than on xml.apache.org subprojects. And if
> > something from xml-tools becomes used by some xml.apache.org
> > subprojects it always can be moved over to xml-commons.
> 
> I agree with this.  The reason we're using the xml-commons stuff is to
> be sure that our DOM, SAX, and JAXP classes/interfaces will
> interoperate smoothly with other projects.  Anything beyond that may
> be something that we've duplicated or that we don't need, and should
> be kept part of a separate project... Though, it would be nice if some
> of those common utils could become part of an xml-tools project.

This would of course work nicely: xml-tools would just as any other
xml.apache.org subproject be *encouraged* to use anything useful from
xml-commons. To ease development no xml.apache.org subproject should use
code from anywhere but it's own repository and xml-commons. If any code
is in use by more than one subproject this is the clear sign this code
has to be moved to xml-commons asap.

One *could* put stuff in xml-commons which is *expected* to be used in
more than one subproject, but from my personal experience (both
programmer and project manager) I found this usually leads cluttering up
the common repository with maybe useful stuff so no one dares to dig in
that mess, making the common useless. OTOH it's quite easy to move stuff
from one project's repository to common and get it at build time.

Another idea which has proven itself useful is a "providing" and a
"searching" document for each subproject where possibly reusable code
can be advertised. Looking through these documents provides easy
detection of possible synergies for the project manager or anyone in one
of the subprojects.

Just some assorted thoughts...

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

Re: xml-commons charter

Posted by Tom Bradford <br...@dbxmlgroup.com>.
Martin Stricker wrote: 
> A repository of XML and XSL tools, maybe called "xml-tools", should be
> kept separate from xml-commons. I see xml-commons as a
> inter-xml.apache.org project, and a tool collection definitely would
> target more on users than on xml.apache.org subprojects. And if
> something from xml-tools becomes used by some xml.apache.org subprojects
> it always can be moved over to xml-commons.

I agree with this.  The reason we're using the xml-commons stuff is to
be sure that our DOM, SAX, and JAXP classes/interfaces will interoperate
smoothly with other projects.  Anything beyond that may be something
that we've duplicated or that we don't need, and should be kept part of
a separate project... Though, it would be nice if some of those common
utils could become part of an xml-tools project.

-- 
Tom Bradford - http://www.tbradford.org
Developer - Apache Xindice (formerly dbXML)
Maintainer - jEdit-Syntax Java Editing Bean

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Re: xml-commons charter

Posted by Tom Bradford <br...@dbxmlgroup.com>.
Martin Stricker wrote: 
> A repository of XML and XSL tools, maybe called "xml-tools", should be
> kept separate from xml-commons. I see xml-commons as a
> inter-xml.apache.org project, and a tool collection definitely would
> target more on users than on xml.apache.org subprojects. And if
> something from xml-tools becomes used by some xml.apache.org subprojects
> it always can be moved over to xml-commons.

I agree with this.  The reason we're using the xml-commons stuff is to
be sure that our DOM, SAX, and JAXP classes/interfaces will interoperate
smoothly with other projects.  Anything beyond that may be something
that we've duplicated or that we don't need, and should be kept part of
a separate project... Though, it would be nice if some of those common
utils could become part of an xml-tools project.

-- 
Tom Bradford - http://www.tbradford.org
Developer - Apache Xindice (formerly dbXML)
Maintainer - jEdit-Syntax Java Editing Bean

Re: xml-commons charter

Posted by Stefano Mazzocchi <st...@apache.org>.
Martin Stricker wrote:
> 
> Shane Curcuru wrote:
> 
> > Let's work on this discussion for a bit and get more participants.  If
> > needed we might cross-post once to general@xml to get more folks to
> > come look over here (I was impressed you all actually subscribed! I
> > thought it was still edwin and sam and me!)  I'm glad there's interest
> > here, it will remind me to come back to visit more from the many
> > emergencies at work...
> 
> I concur mostly with you, Shane: xml-commons shouldn't become a
> repository of useful pieces of code (but another subproject like
> "xml-tools" might, that's not a bad idea) but more of "glue code"
> between the different xml.apache.org subprojects. 

Sorry but I'm not sure of what you mean by 'glue code': for example,
Cocoon 'glues' together Xerces, Xalan, Fop, Batik, XIndice and Soap.
What more 'glue code' do you need?

> xml-commons should
> prevent subprojects to reinvent the wheel and provide a common
> repository of shared code (hence the name).

Yes, I share this vision, but "shared code" is very different from "glue
code" in my vision of software architectures.

For example, Norman's entity resolver is such a code that is very likely
to be shared across different projects (just like SAX, DOM, JAXP and all
the 'very basic' XML stuff)

This is also why I don't like the idea of 'xml-tools': it's too general.
'commons' is appropriate for stuff that are so common that could be
placed in almost any other project. Sort of common denominator between
projects.

This is what I'd like to have.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<st...@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org