#1646: Standardize Normative Language: Convert All RECOMMENDED Statements to SHOULD

guidelines/editorial-guidelines.md

@@ -135,7 +135,7 @@ These guidelines can be modified through a Pull Request (PR), which the members
       <td><strong>Tables</strong></td>
       <td><img width="492" alt="image" src="https://github.com/user-attachments/assets/5185cbf9-306d-4663-a1c7-c8b7ab5c5bb8"></td>
       <td><img width="492" alt="image" src="https://github.com/user-attachments/assets/83d0977f-a731-4def-93e3-b3e5f5dedb72"></td>
-      <td> - Tables: Simple tables can be created using markdown, but for more complex tables, it is RECOMMENDED to use HTML elements. See the example below. </td>
+      <td> - Tables: Simple tables can be created using markdown, but for more complex tables, it is recommended to use HTML elements. See the example below. </td>
     </tr>
 </table>
 
@@ -148,6 +148,9 @@ These guidelines can be modified through a Pull Request (PR), which the members
 
 * **Display Names:** They SHOULD be used in introductory or explanatory sections where natural language context is more appropriate. In these sections, display names should follow normal text conventions, including spaces between words (e.g., Commitment Discount ID).
 
+* **Normative Keyword Standardization:** To ensure consistency in the specification, normative language MUST use only the BCP-14 keywords MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY. The group agreed the term "RECOMMENDED" MUST NOT be used as a normative keyword. Where legacy text uses RECOMMENDED, it MUST be replaced with SHOULD.
+
+* **Non-Normative Use of “recommended”:** The lowercase word “recommended” may still be used in non-normative, descriptive text (e.g., “Feature level: Recommended”) provided it does not express a normative requirement on implementers.
 
 ### Example
 

specification/attributes/data_generator_calculated_split_cost_allocation_handling.md

@@ -31,7 +31,7 @@ An attribute that allows data generators to offer more detailed cost and usage i
 * A FOCUS dataset MAY contain records for concepts not related to resource usage, if documented in the split cost allocation method.
 * A FOCUS dataset MAY contain records for the unused or unallocated usage from the origin charge as separate allocated charges, if it aligns to the data generator's documented allocation method.
 * Allocated charge records MAY contain apportioned costs for the unused or unallocated usage from the origin charge, if it aligns to the data generator's documented allocation method.
-* Split cost allocation is RECOMMENDED to be applied to charges on an opt-in basis.
+* Split cost allocation SHOULD be applied to charges on an opt-in basis.
 
 ## Exceptions
 

specification/datasets/cost_and_usage/columns/availabilityzone.md

