Skip to content

Define FB_29 (Temperature Interval Metering) query requirements #283

Open

Description

@dfcoffin

Problem

FB_29 (Temperature Interval Metering) has no defined rule for which data it grants in the Data Custodian's resource API, so the DC cannot gate temperature data on it.

Requirements to define

  1. Identification: how temperature data is recognised: ReadingType commodity, ReadingType uom (e.g. degrees Celsius or Fahrenheit), a UsagePoint ServiceCategory, or a combination. Cite the REQ.21 v4.1 FB_29 text and the GBA certification test expectations.
  2. Granularity: whether missing FB_29 removes whole UsagePoints or only the temperature MeterReadings (with their ReadingTypes and IntervalBlocks) under a UsagePoint of another commodity.
  3. Combination with FB_4: whether FB_29 alone (with FB_4) is enough for Batch/Subscription and the per-resource endpoints, and what a token with FB_29 but no other commodity FB receives.
  4. Query parameters: whether temperature IntervalBlocks follow the same published-min/max overlap, 24-hour default and HistoryLength ceiling as other interval data (DC: serve Batch/Subscription/{id} (the customer token's resourceURI) as one subscription-scoped Atom feed #279).
  5. Test data: a certification-style fixture with temperature readings (schema values only).

Then

Related: #279, #282, #187.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions