3.1.5 Allocated Tags

The Allocated Tags column represents the set of tags assigned to tag sources which are specifically applicable to allocated charges resulting from a data generator-calculated split cost allocation.

AllocatedTags MUST adhere to the following requirements:

• AllocatedTags MUST be of type JSON Object (serialized as a String where necessary).
• AllocatedTags MUST conform to StringHandling requirements.
• AllocatedTags MUST conform to KeyValueFormat requirements.
• AllocatedTags MUST adhere to the following nullability requirements:
  • AllocatedTags MUST be null when a charge is not related to a data generator-calculated split cost allocation.
  • AllocatedTags MAY be null in all other cases.
• When AllocatedTags is not null, AllocatedTags MUST adhere to the following requirements:
  • AllocatedTags MUST NOT include resource tags already present in Tags.
  • AllocatedTags MUST include all applicable user-defined and data generator-defined tags for the AllocatedResourceId.
  • Tag keys that do not support corresponding values MUST have a corresponding true (boolean) value set.
  • Tag values MUST match the provided values unless true (boolean) is applied to valueless tags.
• Data generator-defined tags MUST adhere to the following requirements:
  • Data generator-defined tag keys MUST be prefixed with a predetermined, data generator-specified tag key prefix that is unique to each corresponding provider-specified tag scheme.
  • Data generator-specified tag key prefixes SHOULD be publicly documented.
• User-defined tag keys in all user-defined tag schemes MUST include a predetermined, data generator-specified tag key prefix that is unique to each corresponding user-defined tag scheme when the data generator has more than one user-defined tag scheme.

This example illustrates various tags produced from multiple user-defined and data generator-defined tag schemes. The first two tags illustrate examples from two different, user-defined tag schemes. The second tag is produced from a valueless, user-defined tag scheme, so the data generator also applies true as its default value.

The last two tags illustrate examples from two different, data generator-defined tag schemes.

    {
        "userDefinedTagScheme1/foo": "bar",
        "userDefinedTagScheme2/foo": true,
        "providerDefinedTagScheme1/foo": "bar",
        "providerDefinedTagScheme2/foo": "bar"
    }

A set of tags assigned to tag sources that are applicable to allocated charges in data generator-calculated split cost allocation.