Octue

Strands documentation

Overview

Getting started

Get started with Strands

Glossary

JSON Schema fundamentals

Introduction

Key JSON Schema concepts

Anatomy of a JSON Schema

JSON Schema best practices

Use cases

Standardizing scientific data management: Enhancing research efficiency with Strands

<h2 class="slate-h2 " >The pain points of data governance</h2><p class="slate-p " >Large enterprises face increasing pressure to maintain data quality, ensure compliance, and facilitate collaboration across teams. Modern relational databases increasingly support JSON, but managing JSON-based schemas at scale becomes a major challenge without proper governance. A lack of standardization leads to fragmented data models, compliance risks, and inefficiencies in collaboration.</p><h3 class="slate-h3 " >🧩 Challenge 1: Schema fragmentation across teams</h3><p class="slate-p " >Without a centralized schema repository, teams develop and manage schemas independently, leading to inconsistencies, redundant work, and integration issues. See the example of the UK&apos;s <a href="https://conference.json-schema.org/presentation/JSON%20Schema%20for%20data%20design%20and%20contract.pdf" target="_blank">Driver and Vehicle Licensing Agency (DVLA)</a>.</p><h3 class="slate-h3 " >🧩  Challenge 2: Lack of version control and compliance tracking</h3><p class="slate-p " >Manual schema management makes it difficult to track changes, enforce data standards, and maintain audit trails for compliance purposes.</p><h3 class="slate-h3 " >🧩  Challenge 3: Time-consuming and costly manual processes to maintain data compliance</h3><p class="slate-p " >You and your team likely spend countless hours manually managing schemas, validating formats, and resolving inconsistencies—wasting valuable resources that could be better spent on strategic initiatives.</p><h2 class="slate-h2 " >Strands: Enforcing proactive data governance and compliance for long-term security</h2><p class="slate-p " >Strands is a specialized platform for creating, publishing, and managing JSON Schemas that provides enterprise-grade controls for data governance. Our solution empowers your data management team to establish and enforce data standards while facilitating collaboration between technical and business teams.</p><h3 class="slate-h3 " >💡<strong class="slate-bold">  Solution 1: Centralized schema repository - Say goodbye to data silos</strong></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">What it does: Strands provides a central hub where all your organization&apos;s JSON schemas are stored, managed, and distributed.</div></li><li class="slate-li " ><div style="position:relative">What this means for you: You eliminate schema inconsistencies across teams and projects, making data integration seamless and improving data quality organization-wide. Teams across your enterprise work with the same schema definitions, drastically reducing data validation errors.</div></li></ul><h3 class="slate-h3 " >💡<strong class="slate-bold">  Solution 2: Version control and audit trails - Maintain control and compliance</strong></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">What it does: Strands implements semantic versioning for all schemas, allowing you to track changes, identify breaking updates, and maintain backward compatibility.</div></li><li class="slate-li " ><div style="position:relative">What this means for you: You gain complete visibility into schema evolution with clear audit trails. Your teams can confidently update schemas knowing which changes are breaking and which are compliant with industry regulations, while having the ability to roll back to previous versions when needed.</div></li></ul><h3 class="slate-h3 " >💡<strong class="slate-bold">  Solution 3: Schema composition and referencing - Build complex data models</strong></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">What it does: Strands allows teams to reference and reuse schema components across multiple schemas, promoting standardization and reducing duplication of work.</div></li><li class="slate-li " ><div style="position:relative">What this means for you: You can build and maintain complex data models from reusable components, ensuring consistency across your organization while simplifying maintenance. When a core component changes, all schemas referencing it automatically inherit those changes.</div></li></ul><h2 class="slate-h2 " >The Strands difference</h2><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Increased efficiency:</strong> Replace hours of manual schema management with automated version tracking and distribution, freeing your team to focus on higher-value data governance initiatives.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Cost savings:</strong> Eliminating redundant schema management efforts leads to significant cost reductions in enterprise data operations.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Ease of use:</strong> With an intuitive interface and upcoming no-code schema editor, Strands makes schema governance accessible to both technical and non-technical users.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Automated validation workflow:</strong> Prevent breaking changes across teams by automatically validating schemas against specifications, ensuring references are resolved correctly, and verifying examples within schemas.</div></li></ul><h2 class="slate-h2 " >Real-world example: DVLA&apos;s schema management approach</h2><p class="slate-p " >The <a href="https://conference.json-schema.org/presentation/JSON%20Schema%20for%20data%20design%20and%20contract.pdf" target="_blank">UK&apos;s DVLA</a> has implemented a similar schema management approach to what Strands offers. With over 1,600 schemas in their data dictionary, they&apos;ve built internal tools to manage schemas at scale, validate changes, and generate code. Their vision aligns perfectly with Strands: &quot;Make it easy for teams to use standard data models and naming conventions across their data, contracts, and code.&quot;</p><p class="slate-p " >What took the DVLA significant internal development resources to build is available immediately with Strands as a ready-to-use platform. Their success demonstrates the value of centralized schema management in government and enterprise settings.</p><h2 class="slate-h2 " >Get started with Strands</h2><p class="slate-p " >The first step toward better data governance is to <a href="https://strands.octue.com/account/signup" target="_blank">sign-up for Strands</a> and <a href="67a364563abce46030e148c8/67a3645ca91c8ffa44ab795e" target="_blank">create your first Strand</a>. Our platform provides immediate benefits with seamless integration into your existing systems and workflows. Visit <a href="https://strands.octue.com/" target="_blank">our website</a> to learn more or <a href="https://uk.linkedin.com/company/octue" target="_blank">contact us</a> directly to schedule a personalized demonstration.</p><h2 class="slate-h2 " >What you can expect</h2><p class="slate-p " >After implementing Strands, your organization will experience:</p><p class="slate-p " >⏱️ Reduction in time spent managing schema changes and resolving schema-related issues within the first quarter.</p><p class="slate-p " >✅ Significantly improved data quality metrics within 3-6 months as standardized schemas are adopted across teams.</p><p class="slate-p " >🛡️ Enhanced compliance posture with complete auditability of schema changes and usage across your enterprise.</p><p class="slate-p " >🚀 Streamlined development processes as teams work from the same standard data models across applications.</p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><h2 class="slate-h2 " >Ready to optimize your data governance framework for future scalability?</h2><p class="slate-p " ><a href="https://strands.octue.com/account/signup" target="_blank">Create a free account</a> and start your journey with Strands or <a href="https://uk.linkedin.com/company/octue" target="_blank">send us a message</a> and let us know your needs, we&apos;re here to help you.</p><p class="slate-p " ></p>

