The 6.3.9.3 paragraph states:
The scope attribute with a value that conforms to the syntax http://www.smpte-ra.org/430-1/2017/KDM#mic-key-type-{ID}, where {ID} conforms to the lowercase UUID string representation specified in IETF RFC 4122, shall be associated with the following KeyType value:
The 6.3.10.2 paragraph states:
{ID} in the table above shall conform to the lowercase UUID string representation specified in IETF RFC 4122 and shall be equal to a KeyId value of the key to which the ForensicMarkFlag applies.
I find it curious as to why {ID} is in uppercase, while the statements specify that the {ID} "shall conform to the lowercase UUID string representation specified in IETF RFC 4122..."
The 6.3.9.3 paragraph states: The scope attribute with a value that conforms to the syntax http://www.smpte-ra.org/430-1/2017/KDM#mic-key-type-{ID}, where {ID} conforms to the lowercase UUID string representation specified in IETF RFC 4122, shall be associated with the following KeyType value:
The 6.3.10.2 paragraph states:
{ID}in the table above shall conform to the lowercase UUID string representation specified in IETF RFC 4122 and shall be equal to aKeyIdvalue of the key to which theForensicMarkFlagapplies.I find it curious as to why
{ID}is in uppercase, while the statements specify that the{ID}"shall conform to the lowercase UUID string representation specified in IETF RFC 4122..."Would it make more sense to change
{ID}to{id}?