TianGong PCR

Versioned data original production

Lifecycle status
Candidate
Content maturity
Authored methodology
Current version
0.1.0Last updated
Readiness
Review required

Methodology and translation states come from the source record; publishing this website does not change their review status.

Content languages

zh-CN · Aligned
Status, classification and source details

Readiness

  • Warnings methodology_not_reviewed Authored methodology is candidate guidance and still requires methodology review.

Classification mapping

CPC 3.0:83710 · exact

Source

1. Scope and Applicability

This PCR covers the production of identified digital information content obtained by accessing and observing phenomena and recording, organizing and storing their information. The output is one complete versioned data original under identified ownership/control, usable as input to productive activities. It covers primary observations and compilation of traceable existing data; the declared actual route determines the foreground inventory. Examples include a scoped weather-observation database and an identified business-record compilation. The object is the information product, including its schema, provenance, documentation and required quality results, rather than a file format or a sale. [un-cpc3-data; w3c-dcat3; noaa-ghcnd]

Exclude database-management software and other software originals, physical storage media, crypto assets, brands/franchises, research or exploration conclusions as separate originals, entertainment/online consumption content, commissioned compilation activity sold solely as a service, downloads and continuing access/hosting services. A research project may produce a data product as a separable output; do not reclassify its entire scientific original as data. A digital file can carry data without its creation constituting a new data original. [un-cpc3-data; w3c-dcat3]

2. Product Category Identity

FieldValue
canonical_pcr_idpcr.business-and-production-services.data-products.versioned-data-original
classification_refsCPC 3.0: 83710 Data
covered_productsVersioned productive digital information originals and original databases, with a bounded content manifest
excluded_productsSoftware; physical media; crypto assets; research/design originals; consumption content; compilation services; downloads and hosting
representative_productOne identified observation-data database version, with declared variables, population/locations, period, quality flags and reuse conditions; GHCN-Daily demonstrates version citation, not a mandatory weather route
production_routeSpecify content and collection design; acquire/observe and record; integrate and organize; validate/correct; document and seal one original
market_stateCompleted digitally stored information original available for declared productive reuse; ownership/control and access restrictions are specified

3. Reference Flow

FieldValue
WhatProduce a retrievable, documented digital information original for the declared productive purpose
How muchOne complete original package of the declared content/version; 1 item
How wellActual acceptance specification for variables/schema, coverage, completeness, resolution, quality flags, provenance, integrity and permitted reuse; no invented accuracy threshold
How long or cycleOne bounded creation cycle from project inception to the declared sealed-version cutoff; observation coverage is distinct from production duration; no default asset lifetime
reference_flow_linkreference_data
FieldValue
Reference amount1
Reference product flowVersioned data original package
Reference flow propertyNumber of items 01846770-4cfe-4a25-8ad9-919d8d378345
Reference unit groupUnits of items 5beb6eed-33a9-47b8-9ede-1dfe8f679159
Reference unititem
Required qualifiersoriginal ID; version and content manifest; schema/variables; source provenance; population/spatial and temporal coverage; resolution; missingness and quality flags; acceptance and integrity results; ownership/control and reuse rights; production route and sites; creation period and cutoff; upstream-data reuse and provider boundary

The display unit item is exactly the public count unit Item(s); it is not mass, money, a user or a byte. Required qualifiers belong in the resulting dataset metadata and acceptance evidence. One count without defined content/quality is not a comparable data product. Alternative serializations and duplicate backups of the same content are not additional originals.

4. Measurement and Unit Rules

rule_idApplies toRequired propertyRequired unitRule
reference_countreference productNumber of items 01846770-4cfe-4a25-8ad9-919d8d378345itemExactly one complete declared original; count by signed content/version manifest with cp_original. No mass conversion, byte normalization or license multiplication.
electricity_unitelectricity rowsNet calorific value 93a60a56-a3c8-11da-a746-0800200c9a66MJPreserve the public reference property and Units of energy group 93a60a57-a3c8-11da-a746-0800200c9a66. Meter kWh; convert to MJ with 3.6 MJ/kWh in calculate_energy [nist-si-conversion].
information_metricscontent and allocation metadataRecorded count/capacity/time in its actual unititem; byte; s as separately recordedRecord actual bytes, records, reserved time and transmitted data as separate metrics; no universal relation to item quality or electricity.

