Yes, this property seems to be required for the experience fragments to
work properly. Without this property the experience fragment selection
doesn't show the variant you have to type in the variation manually.
Also, as I was using the newest experience fragment component (from WCM
core), I ran into an issue wherein if this property is not present the
experience fragment component doesn't even show the experience fragment
(when configured on template). So, I think the issue here is that this