Skip to content

AI #1631: Address Minor Editorial Issues in FOCUS 1.3 #1633

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: candidate_recommendation
Choose a base branch
from
Open

AI #1631: Address Minor Editorial Issues in FOCUS 1.3 #1633

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
34112ea
AI #1600: Set working_draft github workflow not to run on candidate_r…
mike-finopsorg Nov 17, 2025
e546b85
FOCUS #1631: minor editorial updates to FOCUS 1.3
ijurica Nov 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/working_draft.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ on:
push:
branches-ignore:
- "main"
- "candidate_release"
- "candidate_recommendation"
Copy link
Contributor

@shawnalpay shawnalpay Nov 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this here and not in #1632...?


jobs:
# The job that will use the container image you just pushed to ghcr.io
Expand Down
2 changes: 0 additions & 2 deletions specification/attributes/invoice_handling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,6 @@ Indicates how invoice-level *charges*, including those not directly tied to usag
* SLA credit details when the credit is already applied to the charged amount
* If such informational items are excluded, data generators MUST document this in their FOCUS implementation guide and ensure the sum of included charges still equals the invoice total.

None

## Introduced (version)

1.3
2 changes: 1 addition & 1 deletion specification/supported_features/contract_commitments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Description

FOCUS supports the tracking of commitments made via contractual agreements between a provider and a customer. Each row in the Cost and Usage dataset is associated with one or more unique identifiers representing those contracts and contract commitments, stored in a JSON column called Contract Applied. A richer amount of detail that describes those commitments is carried in a separate Contract Commitment dataset, which can be joined to the Cost and Usage datset to facilitate various queries involving filtering and aggregation.
FOCUS supports the tracking of commitments made via contractual agreements between a service provider and a customer. Each row in the Cost and Usage dataset is associated with one or more unique identifiers representing those contracts and contract commitments, stored in a JSON column called Contract Applied. A richer amount of detail that describes those commitments is carried in a separate Contract Commitment dataset, which can be joined to the Cost and Usage datset to facilitate various queries involving filtering and aggregation.

The Contract Applied column contains several FOCUS-defined properties. For more information, see the definition of Contract Applied [here](#contractapplied).

Expand Down