5. System Boundary

Boundary Abstraction

FieldValue
declared_starting_conditionActual observation access/collection inception, or receipt of identified existing data, through sealed original completion
starting_condition_roleDeclared original-creation foreground gate; receipt of existing data does not erase upstream creation
product_classification_scopeProductive information content in the CPC Data sense, independently of file format
recursive_input_ruleRecord each reused source-data version as a distinct input with provenance and a conserved upstream-burden share. Stop at its declared upstream dataset; never recalculate the same observations inside the consuming original
upstream_dataset_requirementSupplier data-creation, grid supply, owned hardware and purchased-job inventories matched to actual scopes; missing links are disclosed rather than set to zero
disclosureCreation/observation periods; source cutoffs and prior versions; owned/provider interfaces; physical collection route; hardware, cooling, storage and network boundaries; exclusions and missing upstream layers
rule_idApplies toRulesource_ids
boundary_cycleall production stagesInclude attributable planning, access, observation/recording, ingestion, organization, validation, corrective reruns, documentation and storage up to original sealing. Record failed runs and discarded records as production activity, without counting them as accepted output.un-cpc3-data; unece-gsbpm52
boundary_physicalobservationMap every actual field, laboratory, survey, sensor and scanning route. Add separate specific exchanges for actual fuel, transport, each reagent/consumable, water, wastes and documented direct releases. Their absence needs route evidence. Electronic data output does not justify excluding its physical collection.un-cpc3-data; unece-gsbpm52
boundary_assetscomputing and instrumentsInclude the attributable inventory of identified owned devices outside provider inventories. Hardware production/disposal is an upstream layer, not a local elementary release. Cooling, network and temporary storage inside creation must be metered or supplied by a scoped provider inventory.gsf-sci110
boundary_after_gatecopies and operationsPost-sealing downloads, user access, long-term hosting, updates and data use are separate processes. Initial creation burdens enter downstream through an explicit reuse ledger, never the full original cost in every download. New content versions include actual incremental work and disclosed reused burdens.un-cpc3-data; w3c-dcat3

6. Process Inventory Structure

Process Map

process_idprocess_nameinclusioninclusion_conditionrolequantitative_reference
planningContent and collection designrequiredAll originals; actual design/build workloadoriginal creationper declared reference flow
observationAcquisition and recordingrequiredActual source access and recording; owned physical collection only where usedoriginal creationper declared reference flow
organizationIntegration and organizationrequiredActual schema mapping, cleaning, indexing and processing; transformations are route-specificoriginal creationper declared reference flow
validationQuality and integrity checksrequiredChecks against declared acceptance rules; no universal imputation requirementoriginal creationper declared reference flow
sealingDocumentation and original sealingrequiredOne complete version manifest and bounded storage cutofforiginal creationper declared reference flow
infrastructureOwned supporting devicesconditionalOwned devices support creation and are outside purchased-provider inventoriesoriginal creationper declared reference flow

Each row represents one exchange. Process electricity pools are disjoint. Empty waste/elementary subsections mean no universal release is prescribed, not that a real site has zero exchanges. Dataset production must instantiate all documented route exchanges required by boundary_physical; purchased electricity emissions occur in its upstream supply inventory.

Process: Content and collection design (planning)

Inputs

Product flows
Alternating current (planning_electricity)

Electricity attributable to planning work, including allocated reserved idle/cooling/storage/network within its measured boundary. Use this UUID only for actual CN grid-average user supply below1 kV. Outside that supply condition keep a separate matching identity unresolved until verified. Meter work and retries with cp_energy; apply calculate_energy; do not duplicate provider-inclusive electricity.

  • Selected flow: Alternating current 50657322-939c-4829-a87b-47c093bfa6a7
  • Flow property / unit: Net calorific value 93a60a56-a3c8-11da-a746-0800200c9a66 / MJ
  • Amount rule: Measured attributable amount per declared reference flow; cp_energy.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_energy
  • Sources: gsf-sci110
Waste flows
Elementary flows

Outputs

Product flows
Waste flows
Elementary flows

Process: Acquisition and recording (observation)

Inputs

Product flows
Alternating current (observation_electricity)