Mitigating data governance risks: Future-proofing enterprise data with Strands

<h2 class="slate-h2 " >The struggle for a unified data format across diverse technical equipment</h2><p class="slate-p " >As a systems engineer, you manage data from different technical equipment and face significant challenges with data standardization and management. Each system outputs data in a different format, forcing you to create custom transformations that break when equipment changes. These fragmented, manual processes waste engineering time and introduce errors that compromise operational reliability. Strands automates these data standardization processes, streamlining your equipment data pipelines and eliminating the constant struggle to maintain consistency across your technical ecosystem.</p><h3 class="slate-h3 " >🧩  Challenge 1: Fragmented data across multiple systems</h3><p class="slate-p " >You must manage data from numerous equipment types, each with its own format and structure, creating a fragmented data landscape that&apos;s difficult to unify.</p><h3 class="slate-h3 " >🧩  Challenge 2: Time-consuming manual data transformation</h3><p class="slate-p " >You spend countless hours cleaning, transforming, and normalizing data from different sources, taking valuable time away from your core engineering tasks.</p><h3 class="slate-h3 " >🧩  Challenge 3: Limited tools for data standardization</h3><p class="slate-p " >Without specialized tools, maintaining consistent data definitions across your systems requires extensive custom coding and complex technical workflows.</p><h2 class="slate-h2 " >Why Strands + JSON Schema is a game-changer for automating equipment data pipelines</h2><p class="slate-p " >JSON Schema is a powerful way to standardize, validate, and govern data structures across your organization. Learn more about what JSON Schema is and why it&apos;s important to ensure data consistency in our Introduction to JSON Schema. Strands is a comprehensive JSON Schema management platform designed specifically to address the unique challenges you face as a systems engineer. Our solution empowers you to standardize data collection across your equipment while reducing manual transformation efforts.</p><h3 class="slate-h3 " >💡  Solution 1: Centralized schema repository - single source of truth</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">What it does: Provides a centralized hub to store, manage, and distribute all your JSON schemas across your organization.</div></li><li class="slate-li " ><div style="position:relative">What this means for you: No more scattered data definitions across your various systems or teams. With Strands, you maintain a consistent data structure across all equipment, dramatically reducing fragmentation and improving data reliability.</div></li></ul><h3 class="slate-h3 " >💡  Solution 2: Schema versioning and distribution - controlled evolution</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">What it does: Implements semantic versioning for your schemas and distributes them via a global CDN, ensuring consistent access across all environments.</div></li><li class="slate-li " ><div style="position:relative">What this means for you: As your equipment configurations change or new data requirements emerge, you can evolve your schemas in a controlled manner without breaking existing integrations. Your teams always access the correct schema version, eliminating inconsistencies and errors.</div></li></ul><h3 class="slate-h3 " >💡<strong class="slate-bold">  Solution 3: No-code schema editor - simplified schema creation (Coming soon)</strong></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">What it does: Provides an intuitive visual interface for creating and modifying JSON schemas without coding expertise.</div></li><li class="slate-li " ><div style="position:relative">What this means for you: You can design and implement standardized data structures across your equipment without extensive technical knowledge, democratizing schema creation and allowing you to focus on engineering rather than data formatting.</div></li></ul><h2 class="slate-h2 " >The Strands difference</h2><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Increased efficiency:</strong> Strands reduces the time you spend on data transformation allowing you to focus on analysis and optimization rather than data cleaning.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Ease of use:</strong> Our platform is designed for users with varying technical expertise, making schema management accessible to your entire team without requiring specialized JSON knowledge.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Scalability and flexibility:</strong> As your equipment inventory grows, Strands scales with you, handling everything from a few schemas to thousands while maintaining performance and accessibility.</div></li></ul><h2 class="slate-h2 " >Get started with Strands</h2><p class="slate-p " >Automate your equipment data pipelines in minutes, not months. <a href="https://strands.octue.com/account/signup" target="_self">Sign-up for Strands</a> and <a href="67a364563abce46030e148c8/67a3645ca91c8ffa44ab795e" target="_blank">create your first schema</a> within minutes.</p><p class="slate-p " >Watch your manual data transformation hours disappear as your equipment data is automated through consistent pipelines.</p><h2 class="slate-h2 " >What you can expect</h2><p class="slate-p " >After implementing Strands, you will experience:</p><p class="slate-p " >⏱️ Reduction in time spent on manual data cleaning and transformation within the first month.</p><p class="slate-p " >💯 Improved data reliability with standardized validation across all your equipment within weeks.</p><p class="slate-p " >🔄 Simplified collaboration between your teams working with the same standardized data definitions.</p><h2 class="slate-h2 " >Ready to automate your equipment data pipelines with Strands?</h2><p class="slate-p " ><a href="https://uk.linkedin.com/company/octue" target="">Contact us</a> directly to schedule a personalized demonstration.</p><p class="slate-p " ><a href="https://strands.octue.com/account/signup" target="">Start automating today!</a></p><p class="slate-p " ></p>

Automating equipment data pipelines: Enhancing operational efficiency with Strands

Streamlining API development: Centralized schema management with Strands

Troubleshooting and FAQs

 Fix schema reference validation in Strands

FAQs

Product updates

Release notes

Product roadmap

Support and feedback

Getting Started

Production

