Altova Mailing List Archives

Re: RFD: comp.text.xml

From: Peter Murray-Rust <peter@-----.-----.--.-->
To: "Xml-Dev (E-mail)" <xml-dev@--.--.-->
Date: 5/2/1998 6:34:00 PM
[reply to xml-dev only - I'm sure JamesT will read this].
At 21:34 02/05/98 +0800, James K. Tauber wrote:
>                     REQUEST FOR DISCUSSION (RFD)
>                   unmoderated group comp.text.xml
>This is a formal Request For Discussion (RFD) for the creation of a
>comp.text.xml newsgroup.  This is not a Call for Votes (CFV);
>you cannot vote at this time.  Procedural details are below.

I am deliberately neutral about this - this message is simply to state how
I see XML-DEV's position w.r.t. the propose comp.text.xml

>A newsgroup for the discussion of the Extensible Markup
>Language (XML); including, but not limited to the specifications
>and syntax, document creation and editing, interchange, software,
>processing and database integration. This applies not only to XML
>itself but also the Extensible Linking Language (XLL), the Extensible
>Style Language (XSL), Cascading Style Sheets (CSS) as applied to XML
>documents, and to document types and applications of XML.

XML-DEV has had and continues to have robust and IMO valuable discussion in
these areas.

>XML is a new language, and it appears that it will be extremely
>Over the past few months, traffic on the XML-DEV and XML-L mailing lists has
>grown rapidly.  With the release of the W3C Recommendation for XML 1.0,
>developer interest is growing rapidly and an increasing amount of software
>being released.  A newsgroup would make it much easier for a wider audience
>to participate in and benefit from these discussions.

I will leave Henry to answer whether there are any current problems of
scale. [I would hate to promise his services without checking :-)]

>Policy on Advertising
>We encourage discussion of the merits and shortcomings of
>commercial products. A certain amount of advertising (both objective
>and advocative) is to be expected and this is to be encouraged as
>long as the products and services relate directly to XML and the
>announcements are brief. Company representatives are expected to
>participate in discussions of their product that they themselves did
>not initiate.

There has never been the slightest hint of abuse of this on XML-DEV and for
this I thank the XML community. We aren't yet at the stage where there are
a large number of XML products in common use, so haven't got to the 'I
bought XML-FOO last week and when I try to run DUCKBOOK under it it ...'. 

So far there have also been very few 'What is a DDT?' 'Where do I find the
< and > on my keyboard?'. Peter Flynn and Robin Cover (and many others)
must take great credit for providing answers to every conceivable question.
Since I have asked these sort of Qs on comp.text.sgml 3 years ago, I expect
that there needs to be a similar place for XML. XML-DEV isn't appropriate
for large volumes of such Qs. I'm neutral whether it should be on
comp.text.xml, comp.text.sgml or XML-L.


Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
net connection
VSMS, Virtual Hyperglossary

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as:
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.