Replies: 2 comments 1 reply
-
Although I do not know the answer to this question, I will say that it is
an excellent question. Sub events and sub domains do not have enough
representation because they are so hard to configure as a property.
…On Thu, May 12, 2022, 4:18 PM Scott Ertz ***@***.***> wrote:
Does the PodcastSeries object have a place for episodes in the way an
Event has subEvent? Or do we simply implement the Episode page with a
partOfSeries and allow indexing systems to figure it out on their own?
—
Reply to this email directly, view it on GitHub
<#3108>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFVNUX23RDEQEIL2M4OBW3VJVYR7ANCNFSM5VZQIKOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
As per the example on the PodcastEpisode page, the relationship between an episode and its series is derived via the partOfSeries property. You also have the option of referencing a season it is part of using partOfSeason. Providing the referenced entities are available to those consuming the data, that should be sufficient. If you did want to explicitly reference episodes from within the PodcastSeries description, you could use the hasPart property. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Does the PodcastSeries object have a place for episodes in the way an Event has subEvent? Or do we simply implement the Episode page with a partOfSeries and allow indexing systems to figure it out on their own?
Beta Was this translation helpful? Give feedback.
All reactions