A key feature of this approach is that we can create relationships between the entire corpus: relationships between discrete sections of enormous texts written over 500 years of continuous discourse. Each time a new text is edited and sources are identified, these asserted relationships can be inverted, and we can, for example, automatically collect all the places a paragraph written in the 12th century is discussed or referenced over the next 500 or so years of medieval thought.
Unrealized Potential of Linking Secondary and Primary Sources
This approach un-taps only some of the potential of linked research. While it helps us to link together the primary sources of the corpus as they become available, we do not yet have a mechanism to link together the many secondary articles quoting, referencing, and analyzing various parts of the SCTA corpus.
In an ideal world, we would like an automated way to collect (or be notified about) any discrete section of a primary source text within corpus that has been cited or discussed in any secondary article.
With a list of referencing secondary articles, we can, in our display to the user, offer a list of distributed secondary articles (i.e. hosted anywhere) that discuss the primary source passage in question.
Using LinkedData Notifications to connect distributed scholaraly discussion
What might this look like in practice?
Let's imagine I'm writing an article about a topic discusssed in scholastic philosophy and I'm quoting primary source material from the scholastic corpus. Because of the possibilities inherent in semantic markup, my authoring platform (currently my Jekyll blog you are currently reading) can embed meaningful metadata into every citation. Using RDFa my quotation of a passage can include a reference to the URL for that cited passage, where property="cito:discusses" and resource="http://scta.info/resource/b1d3qun-qnveid" are added the blockquote element as attributes. (Think of this as a cutting edge research footnote, designed for creating connections rather than for being siloed at the bottom of a printed page). In this case the property describes the relationship between the quotation and the targeted resource. Such a reference might look like the following:
Quod non videtur, quia secundum Augustinus in Sermone communi de uno martyre "si servasset in se homo bonum quod in illo creavit Deus, id est imaginem suam, semper laudaret dictum non solum lingua sed et vita" etc.
Following the emerging specifications for Linked Data Notifications, this embeded link becomes the lynch pin for aggregating a distributed discussion. Each resource in the SCTA database has an associated inbox, which can be found by simply de-referencing the targeted resource, searching for the property http://www.w3.org/ns/ldp#inbox and retrieving the value of that property. Now, when this article is published, a "notification" that this target resource is being discussed in this article can be sent to the resource inbox. This notifications is saved in the respective inbox and awaits use and consumption by other clients interacting with this resource.
The following video shows the above described interactions in action.