You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.
The gist is that a type of CreativeWork, for instance a MusicRecording might need to reference the associated rights for various purposes. A realistic example is in the instance of paying for a MusicRecording it is convenient to reference the rights as an array property on the MusicRecording object. This enables the frontend of an application to retrieve JSON data for the object, key into the percentageShares prop and combine the values in the rights array to split the payments.
An idiomatic way of creating this reference is not currently designed in the spec though so application developers might come up with adhoc solutions that fit outside the spec. Additionally, having a rights array on CreativeWork objects does not adhere to the type properties in schema.org. We should have a consistent way of referencing rights via CreativeWorks that is defined within the spec, but also allow for the flexibility for application developers to serialize this in a convenient way
The text was updated successfully, but these errors were encountered:
Please see #29 (comment) for context.
The gist is that a type of
CreativeWork
, for instance aMusicRecording
might need to reference the associated rights for various purposes. A realistic example is in the instance of paying for aMusicRecording
it is convenient to reference therights
as an array property on theMusicRecording
object. This enables the frontend of an application to retrieve JSON data for the object, key into thepercentageShares
prop and combine the values in therights
array to split the payments.An idiomatic way of creating this reference is not currently designed in the spec though so application developers might come up with adhoc solutions that fit outside the spec. Additionally, having a
rights
array onCreativeWork
objects does not adhere to the type properties in schema.org. We should have a consistent way of referencingrights
viaCreativeWork
s that is defined within the spec, but also allow for the flexibility for application developers to serialize this in a convenient wayThe text was updated successfully, but these errors were encountered: