Lists Home |
Date Index |
- From: Paul Grosso <firstname.lastname@example.org>
- To: xml-dev <email@example.com>
- Date: Fri, 1 May 1998 11:31:00 -0400
At 10:01 1998 05 01 -0400, Paul Prescod wrote:
>Here are some more thoughts about open standards processes:
>The XML SIG was pretty wide open, which was admirable, but XSL the DOM,
>etc. seem to have no equivalent.
I don't quite understand this statement.
The open, public firstname.lastname@example.org mailing list has been in existence "forever,"
and the DOM work has been receiving some very useful feedback from people on
The open, public email@example.com has been in existence for only
two weeks less than the xsl-wg itself, and it has been quite active since
The "problem" with the XML SIG was that everyone on that list had to be
an "invited expert" and they were all bound by W3C-member confidentiality
regulations. This was a logistic nightmare, and it actually meant that
some important discussion was pre-empted from truly public lists like xml-dev.
The XSL WG decided instead not to have this "intermediate" (and confusing
and problematic) level mailing group, but instead to have just the public
xsl-list (kindly hosted by Mulberry Technologies). We felt that was the
more open, democratic thing to do.
As far as XSL, if you think you're not seeing something that W3C members
are seeing, you're wrong. We do not have anything yet to show (other than
the requirements document that we are in the process of releasing to the
public as we speak). We plan to have a first draft of the XSL 1.0 spec
released to the public in July--the same time it is released to W3C members,
as I understand it [mega-apologies if I'm wrong about this, but this is my
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)