Learn how Bing Chat on Microsoft Edge can assist editors and reviewers in improving a specification during standard development process, analyzing and improving requirements, assessing implications on stakeholders groups, and identifying security risks.

The development of technical standards is a process that requires input from multiple stakeholders. One critical aspect of this process is the role of editors and reviewers who are responsible for ensuring that the specification is accurate, complete, and meets the requirements of stakeholders and the needs of the industry. Editors are responsible for the creation and maintenance of the specification, while reviewers are responsible for providing feedback on the specification to improve its quality.

This article explores the potential of Bing Chat on Microsoft Edge in supporting technical standard development through specification reviews. By leveraging Bing Chat, editors and reviewers can ask relevant questions and receive real-time responses, which can help identify potential issues or gaps in the specification. This can lead to more efficient and effective specification reviews, ultimately resulting in better quality standards.  

We aim to provide an introduction to the topic, we plan to dive deeper into this area in future articles. 

For now, we will explore 13 prompts that specifications editors and reviewers can use to leverage Bing Chat on Microsoft Edge during the  standard development and specification reviews process. For this, we will use the draft specification Layer 2 Transaction Fee Specification v1 developed by Layer 2 Working Group, an initiative of EEA Community Projects.

Let's dive in. 

#1 - The setup

If you would like to follow along and try for yourself, open the article using Microsoft Edge. Then click on the “Bing” icon on the top right corner.

You will be asked to set the tone of responses, choose “More Precise”. This will allow you to get responses which are factual and concise. In this mode, Bing Chat prioritize accuracy and relevancy.

So now, what to use Bing Chat for ?

#2- Understanding the document structure

Understanding the structure and organization of a technical specification document is critical for effective specification review. A well-organized document structure can help reviewers navigate the specification more efficiently, identify potential issues or gaps more easily, and provide feedback that is relevant to specific sections or requirements.

PROMPT 1 : “What are the key sections in this document ? “

PROMPT 2 : “What are the key sections and subsections in this document? "

Please note the difference in outputs between prompt 1 and 2.

#3- Analysing and improving requirements

Understanding individual requirements is crucial for effective specification review as it allows reviewers to assess the completeness, accuracy, and testability of each requirement. By understanding individual requirements, reviewers can provide feedback that is more focused and relevant, helping to ensure that each requirement is articulated in the best way possible.

PROMPT 3 : “How many requirements are in this document ? “

Please note that the above is in fact incorrect because the document counts 26 requirements. We were able to identify that one of the subsections (3.3) of the specification was not being “seen” and was totally disregarded but we were not able to understand why. We will investigate but in the meantime, if you have any idea, please let us know !

PROMPT 4 : “Please explain requirement 18?”

Analyzing specific sections of a specification is a crucial aspect of effective review. By focusing on specific sections of the specification, reviewers can identify potential issues or gaps, provide feedback that is relevant to the section, and ensure that the section is consistent with the overall goals and objectives of the specification.

PROMPT 5 : “Could you suggest any changes or improvements to the wording or structure of subsection 3.2 to make it clearer or more concise?”

Testability requirements play a critical role in ensuring the effectiveness and reliability of a specification. A well-defined testability requirement can help ensure that the specification can be tested thoroughly, allowing for the identification and resolution of potential issues or vulnerabilities when it is implemented.

PROMPT 6 : “Could you improve the testability requirement for requirement 18?”

PROMPT 7 : “How did you improve the testability requirement for requirement 18?”

#4- Defining, clarifying and understanding technical concepts

Understanding technical concepts and terminology in a specification is essential for effective review, as it enables reviewers to accurately assess the technical requirements and implications of the specification. Technical terminology and concepts are often highly specialized and sometimes not clearly defined. 

PROMPT 8 : “Is the definition on an account in section 1.2 glossary correct ?”

PROMPT 9 : “What is the difference between a direct transaction and a meta transaction ?”

#5- Exploring implications of the specifications for different stakeholder groups

Considering the broader implications of a specification is crucial for effective review as it allows reviewers to identify potential impacts and considerations beyond the immediate scope of the specification. By considering the broader implications, reviewers can help ensure that the specification aligns with industry standards and best practices, is scalable and adaptable to future changes, and does not introduce unintended consequences or negative impacts.

PROMPT 10 : “What are the potential implications of this specification for L2 providers?”

PROMPT 11 : “What are the potential implications of this specification for the industry?”

PROMPT 12 : “What are the potential implications of this specification for L2 users?”

#6- Exploring security risks

Identifying and addressing potential security risks in a specification is critical for ensuring the safety and security of its implementations.

PROMPT 13 : “What are the potential security risks associated with this specification”

In conclusion, Bing Chat on Microsoft Edge has the potential to significantly improve the efficiency and effectiveness of the specification review process in standard development. By providing relevant prompts and insights, Bing Chat can assist editors and reviewers in identifying areas for improvement in the specification, ensuring that requirements are clear, testable, and secure, and exploring the broader implications of the specification for different stakeholder groups. However, this article is only the beginning of our exploration of how Bing Chat can be used to improve the standard development process. In future articles, we intend to delve deeper into each of the sections discussed in this article and provide more detailed guidance on how editors and reviewers can use Bing Chat to improve their review process.

Overall, Bing Chat on Microsoft Edge has the potential to be a valuable tool for editors and reviewers in the standard development process, and we look forward to exploring its full capabilities in the future.