Jekyll/Prose.io

so, healthcare.gov: github/Jekyll/prose.io, and this is the Agile NoCMS approach now, replacing drupal as a shortest path content for anything solution? Weird, wild stuff.

Tuesday+

Several years ago, an acquaintance of mine started a project called "Topic Tag Tuesday". This was back when we were both spending more time on Twitter, and it was great entertainment. In order to hone my own writing, I would like to do something similar on Google+ to see if the entertainment value still holds up.

I am curious if the a Google+ Circle will lend itself to this sort of project, so I'm creating a new Circle, called Story ("Story Circle," see?). On Tuesdays, I'll post a blurb in the Public stream asking for topics. Comment on the blurb with a topic, and I'll add you to my Story Circle. Later that day, I'll write a short story incorporating one of the topics and post it back to the Story Circle, completing the loop.

If you're interested in this idea, follow me on Google+.

I'm crossposting this to my personal weblog...

I'm crossposting this to my personal weblog for further ingestion. This is partially an experiment in google+... when the article (which I shared to blogspot by email) receives the message, it will post as a draft, since google+ sends blogger (along with the original post here), the credentials I am using to transmit the post... Question: How to store a CDA document in a relational database « Health Intersections Pty Ltd Question: How to store a CDA document in a relational database. Posted on August 16, 2011 by Grahame Grieve. 2 commentsLeave a comment. A question (by the ask me a question link above): I am trying to...

Context+

Here are a couple initial thoughts about Google Plus:

1) I would really like to be able to create some content (like a photo album), and publish this to my circles, using different contexts for different circles. Fine grained, but I think this would be really cool. When you post on your blog, you post photos and then you write a story, and you think the story is the content. But when the post comes up as a result of a google search, it's the pictures - the real content - which you see. With short posts (Twitter, Posterous, Facebook, Google+), it becomes more obvious that what is readily shareable is videos and pictures (my content), not words (my context).

2) Because I can't access Twitter during the work day due to a firewall restriction, I appreciate how several techies I follow collect a week's worth of tweets into "Short Form Fragments" - why couldn't Google+ automatically do this for me, collecting a weeks "stream" into an automatic blogger post? Again, this would be very cool.

Canonical Context

The word canon has a literary meaning - in this context, a canon is a set of writing felt by someone to embody and exemplify the norms of those works which are non-canonical. An anti-canon is just a canon appointed by someone else to oppose a hegemonic canon.

In mathematics or informatics, a canonical form is a normative way of expressing or describing an object, so again, a norm created by a group to facilitate sharing of concepts.

In Superman comics, Star Wars books and so forth, "The Canon" refers to the fictional history which is considered (ostensibly by the publishers) as normative by the audience. Other histories may have taken place in alternate realities, parallel storylines and the like, but the canonical events are the ones which "actually" took place, and the chronology within which they are taken to have occurred. Fan fiction, for instance, is non-canonical.

Deepening Context and Content (cont)

For instance, here is an application I've talked about before, which one day I would like to build, what I have called a Content Engagement System, though I don't know if I really like this terminology. As with a standard CMS platform, a logged in user would be able to create a textual context, with associated images, video, documents... Within this textual context (which I will start referring to simply as 'context' since this translates roughly as 'with text', right?), another user can identify a phrase, and rather than linking out, the way a standard hyperlink works, link in. Sounds kind of odd, but this is essentially like adding a comment, except the comment is associated back to a phrase within the original context. In HTML terms, this is similar to a link to an anchor within the same page, and in a textbook we would identify this as a footnote.

Okay so far. A blogger posts something, which is then considered canonical, after which anyone else can add footnotes, and these offer an alternative view. A use case then: say I am writing a novel, which is serialized in weekly installments. The math is something like, 1000 words/week = 52,000 words/year, which then gets bundled up into EPUB or PDF and flogged off on Kindle, Smashwords or whatever. The idea is to create demand through serialization, then capitalize on the demand with the actual content.

But, and here's the thing. I want to engage my audience. And but, I want to entertain my audience. And but, a vocal minority within this audience typically demands something edgier; or racier; or, well, smuttier. Which, for the purposes of illustration, let's assume is not really my style. So what I want to provide is the canonical safe version of my novel, and a mechanism, a backstage, which allows the audience created by the canonical story to add (share) their own non-canonical additions to the story, which can then be linked to from within the canonical context as an alternative or supplement. This is similar to a literary parallax (events viewed from multiple vantage points).

More on this at some point. This is an idea I really want to pursue... but it is hard to articulate, so bear with me.

Deeper Context and Content

I've posted several times now about what I consider the differences between context and content, and why the word "content" kind of annoys me. It's okay, I don't mind being annoyed, and in the right context, content is fine. What I find annoying is that the two terms augment each other, but, so often, one is used when the other is more appropriate. For instance, if I have a web page that you can use to download a PDF of an article I have written, and this web page contains an excerpt of the article - the PDF is the content. Everything on the page, as far as I am concerned, is the context for your act of downloading. Of course, this is important if I am concerned about monetizing, since I have no problem with requiring a specific digital signature or some sort of payment; and I feel that everything else, the context, is like a smile. Why not give this away?

