Interactive Entity Relationship Diagram for Stakeholder Feedback
Why GitHub? We use GitHub Discussions to collect structured feedback from stakeholders across the biomass supply chain. It's free, open, and designed for collaborative input on technical standards.
New to GitHub? No problem! Creating an account takes just 2 minutes:
Create Free GitHub Account →Prefer email? You can also send feedback to the BOOST working group at public-boost-01@w3.org
Entities represent the core data objects in biomass supply chains - things like Organizations, Certificates, Material Feedstock, and Transactions. Each entity captures specific information needed for chain of custody tracking.
Attributes are the data fields within each entity (like organization name, certificate expiry date, or biomass quantity). These define what information must be recorded and tracked.
Relationships show how entities connect to each other - for example, how a Certificate relates to an Organization, or how Material Feedstock flows through Transactions. These connections enable complete supply chain traceability.
Reading the Diagram: Entities are shown as rectangular boxes containing their names (like Organization, Certificate, MaterialFeedstock). Lines connect related entities to show how they interact - for example, an Organization "is issued" a Certificate, or a Supplier "provides" MaterialFeedstock. Text along the lines describes the nature of each relationship in the biomass supply chain.
Purpose: This diagram maps the complete data structure needed to track biomass from source to end use, supporting regulatory compliance, sustainability verification, and carbon accounting.
Our Goal: Collect real-world input from stakeholders to ensure the BOOST data standard meets practical biomass supply chain needs.
Explore the interactive diagram below to understand the complete BOOST data model. You can zoom in/out, pan around, and use the filtering controls to examine entity relationships in detail.
To provide feedback on a specific entity, click on the purple 💬 discussion icon in any entity header to jump directly to its GitHub discussion thread.
💡 What we're looking for: Field completeness, data types, real-world applicability, missing attributes, validation requirements, and integration challenges.
Navigation: Use your mouse wheel to zoom, click and drag to pan around the diagram. The purple 💬 icons in entity headers link directly to GitHub discussions for that entity.
Filtering: Use the colored filter buttons to focus on specific areas of the data model (Core Traceability, Organizational, Material & Supply, etc.).
Focus Mode: Click the 🎯 button in the controls to highlight only essential TraceableUnit relationships, reducing visual clutter.
Field Legend: PK = Primary Key (red), FK = Foreign Key (blue), ● = Required Field, ○ = Optional Field
Direct Links in ERD: Each entity in the interactive diagram above has a purple 💬 discussion icon in its header. Click these icons to go directly to the GitHub discussion for that specific entity.
Complete Coverage: All 33 entities in the BOOST data model have dedicated discussion threads where you can provide feedback on schemas, relationships, and real-world applicability.
💡 Pro Tip: Use the thematic filter buttons above the diagram to focus on specific areas, then click the discussion icons for targeted feedback.
Beyond Individual Entities: While the entity links above are for specific schema feedback, we also welcome input on the overall data model structure and organization.
Structural Questions: Are these the right entities in the right relationships? Should any entities be consolidated or split? Are there missing supply chain stages or processes?
Implementation Considerations: Will this structure work well for real-world deployments? How does it compare to existing industry data models?
Have Questions? Use our Q&A section for general questions about the BOOST data model, implementation guidance, or clarifications about entity relationships.
Examples: "How do I implement mass balance tracking?" or "What's the difference between Claim and VerificationStatement?" or "How does BOOST compare to other standards?"
Community Support: Get help from other stakeholders, implementers, and the BOOST working group.