Skip to content
Novus Examples
xml6 KB

Fieldnote Supply Shop: Inventory and price feed XML

Inventory and price feed XML for Fieldnote Supply Shop. The same 12 variants as inventory-feed.csv. Because the gtin values are element text rather than spreadsheet cells, the leading zeros survive here, which makes this file the reference against which the CSV round trip is checked.

xml

application/xml

6 KB
Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Rows
12

Binary xml: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Rows
12
Root Element
ProductFeed
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Parse the feed and verify every Gtin check digit.
Expected result
12 Item elements parse, every Gtin is 13 characters beginning with 0, and every modulo-10 check digit verifies.

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

“Fieldnote Supply Shop: Inventory and price feed XML” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 12 rows · 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("inventory-feed.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.