<p class="slate-p slate-indent-0" style="0px">Learn everything you need to know about managing and sharing JSON Schemas with Strands, your complete schema repository solution.</p><p class="slate-p slate-indent-0" style="0px">Strands is your centralized JSON Schema management tool that empowers teams to easily create, publish, and share schemas. With built-in semantic versioning (SemVer) for tracking changes, global CDN distribution for speed, and robust collaboration features, Strands accelerates your development workflow. Maintain consistent data quality across applications through our modern schema registry and editor.</p><p class="slate-p slate-indent-0-1-1" style="NaNpx"></p><div style="text-align:center"><img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/168c7578-050f-4e6d-ab54-f12f259c3d10.png" style="
              width:549px;
	            height:549px;
	            aspect-ratio:549 / 549"
         /></div><p class="slate-p slate-indent-0-1-1" style="NaNpx"></p><h2 class="slate-h2 " >Create an account</h2><p class="slate-p slate-indent-0" style="0px">Create a Strands account using your email to start building JSON schemas. Choose between a free account or a monthly subscription. As a non-profit venture, all funds support the JSON Schema community and the broader open-source ecosystem.</p><a href="https://strands.octue.com/account/signup" target="_blank" class=card-anchor><div class="card-box" style="width:60%;"><svg width="24" height="24" viewBox="0 0 24 24" fill="none" class="icon-style" xmlns="http://www.w3.org/2000/svg"> <g clipPath="url(#clip0_2631_4537)"> <path d="M22.3188 4.43107L8.49985 18.2491C8.40694 18.3423 8.29652 18.4164 8.17494 18.4669C8.05336 18.5174 7.923 18.5434 7.79135 18.5434C7.65969 18.5434 7.52933 18.5174 7.40775 18.4669C7.28617 18.4164 7.17576 18.3423 7.08285 18.2491L1.73885 12.9001C1.64594 12.8068 1.53552 12.7328 1.41394 12.6823C1.29236 12.6318 1.162 12.6058 1.03035 12.6058C0.898693 12.6058 0.768335 12.6318 0.646752 12.6823C0.52517 12.7328 0.414756 12.8068 0.321847 12.9001C0.22857 12.993 0.154557 13.1034 0.104056 13.225C0.053554 13.3466 0.0275574 13.4769 0.0275574 13.6086C0.0275574 13.7402 0.053554 13.8706 0.104056 13.9922C0.154557 14.1137 0.22857 14.2242 0.321847 14.3171L5.66785 19.6621C6.23179 20.225 6.99604 20.5411 7.79285 20.5411C8.58965 20.5411 9.3539 20.225 9.91785 19.6621L23.7358 5.84707C23.829 5.75418 23.9029 5.64383 23.9533 5.52234C24.0037 5.40085 24.0296 5.2706 24.0296 5.13907C24.0296 5.00753 24.0037 4.87729 23.9533 4.7558C23.9029 4.63431 23.829 4.52396 23.7358 4.43107C23.6429 4.33779 23.5325 4.26378 23.4109 4.21328C23.2894 4.16278 23.159 4.13678 23.0273 4.13678C22.8957 4.13678 22.7653 4.16278 22.6438 4.21328C22.5222 4.26378 22.4118 4.33779 22.3188 4.43107Z" fill="#374957"/> </g> <defs> <clipPath id="clip0_2631_4537"> <rect width="24" height="24" fill="white"/> </clipPath> </defs> </svg><div ><p class="slate-p slate-indent-0" style="0px">Sign-up to Strands</p><p class="slate-p slate-indent-0" style="0px">Create an account with your email</p></div></div></a><p class="slate-p " ></p><h2 class="slate-h2 " >Getting started</h2><p class="slate-p slate-indent-0" style="0px">If you&apos;re new to Strands, start here to learn the essentials of using JSON Schema and create your first Strand in our online editor. </p><p class="slate-p slate-indent-0" style="0px"></p><div class=card-group-box style="width:100%; min-width:540px;"><a href="https://app.theneo.io/octue/strands-documentation/getting-started/get-started-with-strands" target="_blank" class="card-box-anchor"><svg width="24" height="24" viewBox="0 0 24 24" fill="none" class="icon-style" xmlns="http://www.w3.org/2000/svg"> <g clipPath="url(#clip0_2631_5353)"> <path d="M18 6.99959C18 7.19737 17.9414 7.39071 17.8315 7.55516C17.7216 7.71961 17.5654 7.84778 17.3827 7.92347C17.2 7.99916 16.9989 8.01896 16.8049 7.98038C16.6109 7.94179 16.4327 7.84655 16.2929 7.7067C16.153 7.56685 16.0578 7.38866 16.0192 7.19468C15.9806 7.0007 16.0004 6.79963 16.0761 6.61691C16.1518 6.43418 16.28 6.278 16.4444 6.16812C16.6089 6.05824 16.8022 5.99959 17 5.99959C17.2652 5.99959 17.5196 6.10495 17.7071 6.29249C17.8946 6.48002 18 6.73438 18 6.99959ZM14 8.99959C13.8022 8.99959 13.6089 9.05824 13.4444 9.16812C13.28 9.278 13.1518 9.43418 13.0761 9.61691C13.0004 9.79963 12.9806 10.0007 13.0192 10.1947C13.0578 10.3887 13.153 10.5668 13.2929 10.7067C13.4327 10.8466 13.6109 10.9418 13.8049 10.9804C13.9989 11.019 14.2 10.9992 14.3827 10.9235C14.5654 10.8478 14.7216 10.7196 14.8315 10.5552C14.9414 10.3907 15 10.1974 15 9.99959C15 9.73438 14.8946 9.48002 14.7071 9.29249C14.5196 9.10495 14.2652 8.99959 14 8.99959ZM11 11.9996C10.8022 11.9996 10.6089 12.0582 10.4444 12.1681C10.28 12.278 10.1518 12.4342 10.0761 12.6169C10.0004 12.7996 9.98063 13.0007 10.0192 13.1947C10.0578 13.3887 10.153 13.5668 10.2929 13.7067C10.4327 13.8466 10.6109 13.9418 10.8049 13.9804C10.9989 14.019 11.2 13.9992 11.3827 13.9235C11.5654 13.8478 11.7216 13.7196 11.8315 13.5552C11.9414 13.3907 12 13.1974 12 12.9996C12 12.7344 11.8946 12.48 11.7071 12.2925C11.5196 12.1049 11.2652 11.9996 11 11.9996ZM23.866 2.95759L23.791 3.16859C22.289 7.33659 20.848 11.2996 18 14.8196V14.9996C17.9982 16.5313 17.6772 18.0458 17.0574 19.4465C16.4375 20.8472 15.5325 22.1033 14.4 23.1346C13.8005 23.6877 13.0157 23.9963 12.2 23.9996C11.3511 23.9969 10.5378 23.6581 9.93806 23.0573C9.33834 22.4565 9.00105 21.6425 9 20.7936V19.6426C8.26209 19.4046 7.59039 18.9967 7.039 18.4516L7 18.4136L4.707 20.7066C4.5184 20.8888 4.2658 20.9895 4.0036 20.9873C3.7414 20.985 3.49059 20.8798 3.30518 20.6944C3.11977 20.509 3.0146 20.2582 3.01233 19.996C3.01005 19.7338 3.11084 19.4812 3.293 19.2926L5.586 16.9996L5.547 16.9616C5.00157 16.4096 4.59269 15.7377 4.353 14.9996H3.363C2.47149 14.9988 1.61671 14.6444 0.98623 14.0141C0.355746 13.3838 0.00105907 12.5291 0 11.6376C0.00176888 10.7669 0.337503 9.93007 0.938 9.29959C1.9835 8.22585 3.23879 7.37876 4.62576 6.81104C6.01272 6.24332 7.50169 5.9671 9 5.99959H9.18C12.7 3.15259 16.66 1.71159 20.826 0.210592L21.042 0.133592C21.4362 -0.011327 21.8636 -0.0403829 22.2738 0.0498572C22.684 0.140097 23.0598 0.345862 23.3568 0.64284C23.6537 0.939817 23.8595 1.3156 23.9497 1.72578C24.04 2.13596 24.0109 2.5634 23.866 2.95759ZM3.363 12.9996H4.1C4.17512 12.1185 4.48258 11.2731 4.991 10.5496C5.54904 9.7467 6.15305 8.97675 6.8 8.24359C5.12253 8.59081 3.58896 9.43636 2.4 10.6696C2.14706 10.9288 2.00379 11.2755 2 11.6376C2.00053 11.9988 2.14433 12.3451 2.39986 12.6004C2.65539 12.8558 3.00176 12.9993 3.363 12.9996ZM15.7 17.2516C14.9827 17.8795 14.2309 18.4667 13.448 19.0106C12.7239 19.5141 11.8791 19.8164 11 19.8866V20.7936C11.0005 21.1135 11.1279 21.42 11.3542 21.6461C11.5804 21.8722 11.8871 21.9993 12.207 21.9996C12.5241 21.9949 12.828 21.8719 13.059 21.6546C14.3482 20.4745 15.2659 18.9446 15.7 17.2516ZM21.937 2.06259C21.9104 2.03295 21.8751 2.01239 21.8362 2.00378C21.7973 1.99517 21.7567 1.99895 21.72 2.01459L21.505 2.09259C16.661 3.83759 12.478 5.34559 8.876 8.94659C8.04974 9.79866 7.29768 10.7197 6.628 11.6996C6.22066 12.2778 6.03069 12.9813 6.09162 13.6859C6.15255 14.3905 6.46046 15.0509 6.961 15.5506L8.453 17.0406C8.95242 17.5408 9.6124 17.8485 10.3166 17.9097C11.0208 17.9708 11.7239 17.7813 12.302 17.3746C13.2814 16.705 14.2017 15.9529 15.053 15.1266C18.653 11.5266 20.163 7.33959 21.909 2.49359L21.985 2.28259C22.0012 2.24554 22.0053 2.20432 21.9966 2.16482C21.988 2.12531 21.9671 2.08954 21.937 2.06259Z" fill="#374957"/> </g> <defs> <clipPath id="clip0_2631_5353"> <rect width="24" height="24" fill="white"/> </clipPath> </defs> </svg><div ><p class="slate-p slate-indent-0" style="0px">Get started with Strands</p><p class="slate-p slate-indent-0" style="0px">Create your first strand</p></div></a><a href="https://app.theneo.io/octue/strands-documentation/fundamentals" target="_blank" class="card-box-anchor"><svg width="24" height="24" viewBox="0 0 24 24" fill="none" class="icon-style" xmlns="http://www.w3.org/2000/svg"> <g clipPath="url(#clip0_2631_4457)"> <path d="M20.1371 24C19.7672 23.999 19.4011 23.9247 19.0601 23.7813C18.719 23.638 18.4097 23.4285 18.1501 23.165L12.0001 17.051L5.85012 23.169C5.45515 23.5697 4.94861 23.8422 4.39654 23.9508C3.84447 24.0594 3.27247 23.9992 2.75512 23.778C2.23264 23.5678 1.78567 23.205 1.47258 22.7369C1.15949 22.2688 0.994841 21.7171 1.00012 21.154V5C1.00012 3.67392 1.52691 2.40215 2.46459 1.46447C3.40227 0.526784 4.67404 0 6.00012 0L18.0001 0C18.6567 0 19.3069 0.129329 19.9135 0.380602C20.5202 0.631876 21.0714 1.00017 21.5357 1.46447C22 1.92876 22.3683 2.47996 22.6195 3.08658C22.8708 3.69321 23.0001 4.34339 23.0001 5V21.154C23.0057 21.7167 22.8417 22.268 22.5293 22.7361C22.217 23.2041 21.7709 23.5672 21.2491 23.778C20.8969 23.9253 20.5189 24.0008 20.1371 24ZM6.00012 2C5.20447 2 4.44141 2.31607 3.8788 2.87868C3.31619 3.44129 3.00012 4.20435 3.00012 5V21.154C2.99976 21.3206 3.04879 21.4836 3.14102 21.6224C3.23325 21.7612 3.36455 21.8695 3.51831 21.9337C3.67208 21.9979 3.84143 22.0151 4.00496 21.9831C4.1685 21.9512 4.31888 21.8714 4.43712 21.754L11.3001 14.933C11.4875 14.7468 11.7409 14.6422 12.0051 14.6422C12.2693 14.6422 12.5228 14.7468 12.7101 14.933L19.5651 21.752C19.6834 21.8694 19.8338 21.9492 19.9973 21.9811C20.1608 22.0131 20.3302 21.9959 20.4839 21.9317C20.6377 21.8675 20.769 21.7592 20.8612 21.6204C20.9535 21.4816 21.0025 21.3186 21.0021 21.152V5C21.0021 4.20435 20.6861 3.44129 20.1234 2.87868C19.5608 2.31607 18.7978 2 18.0021 2H6.00012Z" fill="#374957" /> </g> <defs> <clipPath id="clip0_2631_4457"> <rect width="24" height="24" fill="white" /> </clipPath> </defs> </svg><div ><p class="slate-p slate-indent-0" style="0px">JSON Schema fundamentals</p><p class="slate-p slate-indent-0" style="0px">Learn the fundamentals of JSON Schema and master best practices to create schemas</p></div></a></div><p class="slate-p " ></p><h2 class="slate-h2 " >Need help? </h2><p class="slate-p slate-indent-0" style="0px">Browse our GitHub discussions to find solutions, share feedback, and ask questions. Our community and team are here to help you build the future of data together. </p><a href="https://github.com/orgs/octue/discussions" target="_blank" class=card-anchor><div class="card-box" style="width:60%;"><svg width="24" height="24" viewBox="0 0 24 24" fill="none" class="icon-style" xmlns="http://www.w3.org/2000/svg"> <g clipPath="url(#clip0_2631_5322)"> <path d="M0 22.9993V15.9993C0.00264685 13.6132 0.951708 11.3255 2.63896 9.63829C4.32622 7.95103 6.61386 7.00197 9 6.99933H13.83V5.41333C13.8301 5.01783 13.9474 4.63123 14.1672 4.30241C14.387 3.97359 14.6993 3.71731 15.0647 3.56597C15.4301 3.41464 15.8322 3.37503 16.2201 3.45216C16.608 3.5293 16.9643 3.71971 17.244 3.99933L23.124 9.87832C23.6864 10.4409 24.0024 11.2038 24.0024 11.9993C24.0024 12.7948 23.6864 13.5577 23.124 14.1203L17.244 19.9993C16.9643 20.2789 16.608 20.4693 16.2201 20.5465C15.8322 20.6236 15.4301 20.584 15.0647 20.4327C14.6993 20.2813 14.387 20.025 14.1672 19.6962C13.9474 19.3674 13.8301 18.9808 13.83 18.5853V16.9993H8C6.40919 17.0009 4.88399 17.6336 3.75911 18.7584C2.63424 19.8833 2.00159 21.4085 2 22.9993C2 23.2645 1.89464 23.5189 1.70711 23.7064C1.51957 23.8939 1.26522 23.9993 1 23.9993C0.734784 23.9993 0.48043 23.8939 0.292893 23.7064C0.105357 23.5189 0 23.2645 0 22.9993ZM15.83 7.99932C15.83 8.26454 15.7246 8.51889 15.5371 8.70643C15.3496 8.89397 15.0952 8.99932 14.83 8.99932H9C7.14414 9.00144 5.36489 9.73962 4.05259 11.0519C2.7403 12.3642 2.00212 14.1435 2 15.9993V17.7133C2.74957 16.8603 3.67249 16.1769 4.70715 15.7089C5.74182 15.2409 6.86441 14.999 8 14.9993H14.83C15.0952 14.9993 15.3496 15.1047 15.5371 15.2922C15.7246 15.4797 15.83 15.7341 15.83 15.9993V18.5853L21.709 12.7063C21.8965 12.5188 22.0018 12.2645 22.0018 11.9993C22.0018 11.7342 21.8965 11.4798 21.709 11.2923L15.83 5.41333V7.99932Z" fill="#374957"/> </g> <defs> <clipPath id="clip0_2631_5322"> <rect width="24" height="24" fill="white"/> </clipPath> </defs> </svg><div ><h3 class="slate-h3 " >GitHub discussions</h3><p class="slate-p " >Ask questions, share feedback, and find solutions</p></div></div></a><p class="slate-p " ></p>

