"Publish" in the context of this page means publication as an act of scholarly communication.

Things people could conceivably want to publish

• evidence for new insights
• a process or milestones in a process
• publish notes and annotations
• a collection (rights permitting)

Places where they might want to publish them

• print only journals
• print plus PDF journals, for example Literary and Linguistic Computing
• born digital journals, for example Digital Humanities Quarterly
• blogs
• ManyEyes
• Second Life
• anywhere else on the Web

Question: What would it mean to work towards a more dynamic publication model for humanities researchers?

What "Dynamism" Might Mean

• temporal behaviors
• user annotation
• user interaction
• transclusion (http://ajaxian.com/archives/purple-include-transclusions-you-know-you-want-them)
• RSS, COinS, RDF

Possible Publication Models for MONK

0. Narrative description of MONK operations and narrative or tabular display of data and outcomes.

1. Static screenshot of a MONK visualization or operation.

2. State-based access to MONK operations, allowing a reader to step into an activity sequence and take control of operations at an arbitrary point.

3. State-based access to MONK operations, allowing a reader to step into an activity sequence and take control of operations at an arbitrary point, also altering or adding to the dataset.

4. State-based re-presentation of a MONK operation, allowing a reader to step backward or forward in the activity sequence. Will require a viewer (see below). Viewer could be embedded in an arbitrary public Web page--a refereed article in DHQ, say.

5. Export of MONK data to a third party environment (for example, to ManyEyes).

Dynamism Table

Requirements for Viewer

• embeddable in (potentially) any Web page (just like a YouTube video)
• tightly coupled to command (state?) history in application
• user can step backwards and forwards through that history
• user can annotate (either publicly or privately)
• it knows about rights management