Electricity attributable to observation work, including allocated reserved idle/cooling/storage/network within its measured boundary. Use this UUID only for actual CN grid-average user supply below1 kV. Outside that supply condition keep a separate matching identity unresolved until verified. Meter work and retries with cp_energy; apply calculate_energy; do not duplicate provider-inclusive electricity.

  • Selected flow: Alternating current 50657322-939c-4829-a87b-47c093bfa6a7
  • Flow property / unit: Net calorific value 93a60a56-a3c8-11da-a746-0800200c9a66 / MJ
  • Amount rule: Measured attributable amount per declared reference flow; cp_energy.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_energy
  • Sources: gsf-sci110
Existing observation dataset package (source_data)

Conditional: one identified existing observation-data version is acquired, received (including free or open data) or reused in compilation. Bind its manifest, source variables, coverage, quality flags and reuse rights. Count actual scoped packages; carry the justified upstream creation share, rather than copying their bytes as newly observed facts. New primary observations on own account in the current creation cycle instead require the actual observation-route inventory.

  • Selected flow: Existing observation dataset package
  • Flow property / unit: Number of items 01846770-4cfe-4a25-8ad9-919d8d378345 / item
  • Amount rule: Measured attributable amount per declared reference flow; cp_source.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_source
  • Sources: w3c-dcat3
Waste flows
Elementary flows

Outputs

Product flows
Waste flows
Elementary flows

Process: Integration and organization (organization)

Inputs

Product flows
Alternating current (organization_electricity)

Electricity attributable to organization work, including allocated reserved idle/cooling/storage/network within its measured boundary. Use this UUID only for actual CN grid-average user supply below1 kV. Outside that supply condition keep a separate matching identity unresolved until verified. Meter work and retries with cp_energy; apply calculate_energy; do not duplicate provider-inclusive electricity.

  • Selected flow: Alternating current 50657322-939c-4829-a87b-47c093bfa6a7
  • Flow property / unit: Net calorific value 93a60a56-a3c8-11da-a746-0800200c9a66 / MJ
  • Amount rule: Measured attributable amount per declared reference flow; cp_energy.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_energy
  • Sources: gsf-sci110
Data-compilation compute job (compute_job)

Conditional: an external provider delivers one completed, uniquely scoped compilation job. Record job ID, transformation, dataset version, executed/reserved resources, duration and actual provider inventory scope. Count completed jobs from logs, not billed currency; omitted cooling/hardware/storage/network must be supplied separately. Replace the same embedded energy/device exchanges rather than adding them twice.

  • Selected flow: Data-compilation compute job
  • Flow property / unit: Number of items 01846770-4cfe-4a25-8ad9-919d8d378345 / item
  • Amount rule: Measured attributable amount per declared reference flow; cp_provider.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_provider
  • Sources: gsf-sci110
Waste flows
Elementary flows

Outputs

Product flows
Waste flows
Elementary flows

Process: Quality and integrity checks (validation)

Inputs

Product flows
Alternating current (validation_electricity)

Electricity attributable to validation work, including allocated reserved idle/cooling/storage/network within its measured boundary. Use this UUID only for actual CN grid-average user supply below1 kV. Outside that supply condition keep a separate matching identity unresolved until verified. Meter work and retries with cp_energy; apply calculate_energy; do not duplicate provider-inclusive electricity.

  • Selected flow: Alternating current 50657322-939c-4829-a87b-47c093bfa6a7
  • Flow property / unit: Net calorific value 93a60a56-a3c8-11da-a746-0800200c9a66 / MJ
  • Amount rule: Measured attributable amount per declared reference flow; cp_energy.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_energy
  • Sources: gsf-sci110
Waste flows
Elementary flows

Outputs

Product flows
Waste flows
Elementary flows

Process: Documentation and original sealing (sealing)

Inputs

Product flows
Alternating current (sealing_electricity)

Electricity attributable to sealing work, including allocated reserved idle/cooling/storage/network within its measured boundary. Use this UUID only for actual CN grid-average user supply below1 kV. Outside that supply condition keep a separate matching identity unresolved until verified. Meter work and retries with cp_energy; apply calculate_energy; do not duplicate provider-inclusive electricity.

  • Selected flow: Alternating current 50657322-939c-4829-a87b-47c093bfa6a7
  • Flow property / unit: Net calorific value 93a60a56-a3c8-11da-a746-0800200c9a66 / MJ
  • Amount rule: Measured attributable amount per declared reference flow; cp_energy.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_energy
  • Sources: gsf-sci110
