silverpill
@dave Standard types and properties are preferable (interop with existing software is easier that way). I'd use Audio type for podcasts and attachment property and Document type for transcripts. Collection type can be used for all kinds of collections.
If you need something that standard ActivityStreams vocabulary doesn't provide, Fediverse Enchancement Proposals is a good way to propose an extension to ActivityPub developer community.
Dave
The existing types are probably fine for most of the subclasses we need. So, the transcript property can just reference an Attachment object or set of Attachments if multiple.
The Podcast object itself can subclass Object of course, and then perhaps things like Podroll can just be a collection of Podcast objects since each will contain a guid and feedUrl.
Dave
That would allow bringing in the properties needed for both podcast apps and Fediverse apps to treat them the same way.
An example would be the transcript uri. Where does that go? It doesn’t fit into a Document or any of its sub-types cleanly. There will be many such properties.
Dave
#activitypub It seems like we will need to define a Podcast ActivityStreams object type. I’ve been trying to see if we can just transmute a podcast into an Audio or Video object type. But the loss of fidelity is so high. I think a dedicated object type is going to be pretty necessary.
０７６萌ＳＮＳ is a social network, courtesy of ０７６. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.
All ０７６萌ＳＮＳ content and data are available under the Creative Commons Attribution 3.0 license.