Enum values that ignore naming conventions in Media Capabilities

[dontcallmedom-bot]

While crawling Media Capabilities, the following enum values were found to ignore naming conventions (lower case, hyphen separated words):

• [ ] The value "smpteSt2086" of the enum HdrMetadataType does not match the expected conventions (lower case, hyphen separated words)
• [ ] The value "smpteSt2094-10" of the enum HdrMetadataType does not match the expected conventions (lower case, hyphen separated words)
• [ ] The value "smpteSt2094-40" of the enum HdrMetadataType does not match the expected conventions (lower case, hyphen separated words)

See Use casing rules consistent with existing APIs in Web Platform Design Principles document for guidance.

_{This issue was detected and reported semi-automatically by Strudy based on data collected in webref.}

[markafoltz]

I'm self assigning but not committing to making any changes here. Questions I have:

• Were these names chosen intentionally to match SMTPE standards IDs?
• How much effort is needed across the ecosystem to migrate?

[markafoltz]

Answering question 1:

Yes, they correspond to the following specification names, like e.g. SMPTE ST-2086

I suppose these could have been converted to e.g. smpte-st-2086 enum values instead.

Note, that the spec links in the biblio for these formats are currently broken.