ClioWire

Presentation

ClioWire is the platform developed by the EPFL Digital Humanities master students and the members of the EPFL Digital Humanities Lab (DHLAB). The platform is an hybridation between Twitter and Wikipedia. The ambition of this platform is to curate simple open bricks for historical knowledge, shaped as short texts. It is meant to be based on no prefixed ontology, but collectively negotiated conventions and reformatting by bots. This is what works well on Wikipedia and in our Digital Humanities bachelor course. It is meant to offer easy onboarding, i.e. the process in which one get accustom to a new system/platform (even for beginners and people with only very basic IT skills). This is what works well on Twitter. One goal is to offer simple and robust long-term archiving for bricks of historical knowledge.

ClioWire curates Pulses as basic bricks for historical knowledge. They constitute some sort of minimal information unit coding relationship between entities and sources. They typically encode what is usually referred as events. Pulses are artificial construction that can be continuously being remolded and combined in order to create greater pieces of knowledge. We suggest to try to model our historical knowledge as an immense collection of Pulses.

Main characteristics

Their main characteristics are the following

• Pulses are 140-character long textual sequence (like tweets) (this constraint may be dropped)
• Syntax of Pulses follows some (evolving) conventions but no strict rules (like tweets)
• Pulses can be written by humans or by machine, and read by humans or machines (like tweets).
• Pulses have a first author but can be modified and rewritten by anyone. They are fundamentally considered as a common good (unlike tweets)
• Sequences of pulses are fully versioned. The history of their modification can be visualized (unlike tweets)
• Pulses can be attached to geographical coordinates, temporal coordinates, sources (URLs), document segments
• Each Pulses as a unique universal ID (like tweet), that can serve as reference in other Pulses and on the web.
• Pulses can be tagged as dubious or any other classification characterizing the trust one can have. The tagging itself can be partly done by bot (like for tweets)
• In sum, tweets are particular kind of Pulses, but Pulses are more general than tweets

The managing system for Pulses enables to do the following operations

• Inserting massive numbers of Pulses based on existing sources. If a bot imports Pulses massively, it will be their first author.
• More generally applying bot operation at a massive scale on Pulses (like for Wikipedia)
• Retrieving all the Pulses mentioning an entity (people, place) and visualizing them as timelines or maps or both.
• Retrieving all the intervention of a given user (i.e creation or editing of Pulses)
• Retrieving all the Pulses mentioning a given source (URL)
• Visualizing the editing history a sequence of Pulses
• Mapping the worldwide activity of Pulses
• Computing the list of the most active user, the most edited Pulses (like in Wikipedia)
• More things in the same spirit …

Examples

Coding Pulses

It is possible to use standardized vocabulary but this is not compulsory. For instance, someone may simply write in natural language, without any source or conventional naming

• Francesco Raspi lived on the Rialto Bridge.

However, this Pulse may being tagged as unreliable. It is better to automatically produce a Pulse.

• Francesco Raspi is the owner of parcels 514 in the Napoleonic Cadaster of 1808.

In order to increase possible articulatation between Pulses, hashtags can be used. Like for Twitter, there are no predefined hashtags but communities can negociate common ways to articulate the content of pulses. A community may decide to use very generic hashtag in order to increase the potential for generic processing. A list of core hashtags are currently under discussion.

Entities

Each entities (Place, people, book, segment, volume, etc) is associated with a unique hastag.

Example: #MarinoZorzi is an entiy

Predicate #Eq

Predicate #Eq defines the commutative equivalence between two entities. This means that one can be replaced by another. It can be used to disambiguate mentions.

Syntax: #Eq (Entity or URL) (Entity or URL)

Ex: #Eq #MarinoZorzi #MarinoZorzi34 Ex: #Eq #MarinoZorzi http://..

Predicate #In

Predicate #In defines that one entity is a subpart / is included in another

Syntax: #In #Venice #Italy Syntax: #In #PietyandPatronage_p3 #PietyandPatronage Syntax: #In #YoungFilmmakers #Filmmaker

Coding knowledge

Pulses can also be used to code knowledge ungrounded in Space and Time like:

• Francesco Raspi is the son of Domenico Raspi

Or better:

• SonOf #FrancescoRaspi #DomenicoRaspi in http://…

Attributing ID

Pulses can be used to document segment, artwork images and other entities that do not typically receive conventional name can receive a unique Id (possibly generated automatically)

• IDassignment #ImprintingCini434 http://…

Coding inferred facts

Pulses can be used to code inferred fact like

• Francesco Raspi is the grandson of Giovanni Raspi (inferred base on Pulse1, Pulse2 and Pulse3 and Rule3)

Encoding Rules

Inferring rules may also be coded with Pulses (using convention of variables)

• R: If ($A is the son of $B) and ($B is the son of $C$) then ($A is the grandson of $C)