Let me try to explain on a simple example. Please take a look at Front | Portfolio of CDM Gaps, Solutions and Trials
For simplicity, let us just look at two data models that are managed on the PoS: Gaps and Solutions.
Here is example of a Gap: Faciliate matching of CDM solutions to capability needs | Portfolio of CDM Gaps, Solutions and Trials. Couple of solutions are linked to it, click on them to see what solutions look like.
Both Gaps and Solutions have a relatively complex model compared to data models used on social media. Gap is a simpler one, so I’ll only explain the gap data model:
- Gap has a “title”, a “motivation”, a “summary” and 1…* “rationales”.
- each rationale links to 1…* “CM function” taxonomy terms. (With other words, each rationale can be tagged by one or more taxonomy terms)
In addition, gaps can be “endorsed” by 1…* “Organization” and automated matching is established to the solutions that may be answering this gap.
Solution is a bit more complex, but it’s the same type of building blocks - title, abstract and then links to various taxonomies, some of them simple tags and some of them separate text pieces with tags attached to these pieces of text. E.g. a solution has 1…* use cases, and each use case has 1…* CM function associated with it. This is what enables gap/solution and solution/solution matching at the moment.
Data models for gaps and solutions are OK as they are. What s not OK is that PoS is a Centralised site, or “yet another knowledge silo”. What I would like to do now is to develop a “federated PoS”.
The idea is that a Gap that’s posted on one site can be integrated on other sites - or not, depending on what the site owner wants to show on their site. And that users can choose what they want to see independently on the site - including search and automated gap/solution matching.
The idea is also that a title & summary of this gap is shared with the rest of the Fediverse, so that people can commend on it. Or vote on it. which in turn could be used as part of the ranking algorithm when showing the data to the users…
*Long story cut short, I want to know how to encode a “Gap” in a way that’s compatible with
title & abstract are clear, that’s what every mastodon message also has.
But how to encode the “motivation” and the 1…* rationales, each with 1…* associated tags?
Basically I’m just looking for a way to express the meanings and relations between bits and pieces of a structured message that’s then shared through Fediverse using ActivityPub protocol.
What I hope to achieve is:
- share the message with other types of fediverse services, so that MANY people can interact with them. I presume that these services will only pick up Title + abstract and ignore the rest
- At a same time allow services of the same type to pick up the whole message, correctly interpret it as “this is a Gap” and correctly interpret each piece of the message and then decide what they want to do with it.
On top of this, the ActivityPub provides nice mechanisms for sharing updates and even for indicating that Alice has stated that solution S addresses Gap G - another useful information for a service that’s trying to match gaps and solutions in semi-intelligent way…