Thanks @vholland. @elf-pavlik - care to take a look?

The term 'interaction' is included in every property and class that is related to this issue, I doubt that this is a best practice for good vocabulary design. Unfortunately, it is obviously necessary to keep everything under the schema.org namespace ... ;)

@Zazi yes it natural consequence of various design tradeoffs, to drift towards having soft / pseudo namespaces in various places. Although it might not look particularly elegant it does keep several things simpler for publishers/webmasters. I think we can live with it for now.

@vholland LGTM 😄 thank you!

1. I wonder why userInteractionCount and not simply interactionCount ?
2. At some point we still could try to find a way of linking to the collection/container with actual references to all the interactions (e.g. Comment - all the comments, Share - all the shares, Follow - all the followers). In lines of what I tried to brainstorm in this comment replace interactionCount with interaction #137 (comment)

@elf-pavlik I was going to use interactionCount, but that already exists with different semantics. It seemed confusing to completely change the property's meaning.

If people would rather, I can go back to that name.

I just noticed

• https://schema.org/downvoteCount
• https://schema.org/upvoteCount
• https://schema.org/answerCount
• ...

https://schema.org/docs/search_results.html#q=count

Merged in. We have some work on deprecation UI, but the new stuff shows up, e.g. http://webschemas.org/InteractionCounter (also in sdo-ganymede test site)

SGTM. Feel free to kick back merges back to me.

Some HTML changes: #593