No semantic difference between Read Activity and View Activity

[akuckartz]

In https://github.com/w3c/activitypub/issues/353#issuecomment-1384299974 it was noted that there is no semantic difference between the Read activity with View activity.

[evanp]

I believe that there is in fact a semantic difference between Read and View. In particular:

• Read primarily applies to textual content. For example, we would not apply Read to an Image, Video, or other visual medium. View would make more sense for these.
• Read may be applicable for Audio objects that are translated or read from primarily text items, such as audiobooks. It would probably make more sense to use Listen here, but in some applications Read would be appropriate.
• Even for textual works, there is a semantic difference between View and Read. For example, clicking through on a link to an article may count as "viewing" the article, and it may make sense to track a longer experience, especially scrolling through a long article to the end, as "reading" it.

It is unfortunate that the example for View in the Activity Streams Vocabulary document is for reading an Article, which is not helpful for making these distinctions. I am adding a page in the Activity Streams Primer specifically for representing this kind of activity.

[evanp]

We had two resolutions here:

1. I added a note to the primer about experiencing objects: https://www.w3.org/wiki/Activity_Streams/Primer/Experiencing_objects
2. We added a TODO for Activity Streams 2.0 to change the technically-correct example for View to something more illustrative of best practices

Thanks!