> But I realize now that the schema.org stuff is embedded only in the default view that does take all the values from Solr stored field. If I'm not using that view (as I'm not), then I guess I wouldn't get it anyway.

Sounds right, although there's nothing stopping you from using the `render_field_value` helper, I suppose. To me, it sounds like you have a use case that's slightly more advanced (and interesting) than this naive approach, and one that would benefit from some of the "advanced" schema.org features this patch neglects anyway.

I think it makes sense, though, to add a new ticket to provide some feature parity between the semantic fields and the solr fields, all the better if they can be used interchangeably with some of the templates and solr configs (why shouldn't you be able to use `add_index_field` with a field that is made available in ruby-land? I can't think of a problem off-hand..)