[FR] Add 1.3 Specification revisions to Requirements Model

[Matt-Cowsert]

Problem Statement

Practitioners need to validate the output they are receiving from their provider matches the FOCUS spec for a given version (e.g., v1.3).

Use Case (Optional)

As a FinOps Practitioner, I want to evaluate the output of my provider's FOCUS implementation of a given version, so I can rely on the providers' output as I integrate FOCUS into my FinOps practice.

Desired Outcome / Practitioner Impact

Practitioners have certainty of the outputs they are getting from their providers that support FOCUS. This includes column, attribute, and metadata validation.

Type of Request

Refinement of an existing FOCUS attribute

Organizations Requesting or Supporting This Feature

No response

FinOps Scope Alignment (Optional)

• Public Cloud – e.g., AWS, Azure, GCP, OCI
• Software-as-a-Service (SaaS) – e.g., Salesforce, Snowflake
• Data Center – on-prem compute and infrastructure
• Licensing – subscription or usage-based licensing (under development)
• AI – cost and usage for AI models and platforms (under development)
• Custom – internal tooling, specialized infra (under development)

Impacted Parties

• FinOps Practitioner – end users who analyze or act on the data
• FOCUS Data Generator – providers generating aligned output
• Vendor Supporting FOCUS – tools or platforms using the spec
• Other (please explain in comments)

Level of Ambiguity (1–5)

2

Supporting Documentation

No response

Proposed Solution / Approach

No response

[Matt-Cowsert]

We need to include metadata requirements in the scope for 1.3 conformance requirements (it's not included for 1.2 conformance requirements).