It won’t become a problem. People very much overstate the significance of errors and warnings in Google’s search tools.
The error is there to tell you precisely one thing: they won’t show a rich snippet in the search results. That’s it. It won’t affect anything further long term or otherwise harm your site. That’s just not how it works.
The problem is that while there are workarounds, presumably by changing the metadata to a different type that Google considers to be valid for reviews, that’s not something you could or should do unless it is a relevant type for your resource.
While there are no repercussions for simply having an error in the schema data, Google would take a very dim view of sites trying to manipulate the search results to include snippets that they feel don’t apply.
Regardless, these workarounds are not something we can roll out to customers due to this risk so we have to include the data that most generally fits and complies with the schema.org standard. If Google chooses to do something different, that’s down to them. But at least other search engines will display the rich snippets without issue.
If there is a more applicable type that applies to your content that complies with Google’s metadata schema then you may be able to make adjustments in the xfrm_resource_view template.