It's quite simple really. People require, create, digest and absorb context. But people like stuff. They like content, because it is something they can grasp onto, whether it's a PDF, an MP3, JPEG, AVI. Something "file-ish." The reason I bring this up, I suppose, is because, well, these things are easy. You can set up a microphone, you can use Prince, DocBook or FOP to turn your words into something more portable in a document format... then you can shade down your context a bit, broaden it, focus attention on the page content. Everything else is really just part of the transmission wrapper. The rest is just part of the vector.

I mean really, is a platform like Blogger or Wordpress actually a Content Management System? No, at best, these are discontent platforms. They separate us from content by masquerading context as content. It's not a bad thing, but I feel it's something we need to move past. You take good pictures, make a commodity out of your pictures. You tell good stories, make a commodity out of your stories. Allow people to focus through the context.

Context, content and getting over ourselves...

I am a huge fan of Lucas Gonze's weblog, where he wrote something recently which strikes me as quite profound.

Keep music from the web in the web. Don't go to a music blog, download a track, and then listen in iTunes.

Instead, he advocates bookmarking and playing music in the page that contains it, once again returning to fundamental link between URI and resource, between index and content.

What, for that matter, is a Content Management System? The term is a necessary evil; it's not like it is meaningless. But when you use this term to refer to WordPress or Blogger, I get an uneasy feeling, and reading Gonze's comment really cemented for me the reason why. The text on the page in front of you? It's not content. It's context. The page may provide content, but it is itself a context for whatever content it provides.

More on this later, just passing around the lightbulb moment, as it were.

Reader, Writer, User Points: Engagement Engines

This comes as a response to an ongoing discussion at weblit.us regarding user points and reward systems for online fiction readers. Essentially, the motivation for a user points system is to increase engagement by giving readers something to achieve. The downside is that in order to implement a points system, as a writer you need to produce more, or deny some of your readership access to writing in which they would normally participate. This is problematic.

The system I am trying to sketch out here works within a larger framework that I am proposing, which I am calling an engagement engine. It works like this:

A writer begins with a blank slate, on which she can add descriptions of people, places and things. These are big categories that structure the engagement engine. As a writer, you are able to write as much as you want, but you cannot publish a new person, place or thing until the system allows you to do so - shortly after you start writing, you receive a gift (much like a gift in a social networking environment), which upon opening reveals itself to be, for instance, a place. You use this gift to breathe life into one of the locations you have already privately given a description, and this location is now available for use in your story. After you describe your location more deeply, you receive another gift, and this in turn allows you to breathe life into one of the characters you have described. Now you have a place and you have a person. You can start to really tell your story.

In an engagement engine, multiple writers are supported. This is not essential to the points and rewards system, but I honestly think this is an important component in creating a community, by creating healthy competition and collaboration. As opposed to a content management system, an content engagement system, applies many of the concepts of game-play and social networks, and these work best if they operate within and encourage a wider community.

What really drives the engagement system is the act of creating content, so as you add more content to the system, you receive more gifts, which allows you to breathe life into more people, places and things. This may seem artificial, but I am hazarding a guess that it actually plays well to a strength of many writers that I have known: they are more creative when faced with restrictions and challenges. And there is no limit on the amount of detail, narrative and dialog you can write, or the number of people, places and things you can describe - it's just that you can't actually publicly use these people, places or things until the system has allowed you to breathe life into them. Which means you will want to use your best ideas, and that is what you do anyway.

So this is where the points system comes into play. As your story is published in serial and people read it, you collect extra points from them toward the gifts you use to breathe life into your creations. So you might say "I need 50 more readers before I can add this really cool story arc," and your existing reader base have an incentive to pass the word along, because they benefit from the gifts you receive.

The more readers read a writer, the more that writer can write. This defines story arcs, and encourages reader and writer engagement in an organic fashion. This is by no means a complete description of what I am describing when I say engagement engine, but it is a start. Please feel free to leave a comment with any questions.

Instant Metafiction

It has been a hectic month so far, for a variety of reasons, and I'm glad that I deferred/diverted my plans for National Novel Writing Month this year. Kudos to all of you who are participating, and particularly to those of you in the Weblit community who are simultaneously keeping up with serialized writing. This is quite frankly an amazing achievement!

Several months back, I invested some time (okay, a weekend) in developing a framework for what I call "Instant Metafiction" - which I was planning to use for NaNoWriMo this year. I have mentioned this before, but, because I want to capture the project properly before moving on (and eventually taking it to the next level), I am going to describe it in a fair detail here.