Learn everything you need to know about managing and sharing JSON Schemas with Strands, your complete schema repository solution.

Strands is your centralized JSON Schema management tool that empowers teams to easily create, publish, and share schemas. With built-in semantic versioning (SemVer) for tracking changes, global CDN distribution for speed, and robust collaboration features, Strands accelerates your development workflow. Maintain consistent data quality across applications through our modern schema registry and editor.

Create a Strands account using your email to start building JSON schemas. Choose between a free account or a monthly subscription. As a non-profit venture, all funds support the JSON Schema community and the broader open-source ecosystem.

If you're new to Strands, start here to learn the essentials of using JSON Schema and create your first Strand in our online editor. 

Browse our GitHub discussions to find solutions, share feedback, and ask questions. Our community and team are here to help you build the future of data together. 

<p class="slate-p " >Strands is an online application designed to simplify the creation, publishing, and management of JSON Schemas. It provides a centralized schema management platform that enables developers, data engineers, and technical teams to maintain control and consistency across their data structures.</p><p class="slate-p " >This <em class="slate-italic">Getting started</em> section introduces you to Strands and helps you begin your journey with the platform. Here, you&apos;ll find:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">A detailed <a href="67a3645ca91c8ffa44ab795e" target="_blank"><strong class="slate-bold">Get started guide</strong></a><strong class="slate-bold"> </strong> that walks you through initial setup and basic operations</div></li><li class="slate-li " ><div style="position:relative">A comprehensive <a href="67a364563abce46030e148c8/67a4c6eb13fef684c6573d02" target="_blank"><strong class="slate-bold">Glossary</strong></a> that clarifies the technical vocabulary used throughout the documentation</div></li></ul><p class="slate-p " >The following sections will guide you through Strands&apos; core concepts and help you quickly become productive with the platform.</p>