Waste flows
Elementary flows

Outputs

Product flows
Versioned data original package (reference_data)

Exactly one complete original with declared content and version, accepted against its actual quality specification and sealed manifest. It comprises the information and required documentation, not each duplicate file, sale, download or license. Required content with missing data must retain declared flags; acceptance does not imply legal or scientific approval.

  • Selected flow: Versioned data original package
  • Flow property / unit: Number of items 01846770-4cfe-4a25-8ad9-919d8d378345 / item
  • Amount rule: 1 item
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_original
  • Sources: un-cpc3-data
Waste flows
Elementary flows

Process: Owned supporting devices (infrastructure)

Inputs

Product flows
Data-production computing server (server_hardware)

Conditional: an identified owned computing server supports creation. Bind actual model, processors, memory, storage and upstream device inventory. Record reserved time, evidenced installed life and capacity share, retaining uncertainty; allocate device inventory using allocation_device. No generic service proxy establishes its identity.

  • Selected flow: Data-production computing server
  • Flow property / unit: Number of items 01846770-4cfe-4a25-8ad9-919d8d378345 / item
  • Amount rule: Measured attributable amount per declared reference flow; cp_device.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_device
  • Sources: gsf-sci110
Electronic observation data logger (logger_hardware)

Conditional: an identified electronic instrument records observations for this original. Bind measured variables, calibrated sensing/recording configuration, location and power interface. Record actual utilization and installed life from site evidence; include individual probe, battery and other actual replaced components as separate exchanges if outside the device inventory.

  • Selected flow: Electronic observation data logger
  • Flow property / unit: Number of items 01846770-4cfe-4a25-8ad9-919d8d378345 / item
  • Amount rule: Measured attributable amount per declared reference flow; cp_device.
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per declared reference flow
  • Basis kind: Process output (process_output)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_device
  • Sources: gsf-sci110
Waste flows
Elementary flows

Outputs

Product flows
Waste flows
Elementary flows

7. Allocation and Co-product Handling

rule_idApplies toRulesource_ids
allocation_subdivideshared data projectsSeparate project and stage workloads using meters, collection logs and job IDs before allocating. Keep residual unassigned shares and failed work visible. Do not default to revenue, licenses, users or data byte shares without a causal measured relationship.gsf-sci110; unece-gsbpm52
allocation_computeshared electricityReconcile attributable measured job/storage/network shares to the same facility meter period, including reserved idle and cooling scope. A traffic or storage metric is an attribution driver requiring justification and reconciliation, never a universal kWh conversion.gsf-sci110
allocation_deviceserver_hardware; logger_hardwareUse the actual device inventory fraction attributable to the creation cycle. For a reserved computing device, use reserved time divided by evidenced installed life and reserved resource divided by total resource. Noncomputing sensor duty allocation needs its own measured causal utilization evidence. Do not invent life or duplicate provider hardware.gsf-sci110
allocation_reusesource_data and joint original versionsTrace upstream source content and retained prior-version work separately from incremental creation. Maintain a conserved beneficiary ledger with an explicit finite output/use scenario when sharing original burdens downstream; report sensitivity to reuse assumptions. Copies never multiply information creation. Joint research/software outputs require actual subdivision; unresolved joint attribution needs review.un-cpc3-data; w3c-dcat3

8. Foreground Data Collection, Calculation, and Quality Rules

Data Collection Protocols

