You are viewing a plain text version of this content. The canonical link for it is here.
Posted to p-dev@xerces.apache.org by "Jason E. Stewart" <ja...@openinformatics.com> on 2001/01/22 18:59:53 UTC
Getting 1.3 into CVS
Hey All,
The list now seems to be working fully, so I can finally begin to do
something ...
It would be a major step forward to for us to get a version of 1.3
into CVS. I was hoping to have more people test it before I stick it
in but I haven't heard from anyone yet.
I made the latest developer release from Harmon available from public
ftp:
genex.sourceforge.net:/pub/genex/xerces-perl-devel.tar.bz2
Please try this and let me know of any issues, otherwise I will be
moving Tom's old files into the Attic, and replacing them
lock-stock-and-barrel with the new versions.
jas.
Re: Getting 1.3 into CVS
Posted by Fredrick Paul Eisele <ph...@netarx.com>.
>
> So, in conclusion, I agree with Bjoern in that the namespace should be
> XML::Xerces.
We are actively using XML::Xerces here at Netarx.
Our big concern is not to muddy the waters prior to the most recent
changes to Xerces-P being incorporated into Apache project under CVS.
As far as putting Apache in the Perl package name it seems to me that
the Xerces name implies Apache.
Re: Getting 1.3 into CVS
Posted by "Eric J. Peters" <er...@sammg.com>.
On Wed, 24 Jan 2001, Ask Bjoern Hansen wrote:
> On Wed, 24 Jan 2001, Pier Fumagalli wrote:
>
> [...]
> > > That said, we could use something like XML::Apache::Xerces::*, thus
> > > leaving room for XML::Apache::Xalan::*, etc. Or, we could invert it to
> > > Apache::XML::Xerces.
>
> It doesn't have anything to do with Apache (except for being an ASF
> project), so the Perl way would probably be to call it XML::Xerces
> (and XML::Xalan later for that). If I was to look for an XML
> something for Perl I would write i /^XML::/ in the CPAN shell and it
> will return all the module names in the XML:: namespace.
>
> The people at modules@perl.org has much experience with helping to
> put modules into the appropiate place in the namespace so it can be
> found easily.
>
I know I'm not an ASF member, but I'll toss out my opinion anyway...
The initial statement by Pier was:
* I don't know ANYTHING about PERL, but what are the mod_perl guys doing on
* this? Can't you guys use something like APACHE::XERCES::*?
which indicates to me that the idea of including APACHE was not really to
show ownership or corporate branding, but instead to somehow incorporate it
with mod_perl. Is this a fair assumption Pier?
If that's the case, then there isn't (to my limited mod_perl knowledge) any
*need* to include APACHE in the namespace - the namespace doesn't affect
mod_perl integration at all does it? So, the APACHE namespace is strictly
an option.
Being that this is an open-source project for the community good, I think that
branding it in the namespace is a little much - especially since I've seen as
much IBM contribution as Apache contribution, I hate to see a brand war. I
feel comments in the code stating that this project was contributed to and
supported by the Apache group would be sufficient. Using the namespace to
imply such a statement would just be noise - and actually degrade the value
of the namespace in the long run.
So, in conclusion, I agree with Bjoern in that the namespace should be
XML::Xerces.
Yet, this is just my opinion. Enjoy in moderation.
-Eric.
Re: Getting 1.3 into CVS
Posted by Ask Bjoern Hansen <as...@valueclick.com>.
On Wed, 24 Jan 2001, Pier Fumagalli wrote:
[...]
> > That said, we could use something like XML::Apache::Xerces::*, thus
> > leaving room for XML::Apache::Xalan::*, etc. Or, we could invert it to
> > Apache::XML::Xerces.
It doesn't have anything to do with Apache (except for being an ASF
project), so the Perl way would probably be to call it XML::Xerces
(and XML::Xalan later for that). If I was to look for an XML
something for Perl I would write i /^XML::/ in the CPAN shell and it
will return all the module names in the XML:: namespace.
The people at modules@perl.org has much experience with helping to
put modules into the appropiate place in the namespace so it can be
found easily.
- ask
--
ask bjoern hansen - <http://ask.netcetera.dk/>
more than 70M impressions per day, <http://valueclick.com>
Re: Getting 1.3 into CVS
Posted by "Parand T. Darugar" <td...@velocigen.com>.
Hello all,
Any reason 'Apache' needs to be part of the package
name, other than that's the java convention? Most other
Perl packages don't include the vendor name, and putting
Apache in there would associate the project with the
web server in most people's minds.
> > > That said, we could use something like XML::Apache::Xerces::*, thus
> > > leaving room for XML::Apache::Xalan::*, etc. Or, we could invert it to
> > > Apache::XML::Xerces.
> >
> > I would like to hear also the members of the Apache Software Foundation (I'd
> > love to see the Apache name in there).
> >
> > Members, anyone with an opinion on the PERL package name for Xerces-P?
>
> +1 for XML::Apache::Xerces
Best,
Parand Tony Darugar tdarugar@velocigen.com
858-622-1164 Leading the Web Services Revolution
858-622-0303 fax VelociGenX Server
http://www.velocigen.com/
Wrap IT, Link IT, Run IT
Only VelociGen lets you WRAP data from any source, LINK it
into e-Business meta-applications, and RUN them over the Web
and Wireless Networks
Re: Getting 1.3 into CVS
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 24 Jan 2001, Pier Fumagalli wrote:
> > That said, we could use something like XML::Apache::Xerces::*, thus
> > leaving room for XML::Apache::Xalan::*, etc. Or, we could invert it to
> > Apache::XML::Xerces.
>
> I would like to hear also the members of the Apache Software Foundation (I'd
> love to see the Apache name in there).
>
> Members, anyone with an opinion on the PERL package name for Xerces-P?
+1 for XML::Apache::Xerces
- donald
Re: Getting 1.3 into CVS
Posted by Pier Fumagalli <pi...@betaversion.org>.
Jason E. Stewart <ja...@openinformatics.com> wrote:
> "Pier Fumagalli" <pi...@betaversion.org> writes:
>
>> Jason E. Stewart <ja...@openinformatics.com> wrote:
>>>
>>> - deciding on a namespace (Xerces::*, XERCES::*, XML::Xerces::*)
>>
>> I don't know ANYTHING about PERL, but what are the mod_perl guys doing on
>> this? Can't you guys use something like APACHE::XERCES::*?
>
> Yes, we could. There is already a *huge* Apache::* namespace. However,
> all these modules have to do the the WWW server. All existing XML
> modules live under the XML namespace.
>
> Since not everyone knows about the Xerces project, I would like to
> include it under the XML::* namespace, so that developers looking for
> XML parsers would find it. Just having it live under Apache::Xerces,
> they might confuse it for a WWW server extension.
>
> That said, we could use something like XML::Apache::Xerces::*, thus
> leaving room for XML::Apache::Xalan::*, etc. Or, we could invert it to
> Apache::XML::Xerces.
I would like to hear also the members of the Apache Software Foundation (I'd
love to see the Apache name in there).
Members, anyone with an opinion on the PERL package name for Xerces-P?
Pier
--
Pier Fumagalli <ma...@betaversion.org>
Re: Getting 1.3 into CVS
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
"Pier Fumagalli" <pi...@betaversion.org> writes:
> Jason E. Stewart <ja...@openinformatics.com> wrote:
> >
> > - deciding on a namespace (Xerces::*, XERCES::*, XML::Xerces::*)
>
> I don't know ANYTHING about PERL, but what are the mod_perl guys doing on
> this? Can't you guys use something like APACHE::XERCES::*?
Yes, we could. There is already a *huge* Apache::* namespace. However,
all these modules have to do the the WWW server. All existing XML
modules live under the XML namespace.
Since not everyone knows about the Xerces project, I would like to
include it under the XML::* namespace, so that developers looking for
XML parsers would find it. Just having it live under Apache::Xerces,
they might confuse it for a WWW server extension.
That said, we could use something like XML::Apache::Xerces::*, thus
leaving room for XML::Apache::Xalan::*, etc. Or, we could invert it to
Apache::XML::Xerces.
jas.
Re: Getting 1.3 into CVS
Posted by Pier Fumagalli <pi...@betaversion.org>.
Jason E. Stewart <ja...@openinformatics.com> wrote:
> Here's my stab at the TODO
>
> 1) get 1.3 code into repository. This means:
> - decide whether to use Eric's modifications to Tom's code
> - use Harmon's code
> - merge them together into a single item
> - deciding on a namespace (Xerces::*, XERCES::*, XML::Xerces::*)
I don't know ANYTHING about PERL, but what are the mod_perl guys doing on
this? Can't you guys use something like APACHE::XERCES::*?
Pier
--
Pier Fumagalli <ma...@betaversion.org>
Re: Getting 1.3 into CVS
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
"Eric J. Peters" <er...@sammg.com> writes:
> Just so you don't think everybody has abandoned the list:
>
> I've got the new version and will be playing with it sometime early
> next week. Let me know if you see any issues and I will keep you
> informed on any problems or successes I come across next week.
Great! I'm glad to see your postings again, Eric.
> I think it'd be great to see a "To Do" list and some documentation
> in the not too distant future -- that would only assist in getting
> developers to look at this project... I'm happy to help where
> needed. I'll (re-) start looking at things early next week.
I'm going to make a posting to the Bio::Perl and Bio::XML groups there
may be people willing to contribute.
Here's my stab at the TODO
1) get 1.3 code into repository. This means:
- decide whether to use Eric's modifications to Tom's code
- use Harmon's code
- merge them together into a single item
- deciding on a namespace (Xerces::*, XERCES::*, XML::Xerces::*)
Harmon's group at Netarx did a lot of work, but since the group has
been so inactive, no one has ever decided whether this is the way to
move. My feeling is that it is a good place to start. I'm looking
forward to what Eric has to say.
Harmon has added some features:
- operator overloading
- exception handling
But I don't want to make the decision unilaterally to adopt the code,
especially since Eric has done a lot of work updating Tom's code.
Once we decide *what* code to use we need to give it a namespace. It
would be nice to register it with CPAN, and if we do, we ought to
following the namespaces already in use, which suggests we place it
somewhere under the XML::* namespace. Following the convention of
capitalized first letters for non-pragma modules would give us the
XML::Xerces namespace.
If we decide on this, I'll submit the module request to CPAN (I'm
already registered as a module submitter).
2) deal with SWIG problems
- doesn't handle operator overloading
- doesn't run well in the debugger (SIGSEGV) after displaying any
data structures
- directly maps the C++ data strucutres, which does not necessarily
map well into Perl data types (e.g. forcing the creation of String
objects instead of just using Perl strings)
3) ensuring that the XML::Xerces::* modules use a Perl-like API,
e.g. it would be nice to be able to use perl strings, and perl
arrays, and have those converted behind the scenes to internally
required data types, and vica versa.
That's my start,
jas.
Re: Getting 1.3 into CVS
Posted by "Eric J. Peters" <er...@sammg.com>.
On Mon, 22 Jan 2001, Jason E. Stewart wrote:
> Hey All,
>
> The list now seems to be working fully, so I can finally begin to do
> something ...
>
> It would be a major step forward to for us to get a version of 1.3
> into CVS. I was hoping to have more people test it before I stick it
> in but I haven't heard from anyone yet.
Just so you don't think everybody has abandoned the list:
I've got the new version and will be playing with it sometime early next
week. Let me know if you see any issues and I will keep you informed on any
problems or successes I come across next week.
I think it'd be great to see a "To Do" list and some documentation in the not
too distant future -- that would only assist in getting developers to look at
this project... I'm happy to help where needed. I'll (re-) start looking at
things early next week.
-Eric.
> I made the latest developer release from Harmon available from public
> ftp:
> genex.sourceforge.net:/pub/genex/xerces-perl-devel.tar.bz2
>
> Please try this and let me know of any issues, otherwise I will be
> moving Tom's old files into the Attic, and replacing them
> lock-stock-and-barrel with the new versions.
>
> jas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-p-dev-help@xml.apache.org
Re: Getting 1.3 into CVS
Posted by Pier Fumagalli <pi...@betaversion.org>.
Jason E. Stewart <ja...@openinformatics.com> wrote:
> "Pier Fumagalli" <pi...@betaversion.org> writes:
>
>> Jason E. Stewart <ja...@openinformatics.com> wrote:
>>>
>>> If there is a way that I can make files available via public based at
>>> apache, that would be great.
>>
>> Sure there is... You can SCP files over to daedalus.apache.org, and
>> especially for xerces-p you would want to put your files in the
>> /www/xml.apache.org/dist/xerces-p/ directory...
>
> Excellent! The current devel tarball is now at:
>
> /www/xml.apache.org/dist/xerces-p/xerces-perl-devel.tar.bz2
Eeeecseeeeleeeeent :) (pronounced like Mr. Burns in the Simpson)
> Sorry, but since no-one on this list is well-versed in the apache
> standard operating procedures, I was attempting to subscribe to
> xerces-c-dev to ask the committers there for help. That's when I
> discovered that xml.apache.org never responded to me ...
For all you having commit access to the Apache Machines, the right list for
question related on how to deal with WWW/CVS/MAIL and so on is
committers@apache.org...
Just for future references...
Take Care..
Pier
--
Pier Fumagalli <ma...@betaversion.org>
Re: Getting 1.3 into CVS
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
"Pier Fumagalli" <pi...@betaversion.org> writes:
> Jason E. Stewart <ja...@openinformatics.com> wrote:
> >
> > If there is a way that I can make files available via public based at
> > apache, that would be great.
>
> Sure there is... You can SCP files over to daedalus.apache.org, and
> especially for xerces-p you would want to put your files in the
> /www/xml.apache.org/dist/xerces-p/ directory...
Excellent! The current devel tarball is now at:
/www/xml.apache.org/dist/xerces-p/xerces-perl-devel.tar.bz2
Sorry, but since no-one on this list is well-versed in the apache
standard operating procedures, I was attempting to subscribe to
xerces-c-dev to ask the committers there for help. That's when I
discovered that xml.apache.org never responded to me ...
Thanks Pier!
jas.
Re: Getting 1.3 into CVS
Posted by Pier Fumagalli <pi...@betaversion.org>.
Jason E. Stewart <ja...@openinformatics.com> wrote:
>
> There is no CVS for the project at sourceforge, just a single file.
>
> I needed to make a single tarball available before I committed the
> individual files to CVS. I didn't have access to public ftp at apache
> so I made it available via a different project I administer at
> sourceforge.
I don't really understand why you need to make a tarball before committing
changes to the CVS, but anyway I don't even know what PERL is, so... :)
> If there is a way that I can make files available via public based at
> apache, that would be great.
Sure there is... You can SCP files over to daedalus.apache.org, and
especially for xerces-p you would want to put your files in the
/www/xml.apache.org/dist/xerces-p/ directory...
Pier
--
Pier Fumagalli <ma...@betaversion.org>
I'm selling my Sony Vaio Z505. Check out <http://www.betaversion.org/~pier/>
Re: Getting 1.3 into CVS
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
"Pier Fumagalli" <pi...@betaversion.org> writes:
> Jason E. Stewart <ja...@openinformatics.com> wrote:
>
> > I made the latest developer release from Harmon available from public
> > ftp:
> > genex.sourceforge.net:/pub/genex/xerces-perl-devel.tar.bz2
> >
> Why are we still using SourceForge? Can't we move the CVS over on
> Apache?
There is no CVS for the project at sourceforge, just a single file.
I needed to make a single tarball available before I committed the
individual files to CVS. I didn't have access to public ftp at apache
so I made it available via a different project I administer at
sourceforge.
If there is a way that I can make files available via public based at
apache, that would be great.
jas.
Re: Getting 1.3 into CVS
Posted by Pier Fumagalli <pi...@betaversion.org>.
Jason E. Stewart <ja...@openinformatics.com> wrote:
> Hey All,
>
> The list now seems to be working fully, so I can finally begin to do
> something ...
>
> It would be a major step forward to for us to get a version of 1.3
> into CVS. I was hoping to have more people test it before I stick it
> in but I haven't heard from anyone yet.
>
> I made the latest developer release from Harmon available from public
> ftp:
> genex.sourceforge.net:/pub/genex/xerces-perl-devel.tar.bz2
>
> Please try this and let me know of any issues, otherwise I will be
> moving Tom's old files into the Attic, and replacing them
> lock-stock-and-barrel with the new versions.
Why are we still using SourceForge? Can't we move the CVS over on Apache?
Pier
--
Pier Fumagalli <ma...@betaversion.org>
I'm selling my Sony Vaio Z505. Check out <http://www.betaversion.org/~pier/>