Open thill-odi opened 4 years ago
I think in this case it's useful to have a 'miscellaneous' property. Use-cases that have emerged on W3C calls have included user-uploaded path traces and audio descriptions. Defining a separate property for each of these would be laborious and difficult to maintain, so I think a grab-bag is useful here.
oa:userContributedContent
also arguably reduces complexity for data-processors. Conceivably platforms will want to distinguish between publisher- and user-generated content. Relying on this property is IMV much lighter-weight and less error-prone than running a publisher/creator comparison to determine the provenance of each media item.
From @ldodds:
"oa:userContributedContent seems a bit of a "miscellaneous" property. Why handle this separately? You could equally annotate the pictures/images, etc of the route with publisher / creator information as a means to identify the source. "