Technical Standards are:
Standards are sometimes used by regulators and cited in regulations as a tool to demonstrate compliance. They can also serve as a catalyst for innovation and help in anchoring solutions more quickly on the market. Innovations that extend across industries and value chains are becoming increasingly important. Incorporating innovative aspects into standards can prove crucial for market success since the market is then best prepared for the product.
Each standard is developed by a working group that is assigned a TSC sponsor. The sponsors independently oversee the working group and ensures policies and processes are maintained to guarantee high-quality outputs and reinforce the relevance of industry and technology standards.
More details can be found in the Get involved section of the TSC website.
The submission of a proposal to develop a standard is the next point in the standards process. At this stage, the solution overview should not be too detailed. The solution will be defined by the parties involved in writing the standard once in development if the submission is successful. The TSC will review the submission and if successful, a Working Group will be created to drive the standard forwards to completion. As this will be made public, nothing in this form should disclose key inventions that may be part of the proposal – in order to protect any intellectual property that may otherwise become public knowledge (and therefore prior art).
Before the standard is released publicly, we will confirm if the author(s) have contributed to any IP and if the IP is protected to the satisfaction of their company. Though we encourage open-BSV licensing, we leave it at the IP owner’s discretion under which conditions the standards can be implemented. We make IP licensing information and templates available to our working groups.
Time commitment – Authors
The time that it takes to create technical documentation directly correlates with the length of the documents. As a rule of thumb for estimating the creation of technical documentation, it takes about 2 hours per page to write a new document for a non-professional writer. Like any writing project, authors must also allow time for research, outlining, review and coming up with diagrams/images. As a guideline, a typical technical document can take between 24 and 50 hours to complete usually across 3-4 months.
Time commitment – Reviewers
The review cycle will vary depending on the complexity of the technical standard. A common process follows a first draft, revised draft, and final draft/version of the document. Each review will refine and improve the document. Therefore, a lengthier or more critical document will require additional rounds of review. As a guideline, the time commitment to the review process over the expected lifetime of the workgroup are expected to be in the range of 2-3 months and would typically require 5-10 hours of review work split across 2-3 iterations of a draft standard.
Being a member of a working group will provide the opportunity to shape the technical content of the standard based on your own interests, knowledge and ideas, ensuring that the standard being recommended integrates with your companies long-term technical needs.
Joining a working group presents a fantastic opportunity to expand your network and meet other experts in the fields. It provides access to information about worthwhile technologies and regulations at an early stage, helping you keep up to date.
Any modifications or derivative works must be identified clearly and offered under the same licence. For example, a third party is free to expand on the standard further and even commercialise the improvement into a product, if the product is for use with the BSV blockchain only. If a third party wanted to use a different blockchain, they would need to seek a commercial licence from Bitcoin Association.