Contextive knowledge sharing outside of development environments

[FH-Inway]

In Ubiquitous F# in Contextive, the Ubiquitous Language Tool | fsharpConf 2023, @chrissimon-au shared a vision where Contextive is not just a tool for sharing knowledge in development environments. Instead, it acts as a core for a whole ecosystem of tools that enable the continued exchange of knowledge with a ubiquitious language.

Examples include a Slack chat bot, a browser extension and an Office 365 integration. A proof of concept demo is shown in the video for the Slack chat bot.

In the discussion of #28 , proof of concept implementations for all three examples were mentioned. This discussion is intended to continue this discussion.

Have fun!

[chrissimon-au]

Thanks for setting this up @FH-Inway!

I've been thinking about this topic for a while, but there are a lot of options/tradeoffs to consider.

I've setup a survey to help capture structured data on folks preferences. Feedback on the survey itself welcome in this discussion as well, but in the first instance, if anyone interested in this topic could fill out the survey, that'd be super helpful!

https://forms.gle/NgSahheaQg1FLX2w7

After some initial discussions, I'll start preparing a draft roadmap.

[chrissimon-au]

Survey result summary here: https://docs.google.com/forms/d/1BQsXmBZM7ORjPb3_H74elLgWcY6zgtGYQ1L8ftIlWqA/viewanalytics

[chrissimon-au]

Back onto this topic... only had a couple of survey respones, but I think enough to formulate a plan.

Here's a rough uncommitted roadmap for getting started on this work:

1. Editor agnostic configuration #54 - it represents a major change to the configuration approach, so would prefer to get started on expanding beyond the IDE after this is done, and it will simplify more flexible ways of identifying which context is relevant in a given usage scenario
2. Browser Extension #73 - see ticket for details on how it's proposed to configure it, including how to identify which context is relevant on a given page
3. Support sharing definitions from multiple sources into the current work environment #43 - once the above are done, it should be straightforward to complete this, which would then offer the option for all the terms to be sourced and hosted externally

Beyond that, the 'later' pile to be prioritised once getting through the above, would include:

• Office 365 Addin #72
• Prod-ready chatbots (slack, teams, etc.)
• Mechanisms to support updating (or suggesting updates) to definitions from other locations