Strands is an online application designed to simplify the creation, publishing, and management of JSON Schemas. It provides a centralized schema management platform that enables developers, data engineers, and technical teams to maintain control and consistency across their data structures.

 section introduces you to Strands and helps you begin your journey with the platform. Here, you'll find:

The following sections will guide you through Strands' core concepts and help you quickly become productive with the platform.

<p class="slate-p " ><h2 class="slate-h2 " >Prerequisites</h2><p class="slate-p " >Before you begin, make sure you have:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">A modern web browser.</div></li><li class="slate-li " ><div style="position:relative">Basic understanding of JSON Schema.</div></li><li class="slate-li " ><div style="position:relative">Understanding of data validation concepts.</div></li><li class="slate-li " ><div style="position:relative">A <a href="https://strands.octue.com/account/signup" target="">Strands account</a>. </div></li><li class="slate-li " ><div style="position:relative">A well-defined schema structure. </div></li><li class="slate-li " ><div style="position:relative">Version number for your schema (using <a href="major.minor.patch" target="_self"><code class="slate-code">major.minor.patch</code></a> format)</div></li><li class="slate-li " ><div style="position:relative">Your user handle (which is displayed next to your username). </div></li></ul><p class="slate-p " ></p><h2 class="slate-h2 " >Create a strand</h2><p class="slate-p " >Creating a strand is a straightforward process:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">Click your profile icon and select Add new strand from the menu.</div></li><li class="slate-li " ><div style="position:relative">Name your strand removing any trailing spaces to avoid errors.</div></li><li class="slate-li " ><div style="position:relative"><em class="slate-italic">Optional:</em> Add labels to your strand.</div></li><li class="slate-li " ><div style="position:relative"><em class="slate-italic">Optional:</em> Write a short description and a Readme.</div></li><li class="slate-li " ><div style="position:relative">Click Create Strand to save your new Strand.</div></li></ol></p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=success ><div class="callout-icon"><svg width="18" height="18" viewBox="0 0 18 18" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M7.77116 10.8968L5.72949 8.8551C5.60449 8.7301 5.45171 8.6676 5.27116 8.6676C5.0906 8.6676 4.93088 8.73705 4.79199 8.87594C4.6531 9.01482 4.58366 9.17455 4.58366 9.3551C4.58366 9.53566 4.6531 9.68844 4.79199 9.81344L7.33366 12.3551C7.45866 12.4801 7.60449 12.5426 7.77116 12.5426C7.93783 12.5426 8.08366 12.4801 8.20866 12.3551L13.2087 7.3551C13.3337 7.2301 13.3927 7.07732 13.3857 6.89677C13.3788 6.71621 13.3128 6.56344 13.1878 6.43844C13.0628 6.29955 12.9066 6.2301 12.7191 6.2301C12.5316 6.2301 12.3684 6.29955 12.2295 6.43844L7.77116 10.8968ZM9.00033 17.3343C7.81977 17.3343 6.72255 17.1225 5.70866 16.6989C4.69477 16.2752 3.81283 15.6884 3.06283 14.9384C2.31283 14.1884 1.72602 13.3065 1.30241 12.2926C0.878798 11.2787 0.666992 10.1815 0.666992 9.00094C0.666992 7.83427 0.878798 6.74399 1.30241 5.7301C1.72602 4.71621 2.31283 3.83427 3.06283 3.08427C3.81283 2.33427 4.69477 1.74399 5.70866 1.31344C6.72255 0.88288 7.81977 0.667603 9.00033 0.667603C10.167 0.667603 11.2573 0.88288 12.2712 1.31344C13.285 1.74399 14.167 2.33427 14.917 3.08427C15.667 3.83427 16.2573 4.71621 16.6878 5.7301C17.1184 6.74399 17.3337 7.83427 17.3337 9.00094C17.3337 10.1815 17.1184 11.2787 16.6878 12.2926C16.2573 13.3065 15.667 14.1884 14.917 14.9384C14.167 15.6884 13.285 16.2752 12.2712 16.6989C11.2573 17.1225 10.167 17.3343 9.00033 17.3343ZM9.00033 16.0843C11.0142 16.0843 12.6982 15.4072 14.0524 14.053C15.4066 12.6989 16.0837 11.0148 16.0837 9.00094C16.0837 6.98705 15.4066 5.30302 14.0524 3.94885C12.6982 2.59469 11.0142 1.9176 9.00033 1.9176C6.98644 1.9176 5.30241 2.59469 3.94824 3.94885C2.59408 5.30302 1.91699 6.98705 1.91699 9.00094C1.91699 11.0148 2.59408 12.6989 3.94824 14.053C5.30241 15.4072 6.98644 16.0843 9.00033 16.0843Z" fill="#06837A"></path></svg></div><div ><p class="slate-p " ><strong class="slate-bold">Tip:</strong> The README of a JSON Schema helps users understand the broader context of a JSON schema. Use this file to document information that the technical schema definition alone doesn&apos;t convey, such as the schema&apos;s purpose, constraints, license, and sponsors.</p></div></div><div style="text-align:center"><img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/9dd243aa-5fbe-472a-abd7-9e87d8ee789c.png" style="
              width:586px;
	            height:593px;
	            aspect-ratio:586 / 593"
         /></div><h3 class="slate-h3 " >Add a schema</h3><p class="slate-p " >Next, you&apos;ll need to enter a complete and valid JSON Schema.</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">Select Add a version.</div></li><li class="slate-li " ><div style="position:relative">Enter a complete and valid JSON Schema. You can:</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Manually write your schema in the text editor.</div></li><li class="slate-li " ><div style="position:relative">Choose a template from our predefined examples.</div></li></ul></li><li class="slate-li " ><div style="position:relative">Click Set the version to store your changes.</div></li></ol><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " ><strong class="slate-bold">Note</strong>: If your schema references other schemas, make sure they are already published on Strands or accessible via a URL.</p></div></div><div style="text-align:center"><img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/cc91409f-71a8-496d-bb29-524d16a0d7c9.png" style="
              width:662px;
	            height:436px;
	            aspect-ratio:662 / 436"
         /></div><p class="slate-p " ></p><h3 class="slate-h3 " >Add a version to your Strand</h3><p class="slate-p " >Strands utilizes Semantic Versioning (SemVer) to manage schema changes:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Major:</strong> Incompatible changes. These changes will likely break existing integrations and require updates.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Minor:</strong> Backward-compatible feature additions. It refers to new features that are added without affecting existing functionality.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Patch:</strong> Backward-compatible bug fixes. Bug fixes are implemented without introducing new features or breaking existing functionality.</div></li></ul><p class="slate-p " >To version your Strand:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">Assign a version number using the <code class="slate-code">major.minor.patch</code> format (e.g., <code class="slate-code">1.0.0</code>).</div></li><li class="slate-li " ><div style="position:relative">To finalize and publish your Strand, click <strong class="slate-bold">Save version</strong>.</div></li></ol><p class="slate-p " >🎉 Success! Your Strand is now live on the CDN.</p><p class="slate-p " ></p><div style="text-align:center"><img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/da44814a-cc4a-4944-bac4-0042f1d493df.png" style="
              width:688px;
	            height:407px;
	            aspect-ratio:688 / 407"
         /></div><p class="slate-p " ></p><h2 class="slate-h2 " >What&apos;s next?</h2><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Your schema is now accessible at the URL shown on the screen—use this URL to reference it in other schemas.</div></li><li class="slate-li " ><div style="position:relative">You can now share your schema, integrate it into your applications, or create new versions as your data model evolves.</div></li></ul><p class="slate-p " ></p><h2 class="slate-h2 " >Want to learn more?</h2><p class="slate-p " >Dive into the following resources to continue growing your skills:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><a href="67cb13e987235bce886041b8/67a4c72d048eed046160ccf4" target="_blank">JSON Schema best practices</a></div></li><li class="slate-li " ><div style="position:relative"><a href="67a3647b7411545922f7990d/67cb0e36b68baa949d1faf2a" target="_blank">Key JSON Schema concepts</a></div></li><li class="slate-li " ><div style="position:relative">JSON Schema design patterns</div></li></ul><p class="slate-p " ></p>

