At first, Frode Hegland shared his findings in the area of addressability. Marc-Antoine Parent pointed out that the WebAnnotation standard is extensible. Regarding the general notion of addressability, we were thinking about ways to augment conversation/dialogue, as one could ask questions to a virtual avatar and get them answered via voice from previous recordings, either by constructing language with the help of an AI or by semantical annotation. YouTube and SoundCloud support time stamp in the URL fragment to reference the start of playback in audio.
It looks like the group generally agrees that when it comes to data sources for the demo, we should work on and with what we ourselves produce during our effort (posts to the Journal, e-mails, call recordings, etc.) in order to bootstrap ourselves and our own communication. Hence, publishing, storing, retrieving and manipulation of those media fragments become relevant capabilities that must be provided by an OHS infrastructure and supporting document formats. Marc-Antoine encourages us to look at Apache Marmotta (a linked data platform), as it might already do most of the stuff we might want/need, plus it supports Memento.
The question is asked, how our calls are recorded. What about a TimeBrowser solution? It could record individual microphones and synchronize the audio tracks via an UTC time mark. Would be very useful for conferences, but we soon realize that we don’t have a lot of experience with audio, so we defer work on audio/video until a later stage, as text is easier to handle for now. Our material should always carry a timestamp, so it can be referenced in the future by the components we will build.
We also believe that there is no need to set up the human system versus the tool system and vice versa, as we’re clearly interested in the symbiosis of the two.
With interaction as the most basic element of the universe over symbols and their addressability, we recognize that the context of interactions, symbols and addressing is indeed very important, too, according how we understand connections.
We discuss the question if it would be a reasonable use case for knowledge representation to map Doug’s terms to their most similar resemblances in today’s terminology, potentially federated by the help of a time line? Does the knowledge representation work help with the shifting meaning of terms and concepts? Can one “import”/apply context?
Stephan Kreutzer gives an update on his progress over Easter: the work focused on writing a downloader for all posts as referenced by a WordPress blog URL, for such data to be converted to XML and JSON to make it available for the systems/components by Gyuri Lajos, Timour Shukin and Marc-Antoine. Marc-Antoine reads the WordPress RSS feed already, but that might not contain all data. Within the next few weeks, something in that direction might help us to make our components more interoperable and force us towards practical bootstrapping.