W3C 工作草案和编辑草案有什么区别? [英] What is the difference between a W3C Working Draft and an Editor's Draft?

问题描述

我正在阅读 XMLHttpRequest 2 级规范(W3C 工作草案 2010 年 9 月 7 日)但在我注意到浏览器正在实现描述为Editor's Draft 消除了很多东西.

I'm reading XMLHttpRequest Level 2 specification (W3C Working Draft 07 September 2010) but after I noticed that browsers are implementing features described into a Editor's Draft that has eliminated many things.

工作草稿和编辑草稿之间的区别是什么?

推荐答案

工作草案是由开发它的小组正式发布的文档，这意味着该小组的成员已经同意它在值得与更广泛的受众分享的状态(通常这是出于反馈目的 - 这当然并不意味着参与者同意文档中的所有内容).

A Working Draft is a document that has been officially published by the group that is developing it, which means that the members of that group have agreed that it is in a state worth sharing with a wider audience (generally this is for feedback purposes — it certainly does not mean that the participants agree with everything that is in the document).

编辑草稿是指负责编写它的人(编辑)当前正在处理的文档.

An Editor's draft is the document as currently being worked on by the person in charge of writing it (the editor).

您可以或多或少地从软件角度考虑:WD 是一个点发布，或者至少是一个标签，而 ED 是最新提交的绝对最新版本.

You can think of it more or less in software terms: a WD is a dot release, or at the very least a tag, while an ED is the absolute freshest version from the latest commit.

决定是否应该查看 WD 或 ED 在很大程度上取决于制定该规范的团队的文化.在 WebApps 组的这种情况下，最好查看 ED，因为它更有可能反映邮件列表中当前快速发展的想法.其他开发 API 的团队也是如此.

Deciding whether one should look at a WD or an ED depends largely on the culture of the group that is working on that specification. In this case with the WebApps group, it is better to look at the ED since it is far more likely to reflect the current fast-moving thinking that goes on on the mailing list. The same tends to apply to other groups that develop APIs.

请注意:在实施和发布规范之前，它只是一个规范.您应该非常小心，不要从中推断出参与该组的各个供应商将按原样实施，甚至根本不会实施.在开发规范时尽早提供它们的目的是收集尽可能广泛的反馈——而不是做出任何形式的承诺(至少在它们达到高于 WD 的成熟度级别之前).

A word of caution: before a specification has been implemented and shipped, it is just a specification. You should be very careful not to infer from it that various vendors participating in the group will be implementing it as is, or even at all. The purpose of making specifications available early, while they are being developed, is to gather the broadest possible feedback — not to make any form of promise (at least not before they reach a maturity level higher than WD).

这篇关于W3C 工作草案和编辑草案有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！