Next, you'll need to enter a complete and valid JSON Schema.

Strands utilizes Semantic Versioning (SemVer) to manage schema changes:

🎉 Success! Your Strand is now live on the CDN.

Dive into the following resources to continue growing your skills:

<h4 class="slate-h4 " >Content Delivery Network (CDN)</h4><p class="slate-p " >A distributed network of servers that delivers content, such as JSON Schemas, to users based on their geographic location, ensuring low latency and high availability.</p><h4 class="slate-h4 " >Dialect</h4><p class="slate-p " >A specific variation of the JSON Schema language, defined by a unique identifier, which allows extensions and modifications to the standard specification.</p><h4 class="slate-h4 " >Draft</h4><p class="slate-p " >A version of the JSON Schema specification that is under development or review before being officially released.</p><h4 class="slate-h4 " >JSON (JavaScript Object Notation)</h4><p class="slate-p " >A lightweight data-interchange format that is easy for humans to read and write, and easy for machines to parse and generate.</p><h4 class="slate-h4 " >JSON Schema</h4><p class="slate-p " >A vocabulary that allows you to annotate and validate JSON documents. It is used to define the structure, format, and validation rules for JSON data.</p><h4 class="slate-h4 " >JSON Schema Specification</h4><p class="slate-p " >The official standard that defines the syntax, keywords, and behavior of JSON Schema for validation and structure description.</p><h4 class="slate-h4 " >Schema</h4><p class="slate-p " >A blueprint that describes the structure and validation rules for a set of data. In the context of JSON, it defines the required properties, data types, and relationships within a JSON document.</p><h4 class="slate-h4 " >SemVer (Semantic Versioning)</h4><p class="slate-p " >A versioning system that uses a three-part number (MAJOR.MINOR.PATCH) to indicate backwards-incompatible changes, new features, and bug fixes, respectively.</p><h4 class="slate-h4 " >Strand</h4><p class="slate-p " >A set of JSON schemas published and managed on the Strands platform, often versioned and distributed via a global CDN.</p><h4 class="slate-h4 " >Vocabulary</h4><p class="slate-p " >A collection of keywords in JSON Schema that are used to express specific validation constraints and structural rules.</p><p class="slate-p " ></p>

