Feedback on Schema.org: Contributing to an Evolving Web Standard

Introduction

Schema.org is a collaborative, community-driven initiative that provides a shared vocabulary for structured data markup on the web. This vocabulary allows webmasters and developers to annotate their content in ways that major search engines like Google, Bing, Yandex, and others can understand. The goal is to create a richer, more useful web by enabling search engines to present information in more informative ways, such as rich snippets, knowledge panels, and other enhanced search results.

Schema.org 是一个由社区驱动的协作项目，它为网络上的结构化数据标记提供了一套共享的词汇表。这套词汇表允许网站管理员和开发人员以主要搜索引擎（如 Google、Bing、Yandex 等）能够理解的方式来标注其内容。其目标是创建一个更丰富、更有用的网络，使搜索引擎能够以信息更丰富的方式呈现信息，例如富媒体摘要、知识面板和其他增强的搜索结果。

As a living standard, Schema.org does not remain static. It evolves to address new use cases, incorporate feedback from its vast user base, and adapt to the changing landscape of the web. This continuous improvement cycle is fundamental to its success and relevance.

作为一个活的标准，Schema.org 并非一成不变。它不断发展以应对新的用例，吸纳来自广大用户群体的反馈，并适应不断变化的网络环境。这种持续的改进周期是其成功和保持相关性的基础。

The Importance of Community Feedback

The development of Schema.org is inherently open and participatory. While the founding companies (Google, Microsoft, Yahoo, and later Yandex) provide stewardship, the direction and details of the vocabulary are heavily influenced by real-world usage and input from developers, SEO professionals, content creators, and toolmakers. Feedback is the primary mechanism through which the community can report issues, suggest improvements, and propose new types or properties.

Schema.org 的开发本质上是开放和参与式的。虽然创始公司（Google、Microsoft、Yahoo 以及后来的 Yandex）负责管理，但词汇表的方向和细节深受实际应用以及来自开发者、SEO 专业人士、内容创作者和工具制造者的输入影响。反馈是社区报告问题、提出改进建议以及提议新类型或属性的主要机制。

This collaborative model ensures that the schema vocabulary solves practical problems and remains applicable across diverse domains, from e-commerce and local businesses to scientific datasets and creative works.

这种协作模式确保了模式词汇表能够解决实际问题，并保持在不同领域的适用性，从电子商务、本地商家到科学数据集和创意作品。

How to Provide Feedback and Report Bugs

The Schema.org website includes a dedicated channel for collecting community input. It is important to note that the main site often reflects the stable, released version of the vocabulary, while ongoing development and discussions about new features may occur elsewhere.

Schema.org 网站包含一个专门的渠道来收集社区意见。需要注意的是，主站点通常反映的是词汇表稳定、已发布的版本，而正在进行的开发和新功能的讨论可能在其他地方进行。

Note: You are viewing the development version of Schema.org. See how we work for more details.

注意：您正在查看 Schema.org 的开发版本。更多详情请参阅我们的工作方式。

Feedback and Bug Reports

Schema.org is an evolving specification. To report bugs or provide general feedback about the site, please use the dedicated feedback form.

Schema.org 是一个不断发展的规范。要报告网站的错误或提供一般性反馈，请使用专门的反馈表单。

• Primary Channel: Use this Google Form to submit your feedback or bug reports.

  • 主要渠道：使用此 Google 表单提交您的反馈或错误报告。

This form is the preferred and most effective way to ensure your input is logged into the system used by the maintainers for tracking and triaging issues.

此表单是确保您的意见被记录到维护人员用于跟踪和分类问题的系统中的首选且最有效的方式。

Best Practices for Effective Feedback

To ensure your feedback is actionable and can be processed efficiently, consider the following guidelines when submitting:

为确保您的反馈具有可操作性并能被高效处理，提交时请考虑以下准则：

1. Be Specific and Descriptive

   • Clearly describe the issue or suggestion. For bugs, include the URL of the page where you encountered the problem and the exact steps to reproduce it.

   • 具体且描述清晰

   • 清晰描述问题或建议。对于错误，请包含遇到问题的页面 URL 以及重现该问题的确切步骤。

2. Contextualize Your Suggestion

   • When proposing a new schema type or property, explain the real-world use case it addresses. Describe why existing schemas are insufficient and provide examples of how the new term would be used.

   • 为您的建议提供背景

   • 当提议新的模式类型或属性时，请解释它要解决的实际用例。说明现有模式为何不足，并提供新术语将如何使用的示例。

3. Reference Relevant Discussions

   • If your feedback relates to an existing GitHub issue, mailing list thread, or community discussion, please include links to those resources.

   • 引用相关讨论

   • 如果您的反馈与现有的 GitHub 问题、邮件列表线程或社区讨论相关，请包含这些资源的链接。

4. Separate Bugs from Feature Requests

   • Distinguish between a technical error on the website (a bug) and a suggestion for enhancing the vocabulary (a feature request or extension proposal). This helps in routing the feedback correctly.

   • 区分错误与功能请求

   • 区分网站上的技术错误（错误）和对增强词汇表的建议（功能请求或扩展提案）。这有助于正确引导反馈。

The Feedback Lifecycle

Submitting feedback is just the first step. Understanding what happens next can manage expectations:

提交反馈只是第一步。了解后续流程有助于管理预期：

• Acknowledgement: Your submission is received into a tracking system.

  • 确认：您的提交被接收到跟踪系统中。

• Triage: Maintainers review incoming feedback, categorize it (e.g., bug, documentation, new feature), and assess its priority and scope.

  • 分类：维护人员审查收到的反馈，对其进行分类（例如，错误、文档、新功能），并评估其优先级和范围。

• Discussion: Significant proposals, especially for new vocabulary, are often discussed publicly on channels like the public-vocabs W3C mailing list or GitHub repositories. Community consensus is sought.

  • 讨论：重要的提案，特别是对新词汇的提案，通常会在 public-vocabs W3C 邮件列表 或 GitHub 仓库等渠道进行公开讨论。以寻求社区共识。

• Implementation & Release: Accepted changes are implemented. Vocabulary updates are batched and released periodically, as documented on the releases page.

  • 实施与发布：已接受的变更会被实施。词汇表更新会分批进行并定期发布，如发布页面所述。

Not all suggestions will be implemented, as they must align with the project's scope, have broad applicability, and gain community support.

并非所有建议都会被实施，因为它们必须符合项目的范围，具有广泛的适用性，并获得社区支持。

Conclusion

Providing feedback is a direct way to contribute to the health and growth of the Schema.org ecosystem. By reporting bugs clearly and proposing well-reasoned extensions, you help make structured data more robust and useful for everyone. The dedicated feedback form is the gateway for this essential community participation, ensuring that the standard continues to evolve in response to the needs of the web.

提供反馈是为 Schema.org 生态系统的健康发展做出贡献的直接方式。通过清晰地报告错误和提出理由充分的扩展建议，您有助于使结构化数据对每个人来说都更加健壮和有用。专门的反馈表单是这种必要社区参与的门户，确保该标准能够持续发展，响应网络的需求。

Remember to consult the official how we work page for the most up-to-date information on the project's governance and development processes.

请查阅官方的我们的工作方式页面，以获取有关项目治理和开发流程的最新信息。