protocol_idprocess_idflow_rolerecord_typeraw_fieldscollection_methodunitfrequencytemporal_coveragesite_scopeaggregation_rulequality_evidence
cp_originalsealingreference outputacceptance_recordoriginal ID; version; files/checksums; content extent; schema; source rights/control; acceptance criteria/results; coverage; quality flags; completion cutoff; complete countInspect original content and producer acceptance records; deduplicate equivalent serializations and bind one complete declared originalitemAt version completionEntire declared creation cycleAll original-producing sites/providersper declared reference flowSigned version manifest and reproducible acceptance/integrity results
cp_energyplanning; observation; organization; validation; sealingstage electricitymeter_recordmeter ID; start/end; stage/job; region; voltage; kWh; reserved/idle load; cooling, storage and network interface; allocation share; provider overlapUse calibrated meters or verified telemetry reconciled to facility totals; bind disjoint stage intervals, reruns and shared-load attributionkWhEach run and creation intervalFull creation cycle including failed workActual owned supply; provider scopes separatelyper declared reference flowCalibration, workload logs, meter reconciliation and gap coverage
cp_sourceobservationexisting observation datasetsource_recordsource ID/version; package count; variables/coverage; flags; rights; upstream creation inventory; beneficiary shares; received bytes; lineageInspect received original and provenance; count defined packages; verify compatibility, rights and upstream burden ledger rather than estimating energy from sizeitemEach source version receivedAll sources of the declared output versionActual suppliers and receiving siteper declared reference flowSource manifest, access record, upstream inventory and reuse ledger
cp_providerorganizationcompilation jobprovider_recordjob ID; source/output version; complete-job count; transformation; resources/time; provider energy/device/network/storage/cooling boundaryInspect provider job acceptance logs and matched job inventory; retain retries and scope exclusions, reconcile billed metrics without treating money as quantityitemEach completed provider jobDeclared creation cycleActual provider facilitiesper declared reference flowJob manifests, scoped provider inventory and embedded-exchange exclusion ledger
cp_deviceinfrastructureindividual deviceasset_recorddevice model/configuration; upstream inventory; installed life; reserved time; reserved/total resources; actual sensor duty; calibration; replacements; provider inclusionInspect device register, configuration, service-life evidence and utilization logs; collect causal shares separately for servers and instrumentsitemEach device and project periodCreation cycle and evidenced device lifeActual owned devicesper declared reference flowAsset records, utilization evidence and life/allocation sensitivity

For physical observation, retain the actual method, sampling/survey coverage, equipment and calibration, field/laboratory locations, collection period and all individual input/output records. Every added atomic exchange must have a linked protocol with its real property/unit, method, coverage and the same per-original basis. Route omissions block a complete dataset; digital-only compilation requires evidence that observation burdens are in its identified upstream sources.

Calculation Rules

rule_idApplies toFormula or ruleInputsOutputsource_ids
calculate_energyplanning_electricity; observation_electricity; organization_electricity; validation_electricity; sealing_electricityConvert attributable metered kWh to MJ by multiplication by 3.6; preserve stage and supply interfaces.cp_energy; kWhMJgsf-sci110; nist-si-conversion
calculate_originalall inventory rowsSum nonduplicated attributable exchange quantities for the one declared original after stage/provider/source subdivision; the output is exactly 1 item. Keep numerator units and upstream shares explicit.cp_original; cp_energy; cp_source; cp_provider; cp_deviceper declared reference flowun-cpc3-data; gsf-sci110
calculate_metricscontent metadataRecord actual completeness, valid/rejected record counts, byte sizes and coverage against declared specifications. These characterize content and do not transform bytes or records into MJ or new originals.cp_original; source and validation logsdeclared quality and content metricsw3c-dcat3; unece-gsbpm52; noaa-ghcnd

Data Quality Requirements

requirement_idApplies toRequirementEvidence
quality_contentreference_dataBind source lineage, coverage, version, schema, missingness, flags, transformations and rights/control. Preserve observed versus imputed records and checks actually performed; acceptance criteria are producer-specific.cp_original; cp_source; w3c-dcat3; noaa-ghcnd
quality_cycleall processesCover actual sites, collection and production periods, failed jobs, corrections, temporary replicas and sealing storage. Disclose missing meter periods, external source burdens and provider exclusions.cp_energy; cp_provider; unece-gsbpm52
quality_identityall inputsRecheck public identities, reference properties/groups, supply conditions, actual hardware and upstream versions. Blank UUIDs remain candidate gaps and cannot establish available provider inventories.cp_device; cp_source; cp_provider
quality_uncertaintyallocation and data representativenessReport workload/meter uncertainty, unknown shares, hardware-life sensitivity, observation coverage limits and reuse scenario sensitivity. No invented benchmark can replace foreground evidence.cp_energy; cp_device; source/reuse ledger

9. Validation Rules

