Hello All!
Just lurkering your discussion..
JM> I agree. IMHO the focus should be on any type of legacy, structured
JM> ASCII files containing some notion of "record".
Does not this give the new name to the project (not only the scope)
ascii
import-ascii
oh wait, and if it is not ASCII? if
Looks great. Actually, Cocoon has a CSVGenerator now that turns CSV
files into XML SAX events. Perhaps factoring stuff out of there is
appropriate if we want to create an independent effort here.
The other formats you mentioned interest me greatly, especially EDIFACT.
--
Ryan Hoegg
ISIS Netwo
start from. It also
limits the number of dependencies/new projects.
Stephen
> from:Simon Kitching <[EMAIL PROTECTED]>
> date:Thu, 26 Jun 2003 08:04:51
> to: [EMAIL PROTECTED]
> subject: Re: [SURVEY] Commons-csv or not?
>
> Hmm .. an "import-stuff-i
Hmm .. an "import-stuff-into-xml" project? Interesting...
I have in fact written exactly this for my current employer, for a
(continuously expanding) series of formats. We then apply stylesheets to
the results, for various purposes.
I doubt I could contribute any code, but can definitely confirm
On 25.06.2003 19:59:19 Joe Germuska wrote:
> A CSV project seems a bit too narrowly focused.
I agree. IMHO the focus should be on any type of legacy, structured
ASCII files containing some notion of "record". It's very interesting to
have code around to easily convert such files to XML (SAX-Event
