-
Notifications
You must be signed in to change notification settings - Fork 41
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.
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
WI #557: Preview - Refinement of FOCUS Columns Normative Requirements #664
base: working_draft
Are you sure you want to change the base?
Changes from 14 commits
812e80e
9f6ee2c
440de4a
fb273d1
287a6fa
6f4c08e
2de3c14
0ce1c00
600825e
1b6ee5d
0d2501e
e202cbb
16160b1
77677cf
a8e01d2
1a49e33
f39b33b
aaf3236
2848253
cb9ed2d
7bc4d13
d5f2d1c
6647d5e
c0979fb
4eea18b
570e8e9
2b5f535
e7de196
10f4c92
d51ffc1
abfcb72
8579930
7ab7d27
6731cc7
2c073d1
96d2134
ead6162
0df2678
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
ijurica marked this conversation as resolved.
Show resolved
Hide resolved
|
ijurica marked this conversation as resolved.
Show resolved
Hide resolved
|
ijurica marked this conversation as resolved.
Show resolved
Hide resolved
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,20 @@ | |
|
||
A Capacity Reservation ID is the identifier assigned to a [*capacity reservation*](#glossary:capacity-reservation) by the provider. Capacity Reservation ID is commonly used for scenarios to allocate charges for capacity reservation usage. | ||
|
||
--- | ||
The CapacityReservationId column adheres to the following requirements: | ||
|
||
* CapacityReservationId MUST be present in a [*FOCUS dataset*](#glossary:FOCUS-dataset) when the provider supports *capacity reservations*. | ||
* If present, CapacityReservationId adheres to the following additional requirements: | ||
* CapacityReservationId MUST be of type String. | ||
* CapacityReservationId MUST conform to [String Handling](#stringhandling) requirements. | ||
* CapacityReservationId MUST be null when a charge is not related to a *capacity reservation*. | ||
* CapacityReservationId SHOULD NOT be null when a charge is related to a capacity reservation. | ||
* CapacityReservationId MUST NOT be null when a charge represents the unused portion of a *capacity reservation*. | ||
* CapacityReservationId MUST ensure global uniqueness within the provider. | ||
* CapacityReservationId SHOULD be a fully-qualified identifier. | ||
|
||
--- | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Approved |
||
The CapacityReservationId column adheres to the following requirements: | ||
|
||
* CapacityReservationId MUST be present in a [*FOCUS dataset*](#glossary:FOCUS-dataset) when the provider supports *capacity reservations* and MUST be of type String. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,16 @@ | |
|
||
Charge Period Start represents the [*inclusive*](#glossary:inclusivebound) start date and time within a [*charge period*](#glossary:chargeperiod). For example, a time period where ChargePeriodStart is '2024-01-01T00:00:00Z' and [ChargePeriodEnd](#chargeperiodend) is '2024-01-02T00:00:00Z' includes charges for January 1, since ChargePeriodStart is *inclusive*, but does not include charges for January 2 since ChargePeriodEnd is [*exclusive*](#glossary:exclusivebound). | ||
|
||
--- | ||
The ChargePeriodStart column adheres to the following requirements: | ||
|
||
* ChargePeriodStart MUST be present in a [*FOCUS dataset*](#glossary:FOCUS-dataset). | ||
* ChargePeriodStart MUST be of type Date/Time. | ||
* ChargePeriodStart MUST conform to [Date/Time Format](#date/timeformat) requirements. | ||
* ChargePeriodStart MUST NOT be null. | ||
* ChargePeriodStart MUST be the *inclusive beginning bound* of the effective period of the charge. | ||
|
||
--- | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I noticed the following was left out, not sure if intentional ChargePeriodStart MUST match the beginning date and time boundary of the effective period of the charge. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar to ChargePeriodEnd, this has been replaced with:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Approved |
||
The ChargePeriodStart column adheres to the following requirements: | ||
|
||
* ChargePeriodStart MUST be present in a [*FOCUS dataset*](#glossary:FOCUS-dataset), MUST be of type Date/Time, MUST be an *inclusive* value, and MUST NOT contain null values. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed in Dec 10 TF1. Propose postponing adding such requirements until lower-hanging fruit of consistency is collected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I must have missed something. Why is linking attributes contentious?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talking to Irena - she suggested postponing this due to provider conformance concerns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we discuss this in the TF-1 meeting. This sheet can serve as the basis for our discussion.