I encountered an expected value in the resource_id field in the response for timepoint 98011753 of the companies data streaming api, which was published at 2025-07-01T11:18:03.
The value was RS009557Z, which is 9 characters. Heretofore, of the approx 60 million timepoints I have processed, this value has always be 8 characters long. This is true across entity types, including in this case when the entity is a registered society.
It appears that the appropriate resource_id should have been RS09557Z, corresponding to the organization known as the Deben Climate Center, which also has some other recent timepoints (98011654 and 98011734).
How can it happen that an extra 0 was inserted into value and/or there was no validation that the resource_id is limited to 8 characters?
Are users able to rely on an expectation of 8 characters or do we need to be flexible enough to accommodate deviation from this otherwise 100% accurate standard going forward?