rule_idApplies toRulesource_ids
validate_productreference_dataRequire one complete identified productive information original with actual ownership/control and declared quality evidence. Reject copies, licenses, file-format conversions, mere compilation services, software or consumption content counted as equivalent originals.un-cpc3-data; w3c-dcat3
validate_basisall inventory rowsRequire consistent per declared reference flow in both languages, linked collection records, count output and numerator-unit preservation. Reject arbitrary mass, bytes-to-kWh or money-to-item conversions.gsf-sci110; w3c-dcat3
validate_routeobservation and processingFail dataset completeness if any actual observation route, provider interface, utility, material, waste, direct release or upstream source burden is unknown or omitted. A conditional row may be absent only with route evidence; do not invent emissions to fill empty subsections.un-cpc3-data; unece-gsbpm52
validate_conservationshared work and reused contentReconcile stage meters, provider embedded flows, device shares, joint outputs and the finite reuse ledger. Reject duplicated original costs per copy and unexplained allocation residuals hidden as zero.gsf-sci110; w3c-dcat3
validate_coveragedataset claimList checks performed/skipped, missing physical and upstream layers, identity gaps and uncertainties. Foreground creation alone is not a complete cradle-to-gate or lifecycle result; metadata conformance is not scientific, privacy or legal approval.un-cpc3-data; w3c-dcat3; gsf-sci110

10. Published Dataset Profile

FieldValue
dataset_roleOriginal-creation foreground inventory for one declared complete data product version
downstream_usesecondary_dataset; background_dataset
allowed_useAfter evidence completion, traceable upstream data product input with explicit source/reuse allocation and matched content quality
excluded_useGeneric impact per byte/user/license/revenue; comparisons of unequal data; full lifecycle claims from foreground alone; approved accuracy or legal status
required_metadataAll reference qualifiers; sites and periods; method/route register; source lineage and upstream inventories; provider and owned-asset scopes; meters/units; reuse allocation and sealing cutoff
required_quality_disclosureIdentity and route gaps; data coverage/missingness; actual acceptance results; meter/allocation uncertainty; device-life and reuse sensitivity; skipped layers
update_triggerNew information/version scope; changed observations, source rights, provider/site/device, quality method, sealing cutoff or measured energy/reuse allocation

11. Data Sources

Source idTypeReferenceUsed for
un-cpc3-dataofficial_guidanceUNSD CPC Version3.0, Code83710, explanatory note inclusion, Notes1–3 and exclusions: https://unstats.un.org/unsd/classifications/Econ/Structure/Detail/EN/2100/83710Information product, ownership/control and software/media/consumption exclusions; no LCA factors
w3c-dcat3standardW3C, Data Catalog Vocabulary (DCAT) Version3, Recommendation22 August2024; §§5,6.6,6.8,9,11,14: https://www.w3.org/TR/2024/REC-vocab-dcat-3-20240822/Dataset/distribution distinction, version, rights and quality metadata; DCAT scope alone does not establish CPC applicability
unece-gsbpm52official_guidanceUNECE, Generic Statistical Business Process Model Version5.2 (May2025, CES endorsed June2025); Collect/Process, paragraphs93–114: https://unece.github.io/GSBPM-5.2/Acquisition, integration, validation and route-specific correction; statistical framework, no mandatory imputation or energy coefficients
gsf-sci110standardGreen Software Foundation, Software Carbon Intensity specification1.1.0; Energy and Embodied emissions: https://sci.greensoftware.foundation/Measured computing energy scope and reserved-time/resource device attribution only; no default lifetime or complete data LCA score
noaa-ghcnddatasetNOAA NCEI GHCN-Daily README Version3.35; header/version citation and §III FORMAT OF DATA FILES, MFLAG/QFLAG/SFLAG; dataset DOI10.7289/V5D21VHZ: https://www.ncei.noaa.gov/pub/data/ghcn/daily/readme.txtActual versioned observation database example and source/quality flags; weather-specific metadata only, no producer quantities or generic quality threshold
nist-si-conversionofficial_guidanceNIST SP811 (2008), Appendix B.8 K, exact kilowatt hour to joule factor: https://www.nist.gov/pml/special-publication-811/nist-guide-si-appendix-b-conversion-factors/nist-guide-si-appendix-b81 kWh = 3.6 × 10^6 J = 3.6 MJ, exact conversion only; historical table, not used for pre-2019 base-unit definitions or production coefficients

Raw downloads

These files are byte-identical to the canonical files for this revision in the repository.

Structured rule index

This index comes from verified structured.yaml and retains the canonical English rule text.