A distributed network of servers that delivers content, such as JSON Schemas, to users based on their geographic location, ensuring low latency and high availability.

A specific variation of the JSON Schema language, defined by a unique identifier, which allows extensions and modifications to the standard specification.

A version of the JSON Schema specification that is under development or review before being officially released.

A lightweight data-interchange format that is easy for humans to read and write, and easy for machines to parse and generate.

A vocabulary that allows you to annotate and validate JSON documents. It is used to define the structure, format, and validation rules for JSON data.

The official standard that defines the syntax, keywords, and behavior of JSON Schema for validation and structure description.

A blueprint that describes the structure and validation rules for a set of data. In the context of JSON, it defines the required properties, data types, and relationships within a JSON document.

A versioning system that uses a three-part number (MAJOR.MINOR.PATCH) to indicate backwards-incompatible changes, new features, and bug fixes, respectively.

A set of JSON schemas published and managed on the Strands platform, often versioned and distributed via a global CDN.

A collection of keywords in JSON Schema that are used to express specific validation constraints and structural rules.

<p class="slate-p " ><p class="slate-p " >JSON Schema is a powerful tool for validating, documenting, and controlling the structure of JSON data. <span style="background-color:rgb(8, 8, 8);color:rgba(255, 255, 255, 0.84)">Whether you&apos;re just starting with JSON Schema or looking to improve existing implementations, having a solid foundation of JSON Schema concepts </span>will help streamline data management and improve interoperability across different applications. By treating your schemas as first-class citizens in your development process, you&apos;ll create more robust, maintainable, and effective systems.</p><p class="slate-p " >This section provides a comprehensive foundation in JSON Schema concepts and practical guidance to help you implement JSON Schema effectively across your organization.</p></p><h3 class="slate-h3 " >What You&apos;ll Learn</h3><p class="slate-p " >In this section, you&apos;ll explore:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><a href="67a3647b7411545922f7990d/67a4c71d048eed046160ccda" target="_blank"><strong class="slate-bold">Introduction to JSON Schema</strong></a>: Understand the purpose, benefits, and common use cases for JSON Schema in modern data ecosystems.</div></li><li class="slate-li " ><div style="position:relative"><a href="67a3647b7411545922f7990d/67cb0e36b68baa949d1faf2a" target="_blank"><strong class="slate-bold">Key JSON Schema concepts</strong></a>: Learn about the building blocks that drive effective schema design and implementation.</div></li><li class="slate-li " ><div style="position:relative"><a href="67a3647b7411545922f7990d/67cb1987b68baa949d2038d9" target="_blank"><strong class="slate-bold">Anatomy of a JSON Schema</strong></a>: Examine the structural components that make up a schema and how they work together. </div></li><li class="slate-li " ><div style="position:relative"><a href="67cb13e987235bce886041b8/67a4c72d048eed046160ccf4" target="_blank"><strong class="slate-bold">JSON Schema best practices</strong></a>: Master the essential practices for creating effective schemas that balance validation rigor with practical implementation requirements.</div></li></ul><p class="slate-p " >Armed with these fundamentals, you&apos;ll be positioned to fully leverage Strands as your centralized schema repository. Strands doesn&apos;t just store your JSON Schemas—it transforms them into living, collaborative assets that drive consistency and take your organization&apos;s schema management to new heights of efficiency and reliability.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Armed with these fundamentals, you'll be positioned to fully leverage Strands as your centralized schema repository. Strands doesn't just store your JSON Schemas—it transforms them into living, collaborative assets that drive consistency and take your organization's schema management to new heights of efficiency and reliability.

