This schema represents the foundational structure for data entries served over the API. At this stage, all attributes are defined within a single model for simplicity. However, we recognize that more structured representations—such as dedicated models for activities, locations, products, and measurements—would improve clarity, reusability, and validation. These improvements are planned for Version 1, which will introduce a more modular and extensible schema while maintaining backward compatibility where possible.
For now, this prototype serves as a working implementation that supports early integrations. Developers should expect refinements in future releases. Feedback is welcome as we iterate toward a more robust v1!
activity_id : Human-readable description of the activity (e.g., 'Fishing products', 'Kiwi fruit').activity_classification_system : The classification standard used for activities (e.g., ANZSIC).level : Position in the hierarchical classification within activity_classification_system.company: Organization undertaking the activity (often absent in some databases).product_classification_system : Classification system for products (e.g., UPC, Stripe's taxable goods code).product : Specific commodity (e.g., '500g Kelloggs corn flakes').product_id : Unique identifier within product_classification_system (e.g., barcode).region : Super-national area (varies between sources).country : Self-governing nation-state (mostly universally recognized).subnational : Finer resolution, either jurisdictional or geographic (e.g., state, LGA, catchment).scope : Contextual reference for the measure of the activity's impact (e.g., scope 1-3 for emissions factor, cradle-to-shelf for LCA). May be blank if scope is context-dependent.impact_category : Sustainability category the activity or product contributes to (e.g., GHG emissions, eutrophication, modern slavery).lca_activity : The process(es) for which the impact is quantified (e.g., 'cereal_production', 'market_for_cereal').