From f44b9168f9ac9960f36539d1f930ce3a531929d1 Mon Sep 17 00:00:00 2001 From: Joaquin Date: Thu, 31 Oct 2024 00:08:57 -0700 Subject: [PATCH] SubAccountName: convert normative statements into bullet points --- specification/columns/subaccountname.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/specification/columns/subaccountname.md b/specification/columns/subaccountname.md index b64f56fd6..7fcd2caaf 100644 --- a/specification/columns/subaccountname.md +++ b/specification/columns/subaccountname.md @@ -2,7 +2,11 @@ A Sub Account Name is a display name assigned to a [*sub account*](#glossary:sub-account). Sub account Name is commonly used for scenarios like grouping based on organizational constructs, access management needs, and cost allocation strategies. -The SubAccountName column MUST be present in a [*FOCUS dataset*](#glossary:FOCUS-dataset) when the provider supports a *sub account* construct. This column MUST be of type String. If a charge does not apply to a *sub account*, the SubAccountName column MUST be null. +The SubAccountName column adheres to the following requirements: + +* The SubAccountName column MUST be present in a [*FOCUS dataset*](#glossary:FOCUS-dataset) when the provider supports a *sub account* construct. +* This column MUST be of type String. +* If a charge does not apply to a *sub account*, the SubAccountName column MUST be null. See [Appendix: Grouping constructs for resources or services](#groupingconstructsforresourcesorservices) for details and examples of the different grouping constructs supported by FOCUS.