+1 to boxing Xindice into the Attic.
The code is still available, so if a healthy and diverse community does
appear we can always incubate a new project for it.
- Shane
On 8/12/2011 1:23 PM, Gianugo Rabellino wrote:
Further to lack of volunteering on the headsup given to the XIndice
mailing
+1 to moving the future versions to 1.4, it sounds like it's the right
time for that now, especially with the Schema differences. It would be
helpful to have one last release using 1.3 with a big notice on the
homepage so people are prepared.
And I agree overall with Michael about sticking wi
Most information about ECCN numbers at the ASF can be found here:
http://www.apache.org/licenses/exports/
Apache Crimson is in "hibernation" and is no longer actively being
developed. We strongly recommend - from a technical viewpoint - that
everyone switch to using Apache Xerces instead:
+1 to dropping 1.2 support.
Please - be sure that the main website clearly lists the last release we
think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and
is used directly or within other products virtually everywhere. While
we don't need to spend developer time worrying abo
Have you looked at Eclipse? In particular:
- New builds include the WTP - web tools project - which has a bunch
of XML Schema-aware XML editing tools, pretty nifty for manual editing.
- Alternately, the EMF project in the Eclipse Modelling Project lets
you programmatically or builder-wise b
I really thought I replied earlier! Yes, I would love to see a new
release of xml-commons-external. However, there are a couple of
questions we need answered. Anyone from the Xerces/Xalan teams want to
chime in with the info, since they've done much of the maintenance in
the past here?
- W
I don't have a particular opinion on the author tags; it sounds like
we're happy enough with the code at this point.
In terms of voting in new committers, any ASF community - xml-commons
included - would be happy to consider voting in anyone who shows an
active interest in working in the projec
Hmmm... I'm presuming we'll get JAXP 1.3 checked in and then have
Xerces/Xalan evaluate to form a plan on when/how they want to upgrade to
supporting these new interfaces. They're currently supporting the
checked-in JAXP 1.2 version code, with some spot improvements, now.
Basically, it's a ne
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
I know a number of projects have already converted to Subversion, but
I'd like to remind everyone that eventually (perhaps within this year)
the infrastructure team is going to require all projects to migrate to
Subversion.
This is a particular issue for XML-land since many of our projects
referen
Especially now that xml-graphics and Xalan are moving on to become
their own top-level projects (yay!) let's use this time to actually get
all the rest of the xml-related projects off of the old wiki
installation and onto the new moinmoin-based one. Heck, several of our
projects don't even have en
A couple of comments:
- Please cc: [EMAIL PROTECTED], since xml-commons is the
actual repository that holds the JAXP code.
- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
and Sun folks for getting the process unstuck. 8-)
- Both Elliotte's and Clay's questions below are imp
This means you! There were plenty of people interested in XML-related
subjects last year, but not nearly enough XML-related talks! (well, except
for the Cocoon folks). Please be sure to submit your ideas - it doesn't
take long to submit an idea (you just need a brief description for now) and
I'm happy to have xml-commons be the home for clearly useful xml-related
utilities, even if there aren't other existing XML projects (or parts of
the federation) that use it currently. Originally, I was concerned about
having too much activity and not being able to handle it well - I figured
At 06:26 AM 3/12/2004, Berin wrote:
Accordingly, I'd request that all committers vote on the proposal that was
put forward last week, and which can be found at :
http://nagoya.apache.org/wiki/apachewiki.cgi?XMLProjectPages/OpenSSLJCEProposal
+1 from Shane (xml-commons, xml-xalan, PMC) for this pr
Here's tardy Shane's:
+1 to the FederationProposal.
Note that one thing I want to make sure of is cleaning up the charter
before (or as) we split off any projects. We could definitely look to
jakarta or other more recent TLP's charters to have some clearer and
simpler voting procedures (stating w
Adding Shane's +1 to Neil's email.
- Shane
From: Neil Graham <[EMAIL PROTECTED]>
Hi all,
So how did Joerg Pietschmann vote I wonder? :)
Anyway, my +1 below.
[ ] Scott Boag
[ ] Andy Clark
[ +1] Shane Curcuru
[+1] Neil Graham
[ ] Kip Hampton
[ ] Vincent Hardy
[ ]
I agree the main discussion should happen on general@, however everyone has
to forgive me for unpolished style writing in the airport.
My feeling is xml should do two things, which hopefully both will make
sense, and will address the issue:
-- Split the ASF organizational structure up into 3ish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The xml-commons team is pleased to announce a beta release of our
popular Resolver component version 1.1b1 (beta before a 1.1 release).
The release is available at
http://www.apache.org/dyn/closer.cgi/xml/commons/
Blurb
- -
Resolver
(http://xml.apa
Is it just me, or don't we have a policy that all software distributions
should be PGP/GPG or equivalently signed with the release manager's key? 8-)
Admittedly, plus points to Forrest and Xindice since they've already moved
their distributions to the mirroring system at
www.apache.org/dist/xm
I'll move commons in the next day or so. Thanks for getting the structure
up in place.
Anyone want to share the specific command line to create the appropriate
-current- links for us Windows users?
- Shane
At 08:24 PM 9/10/2003 +1000, Berin wrote:
Peoples,
The general xml.apache.org mirrors
Here's my +1 to both of you!
Personally, I'd like to go with Berin's layout and top half of the page,
since I'd like to see more sites use Forrest (we are the XML processing
project, after all). But you need to add the 'how to verify' stuff from
Gareth's page to the bottom, especially the hand
>
> Please put your votes on [EMAIL PROTECTED]
>
>
> Require votes from :
>
> Scott Boag [ ]
> Andy Clark [ ]
> Shane Curcuru [+1] to both nominees
> Neil Graham [ ]
> Kip Hampton
A couple of comments out to general@; I'm presuming that all PMC members
read general somewhat regularly... Two quick notes on mirrors and PGP:
> Ted Leung wrote:
> As promised, here's a list of work items for the PMC
> ...
> o Encourage projects to start using the ASF mirroriing guide
You can simply use a JAXP Transformer to do it *without* a stylesheet by
using the identity transform (in JAXP, you simply get a newTransformer()
without a source document); or you can copy a stylesheet that does the
identity transform and then set the indent-amount yourself (since Xalan's
defa
Not ACKd.
As always, the appropriate place for technical questions about any of
xml.apache.org's software is on the -dev or -users list for that
particular project. In this case, you should be asking on the
[EMAIL PROTECTED] mailing list as described in
http://xml.apache.org/mail.html#xalan-j-use
Ooops! My bad since I meant to nominate someone and then got caught up
in too much other work lately.
+1 to running the vote on commons-dev@xml, since that is the mailing
list that the commons community should be living on.
+1 to announcing the vote on general@xml, since technically according
to
Good idea, although it certainly falls on someone to volunteer to help
fix this kind of stuff. Thanks for bringing it up.
xml-commons - eek, that's a lot! Of course, some of xml-commons isn't
sourced originally from Apache projects, so some of those may not be
our 'fault' and I may not want to f
Legal issues, PMCs/Members/Committers, etc.
Unfortunately, this is an area that some people have concern about, but
few of us seem to be actual lawyers with the experience to accurately
describe the details... And when it comes to legal issues, the details
ARE the important stuff.
In te
Technical organization of xml.apache.org
I think Scott and perhaps others brought up the idea of having some
sort of architectural and technical organization in xml to encourage
code sharing, cross-pollination, etc. This is an excellent idea, and
again is something that we can talk about
The public face of xml projects
Yes, this is an excellent point - it would be nice to have a much more
nicely organized website to help anyone more easily find the ASF
software that they might want to use. But I'd really like to discuss
this as a separate issue from the corporate organiz
Corporate organization of xml.apache.org
Why do I say 'corporate' organization? Because the ASF is just that -
a corporation, and has to act like one, even if it's structure and
goals are pretty unusal. That means oversight of the actions taken on
behalf of the corporation by individual
OK, as usual I'm late to the party! There are a bunch of good ideas on
this thread, but some have gone off on tangents.
Instead of trying to copy&paste to respond to individual notes I'll
just summarize my thoughts. To help on threading,
I'll respond in separate replies to the main issues I wa
Just in case folks interested in xml-apis.jar or resolver or which
aren't on commons-dev: we're having some interesting discussion about
versions of DOM/SAX/JAXP files and how we'd like to release xml-commons
tools in the future.
Follow the discussion at:
http://nagoya.apache.org/eyebrowse/Summari
If anyone can track down where that offending xml-apis.jar came from
and squash it, that'd be great. xml-apis.jar should be owned by
xml-commons, and it should always have a full set of JAXP.
(Hmmm - did we ever have an xml-commons release of just JAXP 1.0, which
didn't include transformations in
If ya wanna talk turkey about xml-apis.jar, then come over to the
commons-dev@xml list. But general answers follow:
- xml-apis.jar should always have the full DOM/SAX/JAXP set in it. The
specific versions of these files may change; in the near future we hope
to have one that is TCK-compatible bu
This is a question for the [EMAIL PROTECTED] list; I've
forwarded it there.
(I've really gotta get my old mailing list FAQ found and sent out again...)
=
- Shane
__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
The appropriate place to discuss xml-commons is on
[EMAIL PROTECTED] We do have a web page at
http://xml.apache.org/commons although it's a little thin so far.
xml-commons is explicitly a bit 'quieter' than jakarta-commons,
although lately it's been a bit *too* quiet (not that I have extra time
I'm guessing you mean the one from Xalan-J 2.x, although the last
change to our PrefixResolver.java was on June 11th, so I'm not sure why
this is coming up now.
In any case, you can apply the same patch that we made to our
PrefixResolverDefault r1.3 by simply adding:
/**
* @see
Great! Thanks for the note.
Sander/RefactorIT: yes, in my opinion you should definitely add the
javax.xml* packages, since we have apache code there and they're quite
important packages for our xml work (and some work in jakarta). Note
that Apache has several main communities, each of which have
For those of you interested in the technical details about versioning
of xml-apis.jar and SAX/DOM/JAXP in xml-commons, please join us on the
[EMAIL PROTECTED] mailing list.
You can also follow the discussion in one of the archives:
http://marc.theaimsgroup.com/?l=xml-commons-dev&m=102540170321171
Well, as in any licensing issue, the devil is in the details. Which
copy of the file are you wondering about?
As far as I can tell, all the source code in xml.apache.org's
xml-commons repository is either covered under the apache license (in
each source file) or covered under clearly marked LICE
Let me also extend congratulations to *all* of the other folks who were
also elected to be members (in the XML world, you might recognize Ted
Leung, Keiron Liddle, John McNally, Daniel L. Rall, and Davanum (Dims)
Sriniva) as well as the new members of the board of directors
Curious about all th
(I'm not sure which is more amusing: asking basic questions about XML
use with Micro$oft products, or Sam's empty reply 8-)
Actually this is a list for cross-project technical issues with
xml.apache.org software, not a general list for XML learning.
We should probably have a nifty links page on
OK, I really need to go back and read this thread.
>From my perspective, there is definite value in having a project to
supply just interfaces. But everyone has their own opinion. And we
hoped that the first major customers of xml-commons wouldn't be end
users, but would be the other Apache xml
The appropriate list for Xalan-J questions would be
[EMAIL PROTECTED], not general@xml. And you'll need to
provide a few more details, especially what specific problem you're
having (error messages, incorrect output versus what you expect, etc.).
Presuming it really is well-formed XHTML, Xalan s
you Paul Libbrecht <[EMAIL PROTECTED]> wrote
> Hey, hey, that would be new !
Actually, it's been there for several months. We even have a web page
for xml-commons, although the project is still moving a bit slowly.
xml.apache.org/commons
> Can someone confirm this somewhere ??
> Whic
There are a number of people (although not me currently) working on
this kind of issue.
One comment about JAXP: in my non-lawyerly way, I'm presuming there is
no issue here. The xml-commons project is how Xalan (and soon Xerces)
get their SAX/DOM/JAXP code. The actual source files for the
javax.
Could you or some other Xerces committer please sign these release
files and upload the signatures so we can be sure the distros aren't
tampered with? PGP seems to be the most popular way to sign, but GPG
is often used too.
Although I'm not sure where the standard is, we really do need to sign
o
Here's a brief report on what the xml-xalan committers have done to
address potential licensing issues brought up recently.
The xml-xalan project includes a number of .jar files in
xml-xalan/java/bin:
-- ASF licensed files with corresponding licenses from their project:
ant.jar (jakarta-ant)
ant
Here's a brief report on what the xml-commons project has done to
address potential licensing issues brought up recently.
The xml-commons project is a little unusual in that it contains a
variety of different items, including code sourced from several
locations. Hopefully we've made it obvious t
you Guillaume Rousse <[EMAIL PROTECTED]> wrote
> Yes, it requires a net connection, but from
> where did you get your initial source tarball anyway ?
Well, a couple of points:
-- The initial download requires a net connection somewhere, but many
folks only download once and then work on
Torsten Curdt wrote:
> > ...why don't we just store the uri where the required jar can
> > be found and let "ant" get those jars for us?
you Andy Clark <[EMAIL PROTECTED]> wrote
> For the same reason that I was opposed to changing the Xerces-J
> build to pull the xml-commons
(Butting in with my non-lawyerly non-PMC-member opinion)
Yes, I think legally we do have to include the licenses for other
apache jars that each subproject re-ships. In some ways it's silly,
but remember with 1.1 of the license, the name of the subproject (Ant,
Xerces, etc.) actually appears (or
Xalanites: for legal or coordination issues, please
followup-to:[EMAIL PROTECTED]; for specific technical issues
about how we'd address these points followup-to:xalan-dev.
A few comments/opinions from my perspective and comments
on xalan-related items. -sc
you Dirk-Willem van Gulik <[EMA
Off the top of my head I would rather not see a project in this very
early stage of development be 'hosted' in an official way at
xml.apache.org, at least not unless a number of existing xml committers
were planning to devote resources to it immediately.
I think one of the strengths of apache is
One important question about the resolver: what dependencies does it
have? I'm presuming that it will only depend on JDK 1.2 and other code
in xml-commons, and not have other external dependencies. Correct?
you Norman Walsh <[EMAIL PROTECTED]> wrote
> Some time ago, Stefano started a
I'm happy to announce the first 'preview' release of the xml-commons
project. This includes the environment checking utility
org.apache.env.Which, plus updated copies of DOM L2, SAX 2.0x, and JAXP
1.1.3x.
Website: http://xml.apache.org/commons/
Downloads: (with associated .sig files)
http://x
> you [EMAIL PROTECTED] (Kevin A. Burton) wrote
> > Which is a General environment checking and version finding
service.
> Just a humble suggestion. Under *NIX the 'which' command is
used for finding
> the binary that would be executed if you were to execute the given
command.
Indeed
Here's my:
+1
VOTE for adding Entity Resolver to the xml-commons project.
I suppose at some point we should count the actual number of
committer's votes (theoretically in the xml-commons project itself, to
be really strict) and decide that we are ready for this; then we'll
need to wait for Norman
OK, this is frustrating. Here I've been thinking my mailer is dropping
messages, when I realize that apparently *all* the messages I send to
Apache lists from this '[EMAIL PROTECTED]' account are
mysteriously being lost.
Am I missing some magical setting on my account or has someone
blacklisted
There are a number of good overview sites for learning about XML; they
might be a better resource than this list, which is devoted to
cross-project issues about Apache projects here at xml.apache.org.
General resources:
http://www.oasis-open.org/cover/xml.html
http://www.xml.org/xml/resources_co
I'm pretty sure he meant APL = Apache Public License, it seems to be
such an inviting acronym to be made. But I'd have to weigh in with
Edwin with my non-lawyer answer: I'm pretty sure that the MPL 1.1 is
*not* useable in Apache projects. (Sure, you can use Apache projects
and MPL-covered projec
you Martin Stricker <[EMAIL PROTECTED]> wrote
> Ummm, maybe I'm just too stupid, but why should all the projects keep
a
> copy of their xml-commons code if it already is in xml-commons?
Please
> enlighten me since I get the feeling that this approach obsoletes
> xml-commons.
Well, it's
A brief and completely non-scientific poll of the people in the vendor
booths on the show floor at JavaOne SF 2001 showed a tremendous number
of users of Xalan-J and Xerces-J. I didn't get version numbers or lots
of details, but it was pretty clear we were being used in a large
percentage of majo
Sounds good. We should probably tag the files after checking them in
so we can cross-correlate each of our versions with external sources.
Xalan is already using the xml-commons files in posted builds; as a
fallback we use the xml-xalan copy of files if we can't find a local
xml-commons director
you Isaac Shabtay wrote
> jaxp.jar contains an implementation of
> javax.xml.parsers.DocumentBuilderFactory. This implementation's
> "newInstance" method does the search using the four steps above. When
it
> comes to step number 4, it looks for Crimson.
>
> So, if tomorrow there'll be an
Huh? I'm not sure what you mean. The JAXP specification is effectively
a bunch of interfaces that anyone can implement (along with the rest of
the docs, etc.). Apache happens to have several implementations of
JAXP 1.1: Crimson, Xerces 1.x, Xerces 2.x, and Xalan 2.x - because we
already had the
Here's my xml-xalan/xml-commons committer:
+1 to blocking "Christine Hall" <[EMAIL PROTECTED]> from any and
all applicable apache.org mailing lists.
(I forget: do we have a spam-master at apache for mailing list
management?)
And a friendly reminder: please don't post HTML to the list, just text
This kind of question is best answered on the
[EMAIL PROTECTED] mailing list - general@xml is for bigger
cross-project issues.
Oh - this is a cross-project issue. 8-) Since it's a specific
technical question about Xerces/Xalan, I'd ask on thier project's -dev
or -users lists first.
- Shane
This question is best answered on the [EMAIL PROTECTED]
question. [EMAIL PROTECTED] is reserved for cross-project issues.
When you follow-up with xalan-j-users, be sure to include the full .xsl
and .xml files you're using, so we can better diagnose the problem. In
general, redirect works well;
you "Arnold, Curt" <[EMAIL PROTECTED]> wrote
> This is the wrong forum for this type question.
> However, the right form of the URL would be file:///c:/test.xml.
> See http://www.ietf.org/rfc/rfc1738.txt
So, while I agree with Curt about this being the wrong forum, I'm going
to be s
Please see my followup to xalan-dev and xalan-j-users.
(Sorry, forgot to cc: here)
- Shane
=
mailto:[EMAIL PROTECTED]";
humor="'A Midsummer Night's Dream' - pick your quote" />
__
Do You Yahoo!?
Get personalized email addresses from Yahoo! M
Actually, you just caught us as we're beginning to
split the Xalan discussion lists!
Today and in the future you should address
development-oriented issues about Xalan to
[EMAIL PROTECTED] This is for people actively
developing new code on Xalan-J or Xalan-C.
Starting today, you should address
74 matches
Mail list logo