The idea was to make it possible to create a finished product resembling metafictional works inspired by David Foster Wallace's Infinite Jest and Mark Danielowski's House of Leaves, which are characterized by narratorial insertions like footnotes, endnotes and sidebars. To do this, I would use a source document conforming to the DocBook document specification, typically used for technical manuals, which provides ample opportunity for annotation.

Using this approach, I could then use the standard transform package to generate a final metatext as an ePub version, an XHTML version, or a PDF version from the same source. Using DocBook would facilitate two other things, scheduling and crowdsourcing.

Scheduling is handled by using Blogger as a backend. Like many 'blogging platforms, Blogger allows you to date a post in the future. When the day arrives, the post is published. Conveniently, Blogger also uses labels, so I was able to label all posts I wanted to serialize with the same label. With a handful of lines of XQuery hosted on Google AppSpot (using Java and Saxon 8 to run the XQuery), I could now take the Atom syndication from Blogger, and convert it into DocBook.

Crowdsourcing is also handled by Blogger. Like any 'blogging platform, Blogger allows comments, which are then published in a separate syndication. A small modification to the XQuery used to extract the main Atom feed allowed any comments authored by me to be added to the DocBook source as a sidebar element (I had by this point chosen to focus on sidebars instead of endnotes for sylistic reasons).

By ignoring any other comments, the final metatext remains my own; however, if someone comments on a chapter, I can comment back with a response. And this response gets integrated into the metanarrative as a sidebar. In this way, as people read the narrative, the story is deepened. I am not sure how successful this would actually be, but it seemed like fun, and the tools are all free.

Beyond a weekend project using free technology, this approach offers several advantages - using an existing CMS can be limiting, as it is hard to extend its functionality unless you are familiar with its plugin hooks, and you are hosting your own deployment. This was not something that appealed to me. To my mind, integrated crowdsourcing may be a very important facet for serialized online literature, as it encourages deeper engagement, and it breaks down the barrier between author and audience. And it is something print literature just cannot do.

I would be happy to discuss any of the ideas and approaches described above further. This is definitely a project I will revisit in the near future, when time is more plentiful. I am just looking for a good excuse to do so.

Memory and Games: Book as Single Page Application

From time to time I find myself finding a use for Jeremy Ruston's TiddlyWiki. TiddlyWiki is what has been dubbed a "single page application" or SPA, because what it really amounts to is an HTML page, complete with a JavaScript active layer which allows one to add, edit, show, hide and reorder content layers. When you have made the desired changes to your TiddlyWiki, you use your browser to save the entire file. I have found TiddlyWiki to be especially useful for creating information on the go using a USB device.

One of the things I appreciate about my workplace is the "leave one; take one" bookshelf, where recently I discovered a copy of an old Steve Jackson game book called "The Crown of Kings" - sort of like a Choose Your Own Adventure book, except you roll dice a lot, and you keep track of your Stamina and Skill statistics; you fight monsters as you explore. I believe there were four or five books in the series, and you could carry your "character" over from one to the next. The sort of thing you couldn't publish as a book in this day and age, because this sort of technogy has been subsumed by FaceBook and iPhone applications.

But this book does something that completely blew me away, that I have never really seen in a web application: it relied on memory. See, when you start the game, you consult an appendix which contains all of the various spells you can learn, indexed by a three letter code, along with Stamina cost and effect. At various points in the story, you are given a choice of several three-letter spell codes you can cast. You select a spell by its code, and go to the appropriate page, where you pay the cost and the resulting effect takes place.

But the trick is this - you can only look at the appendix one time, at the beginning of your adventure. And if you forget what all the spells do, you can injure yourself, or do something foolish. The game does not actually test your ability to be a warrior in real life, but it does test your problem-solving ability, and it tests your real life ability to remember important details.

Well, any book can be like this. If a book forces me to flip around, I need to remember what page I was on, in order to return to it. This is a disadvantage of a print book, of course. Book applications remember things for us. Browsers bookmark for us. We do not need to remember as much. I honestly do not think this makes either medium beter, just different.

But this got me thinking about how different forms of memory work. Imagine I can add annotations to a book I am reading. I get a pencil and I scribble notes in a margin. Over the years, these fade, or I lend the book to someone else, lose it on the bus and buy a different edition, which has been annotated by someone else.

Now imagine I can add annotations to an online book. I can add semantic tags to deepen the meaning and store the details of these tags in a data store for my next reading. I can share this information with other people, adding to the meaning of the book as a whole, without actually changing the book's narrative. If I am an author of the book, I can even retag the book to change the book's narrative.

But what if I add semantic data to the book that is purely transient... it evaporates as soon as I close the book, but it persists as long as I have the book open, as I flip through the chapters. How would that be?

I imagine something slightly more interactive than your average book, but less interactive than the simplest of video games. Perhaps a detective story, where you are the detective, and as you add semantic data to the narrative, the narrative reveals itself in more depth. And then, what if two people could arrange to read the same book, at the same time, so that the narrative evolved along two separate axes?

This would be a book as a single page application.