Context reference check is not collapsing whitespace

[jstone-psi]

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

When I created test labels that has a line break in a particularly long observing system component name ("The Origins, Spectral Interpretation, Resource Identification, Security, Regolith Explorer (OSIRIS-REx) Spacecraft"), I noticed that the validate tool was raising a warning that the component name did not match the context object.

This warning does not appear when there are no line breaks in the component name. However, it does appear again when I have multiple spaces in the name.

🕵️ Expected behavior

The data type of Observing_System_Component/name is UTF8_Short_String_Collapsed, so these extra spaces and line breaks should be collapsed into a single space before the check is performed. When the values are collapsed, no warning would occur for these labels.

📜 To Reproduce

1. Find a label that validates correctly.
2. Add additional spaces in the middle of the Observing_System_Component/name
3. Try to validate the new label, and observe the warning

🖥 Environment Info

• Version of this software: validate 3.7.1
• Operating System: MacOS Sonoma 14.7.5 with OpenJDK openjdk 23.0.2

📚 Version of Software Used

validate 3.7.1

🩺 Test Data / Additional context

sample_labels.zip

orex-hk.txt

🦄 Related requirements

• 🦄 As a user, I want to includes titles and aliases in context product name validation #970
• 🦄 As a user, I want to receive a WARNING message when the Target_Identification.name does not match the value in the context product #861
• 🦄 As a user, I want to receive a WARNING message when the Observing_System_Component.name does not match the value in the context product #857

⚙️ Engineering Details

No response

🎉 Integration & Test

No response

[al-niessner]

@jordanpadams @jstone-psi

I am not a lawyer nor do I play one on television nor do I want to do either. However the definition of the UTF8_Short_String_Collapsed says that it is collapsed white space not will be or should be or could be. In other words, what is written in the XML is collapsed as needed not that the reader should collapse it. Is this going to become a DDWG thing?