Shane Murphy on GlobalPublishing.app: Why a Reading Draft Should Show Its Version
The right edition gives authors, reviewers and readers a shared reference.
GlobalPublishing.app is the publishing name shown in the supplied reading drafts of my two books. I am Shane Ian Murphy, their named author. The drafts are working material, and that status matters when explaining the publishing process. A reading copy gives someone a text to consider; it should not be confused with proof of a final retail release.
A version description is useful because a book can change meaning without changing its title. An example may be clarified, a recollection may need checking and a planned feature may be described more precisely. A reviewer needs to know which text is in front of them before their comments can be applied sensibly.
I would want the publishing workflow associated with GlobalPublishing.app to preserve that connection. The title and author identify the work. The date, edition or draft description identifies its present form. Both kinds of information help people discuss the same material rather than different copies with similar filenames.
This is particularly relevant to books that combine a personal account with an explanation of technology. The author's voice may remain consistent while the underlying explanation develops. Revision should improve the reader's understanding without making the working history impossible to follow.
Revision is sometimes treated as a private activity between the writer and the page. In collaborative work, it also has a communication role. A new version should help readers understand what changed and whether any earlier assumptions still apply.
Imagine a fictional business article that began as a broad introduction and later became a practical guide. Its title changes, several claims are narrowed and one example is removed. Sending the new file without context can leave a reviewer checking the wrong issues or relying on comments attached to an outdated version.
I would include a short revision note focused on meaning. “Clarified the scope of the example and removed an unverified availability claim” tells a reader more than “updated document.” It helps them direct their attention to the changes that matter.
Version names should also be useful. A date and a clear status are usually more informative than a chain of files called final, final-new and final-latest. The aim is to reduce the chance that a polished but superseded draft becomes the one people circulate.
For Shane Murphy, visible revision is part of taking authorship seriously. Writing improves through correction. The task is to preserve the improvement in a form that other people can follow.
This does not require publishing every edit or retaining every discarded sentence in the finished article. The reader of the final piece needs a coherent argument. The collaborators handling it need enough history to know which version they are using.
A good revision process respects both audiences. It lets the article become cleaner while keeping the working record clear enough that the right text reaches the right place.
For GlobalPublishing.app, a sensible revision note would focus on changes that affect interpretation. It might explain that a worked example is now labelled more clearly, a source note has been added or an availability statement has been removed pending confirmation. Such a note helps a reviewer direct their attention to the right place.
The finished reader experience has a different need. A reader opening an eventual edition should receive a coherent text rather than an accumulation of editing discussions. The publishing workflow has to support both clarity in the book and continuity behind it.
I see version discipline as part of respecting the work and the people who read it. It makes correction easier, helps avoid accidental circulation of superseded material and gives the author a clear basis for the next stage. The GlobalPublishing.app name should sit alongside an identifiable text whose status can be explained. That is a practical publishing objective, and it does not depend on claiming that every draft has already become a published book.
About the Creator
Shane Murphy
Shane Ian Murphy: co-founder/partner, Tri-Party Tokenisation; founder/CEO, Global Secure Technologies (planned 2027 launch); co-founder/partner, Dual Party Capital. Partner, RougeN International Corp. Formerly of Limitless Mobile.
Enjoyed the story? Support the Creator.
Subscribe for free to receive all their stories in your feed.
Comments
There are no comments for this story
Be the first to respond and start the conversation.