FOCUS dataset consistency review

[aqu-erp]

Resolving #472

Acceptance

• select a term to used to describe a FOCUS compliant dataset
• defining term in glossary
• maintain consistent usage of term across specification and changelog, etc.
• add glossary anchors where needed
• confirm convention for referring to a generic potentially noncompliant dataset from a provider

Proposed term and definition

FOCUS Dataset
A structured collection of cost and usage data that meets or exceeds the Basic compliance criteria of FOCUS.

---

Open Questions

When to retain use of billing data

• When used in general context of FinOps data at large

Examples

Overview.md

FOCUS aims to establish a community-driven specification for consumption-based billing data.

Billing data generators: Infrastructure and services providers that bill based on consumption

Readme.md

The FOCUS spec will make it easier to merge multiple billing data sources together

---

Notes

• Term replaces instances of -, billing data, and cost data in normative statements
• Term does not refer to dataset supplied/created/provided by the spec
• Term refers to dataset that is being described by normative statements
  • a dataset that meets certain compliance criteria

[ijurica]

We've mentioned that if native/custom columns are present in the FOCUS dataset, they must be prefixed with 'x_'. Do we need to emphasize that, if present, custom columns must also be listed in the Metadata - Schema - Column Definition.

By the way, we've specified that each column is represented with a Column Name. Would Column IDs be more useful in this context?

[jpradocueva]

Action Item

• Maintainers-#474: Andrew to lead the review and discussions in Task Force 3.

[jpradocueva]

Action Items agreed on TF-3, July 12 call:

• Maintainers-#474 : Andrew will lead the review and discussions in Task Force 3.
• TF3- #474 All members to review and provide comments on the PR
• TF3- #474 Members: Discuss and finalize the inclusion of native provider columns in the FOCUS dataset definition in the glossary.

Action Items from TF-3, July 19.

• TF3-#474 Andrew: To update the PR with additional guidelines and links to the glossary.
• Present the PR at the next members' meeting.

[jpradocueva]

This PR was approved by the group during the Maintainers meeting on August 1.