OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] The truth about standards...

[ Lists Home | Date Index | Thread Index ]
  • To: <xml-dev@lists.xml.org>
  • Subject: Re: [xml-dev] The truth about standards...
  • From: "Rick Jelliffe" <ricko@allette.com.au>
  • Date: Fri, 22 Nov 2002 13:20:24 +1100
  • References: <232810-2200211421163918614@M2W031.mail2web.com>

From: <511251@mclean6-mail.usae.bah.com>

> That is absolutely correct - but I would like to respectfully emphasis that
> this document is not intended as a standard, but simply as a series of
> guidelines.  Therefore, it is not considered policy in any way.

Original Message:
From: Bullard, Claude L (Len) clbullar@ingr.com

> Take a look at the Draft Federal Standard for 
> XML Developers.  Note that it prefers W3C specs 
> over works from other organizations even if the 
> W3C specs are works in progress.   So in a policy 
> document, the sort of thing Gosling mentions is 
> indeed happening.

No, I still cannot see it.  Gosling/Len says that standards are
accepted before they are created.  The Draft Fed Standard
says to use W3C Recommendations and check for
Proposed Recommendations: a Proposed Recommendation
is a (three-month) window, when the technology is no
longer a work-in-progress but finalized.  Last Call is over,
and the issue is just one of status. If they said
to favour Candidate Recommendations, it might be
a different matter.  The allowance for checking Proposed
Recommendations would just prevent embarrassment.

Rick Jelliffe


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS