Pine Assembly Workshop: Bill of materials XML
Bill of materials XML for Pine Assembly Workshop. The same structure as genuinely nested XML rather than a flat list with a level column, so a reader has to walk the tree and multiply quantities down the path to reach a leaf requirement. SCREW appears in two different branches with different quantities per parent, 8 under BASE and 4 under TOP.
xml
application/xml
- Document Set
- manufacturing
- Industry
- manufacturing
- Source Kit
- inventory-manufacturing
- Entity
- Pine Assembly Workshop
- Synthetic
- true
- As Of
- 2026-09-08
Binary xml: no in-browser preview. Download it above to open in a compatible application.
Specifications
- Document Set
- manufacturing
- Industry
- manufacturing
- Source Kit
- inventory-manufacturing
- Entity
- Pine Assembly Workshop
- Synthetic
- true
- As Of
- 2026-09-08
- Levels
- 2
- Multi Path Components
- 1
- Encoding
- UTF-8
- Leaf Per Unit LEG
- 4
- Leaf Per Unit PANEL
- 1
- Leaf Per Unit SCREW
- 12
Testing contract
Expected to pass- Scenario
- Walk the tree, multiply quantityPerParent down each path and total by component.
- Expected result
- The walk gives 4 LEG, 1 PANEL and 12 SCREW per finished unit. Reading only the first SCREW element gives 8, which is short by 4.
What is a .xml file?
XML (Extensible Markup Language) is a verbose, self-describing markup language using nested tags, attributes, and namespaces to represent structured, hierarchical data. It supports schemas, entities, and validation and underlies many document and data formats. It remains common in enterprise, publishing, and interchange contexts.
How to use this file
Use an example XML file to test parsers, namespace and schema validation, XPath queries, and protection against entity-expansion and external-entity attacks.
How to use this file for testing
“Pine Assembly Workshop: Bill of materials XML” is a deterministic Novus Examples fixture for Data import, Schema validation. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: UTF-8. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import xml.etree.ElementTree as ET
tree = ET.parse("bill-of-materials.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])Related files
- jsonAlder Table Bistro: Cost of goods sold documentCost of goods sold document for Alder Table Bistro. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1736.91, purchases 2834.82, closing 2996.92, cost of goods sold 1574.81 CAD.
- jsonAlder Table Bistro: Digital menuDigital menu for Alder Table Bistro. One document holding the whole front of house: 3 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.
- jsonldAlder Table Bistro: Menu as schema.org JSON-LDMenu as schema.org JSON-LD for Alder Table Bistro. A schema.org Menu document with 7 MenuSection nodes, 5 of them top level, and 27 MenuItem nodes carrying 27 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.
- jsonAlder Table Bistro: Numeric expected results JSONNumeric expected results JSON for Alder Table Bistro. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 1452.72 CAD.
- jsonAlder Table Bistro: Plate costing documentPlate costing document for Alder Table Bistro. A nested JSON document with 4 dishes and 12 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.
- jsonCedar Street Tacos: Cost of goods sold documentCost of goods sold document for Cedar Street Tacos. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1911.28, purchases 972.73, closing 324.44, cost of goods sold 2559.57 CAD.
Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.