The boundary_scope_term table
The closed vocabulary of the questions a boundary answers: is capital equipment inside, is the fuel's upstream inside. A boundary name alone does not settle those.
Fields#
| field | type | required | example | meaning |
|---|---|---|---|---|
code |
text | yes | capital_goods, upstream_fuel, ... | |
description |
text | yes | Free prose describing this row. | |
stage |
text | yes | Where the term sits in the life cycle, so a consumer can group them: the four phases upstream / production / downstream / eol, plus two stages that are not phases and are drawn apart from them (MOD-0032 R8): beyond_boundary (a credit for what leaves the system) and inclusion (a content counted across every phase: equipment, overheads, an unplaced freight leg). Carbon pools are not terms: the value's co2e_basis and gas legs answer them. | |
subject_kinds |
array | yes | {grid_energy,fuel,transport} | The kinds of subject the term can apply to: product, grid_energy, fuel, transport, service, waste, direct or land. A factor whose category measures another kind does not carry the term. |
Referenced by#
publisher_boundary_scope.term_code, system_boundary_scope.term_code.
Notes#
Terms are answered at three grains: per boundary in system_boundary_scope, per library (or per category of one library) in publisher_boundary_scope, and per factor in emission_factor.boundary_profile. factors_flat.boundary_scope serves the merged answer for each factor.
subject_kinds says what a term can be asked of. A factor's kind comes from its category (category_subject_kind), and a term whose kinds do not include it is left off that factor entirely: packaging is not a question for a consulting hour, and grid losses are not a question for a brick. A term with no answer means not established, never excluded.