@@ -6,7 +6,7 @@ An [*availability zone*](#glossary:availability-zone) is a host-provider-assigne
 
 AvailabilityZone adheres to the following requirements:
 
-* AvailabilityZone is RECOMMENDED to be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset) when the host provider supports deploying resources or services within an *availability zone*.
+* AvailabilityZone SHOULD be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset) when the host provider supports deploying resources or services within an *availability zone*.
 * AvailabilityZone MUST be of type String.
 * AvailabilityZone MUST conform to [StringHandling](#stringhandling) requirements.
 * AvailabilityZone MUST be null when a [*charge*](#glossary:charge) is not specific to an *availability zone*.

specification/datasets/cost_and_usage/columns/chargefrequency.md

@@ -6,7 +6,7 @@ Charge Frequency indicates how often a [*charge*](#glossary:charge) will occur.
 
 ChargeFrequency adheres to the following requirements:
 
-* ChargeFrequency is RECOMMENDED to be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset).
+* ChargeFrequency SHOULD be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset).
 * ChargeFrequency MUST be of type String.
 * ChargeFrequency MUST NOT be null.
 * ChargeFrequency MUST be one of the allowed values.

specification/datasets/cost_and_usage/columns/invoiceid.md

@@ -6,7 +6,7 @@ An Invoice ID is a invoice-issuer-assigned identifier for an invoice encapsulati
 
 InvoiceId adheres to the following requirements:
 
-* InvoiceId is RECOMMENDED to be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset).
+* InvoiceId SHOULD be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset).
 * InvoiceId MUST be of type String.
 * InvoiceId MUST conform to [StringHandling](#stringhandling) requirements.
 * The sum of BilledCost for a given [InvoiceId](#invoiceid) MUST match the sum of the payable amount provided in the corresponding invoice with the same id generated by the [InvoiceIssuerName](#InvoiceIssuerName).

specification/datasets/cost_and_usage/columns/pricingcurrencycontractedunitprice.md

@@ -8,7 +8,7 @@ PricingCurrencyContractedUnitPrice adheres to the following requirements:
 
 * PricingCurrencyContractedUnitPrice presence in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset) is defined as follows:
   * PricingCurrencyContractedUnitPrice MUST be present in a Cost and Usage *FOCUS dataset* when the service provider supports prices in virtual currency and publishes unit prices exclusive of discounts.
-  * PricingCurrencyContractedUnitPrice is RECOMMENDED to be present in a Cost and Usage *FOCUS dataset* when the service provider supports pricing and billing in different currencies and publishes unit prices exclusive of discounts.
+  * PricingCurrencyContractedUnitPrice SHOULD be present in a Cost and Usage *FOCUS dataset* when the service provider supports pricing and billing in different currencies and publishes unit prices exclusive of discounts.
   * PricingCurrencyContractedUnitPrice MAY be present in a Cost and Usage *FOCUS dataset* in all other cases.
 * PricingCurrencyContractedUnitPrice MUST be of type Decimal.
 * PricingCurrencyContractedUnitPrice MUST conform to [NumericFormat](#numericformat) requirements.

specification/datasets/cost_and_usage/columns/pricingcurrencyeffectivecost.md

@@ -8,7 +8,7 @@ PricingCurrencyEffectiveCost adheres to the following requirements:
 
 * PricingCurrencyEffectiveCost presence in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset) is defined as follows:
   * PricingCurrencyEffectiveCost MUST be present in a Cost and Usage *FOCUS dataset* when the service provider supports prices in virtual currency and publishes unit prices exclusive of discounts.
-  * PricingCurrencyEffectiveCost is RECOMMENDED to be present in a Cost and Usage *FOCUS dataset* when the service provider supports pricing and billing in different currencies and publishes unit prices exclusive of discounts.
+  * PricingCurrencyEffectiveCost SHOULD be present in a Cost and Usage *FOCUS dataset* when the service provider supports pricing and billing in different currencies and publishes unit prices exclusive of discounts.
   * PricingCurrencyEffectiveCost MAY be present in a Cost and Usage *FOCUS dataset* in all other cases.
 * PricingCurrencyEffectiveCost MUST be of type Decimal.
 * PricingCurrencyEffectiveCost MUST conform to [NumericFormat](#numericformat) requirements.

specification/datasets/cost_and_usage/columns/pricingcurrencylistunitprice.md

@@ -8,7 +8,7 @@ PricingCurrencyListUnitPrice adheres to the following requirements:
 
 * PricingCurrencyListUnitPrice presence in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset) is defined as follows:
   * PricingCurrencyListUnitPrice MUST be present in a Cost and Usage *FOCUS dataset* when the service provider supports prices in virtual currency and publishes unit prices exclusive of discounts.
-  * PricingCurrencyListUnitPrice is RECOMMENDED to be present in a Cost and Usage *FOCUS dataset* when the service provider supports pricing and billing in different currencies and publishes unit prices exclusive of discounts.
+  * PricingCurrencyListUnitPrice SHOULD be present in a Cost and Usage *FOCUS dataset* when the service provider supports pricing and billing in different currencies and publishes unit prices exclusive of discounts.
   * PricingCurrencyListUnitPrice MAY be present in a Cost and Usage *FOCUS dataset* in all other cases.
 * PricingCurrencyListUnitPrice MUST be of type Decimal.
 * PricingCurrencyListUnitPrice MUST conform to [NumericFormat](#numericformat) requirements.

specification/datasets/cost_and_usage/columns/servicesubcategory.md

@@ -6,7 +6,7 @@ The Service Subcategory is a secondary classification of the [Service Category](
 
 ServiceSubcategory adheres to the following requirements:
 
-* ServiceSubcategory is RECOMMENDED to be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset).
+* ServiceSubcategory SHOULD be present in a Cost and Usage [*FOCUS dataset*](#glossary:FOCUS-dataset).
 * ServiceSubcategory MUST be of type String.
 * ServiceSubcategory MUST NOT be null.
 * ServiceSubcategory MUST be one of the allowed values.