Visual ArtWork may also have an ownership history: owner may be a person or organization and history of ownership should include dates when the owner was changed.
This is already possible to describe using OwnershipInfo when considered from the point of view of the Person or Organization that owns a Product (or Service). Commonly a VisualArtwork could also be described also as a Product to capture its physical attributes, so a VisualArtwork special case might not be needed.
It could possibly be argued that the range of typeOfGood for this case could be expanded to include CreativeWork to enhance this capability.
Your use case is coming at this from the inverse point of starting with a CreativeWork to record its ownership history. This suggests a need for an ownedBy property that also has OwnershipInfo in its range, and CreativeWork, Product and Service in its range.
We normally do not encourage inverse properties unless really needed as the required relationships can usually be described using what is currently available. If a compelling case why the inverse would be needed in this case I may well support it.
I am creating a catalogue raisonne platform and in art ownership information (current and historical) is vital.
It is right that inverse properties are not needed, as they can be checked "the other way around", but problem is that "owns" applies only to Products.
I think the target of "owns" should go down do "Thing", as most "things" have kind of ownership
This issue is being tagged as Stale due to inactivity.