System boundary rules · 4
Rule IDApplies toRuleSource IDs
boundary_cycleall production stagesInclude attributable planning, access, observation/recording, ingestion, organization, validation, corrective reruns, documentation and storage up to original sealing. Record failed runs and discarded records as production activity, without counting them as accepted output.un-cpc3-data, unece-gsbpm52
boundary_physicalobservationMap every actual field, laboratory, survey, sensor and scanning route. Add separate specific exchanges for actual fuel, transport, each reagent/consumable, water, wastes and documented direct releases. Their absence needs route evidence. Electronic data output does not justify excluding its physical collection.un-cpc3-data, unece-gsbpm52
boundary_assetscomputing and instrumentsInclude the attributable inventory of identified owned devices outside provider inventories. Hardware production/disposal is an upstream layer, not a local elementary release. Cooling, network and temporary storage inside creation must be metered or supplied by a scoped provider inventory.gsf-sci110
boundary_after_gatecopies and operationsPost-sealing downloads, user access, long-term hosting, updates and data use are separate processes. Initial creation burdens enter downstream through an explicit reuse ledger, never the full original cost in every download. New content versions include actual incremental work and disclosed reused burdens.un-cpc3-data, w3c-dcat3
Allocation rules · 4
Rule IDApplies toRuleSource IDs
allocation_subdivideshared data projectsSeparate project and stage workloads using meters, collection logs and job IDs before allocating. Keep residual unassigned shares and failed work visible. Do not default to revenue, licenses, users or data byte shares without a causal measured relationship.gsf-sci110, unece-gsbpm52
allocation_computeshared electricityReconcile attributable measured job/storage/network shares to the same facility meter period, including reserved idle and cooling scope. A traffic or storage metric is an attribution driver requiring justification and reconciliation, never a universal kWh conversion.gsf-sci110
allocation_deviceserver_hardware; logger_hardwareUse the actual device inventory fraction attributable to the creation cycle. For a reserved computing device, use reserved time divided by evidenced installed life and reserved resource divided by total resource. Noncomputing sensor duty allocation needs its own measured causal utilization evidence. Do not invent life or duplicate provider hardware.gsf-sci110
allocation_reusesource_data and joint original versionsTrace upstream source content and retained prior-version work separately from incremental creation. Maintain a conserved beneficiary ledger with an explicit finite output/use scenario when sharing original burdens downstream; report sensitivity to reuse assumptions. Copies never multiply information creation. Joint research/software outputs require actual subdivision; unresolved joint attribution needs review.un-cpc3-data, w3c-dcat3
Validation rules · 5
Rule IDApplies toRuleSource IDs
validate_productreference_dataRequire one complete identified productive information original with actual ownership/control and declared quality evidence. Reject copies, licenses, file-format conversions, mere compilation services, software or consumption content counted as equivalent originals.un-cpc3-data, w3c-dcat3
validate_basisall inventory rowsRequire consistent per declared reference flow in both languages, linked collection records, count output and numerator-unit preservation. Reject arbitrary mass, bytes-to-kWh or money-to-item conversions.gsf-sci110, w3c-dcat3
validate_routeobservation and processingFail dataset completeness if any actual observation route, provider interface, utility, material, waste, direct release or upstream source burden is unknown or omitted. A conditional row may be absent only with route evidence; do not invent emissions to fill empty subsections.un-cpc3-data, unece-gsbpm52
validate_conservationshared work and reused contentReconcile stage meters, provider embedded flows, device shares, joint outputs and the finite reuse ledger. Reject duplicated original costs per copy and unexplained allocation residuals hidden as zero.gsf-sci110, w3c-dcat3
validate_coveragedataset claimList checks performed/skipped, missing physical and upstream layers, identity gaps and uncertainties. Foreground creation alone is not a complete cradle-to-gate or lifecycle result; metadata conformance is not scientific, privacy or legal approval.un-cpc3-data, w3c-dcat3, gsf-sci110
Processes and inputs/outputs · 6
Process IDProcess nameInput flowsOutput flows
planningContent and collection design10
observationAcquisition and recording20
organizationIntegration and organization20
validationQuality and integrity checks10
sealingDocumentation and original sealing11
infrastructureOwned supporting devices20

Complete field inspector

Loads this record’s complete manifest and structured projection on demand; values are never truncated. Requires JavaScript.

On this page