<p class="slate-p " ><p class="slate-p " >Welcome to the <em class="slate-italic">Use Cases</em> section of the Strands documentation. This collection of resources highlights practical examples of how Strands&apos; powerful schema management platform can solve real-world challenges across various industries. Each use case demonstrates how Strands enables organizations to streamline workflows, improve data consistency, and ensure data governance, all while enhancing efficiency and collaboration.</p><p class="slate-p " >Explore how Strands is used to:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Enhance research efficiency</strong> by <a href="67a4c953048eed046163274f/67dec2da808534b1f337fa17" target="_blank">standardizing scientific data management and ensuring reproducibility</a>. </div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Future-proof enterprise data</strong> by <a href="67a4c953048eed046163274f/67dd1c6f2b9b64f6500ad0b0" target="_blank">mitigating data governance risks and simplifying compliance</a>. </div></li><li class="slate-li " ><div style="position:relative"><a href="67a4c953048eed046163274f/67dd1cf1923a00b3bef4ebd2" target="_blank"><strong class="slate-bold">Automate equipment data pipelines</strong></a> to boost operational efficiency in complex environments. </div></li><li class="slate-li " ><div style="position:relative"><a href="67a4c953048eed046163274f/67cc75d1b68baa949d293dd6" target="_blank"><strong class="slate-bold">Streamline API development</strong></a> with centralized schema management to improve collaboration and reduce errors. </div></li></ul><p class="slate-p " >These case studies provide actionable insights into how adopting Strands can transform your organization&apos;s data management practices, making it easier to handle data at scale, improve accuracy, and drive innovation.</p></p><p class="slate-p " ></p>

<p class="slate-p " ><p class="slate-p " >In this section, you will find targeted solutions and insights to help you navigate common challenges in schema management and reference validation.</p><p class="slate-p " >Explore how these resources help you:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Fix schema reference validation</strong>: Resolve SSL certificate and external schema referencing issues when using the <code class="slate-code">jsonschema</code> Python library</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Understand Strands platform details</strong>: Get answers to frequently asked questions about schema management, platform capabilities, and integration strategies</div></li></ul><p class="slate-p " ></p><p class="slate-p " >These resources provide you with critical support to maximize the reliability and efficiency of your schema management workflows, ensuring smooth integration and minimizing potential technical obstacles.</p></p><p class="slate-p " ></p>

<p class="slate-p " ><p class="slate-p " >In this section, you will find the latest information about Strands&apos; evolution. These resources provide transparency into our platform&apos;s development and help you understand upcoming features and improvements.</p></p><p class="slate-p " >Explore how these resources help you:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Stay informed</strong>: Get detailed insights into recent product releases and feature enhancements</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Plan your workflow</strong>: Understand our strategic direction and upcoming capabilities</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Anticipate improvements</strong>: Preview features that will streamline your schema management processes</div></li></ul><p class="slate-p " >These resources will keep you updated on Strands&apos; development, ensuring you can make informed decisions about integrating and leveraging our platform in your data workflows.</p><h2 class="slate-h2 " >Contents</h2><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><a href="67a4ca17048eed0461635d00" target="_blank">Release Notes</a></div></li><li class="slate-li " ><div style="position:relative"><a href="67a4c9dc4355f3031bc688d6/67a4ca204355f3031bc689ae" target="_blank">Product Roadmap</a></div></li></ul><h2 class="slate-h2 " >What to expect</h2><p class="slate-p " >Our product updates provide a clear view of Strands&apos; ongoing commitment to simplifying JSON Schema management. By maintaining transparency about our development process, we aim to build a platform that continuously meets the evolving needs of technical teams managing complex data structures. <a href="https://github.com/orgs/octue/discussions/17" target="_blank">Participate in the discussion</a> and help shape the future of Strands! </p><p class="slate-p " ></p>

These resources will keep you updated on Strands' development, ensuring you can make informed decisions about integrating and leveraging our platform in your data workflows.

Our product updates provide a clear view of Strands' ongoing commitment to simplifying JSON Schema management. By maintaining transparency about our development process, we aim to build a platform that continuously meets the evolving needs of technical teams managing complex data structures. 

<h2 class="slate-h2 " >Open-source collaboration</h2><p class="slate-p " >As an open-source project, Strands thrives on community contributions. We welcome developers of all skill levels to join our mission:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Source code</strong>: Check out our <a href="https://github.com/octue/strands" target="_blank">source code on GitHub</a> to explore the codebase, submit pull requests, and help improve Strands for everyone.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Issue tracker</strong>: Report bugs or request features through our <a href="https://github.com/octue/strands/issues" target="_blank">GitHub issue tracker</a>. Please check existing issues before creating a new one.</div></li></ul><h2 class="slate-h2 " >Community support</h2><p class="slate-p " >Our community and team are committed to helping you build the future of data together. No matter where you are in your journey with Strands, we&apos;re here to support your success.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">GitHub discussions</strong>: Browse our <a href="https://github.com/orgs/octue/discussions" target="_blank">GitHub Discussions</a> to find solutions, share feedback, and ask questions. This is often the fastest way to get community-sourced answers.</div></li></ul><p class="slate-p " ></p>

As an open-source project, Strands thrives on community contributions. We welcome developers of all skill levels to join our mission:

Our community and team are committed to helping you build the future of data together. No matter where you are in your journey with Strands, we're here to support your success.

Sections