@Gargron could Mastodon be more rigorous in creating RDF definitions of the arbitrary assortment of properties and types it's pioneered?
For example, for practical reasons I merged this:
But it's not accurate to say "manuallyApprovesFollowers is an ActivityStreams property".
It is why we generally only support a partial vocabulary of the "Mastodon types": https://github.com/go-fed/activity/issues/122
I think i mentioned this to @nightpool before too.
@cj happy to answer any questions or work with you to create something that gofed can use, but since we don't use or consume OWL ourselves, we wouldn't be able to provide anything normative or keep it up to date. JSON-LD documents are not really very static, so I don't think applying a static type system in the way that go-fed does is a very productive enterprise, and it leads to a lot of manual work keeping the typings up to date.
@nightpool oh gotcha! Thanks for clarifying. I still think it's be important work, if only for clearer interoperability and building better tooling. For ex the Owncast dev has already hit problems w/ Mastodon not accepting valid ActivityStreams. That sort of stuff would be great to avoid for Mastodons types too.
@cj I'm always supportive of patches to improve Mastodon's activity streams processing, i just don't think OWL is the right tool to do so. I haven't seen any issues filed from owncast recently (and I read almost all issues that come through the Mastodon issue tracker) but please link me to them if you find them.
@nightpool OWL is just a schema definition language, from which the generated code that does serialization was found to serialize into something Mastodon wouldn't accept. I'll look into that more today and file an issue if one hasn't yet. If you know of a better SDL than OWL2, I'm all ears, it's not my favorite, but it's expressive enough to capture most of ActivityStreams.
I'll take a first stab at outlining the toot vocabulary and in the next day or two post for help on SocialHub