[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href=""?><rss xmlns:content="" xmlns:wfw="" xmlns:dc="" xmlns:atom="" xmlns:sy="" xmlns:slash="" version="2.0">
  4. <channel>
  5. <title>Jon On Tech</title>
  6. <link></link>
  7. <description>Just a nerd trying to save the publishing industry. Again.</description>
  8. <lastBuildDate>Mon, 13 May 2013 23:04:07 +0000</lastBuildDate>
  9. <language>en</language>
  10. <sy:updatePeriod>hourly</sy:updatePeriod>
  11. <sy:updateFrequency>1</sy:updateFrequency>
  12. <generator></generator>
  13. <atom10:link xmlns:atom10="" rel="self" type="application/rss+xml" href="" /><feedburner:info xmlns:feedburner="" uri="jonontech" /><atom10:link xmlns:atom10="" rel="hub" href="" /><item>
  14. <title>How to Avoid CMS Selection Confuction</title>
  15. <link></link>
  16. <comments></comments>
  17. <pubDate>Mon, 13 May 2013 22:53:31 +0000</pubDate>
  18. <dc:creator>Jon Marks</dc:creator>
  19. <category><![CDATA[Future of CMS]]></category>
  20. <category><![CDATA[Ramblings]]></category>
  22. <guid isPermaLink="false"></guid>
  23. <description><![CDATA[In which I reveal the two most important questions one should ask when selecting a CMS.]]></description>
  24. <content:encoded><![CDATA[<blockquote class="dylan"><p>The backstage manager was pacing all around by his chair<br />
  25. &#8220;There&#8217;s something funny going on&#8221; he said &#8221; I can just feel it in the air&#8221;<br />
  26. - LILY, ROSEMARY AND THE JACK OF HEARTS</p></blockquote>
  27. <p>Let me tell you a secret. I probably shouldn&#8217;t, but I&#8217;ve been reading a few more &#8220;How To Select A CMS&#8221; posts recently and, truth be told, they&#8217;re the same as they were when I stopped reading them way back in 2011. Exactly. The. Same. Which is a bit depressing really.</p>
  28. <p>So this is just between you and me: The features of the CMS don&#8217;t matter. At least not in the long term compared to the big things that&#8217;ll fuck you over. You know that big RFP feature matrix? Horseshit. The lovely demos in the vendor Dog And Pony shows? Yawn. Interviewing all your stakeholders? Ho hum &#8211; they don’t really have a clue.</p>
  29. <p>Sure, you might have a decent idea of the features you need today. Maybe even in six months? But you don&#8217;t have a scooby what&#8217;ll happen next year. You could get broadsided by your vendor going to hell. Or that new CIO who wants to (de)centralise. Or that company merger. Or your department mandating Technology X or Open Source or Some Insane Security Policy. Or the thing that doesn’t exist yet that’s going to disrupt your ass back to the stone age.</p>
  30. <p>Here is what matters. Your content needs to be able to outlive the technology that houses it. This is the most important question you should ask in any selection process:</p>
  31. <blockquote><p>Question 1: &#8220;If we select you, and it all goes tits up, how would we get our content out of your system and into something else?&#8221;</p></blockquote>
  32. <p>If it is painless to get your content out in a sensible form, you can&#8217;t go too badly wrong on your product selection. This is especially true if you don&#8217;t need to shell out a whole lot of cash up front for the software, but you are paying-as-you-go.</p>
  33. <p>So that&#8217;s the software problem solved. But, as we all know, it is actually the services where you’re spending a whole lot of cash. So you’ve got your integrator estimate of a few tens or hundreds of man days. That’s a lot of bodies scuttling around on your project doing a whole lot of very important things. So take a step back and ask yourself the next most important question.</p>
  34. <blockquote><p>Question 2: “What the fuck are all those people actually doing, and what part of that work could we keep if we moved to another system?”</p></blockquote>
  35. <p>Some of the work is independent of (and should probably predate) the technology selection. Strategy, design, information architecture, content type modelling, business process modelling and all that good stuff. But on the technology side, there are some pieces that take a fair bit of time and should result in a portable asset. At the very least, all work creating the actual HTML should be independent of the system. If you’re using a standard templating language like XSLT (bite me, @pmonks) or FreeMarker or mustache.js, parts of your templating layer could migrate. And of course any hardcore business logic should be exposed by an API that could outlive your CMS. But if all these busy systems integration bees are plodding away on tech that you need to chuck should you change system, you’re probably doing something wrong.</p>
  36. <p>So it is as simple as that. Read your Darwin again. Change happens. And it will keep happening at an ever increasing rate. Pick something that can change with it. Make portable content and portable technical assets. Don’t make monoliths.</p>
  37. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  38. <wfw:commentRss></wfw:commentRss>
  39. <slash:comments>22</slash:comments>
  40. </item>
  41. <item>
  42. <title>Evil Doctor Browser vs CSS3 Spiderman</title>
  43. <link></link>
  44. <comments></comments>
  45. <pubDate>Tue, 28 Jun 2011 12:21:41 +0000</pubDate>
  46. <dc:creator>Jon Marks</dc:creator>
  47. <category><![CDATA[tablets]]></category>
  48. <category><![CDATA[android]]></category>
  49. <category><![CDATA[iOS]]></category>
  50. <category><![CDATA[mobile]]></category>
  51. <category><![CDATA[performance]]></category>
  52. <category><![CDATA[spiderman]]></category>
  53. <category><![CDATA[uiwebview]]></category>
  54. <category><![CDATA[webkit]]></category>
  56. <guid isPermaLink="false"></guid>
  57. <description><![CDATA[Here at Kaldor Towers, we've been spending a lot of time comparing the performance of the browsers on various phones and tablets. Here is a video of a CSS3 animation powered Spiderman intro running on lots of devices at the same time.]]></description>
  58. <content:encoded><![CDATA[<blockquote class="dylan"><p>Well, she begged, she cried<br />
  59. She pleaded with me all last night<br />
  60. She wants me to go out<br />
  61. And find somebody to fight<br />
  62. - HERO BLUES</p></blockquote>
  63. <p>Here at Kaldor Towers, we&#8217;ve been spending a lot of time comparing the performance of the browsers on various phones and tablets. Our latest scientific study involved the newly created <a href="">CSS3 Spiderman</a> by Anthony Calzadilla (<a href="!/acalzadilla/">@acalzadilla</a>). Have a look at all <a href="">his other animations too</a>. He rocks.</p>
  64. <p>Anyway &#8211; to the experiment. The video below shows our test devices, all of which run <a title="WebKit" href="">WebKit</a>, showing the animation at the same time. <strong>WARNING</strong>: The way Spiderman is dismembered/vanished/frozen in time by some of the villainous devices may offend some viewers. And apologies for the excessive shaking and bad lighting.</p>
  65. <p><object width="640" height="390"><param name="movie" value=";hl=en_US&#038;feature=player_embedded&#038;version=3"></param><param name="allowFullScreen" value="true"></param><param name="allowScriptAccess" value="always"></param><embed src=";hl=en_US&#038;feature=player_embedded&#038;version=3" type="application/x-shockwave-flash" allowfullscreen="true" allowScriptAccess="always" width="640" height="390"></embed></object></p>
  66. <p>The devices used for the experiment:</p>
  67. <ul>
  68. <li>Samsung Galaxy S GT-I9000 running Android 2.2 (Froyo.XXJPO)</li>
  69. <li>Samsung Galaxy Tab GT-P1000 running Android 2.2 (Froyo.XWJJ7)</li>
  70. <li>Motorola XOOM MZ601 running Androod 3.0.1 (Honeycomb H.6.1-38-1)</li>
  71. <li>Google Nexus S running Android 2.3.4 (Gingerbread)</li>
  72. <li>iPad 2 running iOS 5 Beta 1 [REDACTED. DETAILS LATER]</li>
  73. <li>iPad 2 running iOS 4.3</li>
  74. <li>iPad 1 running iOS 4.3.1</li>
  75. <li>iPhone 4 running iOS 4.3.1</li>
  76. </ul>
  77. <p>The repeatable testing methodology:</p>
  78. <ul>
  79. <li>Kill all other applications running on the device</li>
  80. <li>Browse to <a href=""></a> on the device browsers</li>
  81. <li>Run the the whole animation so that all the assets are preloaded</li>
  82. <li>Turn off the sound on all devices except one to avoid going insane</li>
  83. <li>Start all the animations again at roughly the same time</li>
  84. <li>Watch in horror as spidey is mutilated</li>
  85. </ul>
  86. <p>With great power comes great responsibility. Android and iOS both have great power. Time for them to improve their browsers. Especially the Android devices.</p>
  87. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  88. <wfw:commentRss></wfw:commentRss>
  89. <slash:comments>9</slash:comments>
  90. </item>
  91. <item>
  92. <title>Newsstand in a Nutshell</title>
  93. <link></link>
  94. <comments></comments>
  95. <pubDate>Thu, 09 Jun 2011 08:38:15 +0000</pubDate>
  96. <dc:creator>Jon Marks</dc:creator>
  97. <category><![CDATA[Ramblings]]></category>
  98. <category><![CDATA[tablets]]></category>
  99. <category><![CDATA[api]]></category>
  100. <category><![CDATA[apple]]></category>
  101. <category><![CDATA[iOS]]></category>
  102. <category><![CDATA[iPad]]></category>
  103. <category><![CDATA[Newsstand]]></category>
  104. <category><![CDATA[publishing]]></category>
  105. <category><![CDATA[pugpig]]></category>
  106. <category><![CDATA[Zinio]]></category>
  108. <guid isPermaLink="false"></guid>
  109. <description><![CDATA[A year ago I had a dream that I was having an intimate chat with Steve Jobs about newspaper and magazine applications. "All the news apps currently out there ", he said after a thoughtful pause, "are shit. Why on earth should I have to wait tens of seconds, or even minutes, after I start the app before I can see the first page of my publication?"]]></description>
  110. <content:encoded><![CDATA[<blockquote class="dylan"><p>Good and bad, I define these terms<br />
  111. Quite clear, no doubt, somehow<br />
  112. Ah, but I was so much older then<br />
  113. I&#8217;m younger than that now<br />
  114. - MY BACK PAGES</p></blockquote>
  115. <p>A year ago I had a dream that I was having an intimate chat with Steve Jobs about newspaper and magazine applications. &#8220;All the news apps currently out there &#8220;, he said after a thoughtful pause, &#8220;are shit. Why on earth should I have to wait tens of seconds, or even minutes, after I start the app before I can see the first page of my publication?&#8221;</p>
  116. <p>&#8220;Well, Steve-o&#8221;, I said. &#8220;The main problem is that we can&#8217;t quietly download issues in the background. The only way we can do that is shiftily declare our app as a VoIP app in which case we get some background capability. But it only works after starting and stopping the app, and your digilent App Reviewers would reject the app anyway.&#8221;</p>
  117. <p>&#8220;Good point, Boofie, good point&#8221;, he said. &#8220;I think I better fix that.&#8221;</p>
  118. <p>And, with the release of Newsstand for iOS 5, he did.</p>
  119. <p><a href=""><img class="aligncenter size-medium wp-image-1932" title="features_newsstand_folder" src="" alt="" width="300" height="143" /></a></p>
  120. <h3>Newsstand is here</h3>
  121. <p><a href="">Newsstand</a> was announced this week as part of the fanfare that was the WWDC 2011. In essence, a new icon will appear on the home screen of all users and will be used as a folder to store edition based content. It looks rather similar to the iBooks apps. One big difference is that iBooks is an app that one needs to download from the App Store. Newsstand is baked into the operating system.</p>
  122. <h3>End Users: Newsstand is a Clever Folder</h3>
  123. <p>From the point of view of an end user, Newsstand behaves like an iOS folder. Previously, each news application you had would sit on your home screens like any other app. Now, news apps will instead sit inside the Newsstand folder/application. This will give a few nice user interface advantages too. Instead of a generic icon for the publication, Newsstand will show the cover of the latest issue. And it will be able to tell you if a publication is new, and send you push notifications when a new issue is ready for your reading pleasure. As I understand it, publishers can choose to ignore newsstand completely and submit apps as they&#8217;ve always done. But if they do this, they won&#8217;t get the benefits of the new API that apps in the Newsstand can use.</p>
  124. <h3>Developers: Newsstand is an API for background download</h3>
  125. <p>For me, this is the cool part. Steve has come good on his promise. If, when developing your application you register as a Newsstand application, you get access to the <code>NewsstandKit.framework</code>. This lets you do two new things. Firstly, it lets you add and remove issues from the Newsstand application on the user&#8217;s home screen. Secondly, and most importantly, it lets you download your new editions in the background, even if the app isn&#8217;t running in the background. So the user will wake up in the morning, and your new edition will already be on his device. #FTW</p>
  126. <p>Apart from this new API, you write your apps in exactly the same way. You submit them to the App Store in exactly the same way, and they are downloaded from the App Store in exactly the same way. So developers of stand alone news applications don&#8217;t need to worry about Apple stepping on their toes. iOS 5 is wonderful news for them, not a competitor.</p>
  127. <p>It seems that there are some things that the API won&#8217;t support yet. It&#8217;ll work great if you&#8217;re a title that publishes weekly or daily like the good old print days. It isn&#8217;t clear how it will help if you want constantly updated content pushed to your daily edition &#8211; it appears that every background download job relats to a whole issue, a.k.a. a new icon in the Newsstand. We&#8217;ll need to dig deep to see how this can be done.</p>
  128. <h3>Publishers: Newsstand doesn&#8217;t change the publishing workflow, or economics</h3>
  129. <p>Newsstand does not provide any authoring tools, so you create editions in the same way you&#8217;ve always done. If you&#8217;ve got an existing standalone application, not a huge amount changes. You&#8217;ll still pay Apple their 30% as you do at the moment. Your users will still pay for your editions through the App Store or through In-App Purchases.</p>
  130. <p>There seems to be a common misconception that people can discover edition based content (news, magazines, etc) through Newsstand. Now I don&#8217;t believe this is true. Newsstand will only show you titles that you have downloaded already. However, there probably will be a new way to search these titles through the App Store, which will create a new little market dynamic all on it&#8217;s own. I guess there might well be a view of the App Store embedded into Newsstand like there is for iBooks at the moment.</p>
  131. <h3>Winners and Losers</h3>
  132. <p>It&#8217;s a sad fact of life that OS-baked app &#8220;innovations&#8221; from the big boys will <a href="">destroy smaller players that have a competitive product</a>. From my perspective, the winners here are the end users, publishers and developers of stand-alone news applications. Companies like Adobe (with their Digital Publishing Suite) and those that create tools that sit on top of InDesign to create standalone apps (<a href="">Woodwing</a>, <a href="">Mag+</a>, <a href="">Aquafadas</a>, etc) are largely unaffected, unless they had an idea they could also create their own store front.</p>
  133. <p>The losers are the poor sods that are creating aggregator readers and charging outside of the App Store. I&#8217;m thinking mainly of people like poor <a href="">Zinio</a> who I think are going to struggle. For publisher consortiums that are more about the relationships than the technology (for example <a href="">Next Issue Media</a>), things might still be okay if they just adopt the new technology. We mustn&#8217;t forget that iOS isn&#8217;t the only platform out there and that Android is becoming increasingly important. But, for 2011 at least, iOS is really the only platform out there that matters.</p>
  134. <h3>And a Shameless Plug</h3>
  135. <p>And for those of you that don&#8217;t know, my <a href="">new company</a> is working on a hybrid iOS/HTML5 based reader called Pugpig. We&#8217;re lauching very very soon, so follow <a href="">@thepugpig</a> for the latest news. Here is a sneaky screenshot of our Pugpig Guide sample book in the Newsstand.<a href=""><img class="aligncenter size-medium wp-image-1933" title="ppnews" src="" alt="" width="300" height="200" /></a></p>
  136. <p>Disclaimer: The API may change before iOS 5 gets released, so I might be completely wrong about all of this. And, in my dream, Steve didn&#8217;t actually use the word &#8220;shit&#8221;.</p>
  137. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  138. <wfw:commentRss></wfw:commentRss>
  139. <slash:comments>36</slash:comments>
  140. </item>
  141. <item>
  142. <title>Epic Fail Epics</title>
  143. <link></link>
  144. <comments></comments>
  145. <pubDate>Wed, 27 Apr 2011 20:25:45 +0000</pubDate>
  146. <dc:creator>Jon Marks</dc:creator>
  147. <category><![CDATA[Ramblings]]></category>
  148. <category><![CDATA[fail]]></category>
  149. <category><![CDATA[poetry]]></category>
  151. <guid isPermaLink="false"></guid>
  152. <description><![CDATA[I want to write a poetry book, and I want y'all to write it for me. It's going to be a poetry book documenting epic tech fails in 2011. So we've got lots of material from the last few days, and quite a bit more from the year. More than happy to have multiple poems per incident.]]></description>
  153. <content:encoded><![CDATA[<blockquote class="dylan"><p>My mind weaves a symphony<br />
  154. And tapestry of rhyme<br />
  155. - IF DOGS RUN FREE</p></blockquote>
  156. <p>I want to write a poetry book, and I want y&#8217;all to write it for me (*). It&#8217;s going to be a poetry book documenting epic tech fails in history. So we&#8217;ve got lots of material from the last few days, and quite a bit more from the year. More than happy to have multiple poems per incident.</p>
  157. <p><a href=""><img class="aligncenter size-medium wp-image-1919" title="epicfailepics" src="" alt="" width="239" height="300" /></a></p>
  158. <p>What we need for each poem is:</p>
  159. <ul>
  160. <li>The poem, of course. Any form allowed &#8211; haiku, limerick, sonnet, childrens, rambling prose</li>
  161. <li>A brief, two sentence description of the epic fail event</li>
  162. <li>The date of the epic fail event</li>
  163. <li>An illustration or two, handdrawn. It can, of course, by crap. Lots of colours would be nice.</li>
  164. </ul>
  165. <p>Submissions in the comments. If you email/tweet me the images I&#8217;ll add them. And I&#8217;ll add one or two or my own creations as soon as I can pop open a beer. <b>Entries close on Friday 6th May</b>.</p>
  166. <p>(*) By entering the competition you give up all rights to your masterpiece. The editor&#8217;s decision on what to publish is final.</p>
  167. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  168. <wfw:commentRss></wfw:commentRss>
  169. <slash:comments>23</slash:comments>
  170. </item>
  171. <item>
  172. <title>Selling Out Friends on Empire Avenue</title>
  173. <link></link>
  174. <comments></comments>
  175. <pubDate>Sun, 24 Apr 2011 19:33:25 +0000</pubDate>
  176. <dc:creator>Jon Marks</dc:creator>
  177. <category><![CDATA[Ramblings]]></category>
  178. <category><![CDATA[Social]]></category>
  179. <category><![CDATA[This Blog]]></category>
  180. <category><![CDATA[empire avenue]]></category>
  181. <category><![CDATA[social]]></category>
  182. <category><![CDATA[stocks]]></category>
  183. <category><![CDATA[twitter]]></category>
  185. <guid isPermaLink="false"></guid>
  186. <description><![CDATA[In order to understand the social media douchebaggery that happens on our interwebs, you need to hold your nose and dive in some times. I try most things, but get bored of them pretty quickly. So I figured I had to try Empire Avenue (EAv), the stock trading game in which the stocks are people, and the bigger the douchebag the higher the value. Fortunately you don’t need to piss off (invite) your friends to get started.]]></description>
  187. <content:encoded><![CDATA[<blockquote class="dylan"><p>I’d go hungry, I’d go black and blue<br />
  188. I’d go crawling down the avenue<br />
  189. There’s nothing that I wouldn’t do<br />
  190. To make you feel my love<br />
  191. - MAKE YOU FEEL MY LOVE</p></blockquote>
  192. <p>In order to understand the social media douchebaggery that happens on our interwebs, you need to hold your nose and dive in some times. I try most things, but get bored of them pretty quickly. So I figured I had to try <a href="">Empire Avenue</a> (EAv), the stock trading game in which the stocks are people, and the bigger the douchebag the higher the value. Fortunately you don&#8217;t need to <del>piss off</del> invite your friends to get started.</p>
  193. <p><a href=""><img src="" alt="" title="Empire Avenue Logo" width="300" height="43" class="aligncenter size-full wp-image-1905" /></a></p>
  194. <p>First thing to say about this is, unlike most others, it is actually quite fun and quite addictive. By this I mean in the same way a stock market simulation game is fun and addictive. So I can recommend giving it a try by wasting an evening. Your value is based on the usual supply/demand/market forces, but also on your &#8220;score&#8221; on various social networks &#8211; currently Twitter, LinkedIn, FaceBook, Flickr and YouTube. I spent longer on it than I did on SecondLife (in which I spent all my money on poker and whoring and was destitude in about two hours) and it&#8217;s more fun than Quora ever got (which was probably when it was down due to the recent EC2 fiasco).</p>
  195. <p>For me the best thing about the 4 hours of my life I&#8217;ve so far wasted was randomly bumping into and having a chat with Jeremiah Owyang (<a href="!/jowyang">@jowyang</a> / (e)JOWYANG). At the time I was broke so could only buy 1 share in what is likely to become one of the biggest stocks on EAv. And he unwisely invested in (e)BOOF. It was interesting talking with all these big cheeses discussing the potential impact of EAv. There are theories that this&#8217;ll be the next big thing and that the social currency may even have some real world value in the long run. I&#8217;m rather skeptical on that. Although if you&#8217;re a moron you can by Eaves (the game currency) with your hard earned real cash.</p>
  196. <div id="attachment_1907" class="wp-caption aligncenter" style="width: 310px"><a href=""><img src="" alt="" title="BOOFandJOWYANG" width="300" height="132" class="size-medium wp-image-1907" /></a><p class="wp-caption-text">If Jowyang thinks I&#039;m a good investment ... Click to Enlarge</p></div>
  197. <p>I made some pretty dumb-ass investments in (e)IANT, (e)BLOEM, (e)PIEW, (e)BIGBLUEMOOSE and (e)SLWR who were all overvalued already and, seeing as they&#8217;re not douches, probably aren&#8217;t going to rise much. I bought some (e)IRI seeing she&#8217;s responsible for me trying this thing. And in a fit of madness I bought me a piece of (e)PMONKS, which is surely going to be worthless pretty soon. I&#8217;ll dump that after this post I think.</p>
  198. <p>I wasn&#8217;t very surprised to see quite a few of my Twitter followers on EAv already, but only two of my FaceBook friends were on. Good thing too, &#8217;cause my real friends are a worthless bunch that wouldn&#8217;t be worth shit to a shrewd Empire Avenue investor like me.</p>
  199. <p>I have no idea about the strategy of this thing. A good way to make a bit of cash seems to be to monitor the &#8220;Recent Arrivals&#8221; section, and speculatively buy shares in most of them. If you&#8217;re quick, maybe a Google search, in particular to see if they&#8217;re rich in Twitter followers. People with a lot of followers seem to double in value as soon as they link their Twitter account to their profile, so you have to be fast. Price hikes from activity on the other network take much longer as, because they&#8217;re not public like Twitter, EAv has to run off and index them only once they&#8217;ve got your details. I&#8217;m told the algorithms value LinkedIn recommendations. Which I, for one, don&#8217;t.</p>
  200. <p>Finally, a few strategy tips from me, which I sure to be excellent seeing as I&#8217;ve got about 4 hours experience:<br />
  201. - Unlocking achievements gets you cash. So link everything like your blog, FaceBook, LinkedIn and join a few communities<br />
  202. - People seem to search the Recent Arrivals section and buy people cheap if they look cool, before they manage to link their Twitter profiles and share prices rise<br />
  203. - Buy (e)BOOF</p>
  204. <p>Have fun out there.</p>
  205. <p>   <!--- CUT AND PASTE FROM HERE --><br />
  206.    <script type="text/javascript" charset="utf-8">
  208.    //enter your exact ticker
  209.    var eav_t = "BOOF";
  210.    //Size 1 is 100x100 and Size 2 is 190x167
  211.    var eav_s = 2;
  212.    //Do not edit the following:
  213.    var eav_is_ssl = ("https:" == document.location.protocol);
  214.    var eav_asset_host = eav_is_ssl ? "" : "";
  215.    document.write(unescape("%3Cscript src='" + eav_asset_host + "blog/?t=" + eav_t + "&#038;l=" + escape(window.location) +"&#038;s=" + eav_s + "' type='text/javascript'%3E%3C/script%3E"));
  216.    </script><br />
  217.    <!--- TO HERE --></p>
  218. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  219. <wfw:commentRss></wfw:commentRss>
  220. <slash:comments>3</slash:comments>
  221. </item>
  222. <item>
  223. <title>Google’s Moat and Castle</title>
  224. <link></link>
  225. <comments></comments>
  226. <pubDate>Mon, 18 Apr 2011 22:27:18 +0000</pubDate>
  227. <dc:creator>Jon Marks</dc:creator>
  228. <category><![CDATA[Ramblings]]></category>
  229. <category><![CDATA[amazon]]></category>
  230. <category><![CDATA[android]]></category>
  231. <category><![CDATA[app]]></category>
  232. <category><![CDATA[apple]]></category>
  233. <category><![CDATA[chrome]]></category>
  234. <category><![CDATA[cloud]]></category>
  235. <category><![CDATA[facebook]]></category>
  236. <category><![CDATA[google]]></category>
  237. <category><![CDATA[mobile]]></category>
  238. <category><![CDATA[twitter]]></category>
  240. <guid isPermaLink="false"></guid>
  241. <description><![CDATA[In a fit of madness, I tried to draw a summary of everything Google is involved in, and all of their main competitors. Utter madness I tell you.]]></description>
  242. <content:encoded><![CDATA[<blockquote class="dylan"><p>With your mercury mouth in the missionary times<br />
  243. And your eyes like smoke and your prayers like rhymes<br />
  244. And your silver cross, and your voice like chimes<br />
  245. Oh, who among them do they think could bury you?<br />
  246. - SAD-EYED LADY OF THE LOWLANDS</p></blockquote>
  247. <p><em>Short version: I drew a picture while watching crap on TV. Scroll to the bottom to see it.</em></p>
  248. <p>I seem to be bumping into Google absolutely everywhere these days. When you take a step back and think about it, it really is astonishing how many areas they play in, and how many competitors they have. And it changes fast. In the last few days, they&#8217;ve <a href="">ditched Google Video</a>, acquired <a href="">PushLife</a> (their <a href="">94th acquisition</a>) and are rumoured to be <a href="">building a FlipBoard killer</a>.</p>
  249. <p>I also recently read a wonderful article, <a href="">The Freight Train That Is Android</a> by VC Bill Gurley (<a href="">@bgurley</a> &#8211; follow him now). He introduces his article with a famous quote from investor-extraordinaire <a href="">Warren Buffet</a>, who said:</p>
  250. <blockquote><p>In business, I look for economic castles protected by unbreachable moats</p></blockquote>
  251. <p>In Google&#8217;s case, the economic castle is search and ads. That is the cash cow. Gurley then go on to say:</p>
  252. <blockquote><p>Google’s aim is defensive not offensive. They are not trying to make a profit on Android or Chrome. They want to take any layer that lives between themselves and the consumer and make it free (or even less than free). Because these layers are basically software products with no variable costs, this is a very viable defensive strategy. In essence, they are not just building a moat; Google is also scorching the earth for 250 miles around the outside of the castle to ensure no one can approach it. And best I can tell, they are doing a damn good job of it.</p></blockquote>
  253. <div id="attachment_1891" class="wp-caption aligncenter" style="width: 236px"><a href=""><img class="size-medium wp-image-1891" title="GoogleOverviewLowv2" src="" alt="" width="226" height="300" /></a><p class="wp-caption-text">Click for large image. High Res available below.</p></div>
  254. <p>So, inspired by all of this, I drew a picture to give myself a birds-eye view of everything I know that Google is involved in as of 20:00 GMT on Monday 18th April 2011. They&#8217;re not winning on all fronts but they&#8217;re doing pretty well. &#8220;Social&#8221; is their weak point at the moment, which is why Larry P just announced that <a href="">25% of all Googlers bonuses depend on their social success</a>.</p>
  255. <p>Now I am sure I didn&#8217;t waste hours of my life on this beast and you&#8217;re all going to stick it on your wall at work and home. Here are the big versions:</p>
  256. <p><a href="">Download Hi-Res PDF</a>: 1.3 MB<br />
  257. <a href="">Download Hi-Res JPG</a>:  4.2 MB</p>
  258. <p>And feel free to point out all my cock-ups in the comments and I&#8217;ll update this next time my wife watches another shitty romcom.</p>
  259. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  260. <wfw:commentRss></wfw:commentRss>
  261. <slash:comments>22</slash:comments>
  262. </item>
  263. <item>
  264. <title>Crunch Time for RIM</title>
  265. <link></link>
  266. <comments></comments>
  267. <pubDate>Thu, 24 Mar 2011 23:11:48 +0000</pubDate>
  268. <dc:creator>Jon Marks</dc:creator>
  269. <category><![CDATA[Ramblings]]></category>
  270. <category><![CDATA[tablets]]></category>
  271. <category><![CDATA[android]]></category>
  272. <category><![CDATA[App Store]]></category>
  273. <category><![CDATA[apple]]></category>
  274. <category><![CDATA[BlackBerry]]></category>
  275. <category><![CDATA[google]]></category>
  276. <category><![CDATA[mobile]]></category>
  277. <category><![CDATA[playbook]]></category>
  278. <category><![CDATA[rim]]></category>
  279. <category><![CDATA[tablet]]></category>
  281. <guid isPermaLink="false"></guid>
  282. <description><![CDATA[Poor RIM took a beating this evening after announcing their quarterly financials. It all seems rather up and down. Probably more down. Here is my summary of their 2011 so far.]]></description>
  283. <content:encoded><![CDATA[<blockquote class="dylan"><p>Don&#8217;t even hear a murmur of a prayer<br />
  284. It&#8217;s not dark yet, but it&#8217;s getting there<br />
  285. - NOT DARK YET</p></blockquote>
  286. <p>Poor RIM took a beating this evening after announcing their <a href="">quarterly financials</a>. It all seems rather up and down. Probably more down. Either way, I think the next few months are going to decide if RIM have a role to play in The Great Mobile Wars This Decade. Here is my summary of their 2011 so far.</p>
  287. <p style="text-align: center;"><a href=""><img class="aligncenter size-full wp-image-1884" title="rim" src="" alt="" width="192" height="129" /></a></p>
  288. <p><strong>Bad News</strong></p>
  289. <p>In January, some douche decided that he&#8217;d launch the new careers site at I mean, seriously. Surely everyone reads <a href="">Urban Dictionary</a> these days. This is even better than  <a href=""></a> before they stuck in the clarifying hypen.</p>
  290. <p><a href=""><img class="aligncenter size-full wp-image-1881" title="RimJobTweet" src="" alt="" width="400" height="176" /></a></p>
  291. <p><strong>Good News</strong></p>
  292. <p>They took the site to the more sensible domain <a href=""></a>. It briefly redirected but the domain is completely gone now.</p>
  293. <p><strong>Good News</strong></p>
  294. <p>RIM have finally announced that their new tablet, the PlayBook, is shipping this month. It&#8217;s been delayed a few times so hopefully this is it. I think the name is okay, actually. Although if it is meant to refer to a basketball/football playbook, then it makes more sense in the US.</p>
  295. <p><strong>Bad News</strong></p>
  296. <p>It going to have a similar price to the iPad2. It is $500/$600/$700 for the models with 16GB/32GB/64GB RAM. This can&#8217;t be good for them. Tablets need to be cheaper than the iPad to get traction.</p>
  297. <p>At 7 inches, it is much smaller than most other tablets. It seems it ain&#8217;t going to be much good unless you tether it to your Blackberry. And there are still questions about battery life (which has not been mentioned in any spec sheets I&#8217;ve seen yet). Maybe another more detailed post about the features of the PlayBook some other time.</p>
  298. <p><strong>Good News</strong></p>
  299. <p>Their QNX operating system is interesting, and might mean they can run Adobe Flash faster than other Android based tablets. Flash on Android still needs to prove itself. And the fact that they&#8217;re not Android might be a differentiator in a world of<a href=""> Samsung Galaxy</a> and <a href="">Motorola Xoom</a>. Bad news here is that <a href="">some analysts are blaming poor battery life</a> on greedy Flash and the theory that QNX wasn&#8217;t designed for mobile usage.</p>
  300. <p><strong>Bad News</strong></p>
  301. <p>The fact that they&#8217;re not Android means they don&#8217;t have many apps at all. It&#8217;s pretty difficult to write apps for the PlayBook at the moment. This was highlighted in a hilarious blog post &#8220;<a href="">You win, RIM!</a>&#8221; by developer Jamie Murai that went viral. You should read it (seriously), and his <a href="">follow-up post</a>. RIM did respond to his rant pretty well I think. The fact that they&#8217;re trying to lure developers by chucking free PlayBooks at them is a sign of the times.</p>
  302. <p><strong>Good News:</strong></p>
  303. <p><a href=""><img class="aligncenter" title="qnx-android2" src="" alt="" width="562" height="326" /></a></p>
  304. <p>RIM have<a href=""> just confirmed</a> that they&#8217;ll run Android apps. Woot. It&#8217;s been rumoured for a while but they&#8217;ve confirmed it now. Some argue that this is an admission that their own developer SDK is a pile of shite. However, if they didn&#8217;t do this, I think they&#8217;ve have been dead in the water so it is a smart move. You won&#8217;t be able to download your RIM apps from the Android Marketplace (or the shiny new <a href=";node=2350149011">Amazon AppStore for Android</a>). Instead, developers will need to resubmit their apps to <a href="">BlackBerry App World</a>. This is probably okay.</p>
  305. <p>The highlights of the press release:</p>
  306. <blockquote>
  307. <ul>
  308. <li>BlackBerry PlayBook to support BlackBerry Java and Android apps</li>
  309. <li>Native C/C++ development support added, in addition to HTML5, Flash and AIR support</li>
  310. <li>Support from leading game engines: Ideaworks Labs (AirPlay) and Unity Technologies (Unity 3)</li>
  311. <li>BlackBerry PlayBook becomes a new market opportunity for all the developers who have already created over 25,000 BlackBerry Java apps and more than 200,000 Android apps</li>
  312. </ul>
  313. </blockquote>
  314. <p>It&#8217;s probably also slightly good news for RIM that GOOG might be about to annoy the developer community slightly with their <a href="">delayed open sourcing of Honeycomb</a>.</p>
  315. <p><strong>And finally</strong></p>
  316. <p>Note that I really want RIM to do well. The more players in this game the better, and a two horse race between Android and iOS is a bit dull. Having RIM and WebOS in the mix spices things up. And at least they&#8217;re getting a whole lot of press again. There is no such thing as bad publicity, right? Go RIM!</p>
  317. <p>&nbsp;</p>
  318. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  319. <wfw:commentRss></wfw:commentRss>
  320. <slash:comments>93</slash:comments>
  321. </item>
  322. <item>
  323. <title>Shooting down paywalls</title>
  324. <link></link>
  325. <comments></comments>
  326. <pubDate>Tue, 22 Mar 2011 12:44:50 +0000</pubDate>
  327. <dc:creator>Jon Marks</dc:creator>
  328. <category><![CDATA[Ramblings]]></category>
  329. <category><![CDATA[javascript]]></category>
  330. <category><![CDATA[new york times]]></category>
  331. <category><![CDATA[paywall]]></category>
  332. <category><![CDATA[publishing]]></category>
  333. <category><![CDATA[security]]></category>
  334. <category><![CDATA[sunday times]]></category>
  335. <category><![CDATA[wsj]]></category>
  337. <guid isPermaLink="false"></guid>
  338. <description><![CDATA[With the New York Times paywall coming up, I thought I'd dump some more paywall thoughts. Are secure paywalls even a good idea?]]></description>
  339. <content:encoded><![CDATA[<blockquote class="dylan"><p>Now there’s a wall between us, somethin’ there’s been lost<br />
  340. I took too much for granted, got my signals crossed<br />
  341. Just to think that it all began on a long-forgotten morn<br />
  342. “Come in,” she said, “I’ll give you shelter from the storm<br />
  343. - SHELTER FROM THE STORM</p></blockquote>
  344. <h2>The State of Paywalls</h2>
  345. <p>Another high profile publication is putting up walls. <a href="">The New York  Times</a> is planning on charging again. Their paywall is up in Canada, and will be up globally by the end of the month. And it looks to be one of the least secure implementations yet. They seem to have done everything on the client. So, first, the content is always actually on the page. They just pop an obscuring &lt;div&gt; on top of it so that you can&#8217;t see the content, and stop the browser scrolling. <a href="">This guy</a> has already written a 3-line script for dodging it which I&#8217;ll reproduce in full:</p>
  346. <p><code>//Prototype is already installed on NYTimes pages, so I'll use that:<br />
  347. $('overlay').hide();<br />
  348. $('gatewayCreative').hide();<br />
  349. $(document.body).setStyle( { overflow:'scroll' } );</code></p>
  350. <p>So one way for non-techies go get around the paywall is to use something like the above in a <a href="">Greasemonkey </a>or similar script. Or, if you want to be more dramatic about it, you could even use <a href="">this spaceship</a> to shoot away the offending HTML elements. It&#8217;s cool as you can shoot the paywall and the ads together.</p>
  351. <div id="attachment_1868" class="wp-caption aligncenter" style="width: 1008px"><a href=""><img class="size-full wp-image-1868" title="shootingpaywalls" src="" alt="" width="998" height="440" /></a><p class="wp-caption-text">Using an HTML element destroying spaceship to tear down a paywall</p></div>
  352. <p>The New York Times also have a 20 free articles per month thing going. Again, implemented client side using a cookie. Delete your cookies from the site, and it is all yours. Getting around this paywall is so easy that it looks like they didn&#8217;t even try to properly protect the content. And maybe they didn&#8217;t.</p>
  353. <p>In fact, there is a strong argument to say that a secure paywall isn&#8217;t a good idea. The<a href=""> Times of London</a> have a well implemented, pretty secure paywall, but they are one of the few. The Wall Street Journal, probably the most successful pay wall of the lot, do a simple referer check. If you&#8217;re coming from Google, you get access. So if you&#8217;ve got the energy, just search for the headline on Google to get your free access. If you&#8217;ve got less energy but more skillz, just spoof your referer using <a href="">Spoofy</a> or something. This also works on the New York Times site.</p>
  354. <h2>The Problem</h2>
  355. <p>The root of the problem is getting the balance correct between social sharing and decent security, and we all know how users hate (and I mean proper, vitriolic hate) hitting a paywall when clicking on a shared link.</p>
  356. <p>When it comes to the crunch, there are only three models that are possible to securely implement:</p>
  357. <ul>
  358. <li>Option #1: No real security that a monkey couldn&#8217;t avoid. This is the NYT, WSJ and many more. But this will stop the vast majority of folk &#8220;stealing&#8221; the content. The biggest downside is probably the <a href="">press reaction too the joke of a paywall</a>, as has just happened with the NYT.</li>
  359. <li>Option #2: Allow limited access to non-paying users (first click free, 20 free articles per month, or whatever). However, in order to do this securely the user must register first. And although registration is less of a barrier than asking for a credit card, it&#8217;ll still scare people off in droves. And if registration is too easy without a valid email address check, you&#8217;ll get a whole load of Donald Duck&#8217;s registering. Off the top of my head I can&#8217;t think of anyone doing this at the moment.</li>
  360. <li>Option #3: The Full Monty. All users have to pay to see any protected content. The Times of London are doing this. I really don&#8217;t like this option for most people as new readers will be hard to come by. You might do well from existing loyal fans, but in the long term I can&#8217;t see it working. Sharing is caring and all that.</li>
  361. </ul>
  362. <h2><span style="font-size: 20px; font-weight: bold;">The Solution</span></h2>
  363. <p>Fucked if I know.</p>
  364. <p>With all of the above models, not all of the content needs to be protected. The Times of London protects everything. As does the pr0n industry. Others only protect parts of their site. Some protect content until it is a bit stale (a week, or maybe an hour in financial services). I quite like <a href="">The Daily&#8217;s</a> model. They simply don&#8217;t bother to try to protect the stuff on the web site. I don&#8217;t think they&#8217;re even bothered by <a href="">the sites popping up</a> allegedly circumventing the paywall. You pay for the iPad app and hopefully that offers such a lovely experience that it is worth it.</p>
  365. <p>My view is you probably want the paywall to leak, so superficial security is probably best. You certainly want people posting links to your content on FaceBook, Twitter and the rest.  The people that try to &#8220;hack&#8221; it probably wouldn&#8217;t have paid anyway, so you&#8217;ve got some nice differential pricing going there already. Especially if you&#8217;re getting ad revenue too. Maybe show a lot more ads to the non-registered users.</p>
  366. <p>Of course, if it is easy enough for my deceased grandmother to bypass, you&#8217;ve got problems. No-one will pay, and you&#8217;ll piss off the people that already have. But if you lose 3% or something, it doesn&#8217;t sound like the end of the world. Comparable to shoplifting in retail.</p>
  367. <p>Now this clearly doesn&#8217;t work for single, high value assets (books, movies, music) where people will go to a lot of effort to get their grubby little hands on a single item of content. But for newspapers and magazines, it is probably time for most publishers to choose Option #1, give up on 100% security, hope that legitimate experience is a whole lot better than the cheating experience and accept that there are <a href="">some people that won&#8217;t pay for anything</a>.</p>
  368. <h2>Or a better solution</h2>
  369. <p>Wait! Before we give up, I think Option #2 is the long term solution. No-one seems to do it at the moment because the registration barrier is big and people won&#8217;t even register to see content shared with them. But what if they were registered already? If a publisher could throw their proprietary registration system out the window and allow access through Google, FaceBook or TheNextBigThing, they would be laughing. Then they could provide proper, secure metered access/first click free/X free per month and lots lots more without scaring users off. And, of course, when they can do their one-click payment through the above things get even better, but that&#8217;s another topic.</p>
  370. <p><a href=""><img class="aligncenter size-full wp-image-1871" title="JANRAIN" src="" alt="" width="295" height="222" /></a></p>
  371. <p>Secure paywalls aren&#8217;t that hard, and these leaky things offend my sensibilities. I&#8217;m not aware of any publishers doing this properly at the moment. Or are they? Let me know. Over and out.</p>
  372. <p>&nbsp;</p>
  373. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  374. <wfw:commentRss></wfw:commentRss>
  375. <slash:comments>16</slash:comments>
  376. </item>
  377. <item>
  378. <title>Back with a Bang</title>
  379. <link></link>
  380. <comments></comments>
  381. <pubDate>Fri, 18 Mar 2011 14:50:14 +0000</pubDate>
  382. <dc:creator>Jon Marks</dc:creator>
  383. <category><![CDATA[Ramblings]]></category>
  384. <category><![CDATA[This Blog]]></category>
  385. <category><![CDATA[kaldor]]></category>
  386. <category><![CDATA[news corp]]></category>
  387. <category><![CDATA[publishing]]></category>
  389. <guid isPermaLink="false"></guid>
  390. <description><![CDATA[My blog hasn't had enough attention recently. You see, I was involved in some top secret shiftyness and I signed a lot of pieces of paper which meant I couldn't really talk about a lot of interesting things. But I'm free from that now.]]></description>
  391. <content:encoded><![CDATA[<blockquote class="dylan"><p>Call me any name you like<br />
  392. I will never deny it<br />
  393. Farewell Angelina<br />
  394. The sky is erupting<br />
  395. I must go where it’s quiet<br />
  396. - FAREWELL ANGELINA</p></blockquote>
  397. <p>Come gather &#8217;round friends let me tell you a tale. I&#8217;ve been rather quiet these last twelve months. My poor blog has been lacking the frequent wisdom you all grew to depend on. And when the posts did come, they were often <span style="text-decoration: line-through;">inane</span> lacking in substance. You see, friends, I was involved in some top secret shiftyness and I signed a lot of pieces of paper which meant I couldn&#8217;t really talk about a lot of interesting things.</p>
  398. <p>But I&#8217;m free from that now. So while it isn&#8217;t clear that my <a href="">noble attempt to save the publishing industry</a> from itself has been a success, I&#8217;ve emerged from the other side even wiser (gasp!) than before. I&#8217;m once again allowed to talk about things, and I&#8217;ve got a whole lot of shit I&#8217;d like to talk about. So, loyal readers, watch this space for more exciting news about Content Management Systems. And the Publishing Industry. And Paywalls. And Tablets and other Mobile Shit. And Adobe and Woodwing and HTML and iOS and Core Text. And lots lots more.</p>
  399. <p>On the down side, I might not have much time to share all this wisdom with all of you. You see, I&#8217;ve started <a href="">a new company</a> with a <a href="">few other brilliant people</a> and we&#8217;re going to try to save the Publishing Industry from itself yet again. This promises to be time consuming, but I promise I&#8217;ll spend more time on this blog as my readers are worth saving too.</p>
  400. <p><a title="Kaldor Product Development Group" href=""><img class="aligncenter size-medium wp-image-1858" title="logo" src="" alt="" width="300" height="142" /></a></p>
  401. <p>So that&#8217;s the news. Back with a Bang.</p>
  402. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  403. <wfw:commentRss></wfw:commentRss>
  404. <slash:comments>11</slash:comments>
  405. </item>
  406. <item>
  407. <title>The Day of The Daily</title>
  408. <link></link>
  409. <comments></comments>
  410. <pubDate>Wed, 02 Feb 2011 17:30:08 +0000</pubDate>
  411. <dc:creator>Jon Marks</dc:creator>
  412. <category><![CDATA[Events]]></category>
  414. <guid isPermaLink="false"></guid>
  415. <description><![CDATA[So The Daily is live. Just finished watching the launch announcement and was impressed. The app is really feature rich. It can live update during the day, has 360 degree video, live audio articles, a large sports score database, games and good social integration. And it even has the weather!]]></description>
  416. <content:encoded><![CDATA[<blockquote class="dylan"><p>And he was told but these few words,<br />
  417. Which opened up his heart,<br />
  418. &#8220;If ye cannot bring good news, then don&#8217;t bring any.&#8221;<br />
  419. - THE WICKED MESSENGER</p></blockquote>
  420. <p>So The Daily is live. Just finished watching the launch announcement and was impressed. I was lucky enough to see some sneaky preview concept versions a few months ago, and they&#8217;ve really turned it into reality in a ridiculously short amount of time.</p>
  421. <p>Yeah, yeah, it did crash once in the launch demo. But all iPad apps crash, right?  I&#8217;m sure they&#8217;ll iron out the last few kinks over the coming days. If you&#8217;re in the US (or are wise in the ways of <a href="">reverse proxies</a> *), get it from the <a href="">App Store</a> now. If you&#8217;re anywhere else, or don&#8217;t know what a reserve proxy is, have a look at the <a href="">web site</a>, <a href="">blog</a> or <a href="">FaceBook page</a>.</p>
  422. <p><a href=""><img class="aligncenter size-medium wp-image-1840" title="Daily Home Page" src="" alt="" width="300" height="225" /></a></p>
  423. <p>I take my hat off to the techie brains behind the operation, John McKinley (<a href="!/ourparents">@ourparents</a>) who, it turns out, is not only wise but also delivers on time. And of course we all love <a href="">Jon Miller</a> and his basketball analogies . <em>Random aside: It was a year today that Jon Miller interviewed yours truly for his current job. He really is a lovely guy. **</em></p>
  424. <p>The app is really feature rich. It can live update during the day, has 360 degree video, live audio articles, a large sports score database, games and good social integration. And it even has the weather!</p>
  425. <p>I&#8217;m not smart enough to know if The Daily is going to be a roaring success or an unholy disaster. But I love the fact that Rupert tries bold things like this. That&#8217;s one of the many reasons I&#8217;ve loved the last year I&#8217;ve spent <span style="text-decoration: line-through;">on The Darkside</span> at News Corp. Someone in this industry has to try something.</p>
  426. <p><a href=""><img class="aligncenter size-medium wp-image-1842" title="IMG_0017" src="" alt="" width="300" height="225" /></a></p>
  427. <p>* No reserve proxies were harmed in the making of this blog post.<br />
  428. ** This blog reflects my opinions only and not those of my employer.</p>
  429. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  430. <wfw:commentRss></wfw:commentRss>
  431. <slash:comments>14</slash:comments>
  432. </item>
  433. <item>
  434. <title>McBoof’s Predictions For Content Management In 2011</title>
  435. <link></link>
  436. <comments></comments>
  437. <pubDate>Wed, 22 Dec 2010 22:41:57 +0000</pubDate>
  438. <dc:creator>Jon Marks</dc:creator>
  439. <category><![CDATA[Future of CMS]]></category>
  440. <category><![CDATA[Ramblings]]></category>
  441. <category><![CDATA[amazon]]></category>
  442. <category><![CDATA[api]]></category>
  443. <category><![CDATA[cloud]]></category>
  444. <category><![CDATA[CMS]]></category>
  445. <category><![CDATA[facebook]]></category>
  446. <category><![CDATA[galaxy]]></category>
  447. <category><![CDATA[iPad]]></category>
  448. <category><![CDATA[rest]]></category>
  449. <category><![CDATA[rfp]]></category>
  451. <guid isPermaLink="false"></guid>
  452. <description><![CDATA[Right, sheeple - it's time to learn something from the Great McBoof. Normally you'd expect to pay somewhere between $5000 and $10000 for this kind of information in some top secret report. But here it is, completely free. Steal it all when your CIO demands your white paper on Trends for Next Year, or to impress your friends at your local #LastThursdayCMS. So, without further ado, I guess you McBoof's Predictions For Content Management In 2011.]]></description>
  453. <content:encoded><![CDATA[<blockquote class="dylan"><p>When all of your advisers heave their plastic<br />
  454. At your feet to convince you of your pain<br />
  455. Trying to prove that your conclusions should be more drastic<br />
  456. Won&#8217;t you come see me, Queen Jane?<br />
  457. - QUEEN JANE APPROXIMATELY</p></blockquote>
  458. <p>Right, sheeple &#8211; it&#8217;s time to learn something from the Great McBoof. Normally you&#8217;d expect to pay somewhere between $5000 and $10000 for this kind of information in some top secret report. But here it is, completely free. Steal it all when your CIO demands your white paper on Trends for Next Year, or to impress your friends at your local #LastThursdayCMS. So, without further ado, I guess you McBoof&#8217;s Predictions For Content Management In 2011.</p>
  459. <p><a href=""><img class="aligncenter size-medium wp-image-1827" title="Nostradamus" src="" alt="" width="296" height="300" /></a></p>
  460. <p><strong>#1 &#8211; Names Remain Sacred</strong>: Ridiculous crapronyms like WEM and CEM will vanish. Those that invented them will scuttle back in shame, only to crawl back with some new ones. But the CMS twitterati are a wiley bunch, and aren&#8217;t easily fooled. I&#8217;ll try to write a blogpost later about why these crapronyms are so bad, but I&#8217;m currently surrounded by four babies with the <a href="">norovirus</a> (not pleasant), and this is a story that deserves to be told properly.</p>
  461. <p><strong>#2 &#8211; Return To Core Competencies</strong>: New highly-focussed kickass products will appear in areas into which the CMS vendors tried to encroach. The vendors will feel a bit stupid, stop building monoliths and focus on the stuff they&#8217;re good at. They&#8217;ll embrace integration again. The areas include analytics, MVT, search, image manipulation, transcoding and community. Most will be *aaS and easily integrated. Kiss your custom CMS tracking module, A/B testing module, forum module, twitter module, image resize module and full text search module goodbye. They&#8217;re going to look pretty shit compared to what&#8217;s coming.</p>
  462. <p><strong>#3 &#8211; Focus on APIs</strong>: The API will take centerstage in 2011. The next versions of most CMSs will be properly architected for them. A product will be judged by the quality of the API it exposes. The really good news is that this will properly re-establish the split between content management and content delivery. Portals will be portals again. And there will be much rejoicing. Vignette DPM will be unofficially axed. And there will be even more rejoicing. All APIs will become HTTP based. <a href="">CMIS</a> will play a relatively small role in 2011. The vendors will all claim their APIs are RESTful, although only a handful really will be.  Note that there is nothing wrong with these slightly dirty, non-RESTful APIs. I&#8217;d rather have dirty than <a href="">SOAP</a>. And SOAP is going away. Can you believe the S stands for Simple.</p>
  463. <p><strong>#4 &#8211; Enemies Will Stop Sleeping Together:</strong> 2010 had a good few CMS aquisitions that didn&#8217;t make sense. Vendors that had many overlapping products acquired one another or merged. None of these were a good idea, so 2011 won&#8217;t repeat this. No chance of either the speculated <a href="">Microsoft &#8211; Adobe</a> or Interwoven &#8211; Open Text jokes happening. Note that yours truly does still think the <a href="">Adobe &#8211; Day</a> deal was smart, but they didn&#8217;t have overlapping products.</p>
  464. <p><strong>#5 &#8211; New Auth Protocols</strong>: FaceBook Connect is going to become important to the CMS vendors. It&#8217;ll be a checkbox on RFPs. Which sucks, but I&#8217;m sure <a href="">Nostradamus</a> didn&#8217;t like all his predictions either. OpenID and OAuth aren&#8217;t going to set the world alight in 2011.</p>
  465. <p><strong>#6 &#8211; RFPs Continue to Waste People&#8217;s Time</strong>: The CMS choir will continue to all sing that big fat RFPs are not the way to effectively select a product. And this will continue to fall on deaf ears and we&#8217;ll continue to see these dumbass, energy sapping, pointless documents arriving in our inboxes.</p>
  466. <p><strong>#7 &#8211; A Storm Cloud Brewing</strong>: Vendors start to <a href="">properly understand the cloud</a>. They&#8217;ll all architect their software for it. Amazon will be dominant. The smarter CMS vendors will provide EC2 instances all installed and ready to go. I must confess I only properly understood it early this year.</p>
  467. <p><strong>#8 &#8211; Real Multichannel Delivery</strong>: The success of the <a href="">iPad</a> (and, I predict, the Samsung Galaxy Tab) will mean vendors start thinking about multichannel again properly. 2011 will be the year Android becomes really important. Even Windows Phone 7 might start to matter a bit. In fact, we might get people saying &#8220;Digital Content Managament&#8221; instead of &#8220;Web Content Management&#8221;. Which would be yet another craproymn as that is what good old &#8220;Content Management&#8221; is.</p>
  468. <p><strong>#9 &#8211; And Multichannel Authoring</strong>: It won&#8217;t just be delivery to the tablets and smartphones. It&#8217;ll be authoring too. In 2011, half the vendors will write web apps while the other half will write native apps to show off their mobile authoring platforms. By 2012, 80% will be writing web apps.</p>
  469. <p><strong>#10 &#8211; The Crew Trumps The Product</strong>: The realisation will hit home about why <a href="">the implementation is still more important than the product choice</a>. There will be some attempts to start SI/Agency reviews or reports, but I don&#8217;t think they&#8217;ll take off until 2012.</p>
  470. <p><strong>Bonus CMS Prediction:</strong> 2011 Is Gonna Be Fun: The CMS Twitter community will continue to be insane and a good laugh. We&#8217;ll drink lots of beer together. @pmonks will not grow up, @irina_guseva will retain her title as CMS Queen, @piewords will remain the voice of reason, @justincormack will still write very well thought out posts not often enough. Those pesky analysts will continue to stir things up and keep us occupied. The well-meaning vendors will continue to sprout marketing bullshit. And I&#8217;ll continue to be completely wrong about absolutely everything.</p>
  471. <p><a href=""><img class="aligncenter size-medium wp-image-1829" title="macgowan" src="" alt="" width="300" height="297" /></a></p>
  472. <p><strong>Bonus Christmas Prediction</strong>: No new Christmas song will be released that will come even close to Fairytale of New York &#8211; by far and away the best Christmas song ever written. The lyrics are brilliant enough to bring tears to my eyes , the music Irish and folky and Shane MacGowan is the ugliest bastard you&#8217;re ever likely to see in a music video. Listen to <a href="">THIS </a>three times and I&#8217;ll buy you a beer if you aren&#8217;t in love with it.</p>
  473. <p>As usual, comments and flames much appreciated. Happy Christmas to all, and to all a good-night.</p>
  474. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  475. <wfw:commentRss></wfw:commentRss>
  476. <slash:comments>29</slash:comments>
  477. </item>
  478. <item>
  479. <title>Going up to get down</title>
  480. <link></link>
  481. <comments></comments>
  482. <pubDate>Thu, 11 Nov 2010 15:47:42 +0000</pubDate>
  483. <dc:creator>Jon Marks</dc:creator>
  484. <category><![CDATA[Ramblings]]></category>
  486. <guid isPermaLink="false"></guid>
  487. <description><![CDATA[Change is in the air. I'd love to tell you all about it, but I'm afraid I'm under NDA. So, instead, I present in full, for the first time ever on the interwebz, a short story written by my colleague, the great @sallyfoote. Follow her on Twitter, and convince her to start her own goddamn blog so I don't have to pimp her stories for her. Any resemblance to real persons, living or dead, is purely coincidental and the story in no way reflects any personals circumstances.]]></description>
  488. <content:encoded><![CDATA[<blockquote class="dylan"><p>I&#8217;m staying with Aunt Sally, but you know, she&#8217;s not really my aunt<br />
  489. Some of these memories you can learn to live with and some of them you can&#8217;t<br />
  490. - SUGAR BABY</p></blockquote>
  491. <p>Change is in the air. I&#8217;d love to tell you all about it, but I&#8217;m afraid I&#8217;m under NDA. So, instead, I present in full, for the first time ever on the interwebz, a short story written by my colleague, the great <a href="">@sallyfoote</a>. Follow her on Twitter, and convince her to start her own goddamn blog so I don&#8217;t have to pimp her stories for her. Any resemblance to real persons, living or dead, is purely coincidental and the story in no way reflects any personals circumstances.</p>
  492. <h2>Going up to get down &#8211; Sally Foote</h2>
  493. <p>Through the glass boardroom door Jack can see the new IT Director and the woman from HR, heads bent together over sheets of paper, making notes. He counts the straight-backed chairs (fifteen), the potted plants (two) and the framed front pages of the paper (seven). One reads: &#8220;Diana is Dead&#8221; and another &#8220;Does this mean War?&#8221; They nods to one another and then look up. The director motions Jack to come in, offers him a coffee, clips the cup onto the saucer and slides it across the smooth wooden table. He doesn’t really like coffee, but he drinks it anyway. The director leans forward over the table, elbows apart, fingertips pressed together.</p>
  494. <p>&#8220;Now Jack,&#8221; he’d said, &#8220;I’m sure you can guess what this is about?&#8221; He raises one eyebrow and pauses dramatically. Jack shifts in his chair and tucks his hands beneath his thighs. It’s been over two months since the new IT Director stood up in front of the whole department and invited them to ‘get on board the change train’.</p>
  495. <p>&#8220;We’re worried about you Jack. We get the impression you’re unhappy,&#8221; the director pauses, &#8220;That you’re not happy here at the paper.&#8221; They don’t want to alarm him. Would he like some sugar for his coffee? The matching white jar is pushed in his direction. And the meeting isn’t about poor performance, more a lack of engagement.</p>
  496. <p>&#8220;Perhaps failure to thrive?&#8221; suggests the HR woman. She smiles and sets her pen down next to her notebook.</p>
  497. <p>In his last appraisal, Jack’s manager, Peter, had described him as a quiet chap who preferred to work alone. Jack had vigorously nodded his agreement. They’d talked about the fact that Jack did not like meetings and preferred to be left to get on with things. Jack explained that, in fact, this was one of the main reasons he had become a programmer. Peter nodded and then said that he felt that Jack would benefit from working more closely with his colleagues. Jack should be a bit more proactive, a bit more of a team player, a bit more like Jessica: Jessica, with her long blonde ponytail swinging from side to side as she strides round the building, wearing her enthusiasm like a badge. Jack thinks she would do well in palliative care. He imagines her standing at his bedside asking her questions: &#8220;What motivates you Jack?&#8221; &#8220;Do you want to talk about it Jack?&#8221;</p>
  498. <p>&#8220;Jack,&#8221; says the IT Director, &#8220;This is a people kind of company. We’re all about the intellectual property. We like everyone to get stuck in, we like people to get involved. It’s all about vigour. And Jack, we want to help people to get somewhere. Do you know what I mean?&#8221; Jack rubs his hand across his forehead. He remembers the white calves of the IT Director flashing across the finish line at the company fun-day. He’d been pushing a wheelbarrow with Jessica in it, her legs dangling over the front.</p>
  499. <p>The director pours himself another cup of coffee. &#8220;We don’t want you to be,&#8221; he pauses glancing up, &#8220;left behind.&#8221; Jack smiles stiffly.</p>
  500. <p>The woman from HR has been wondering whether Jack would like to move on, or perhaps take some time off? She splays out her fingers on the glossy surface of the table and tips her head to one side. One of her long silver earrings falls against her cheek. Would Jack be interested in taking redundancy? It is being offered, does he understand? No obligation. He can go or stay, as he chooses. They really do just want him to be happy. The director stands and extends his hand. The handshake is vigorous. &#8220;You have a think about it Jack, you have a little think about it, and then get back to us.&#8221;</p>
  501. <p>The foyer of the 6th floor is unusually crowded (only one of the lifts is working) and so Jack stands over to one side, near the windows. A faction of journalists are passing a set of pictures between them. &#8220;No, no, no,&#8221; says the one. &#8220;For god sakes,&#8221; says another, &#8220;does the man even know how to focus a lens?&#8221; On the far wall soldiers in a huge black and white print fire from behind a blockade. Jack turns to look out at the satellite dish pimpled rooftops of the surrounding low rise flats. Two forlorn pigeons stare back at him from their dripping perch. Beyond them the glass buildings of the city glisten and steam. Black umbrellas bob past one another like chequers on the pavement below. In the glass of the window he can just see the faint outline of his face hovering ghostlike on the glass. He presses down a stray tuft of hair that has sprung up on his crown.</p>
  502. <p>When Jack came for the interview seventeen years ago, straight out of university, he had expected a maths test or logic puzzle of some sort. Instead he was taken on a tour of the editorial floor. It was nearly seven o’clock and the pages for the next day’s paper were being finished. Jack stood behind a tall man who was typing headlines standing up and shouting instructions across the room. &#8220;I’m looking for the picture on 17. Can someone revise forty-seven? Twenty-three is good to go.&#8221; The man knocked over a jar of pencils that rolled across the desk and spread themselves in a fan along the carpet. Jack bent to pick them up, scrabbling on his knees between the desks. People moved around him and stepped over him and even when he set the jar back on the desk, no one said a thing. He had a sudden memory of a terrarium of snakes that he had been taken to see as a child. How, invisible in the darkened corridor, he could put his hand right up against the warm glass, palm flat against a snake’s pale belly. He shivered with excitement, to be that close. For all the big breaking stories, he’s been there watching the pages being made, the pictures being chosen, the headlines being typed. He bought the paper after 9/11 and though he had seen the front page a hundred times the night before, he still could not believe it. Lately, what with the change train chuffing its way through IT, he has found himself up there more often, a shadow leaning against a wall, or swivelling, slowly back and forth in an unused chair, disappearing.</p>
  503. <p>A restless woman comments loudly to her companion about the poor quality of the building, the indignity of having to work under these circumstances, the ineffectiveness of the service departments. Jack turns back into the foyer and they disappear round the corner to the stairwell, heels clicking on the polished marble floor, Macintosh tails swishing out behind them. The lift doors open and Jack pushes past the journalists to lean against the mirrored back wall. How’s that for vigour, he thinks. The button console has illuminated numbers for every floor. Jack reaches out and presses &#8220;B&#8221;. B for basement. B for beneath. B for bowel.</p>
  504. <p>The lift descends to the basement and the doors open but Jack doesn’t move. He is staring at the familiar white wall where for seventeen years he has turned left, walked past the PC support team, past the network specialists, down to the corner where the programmers sit. Each morning, he put down his bag, pulled out the chair, sat down, moved the keyboard closer, entered his name (Jack_Everitt), entered his password ([email protected]). For a man who likes routine, it was a comforting pattern. Now the day begins with a scrum meeting &#8211; they stand in a circle and there is a baton that is passed from one person to the next with the turn to speak. There is a chart on the wall where you are supposed to write the good things that happened to you each week. No one is allowed to make their own tea; you have to earn your caffeinated drinks in friendship.</p>
  505. <p>Jessica had once told Jack, leaning forward, palms on her knees, that if she wouldn’t want to work anywhere else. She said she only liked this job because of the people. &#8220;Imagine doing IT somewhere else where you just sat at your desk all day and didn’t go out and chat to people and have discussions about things.&#8221; Jessica closed her eyes and shook her head. Swish, swish went the pony tail. &#8220;Imagine,&#8221; said Jack.</p>
  506. <p>Thanks to Jessica there is invariably a long cold cup of tea waiting for him on his desk.</p>
  507. <p>The doors begin to close, shiny as a mirror, and he watches the two halves of his reflection draw together until there he is &#8211; Jack with a line down the middle.</p>
  508. <p>He glances at the buttons, reaches out and then drops his arm, looks down at his two shoes on the red-brown swirls of the carpet, hooks a lock of hair behind his ear. The lift, like so many other things in modern life, must be controlled by a computer. And it would be programmatically impossible for the lift to know he’s here. The doors are not going to suddenly reopen like a mouth and spit him out. The carpeted silence is so beautiful that he coughs, just the once, to reaffirm it.</p>
  509. <p>He still has the first programming book he bought: &#8220;The Complete Idiot’s Guide to Visual Basic&#8221; with its enticingly titled opening chapter: &#8220;An Introduction to Programming: A Walk on the Wild Side&#8221;. Jack spent the weekends sitting at his parents’ computer working his way through it. He liked that it was called ‘writing code’ and that no one else could understand it. He liked the precision it demanded &#8211; one misplaced colon could meant hours of errors and frustration. He kept the book all through high school and even university. Just last week he took it out of the bottom drawer of his desk and thumbing through &#8220;Looping with Do and Until &#8211; Around and Around we go&#8221; smiled at a blue-biro note from his fourteen-year-old self: &#8220;WOW!&#8221;</p>
  510. <p>Jack designs his programs like formulas. He begins with the problem, defines the solution and then logically and methodically writes out all the possible ways to get to there.</p>
  511. <p><strong>IF</strong> the up button is pressed on the fourth floor<br />
  512. <strong>THEN</strong> go to the fourth floor<br />
  513. <strong>ELSE</strong> wait.</p>
  514. <p>Next he adds exceptions to catch unexpected or unusual things that might happen. For example if the lift is already on the second floor when someone inside pushes ‘two’, then the doors should open. Finally he fits it all together and tests it, watches the computer working through the logic, making the decisions. It feels rather good to be an unhandled exception.</p>
  515. <p>The lift bleeps and begins to rise and Jack almost laughs out loud.</p>
  516. <p>A short, rather wide-hipped woman wearing a blue skirt, steps into the lift on the ground floor. She looks at the seven unlit buttons, presses five and then turns to Jack, eyebrows raised questioningly, finger poised. The world, it would seem, is not designed for travel without destination.</p>
  517. <p>&#8220;Four,&#8221; replies Jack</p>
  518. <p>The doors open on the fourth floor and when Jack makes no move to exit, the blue skirt swooshes round, and the woman says, smiling, &#8220;This is four&#8221; and then presses her finger firmly onto the ‘open door’ button. Jack steps hesitantly out. He hasn’t been on the fourth floor before and has no idea what happens up here. He can feel himself blushing as he pauses uncertainly, feet together. The office spreads out to his left and he is convinced he can hear a settling of silence &#8211; like when someone uninvited steps into a conversation. He checks his watch in what he hopes is a purposeful manner, moves the face back and forth across his wrist. The lift doors slide slowly closed behind him. He takes a deep breath, draws his shoulders back and then strides over to the newspaper stand directly opposite the doors, picks up a copy. He unfolds the paper and turns noisily through a few pages. At page 14 he taps an article with his finger, refolds the newspaper, tucks it under his arm and turns on one foot, back towards the lift doors. He presses the down arrow and waits.</p>
  519. <p>When Jack was 10 an obsession with choose-your-own adventure books had raged through the boys of his age. They read them on the bus, on the stands during athletics and folded open beneath their desks in geography. At the end of each chapter you were required to make a decision and follow the story onto a specified page according to the choice you’d made. &#8220;If you think Araya should head west to seek water, turn to page 27 or, if you think Araya should seek shelter in the village, turn to page 81.&#8221; He hated the randomness of the choices, you just had to take a chance and pick one. Jack had got stuck in the underwater forest for two whole weeks. Back and forth he went between pages 73 and 36, reading the same paragraphs over and over again.</p>
  520. <p>What would he do with the money? Buy a new computer? Take a trip? He could do something completely different altogether. He unfolds the piece of paper from his back pocket to check the figure again. It’s a lot of money. More like fifty computers, two thousand new t-shirts, a long trip.</p>
  521. <p>He gets back into the lift with two young men. They have neat lines pressed into the front of their trousers and the one has little padlocks for cufflinks.</p>
  522. <p>&#8220;Floor?&#8221;</p>
  523. <p>&#8220;Basement&#8221; Jack says and puts his hands into his jeans pockets.</p>
  524. <p>&#8220;It’s set in a newspaper,&#8221; says the one with the padlocks, &#8220;That’s why they’re filming it here. Scarlett Johansen is playing a journalist.&#8221;</p>
  525. <p>&#8220;Playing a hot journalist!&#8221; interjects the other.</p>
  526. <p>&#8220;She’s working undercover investigating something or other, and then she falls in love with the guy she’s writing about. &#8221;</p>
  527. <p>&#8220;Tell me she shags someone over the editor’s desk.&#8221;</p>
  528. <p>&#8220;Oh yeah sure, that’s the one they’re filming on Saturday, to see if it’s possible to actually get you to come in on the weekend.&#8221; They both laugh.</p>
  529. <p>The lift pings its arrival on the third floor.</p>
  530. <p>&#8220;Scarlett Johansen, ready yourself, we’re coming for you!&#8221; says the man with the padlocks, hoisting up his trousers.</p>
  531. <p>The windows of the third floor are blacked out with curtains and huge lamps glare down on the far corner of the room. Jack has only seen film sets in films before. He can smell the heat of the lights and the muted sound of a large group of people being quiet. A microphone on a boom sways above the throng of onlookers. Jack can tell there’s no point in trying to get any closer. Every available space has someone in it. One man has lifted his chair up onto his desk and is sitting, arms folded, watching. From the epicentre of the room a voice roars &#8220;Cut.&#8221;</p>
  532. <p>A young woman gets into the lift carrying a stack of film cans; the red tape running round their sides says &#8220;URGENT: UN-DEVELOPED STOCK&#8221;. Jack knows exactly who Scarlett Johansen is. Last Saturday he went to see &#8220;Girl with the Pearl Earring&#8221; at his local cinema. It was part of a festival of films about art. His usual seat (middle of the front row) was taken and he had to make do with sitting further off to the side which ruined the whole experience. Jack likes to immerse himself in films &#8211; so close that there is nothing between him and the screen, like an invisible protagonist. The woman carrying the film cans gets out on the ground floor and as the lift doors open once again in the basement, Jack presses the close door button with a firm finger. The painting in the film, the girl in the painting, the actress in the girl, and now the real woman. There’s a symmetry to it that appeals &#8211; like opening one of those Russian Dolls. And what’s more:</p>
  533. <p><strong>IF </strong>Miss Johansen is not likely to be the type of woman to take the stairs<br />
  534. <strong>AND IF</strong> this is the only operational lift,<br />
  535. <strong>THEN </strong>at some point, during the course of the day, she is going to get in it.<br />
  536. <strong>ELSE </strong>There is no else; Jack is going to be waiting.</p>
  537. <p>On the seventh floor someone steps up to the doors, and then seeing him standing there, takes a surprised step back. This is one of what Jack dubs ‘the turns’ &#8211; where the lift reaches one of the extremes of the building, and the expectation that he should alight is all the greater because there is nowhere else to go. He begins to explain that he is actually going back down and gives a small apologetic wave of his hand to cover the missing end of his sentence. After three or four of these incidents, he perfects the gesture in lieu of any explanation. It involves a quick flick of the wrist that is both welcoming in a ‘No, no, it’s ok, get into the lift’ way and also directional in an ‘I’m going up’ or ‘I’m going down’ way. It’s astounding how many people immediately understand what he means. Of course he is not alone; thanks to the broken lift there are lots of other people, too impatient to wait, who are going up to get down.</p>
  538. <p>The lift gets busier after noon as people head to lunch. Women scratch in their handbags, discussing where they will buy their sandwiches &#8211; &#8220;Pret or that little Turkish place on the corner?&#8221; Just after one o’clock it is so full that bodies are pressed uncomfortably against one another, and the doors open to disappointed faces of people on each floor who sigh and turn on their heels to take the stairs. Jack wedges himself into the back corner, crosses his arms over his chest. Most people waited to speak until they were out of the lift, snippets of their conversations drifting back. &#8220;Suggested that he just give up. Best thing for it really. There’s nothing more I&#8230;&#8221; and &#8220;That’s what she says she wants but, honestly now, do you think it’s ethical?&#8221;</p>
  539. <p>And then they are all back again after lunch, and no-one comments on the fact that he is still there, though one woman, with a carrier bag of sandwiches, chewing on a soft drink straw, points a finger at him and smiles. She gets out on three.</p>
  540. <p>&#8220;It’s like I’m CCTV,&#8221; thinks Jack, &#8220;I see it all, but no one sees me.&#8221;</p>
  541. <p>Jack shifts his weight from one foot to the other, tugs down the hem of his T-shirt. This could be it. The lights at the far end have been turned off and some of the black curtains pulled open, spilling daylight in. There’s a great heap of cables lying on the floor near the lift, and a woman just out of sight to the left is calling for water. But no one is waiting to get in.</p>
  542. <p>As the doors start to ease closed, a young assistant wearing a headset rushes towards him, her hand stuck out in front of her calling: &#8220;Hold the lift, please.&#8221; He doesn’t move and she has to repeat it &#8211; &#8220;Hold the doors!&#8221; Her forehead creases as the doors begin to close and a soft &#8220;Hey&#8221; escapes her lips. Jack frantically stabs at the ‘three’. The doors yawn open and he apologises. She frowns again, puts a foot in the door, and beckons off to the right. Two men wheel over a large trolley-like piece of equipment. It has rubber wheels that creak over the metal lip of the lift. Jack is forced to step right back against the smoked-glass mirrors.</p>
  543. <p>The men stand on either side of the trolley, looking at Jack.</p>
  544. <p>&#8220;Alright?&#8221;</p>
  545. <p>Jack nods.</p>
  546. <p>By four o’clock Jack is not alright. He is desperate to go to the toilet. He stands quietly, legs crossed, jaw clenched as long as he can and then bursts out on five, where the bathrooms are directly opposite the lift. He hops as he pees. Two floors below Scarlett could be gliding down to her waiting limousine. He skids back, bathroom door slamming behind him, leaves a wet fingerprint on the down button. A man waiting adjacent to him glances over and says: &#8220;Stairs might be quicker mate.&#8221;</p>
  547. <p>Jessica is in the lift.</p>
  548. <p>&#8220;Oh my God, Jack,&#8221; she says, eyes widening with delight, &#8220;Where the hell have you been? Did you have your meeting? Peter’s going mental.&#8221; She gestures on either side of her head with two rotating fingers. &#8220;He called the director and everything to find out what time you finished the meeting and where you were.&#8221; She is standing in his spot and so he’s stopped just inside the closing doors. On the back wall behind her, he can see the curious effect of too many mirrors in such a small space, the reflection of Jessica over and over, diminishing.</p>
  549. <p>&#8220;Jack, are you ok?&#8221; she pauses, rubs the side of her nose, &#8220;That guy from the Arts Desk called again. He’s getting some sort of error message, wants you to call him back. I wrote it all down. It’s on your desk.&#8221; Jack watches her mouth opening and closing. &#8220;Are you going back to your desk now? What are you doing up here? Hey, did you know that Scarlett Johansen is filming on third?&#8221;</p>
  550. <p>&#8220;I’m CCTV,&#8221; says Jack.</p>
  551. <p>&#8220;What?&#8221;</p>
  552. <p>&#8220;Are you getting off?&#8221; says a woman on the 7th floor.</p>
  553. <p>&#8220;Yes,&#8221; says Jessica.</p>
  554. <p>&#8220;No,&#8221; says Jack.</p>
  555. <p>She turns and waves goodbye.</p>
  556. <p>Two men in mid-conversation get in on the second floor, pausing only briefly. The taller of the two is wearing a pale linen suit, its back lightly crumpled, as if he has been sitting down for too long. He talks rapidly and angrily, pointing at the shorter man’s chest:</p>
  557. <p>&#8220;Thing is, right, if you don’t do something about it, it’s cyclical; the whole process, repeats and repeats and repeats,&#8221; he pauses, &#8220;in perpetuity.&#8221; Jack thinks of a furious bee he’d watched on a bus slamming itself against the window. It would crawl slowly up the glass to the very rim where centimetres from fresh air, it would take flight and drop back down again to the base of the frame, and bang, bang, bang. He watched this loop over and over for the whole length of the bus journey. Eventually the bee would die. After he got off, he thought of the bus going round and round its route, with the bee inside going up and down the window. In perpetuity.</p>
  558. <p>When doors open on the third floor there’s a group of people huddled around the lift, facing Jack. He untucks his hands from behind his back and crosses them firmly over his chest. One woman has a clipboard propped on her hip and next to her a tall young man is swinging a roll of thick, silver tape around one finger. Standing in the middle, is Scarlett Johansen. She is lifting her sunglasses up towards her face, and for a very, very brief instant, he catches her eye over the top of the huge fly-lenses.</p>
  559. <p>An assistant gets into the lift and walks towards Jack. She touches his arm and says in a honeyed American accent &#8220;Excuse me sir, I wonder if you could do us just the biggest favour? Miss Johansen, and,&#8221; she indicates the group of people waiting at the lift with a quick round circular motion over her shoulder, &#8220;well, there’s quite a few of us. Would you mind?&#8221; The doors begin to close and her arm darts out, a manicured red nail depresses the open button. She smiles at Jack: &#8220;Thanks so much, really, thanks.&#8221; Scarlett is fiddling with her bracelet, pushing it backwards and forwards over the fine bones of her wrist. The grip on his forearm tightens and he is directed out of the lift.</p>
  560. <p>On the other side of the now deserted floor a man is rolling up a cable, wrapping it over his hooked thumb and down around his elbow, pausing to yank as the plug-end catches somewhere amongst the debris. Behind him the lift pings open again.</p>
  561. <p>&#8220;Hey?&#8221; says the American woman. &#8220;Hey!&#8221;</p>
  562. <p>Jack turns back to face the lift. Scarlett has removed her glasses now and is rummaging in her handbag.</p>
  563. <p>&#8220;Are you the new runner?&#8221;</p>
  564. <p>Jack blinks, sees clearly, nods.</p>
  565. <p>&#8220;Where the hell have you been all day?&#8221; She says gesturing him into the lift &#8220;Come on then&#8221;</p>
  566. <p>Ha, ha, thinks Jack, how’s this for vigour?</p>
  567. <p style="text-align: center;"><a href=""><img class="aligncenter size-thumbnail wp-image-1816" title="foot" src="" alt="" width="90" height="90" /></a></p>
  568. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  569. <wfw:commentRss></wfw:commentRss>
  570. <slash:comments>3</slash:comments>
  571. </item>
  572. <item>
  573. <title>I’ve Learned Stuff In The Past Two Hours</title>
  574. <link></link>
  575. <comments></comments>
  576. <pubDate>Sun, 07 Nov 2010 22:19:49 +0000</pubDate>
  577. <dc:creator>Jon Marks</dc:creator>
  578. <category><![CDATA[Ramblings]]></category>
  579. <category><![CDATA[instalyrics]]></category>
  580. <category><![CDATA[music]]></category>
  581. <category><![CDATA[paperli]]></category>
  582. <category><![CDATA[rockmelt]]></category>
  584. <guid isPermaLink="false"></guid>
  585. <description><![CDATA[The family is sick in bed and fast asleep, so I got a few rare moments to browser the intarwebs. I discovered RockMelt, instalyrics and how much I hate]]></description>
  586. <content:encoded><![CDATA[<blockquote class="dylan"><p>If today was not an endless highway,<br />
  587. If tonight was not a crooked trail,<br />
  588. If tomorrow wasn&#8217;t such a long time,<br />
  589. Then lonesome would mean nothing to you at all.<br />
  590. - TOMORROW IS A LONG TIME</p></blockquote>
  591. <p>The family is sick in bed and fast asleep, so I got a few rare moments to browse the intarwebs. I discovered RockMelt, instalyrics and I also learned about <a class="myButton" href="">jquery-raptorize</a> but that&#8217;s not important right now.</p>
  592. <h2>RockMelt &#8211; @rockmelt</h2>
  593. <p><a href=""><img class="aligncenter size-medium wp-image-1798" title="rockmelt" src="" alt="" width="300" height="168" /></a></p>
  594. <p><a href="">RockMelt</a> is a new browser built on Chrome (my browser of choice) that includes some funky new integrations with the shits the cool kids are using. And I&#8217;m trying to be a cool kid. Let&#8217;s see if it does better than <a href="">Flock</a>, the previous attempt at a social browser that I remember. The fact that it is backed by The Daddy Of Browsers, <a href="">Marc Andreessen</a> certainly can&#8217;t hurt. I was lucky enough to briefly meet Marc at a Top Secret Event a few months ago. He&#8217;s my kind of guy and most things he touches turn to gold. You can watch a video on their site right now. Looking forward to my invite arriving.</p>
  595. <h2>InstaLyrics &#8211; @instalyrics</h2>
  596. <p><a href=""><img class="aligncenter size-medium wp-image-1799" title="instalyrics" src="" alt="" width="300" height="219" /></a></p>
  597. <p>I love my music and, as my legions loyal readers will know, I love searching for lyrics. Every post on this blog starts with <a href="">a Bob Dylan lyric</a>, for example. I take longer finding the lyrics than I do writing the posts! You know how when searching the dark corners of the web for lyrics you get pron-popups and warez assaulting you from all angles? Well none of that here. Kudos really should go to <a href="">musiXmatch</a> that provide the fully legit API that powers this. I heart APIs.</p>
  598. <h2></h2>
  599. <p><a href=""><img class="aligncenter size-medium wp-image-1800" title="paperli" src="" alt="" width="300" height="215" /></a></p>
  600. <p>Okay, I&#8217;ve known about <a href=""></a> for a while. But I never knew how much I fucking hate the thing. I hate hate hate it, and hate it more as it grows every more popular. Sure, it is pretty and all, but this monster turns <em>everyone</em> into an aggregator, and a noisy one at that. It&#8217;s even more annoying than FourSquare for Twitter spam. The sneaky bastard even gets into my &#8220;mentions&#8221; stream. Please, please, dear Tweetdeck, add some functionality to filter out this evil. And dear twits, stop the auto-promote daily tweets I implore you. Oh, and in case you hadn&#8217;t heard, <em>The Who Gives A Fuck Daily is out! <a href=""></a> Top stories by @mcboof @mcboof @mcboof</em></p>
  601. <p>Well, that&#8217;s all I learned. Anything else cool out there?</p>
  602. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  603. <wfw:commentRss></wfw:commentRss>
  604. <slash:comments>2</slash:comments>
  605. </item>
  606. <item>
  607. <title>Hiring Tips That HR Wouldn’t Like</title>
  608. <link></link>
  609. <comments></comments>
  610. <pubDate>Wed, 27 Oct 2010 03:20:51 +0000</pubDate>
  611. <dc:creator>Jon Marks</dc:creator>
  612. <category><![CDATA[Ramblings]]></category>
  613. <category><![CDATA[firing]]></category>
  614. <category><![CDATA[hiring]]></category>
  615. <category><![CDATA[interview]]></category>
  617. <guid isPermaLink="false"></guid>
  618. <description><![CDATA[I've been doing a fair bit of hiring in this year. Turns out that everyone has wildly different ideas about who is a good hire, and who sucks the big one. So here are some top tips to help you get the good apples.]]></description>
  619. <content:encoded><![CDATA[<blockquote class="dylan"><p>When all of your advisers heave their plastic<br />
  620. At your feet to convince you of your pain<br />
  621. Trying to prove that your conclusions should be more drastic<br />
  622. Won&#8217;t you come see me, Queen Jane?<br />
  623. - QUEEN JANE APPROXIMATELY</p></blockquote>
  624. <p>So I&#8217;ve been doing a fair bit of hiring in this year. Turns out that everyone has wildly different ideas about who is a good hire, and who sucks the big one. Let&#8217;s get straight to it &#8211; here are ten questions. Leave your thoughts in the comments. I&#8217;ll share my views (with reasons) once all the important folk have commented. Discussions on the <a href="">#iwouldhire</a> hashtag please.</p>
  625. <p><a href=""><img class="aligncenter size-full wp-image-1792" title="Jerk" src="" alt="" width="318" height="335" /></a></p>
  626. <p>Each persona has a nice short name, so you can leave comments in the form of (assuming you went for the first option in every case):<br />
  628. <p>And that&#8217;s only 62 characters. So you can tweet it with the hashtag and the link back and everything to give me some lovely, sweet, linky love juice.</p>
  629. <p><strong>1. PUSSY OR LEAPFROG</strong><br />
  630. <em> A solid worker than executes the strategy laid out by upper management<br />
  631. OR<br />
  632. Someone with a critical eye and scientific mind that questions everything, clearing escalating their concerns. If their boss doesn&#8217;t listen, they escalate even higher.</em></p>
  633. <p><strong>2. PISSANT vs PLODDER</strong><br />
  634. <em> The developer that whines about everything, even though they&#8217;re less experienced than you, and they&#8217;re wrong most of the time<br />
  635. OR<br />
  636. The developer that quietly goes about their business and doesn&#8217;t rock the boat</em></p>
  637. <p><strong>3. BADGES vs SCARS</strong><br />
  638. <em> A solid developer that is certified in every product in your stack<br />
  639. OR<br />
  640. A seasoned developer with excellent track record who has never been certified in anything and has never touched the products in your stack</em></p>
  641. <p><strong>4. EDU vs EXP</strong><br />
  642. <em> The kid fresh out of college with her three year university degree<br />
  643. OR<br />
  644. The kid that didn&#8217;t bother with college and has three years experience</em></p>
  645. <p><strong>5. SUIT vs SLOB</strong><br />
  646. <em> The well dressed, articulate MBA grad that doesn&#8217;t open their mouth in a meeting<br />
  647. OR<br />
  648. The guy that security tries to escort out of the building twice a week that rants and raves in every meeting</em></p>
  649. <p><strong>6. PLANNER vs REBEL</strong><br />
  650. <em> The dude that submits a well thought out business case for new ideas in the company and requests time and budget to develop them<br />
  651. OR<br />
  652. The dude that doesn&#8217;t ask, builds something off-piste without approval, and presents it when it has some substance</em></p>
  653. <p><strong>7. LATE vs LIE</strong><br />
  654. <em> The guy who was late for the interview<br />
  655. OR<br />
  656. The guy that made some shit up on his CV</em></p>
  657. <p><strong>8. PERFECT vs POTTYMOUTH</strong><br />
  658. <em> Someone that has a perfectly constructed LinkedIn profile<br />
  659. OR<br />
  660. Someone that has a pretty filthy, off-topic blog</em></p>
  661. <p><strong>9. WINNER vs LOSER</strong><br />
  662. <em> Talks about many succesful projects in the interview<br />
  663. vs<br />
  664. Talks about numerous disasters in the interview</em></p>
  665. <p><strong>10. FAD vs SAD</strong><br />
  666. <em> Wants to try the new tech that the kids love on every project, even though they&#8217;ve never used it in production<br />
  667. vs<br />
  668. Happy to stick to the tried and tested old stuff, even though it isn&#8217;t exactly leading edge</em></p>
  669. <p>So answers below in the format suggested. A beer if anyone matches 9 out of 10 on my list, and a job if anyone matched all of them (you&#8217;ve got a 1 in 1024 chance of guessing that).</p>
  670. <p>Note: While the tips outlined in this post are invaluable, they are in no way endorsed by the HR department of any company I have ever worked for.</p>
  671. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  672. <wfw:commentRss></wfw:commentRss>
  673. <slash:comments>14</slash:comments>
  674. </item>
  675. <item>
  676. <title>Microsoft vs Adobe, Ryder Cup Style</title>
  677. <link></link>
  678. <comments></comments>
  679. <pubDate>Sat, 09 Oct 2010 20:31:37 +0000</pubDate>
  680. <dc:creator>Jon Marks</dc:creator>
  681. <category><![CDATA[Future of CMS]]></category>
  682. <category><![CDATA[adobe]]></category>
  683. <category><![CDATA[aquisitions]]></category>
  684. <category><![CDATA[day]]></category>
  685. <category><![CDATA[flash]]></category>
  686. <category><![CDATA[microsoft]]></category>
  687. <category><![CDATA[omniture]]></category>
  688. <category><![CDATA[photoshop]]></category>
  689. <category><![CDATA[silverlight]]></category>
  691. <guid isPermaLink="false"></guid>
  692. <description><![CDATA[In light of recent rumours, I figured it would be a good waste of time to take most of Adobe's products, and line them up, Ryder Cup style, against the closest Microsoft equivalent.]]></description>
  693. <content:encoded><![CDATA[<blockquote class="dylan"><p>You got a lotta nerve<br />
  694. To say you are my friend<br />
  695. When I was down<br />
  696. You just stood there grinning<br />
  697. You got a lotta nerve<br />
  698. To say you gota helping hand to lend<br />
  699. You just want to be on<br />
  700. The side that&#8217;s winning<br />
  701. - POSITIVELY 4TH STREET</p></blockquote>
  702. <p>Let&#8217;s set the record straight. I can&#8217;t play golf. My course record is 120 odd, which sucks. But I love watching it. Especially the Ryder Cup. I actually can&#8217;t think of any sporting event that puts more pressure on the people involved. Let&#8217;s argue that one later.</p>
  703. <p>Unfortunately I wasn&#8217;t watching the Ryder Cup last night. I was trying not to watching some shitty RomCom that my wife was enjoying. So, in honour of the <a href="">New York Times&#8217;</a> rumoured (and stock spiking but highly improbable) Microsoft/Adobe merger, I made me this:</p>
  704. <p><a href=""><img src="" alt="" title="MicrosoftVsAdobe" width="562" height="660" class="aligncenter size-full wp-image-1780" /></a></p>
  705. <p>All of the scores are completely subjective. It&#8217;s worth mentioning that while <a href="">Captain Shantanu</a> played his strongest possible team (of 14 players), <a href="">Captain Steve</a> rested some of his powerhouses including Windows itself, SQL Server, Office, Azure, Team XBox and much much more. Steve picked the players that were the best match for Team Adobe&#8217;s players.</p>
  706. <p>If anyone wants to argue the scoring, or provide their own, I&#8217;d be interested. And if anyone wants to give Apple vs Google a bash, that&#8217;ll be cool too. Winner plays Adobe.</p>
  707. <p>The finish of this one wasn&#8217;t quite a nailbiting as the <a href="">2010 Ryder Cup</a>, so Microsoft Paint&#8217;s controversial win over Adobe Photoshop didn&#8217;t change the outcome. I do so love golf. Although I love cricket more. And, to end on a random fact, Shantanu loves cricket even more than I do. </p>
  708. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  709. <wfw:commentRss></wfw:commentRss>
  710. <slash:comments>4</slash:comments>
  711. </item>
  712. <item>
  713. <title>Five Things I’m Probably Wrong About</title>
  714. <link></link>
  715. <comments></comments>
  716. <pubDate>Fri, 24 Sep 2010 20:42:44 +0000</pubDate>
  717. <dc:creator>Jon Marks</dc:creator>
  718. <category><![CDATA[Ramblings]]></category>
  719. <category><![CDATA[CMS]]></category>
  720. <category><![CDATA[development]]></category>
  721. <category><![CDATA[json]]></category>
  722. <category><![CDATA[perl]]></category>
  723. <category><![CDATA[rdf]]></category>
  724. <category><![CDATA[standards]]></category>
  725. <category><![CDATA[XML]]></category>
  726. <category><![CDATA[xslt]]></category>
  728. <guid isPermaLink="false"></guid>
  729. <description><![CDATA[When people tell me that I'm drunk these days, I normally am. But there are some other things people keep telling me that I don't agree with, so they're probably right. They're all related to the fact that I'm an old school control freak dog that probably can't learn new tricks.]]></description>
  730. <content:encoded><![CDATA[<blockquote class="dylan"><p>Now you would not think to look at him<br />
  731. But he was famous long ago<br />
  732. For playing the electric violin<br />
  733. On Desolation Row<br />
  734. - DESOLATION ROW</p></blockquote>
  735. <p>A few months ago, I was chatting to a <a href="">very wise man</a>. He said to me: &#8220;If three people tell you that you&#8217;re drunk, even if you&#8217;ve had nothing to drink, you&#8217;d best go home and sleep it off&#8221;.</p>
  736. <p>When people tell me that I&#8217;m drunk these days, I normally am. But there are some other things people keep telling me that I don&#8217;t agree with, so they&#8217;re probably right. They&#8217;re all related to the fact that I&#8217;m an old school control freak dog that probably can&#8217;t learn new tricks.</p>
  737. <p>So, I give you Five Things I&#8217;m Probably Wrong About But Strongly Believe I&#8217;m Not. Maybe some long blog posts about any or all of these if people want to have an argument and educate me, but I&#8217;ll keep it short for now.</p>
  738. <p><a href=""><img class="aligncenter size-full wp-image-1770" title="Odd One Out" src="" alt="" width="425" height="282" /></a></p>
  739. <p><strong>I prefer XML to JSON</strong>. Yes, I know they&#8217;re not really competing technologies. One is an interop format, and one is an object serialisation. But they sure feel like they compete from where I&#8217;m standing. The kids all seem to prefer JSON over XML as an API response format, even when the client of the API isn&#8217;t JavaScript. But not me. I&#8217;m old school like <a href="">Dave Winer</a>, even though he&#8217;s sometimes a bit of a cock.</p>
  740. <p><strong>I prefer RDFa to Microformats</strong>. And I prefer RDF to XHTML for structured data. I&#8217;ll take structure and standards over conventions. Microformats are more popular than RDFa, and people are probably right that RDF is complex and hasn&#8217;t taken off. But I can&#8217;t help it. I just don&#8217;t like using CSS classes to imply semantics.</p>
  741. <p><strong>I prefer XSLT to all alternatives.</strong> I love forced well formed markup. I love the fact you can&#8217;t be lazy and hack. I love the override model and the terminology they use. I love XSLT so much that I don&#8217;t really know what the viable alternatives are. <a href="">Freemarker</a>? <a href="">mustache</a>? I hate all web templating languages that end in a P. That includes JSP, ASP(.NET), PHP. It&#8217;s not easy to make XSLT spaghetti like you see in the P langauges. I know the kids all think XSLT is complicated, verbose and slow, but I just don&#8217;t see it.</p>
  742. <p><strong>I prefer strongly typed to weakly typed languages.</strong> The theme of control continues. I&#8217;ve seen to many non-typed programmers write hundreds of test cases for their code which pretty much replicated a typing system. Compilers are an automated test suite in my book. While we&#8217;re here, I hate Perl more than anything else. Especially if the project team size is greater than one. <em>&#8220;<a href="'s_more_than_one_way_to_do_it">There&#8217;s more than one way to do it.</a></em>&#8221; Sneaky fuckers just want to write code that is impossible to understand so that the weird guy on the second floor can keep his job maintaining it. I&#8217;ll have a double helping of consistency with some control sauce on top, please.</p>
  743. <p><strong>I prefer referential integrity to chaos.</strong> I like the fact I can&#8217;t get horseshit data into my system. While I believe the repository administrator should be able to disable referential integrity (<a href="">REFINT</a>) constraints for performance reasons in a tested, production environment, I can&#8217;t handle the mess my development repositories get in to. Many smart folk are telling me REFINT is a slow waste of time and a layer above the repo should be responsible for it. But I don&#8217;t buy that either. Note that I am a big NoSQL fan and prefer a hierarchical repository to a relational one.</p>
  744. <p>So you see, I&#8217;m a freak. My developers are all tree-loving hippies that want flexibility. I want impose technologies that restrict the hell out of all of that. And you all thought I was the hippy! If any of you, dear readers, agree with me on any of the above, I&#8217;d feel a whole lot better. I&#8217;m feeling rather alone out here. I&#8217;m like the guy at the back of the crowd:</p>
  745. <blockquote><p><strong>Brian</strong>: Please, please, please listen! I&#8217;ve got one or two things to say.<br />
  746. <strong> The Crowd</strong>: Tell us! Tell us both of them!<br />
  747. <strong> Brian</strong>: Look, you&#8217;ve got it all wrong! You don&#8217;t NEED to follow ME, You don&#8217;t NEED to follow ANYBODY! You&#8217;ve got to think for your selves! You&#8217;re ALL individuals!<br />
  748. <strong> The Crowd</strong>: Yes! We&#8217;re all individuals!<br />
  749. <strong> Brian</strong>: You&#8217;re all different!<br />
  750. <strong> The Crowd</strong>: Yes, we ARE all different!<br />
  751. <strong> Man in crowd</strong>: I&#8217;m not&#8230;<br />
  752. <strong> The Crowd</strong>: Sch!<br />
  753. - Life of Brian (1979)</p></blockquote>
  754. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  755. <wfw:commentRss></wfw:commentRss>
  756. <slash:comments>16</slash:comments>
  757. </item>
  758. <item>
  759. <title>Broken Bones, Good Deals and My Daddy</title>
  760. <link></link>
  761. <comments></comments>
  762. <pubDate>Tue, 31 Aug 2010 20:29:15 +0000</pubDate>
  763. <dc:creator>Jon Marks</dc:creator>
  764. <category><![CDATA[Ramblings]]></category>
  765. <category><![CDATA[contract]]></category>
  766. <category><![CDATA[doctor]]></category>
  767. <category><![CDATA[negotiation]]></category>
  768. <category><![CDATA[procurement]]></category>
  769. <category><![CDATA[vendor]]></category>
  771. <guid isPermaLink="false"></guid>
  772. <description><![CDATA[Gather round, children. Let me tell you about my Dad. He's a wonderful, smart man. He taught me to play chess when I was 3. He is also an orthopaedic surgeon, which means he fixes broken bones and things. He worked for many many many years in government hospitals until, about ten years ago, he moved from the operating theatre to the courtrooms, working in the medico-legal world.]]></description>
  773. <content:encoded><![CDATA[<blockquote class="dylan"><p>I don&#8217;t have the strength<br />
  774. To get up and take another shot<br />
  775. And my best friend, my doctor<br />
  776. Won&#8217;t even say what it is I&#8217;ve got<br />
  777. - JUST LIKE TOM THUMB&#8217;S BLUES</p></blockquote>
  778. <p>Gather round, children. Let me tell you about my Dad. He&#8217;s a wonderful, smart man. He taught me to play chess when I was 3. He is also an <a href="">orthopaedic surgeon</a>, which means he fixes broken bones and things. He comes from a long line of doctors, which I broke when I turned out to be a computer geek. He worked for many many many years in government hospitals until, about ten years ago, he moved from the operating theatre to the courtrooms, working in the <a href="">medico-legal</a> world.</p>
  779. <p>Here is how it works. Someone gets injured somehow. In South Africa where I grew up, it is normally a car accident. South Africa has one of the worst road safety records in the world. It is often <a href="">whiplash</a>. Don&#8217;t ever get my Dad started on whiplash. Seriously.</p>
  780. <p>Anyway, the insurance companies need to reimburse the victim for medical bills, loss of earnings, psychological trauma and other goodies. And this is where it gets tricky &#8211; you need to put a dollar (or ZAR) value onto all of this. It is complicated even more when some victims (either fraudulenty, subconsciously or due to lawyer&#8217;s pressure) fake or exaggerate their situations.</p>
  781. <p style="text-align: center;"><a href=""><img class="aligncenter size-full wp-image-1763" title="FDA-vision-test_600" src="" alt="" width="420" height="488" /></a></p>
  782. <p>Which is where the experts come in. Both the insurance fund lawyer and the victim&#8217;s lawyer need to ensure that they have medical experts on their benches. And here is the cool bit. All the senior orthopods in South Africa know and respect one another. Most of them will represent both the patient or the insurance fund &#8211; they don&#8217;t play favourite.</p>
  783. <p>So the two doctors will sit in the courtroom, recognise each other, and think to themselves &#8220;Oh look, they&#8217;ve got Doctor {insert name here} . He&#8217;s a good guy who knows his shit and will fairly represent the situation.&#8221; And, more often than not, they&#8217;ll quickly come to a fair and equitable agreement. The doctors normally don&#8217;t even open their mouths in court. They just sit there like finely tuned bullshit detectors and only get involved when the bullshit levels rise. However, if either side lacks a respected expert, things can drag on a whole lot longer and end in a mess. Of course this isn&#8217;t always the case but, as I understand it, it is pretty close.</p>
  784. <p>So what? Well here is my point. I&#8217;ve recently been engaging a lot of third parties product and service vendors. And I&#8217;ve been really fortunate to work with people from these companies that really really know what they&#8217;re doing. And, they seem to think I know what I&#8217;m doing. Which has made the entire process quick, painless and fair. Both sides know what a fair day rate for consultants is. Both sides know which products are real and needed for the solution, and can smell <a href="">snakeoil</a> a mile away.</p>
  785. <p>So, the moral of the story. When engaging third parties, make sure that you have someone on your team that knows the industry backwards, and make sure the third party knows that you know. Secondly, make sure that the third party has someone that knows their industry backwards and doesn&#8217;t just sprout hot air.</p>
  786. <p>You&#8217;ll save yourself a fuckload of time and stress. Trust me. I&#8217;m a Doctor&#8217;s son.</p>
  787. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  788. <wfw:commentRss></wfw:commentRss>
  789. <slash:comments>2</slash:comments>
  790. </item>
  791. <item>
  792. <title>Drifting Yellow Dots – Gartner CMS MQ 2010</title>
  793. <link></link>
  794. <comments></comments>
  795. <pubDate>Fri, 27 Aug 2010 22:08:32 +0000</pubDate>
  796. <dc:creator>Jon Marks</dc:creator>
  797. <category><![CDATA[Ramblings]]></category>
  798. <category><![CDATA[alterian]]></category>
  799. <category><![CDATA[autonomy]]></category>
  800. <category><![CDATA[coremedia]]></category>
  801. <category><![CDATA[day]]></category>
  802. <category><![CDATA[EPiServer]]></category>
  803. <category><![CDATA[fatwire]]></category>
  804. <category><![CDATA[gartner]]></category>
  805. <category><![CDATA[oracle]]></category>
  806. <category><![CDATA[quadrant]]></category>
  807. <category><![CDATA[sdl]]></category>
  808. <category><![CDATA[sitecore]]></category>
  809. <category><![CDATA[tridion]]></category>
  810. <category><![CDATA[vignette]]></category>
  812. <guid isPermaLink="false"></guid>
  813. <description><![CDATA[Lordy, has it been a year already? Sure has. The 2010 Gartner Magic Quadrant for WCM is out. You can get the report here courtesy of our friends at SiteCore. As usual it is worth a read, but here are the juicy bits.]]></description>
  814. <content:encoded><![CDATA[<blockquote class="dylan"><p>I began to think what a deed I&#8217;d done.<br />
  815. I grabbed my hat and I began to run.<br />
  816. I made a god run but I ran too slow;<br />
  817. They overtook me down in Jericho<br />
  818. - IN SEARCH OF LITTLE SADIE</p></blockquote>
  819. <p>Lordy, has it been a year already? Sure has. The 2010 Gartner Magic Quadrant for WCM is out. You can <a href="">get the report here</a> courtesy of our friends at SiteCore. As usual it is worth a read, but here is the juicy bit:</p>
  820. <p><a href=""><img class="aligncenter size-medium wp-image-1755" title="wcmmq2010" src="" alt="" width="279" height="300" /></a></p>
  821. <p>I&#8217;ve marked the guys that have improved a reasonable amount with a green line, indicating  where they&#8217;ve moved to since 2009. No-one has really slipped, although a few have vanished. EMC have given up on WCM and are partnering with Fatwire instead. <a href="">Vignette</a> and Nstein are also now part of the Open Text dot. Expect to see <a href="">Day replaced by Adobe</a> on here in 2011.</p>
  822. <p>They&#8217;ve stuck with the same Big Three (Oracle, Automony/Interwoven and Open Text) in the lead as last time. Two other Big Guys &#8211; Microsoft and IBM &#8211; are inching closer to the Leader Quadrant. It does seem that to be near the top of the &#8220;ability to execute&#8221; axis, you need to be a massive company and have technology that is at least ten years old. I <a href="">ranted about this last year</a>, and the same thoughts apply. I should point out that this dimension is defined as &#8220;<em>how well a vendor sells and supports its WCM products and services</em>&#8220;, not on the success of implementations or happiness of customers. If you want to get the products with the most marketing dollars behind them, this is the axis for you.</p>
  823. <p>The Open Text logic still confounds me. Here is how I see it. In 2009, Open Text was one of the three leaders, based on what I can only assume was The Product Formerly Known As RedDot. Vignette and Nstein were lingering in the shitty quadrant (VIGN on the border, admittedly). So my only conclusion is that RedDot was the favoured product in the eyes of Gartner. However, my spider senses (and OTEX staff layoffs) tell me RedDot is on its way out and the Vignette WCM product is the Chosen One. So I&#8217;d have expected the Gartner folk to move OTEX further into the danger zone, but the uncertainly and product direction have actually given them a boost.</p>
  824. <p>The tussle between the younger upstarts is as close as ever. The Java vendors (FatWire and Day) have gained slightly on the .NET ones (SiteCore, Ektron). The Java/.NET hybrid, SDL, keeps its nose in front. I think we&#8217;ll see bigger gaps in 2011.</p>
  825. <p>Last year, I noted that poor EPiServer had got a bit of a raw deal. That&#8217;s been fixed. I&#8217;ve always felt they should be sitting right next to SiteCore on this thing. And CoreMedia also got a big bonus. Alterian got a little boost, but they&#8217;re still in the quadrant of despair.</p>
  826. <p>There are two new vendors on there, Atex and Dynamicweb. I&#8217;ve heard of the latter but never seen them. And only heard of Atex when they aquired Polopoly as few years ago. Never seen their product either, so not comments here.</p>
  827. <p>Still no Open Source vendors on here, for the same revenue related reasons as last time. I&#8217;m not going over all that again.</p>
  828. <p>Most of these little yellow dots haven&#8217;t drifted very far in a year &#8211; the report is pretty similar despite the M&amp;A activity that has kept us bloggers busy. So pretty much a repeat of last year. And, like last year, here is hoping Gartner&#8217;s lawyers don&#8217;t serve me any takedown notices.</p>
  829. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  830. <wfw:commentRss></wfw:commentRss>
  831. <slash:comments>8</slash:comments>
  832. </item>
  833. <item>
  834. <title>It Can All Change In A ChartBeat</title>
  835. <link></link>
  836. <comments></comments>
  837. <pubDate>Mon, 23 Aug 2010 23:24:55 +0000</pubDate>
  838. <dc:creator>Jon Marks</dc:creator>
  839. <category><![CDATA[Ramblings]]></category>
  840. <category><![CDATA[Analytics]]></category>
  841. <category><![CDATA[chartbeat]]></category>
  842. <category><![CDATA[google]]></category>
  843. <category><![CDATA[social media]]></category>
  845. <guid isPermaLink="false"></guid>
  846. <description><![CDATA[It's pretty addictive watching your blog stats, isn't it? Remember when Google Analytics came to town and instead of waiting days to see traffic reports, you could see updates in mere hours. On a good day, you could sometimes see things in 15 minutes. Well, GA, there is a new new kid on the block, he shows you data in real time, and his name is <a href="">chartbeat</a>.
  847. ]]></description>
  848. <content:encoded><![CDATA[<blockquote class="dylan"><p>The joint is jumpin&#8217;<br />
  849. It&#8217;s really somethin&#8217;<br />
  850. The beat is pumpin&#8217;<br />
  851. My heart is thumpin&#8217;<br />
  852. Spent my money on you honey<br />
  853. - HAD A DREAM ABOUT YOU, BABY</p></blockquote>
  854. <p>It&#8217;s pretty addictive watching your blog stats, isn&#8217;t it? Remember when Google Analytics came to town and instead of waiting days to see traffic reports, you could see updates in mere hours. On a good day, you could sometimes see things in 15 minutes. Well, GA, there is a new new kid on the block, he shows you data in real time, and his name is <a href="">chartbeat</a>.</p>
  855. <p><a href=""><img class="aligncenter size-full wp-image-1743" title="chartbeat_media_logo" src="" alt="" width="318" height="54" /></a></p>
  856. <p>I&#8217;d never heard of it until last week when I was lucky enough to meet the cool folk at <a href="">betaworks</a> (@Borthwick and @aweissman). These guys don&#8217;t mess around &#8211; they&#8217;re behind such social media hits as <a href="">TweetDeck</a>, <a href=""></a> and <a href="">twitterfeed</a>. You heard it here first &#8211; chartbeat is going to be big.</p>
  857. <p>It&#8217;s really easy to get started &#8211; you just stick a couple of JavaScript tags onto all your pages a.l.a. Google Analytics, and you are done. The reports you get are much simpler than those from GA, but it is really real time. You can see the visitors on your site within a couple of seconds of their arrival. I wrote a <a href="">test link bait post (sorry)</a>, tweeted it, and saw my 17 concurrent visitors within seconds.</p>
  858. <div id="attachment_1744" class="wp-caption aligncenter" style="width: 310px"><a href=""><img class="size-medium wp-image-1744" title="chartbeatscreen1" src="" alt="" width="300" height="240" /></a><p class="wp-caption-text">Visitors to your site in real time. Notice one person is writing a comment. Click for large image.</p></div>
  859. <p>But there is more. GA simply registers a hit when a page is loaded. chartbeat has a heartbeat and chats to the server every couple of seconds. This means that it can more accurately measure time spent on the site, user actions like scrolling (giving a nice scroll depth metric), and even keypresses. In the screenshot above, you&#8217;ll see one person is writing &#8211; they were leaving a comment at the time.</p>
  860. <div id="attachment_1746" class="wp-caption aligncenter" style="width: 310px"><a href=""><img class="size-medium wp-image-1746" title="chartbeatscreen3" src="" alt="" width="300" height="227" /></a><p class="wp-caption-text">Typical detail page. Gotta love the scroll depth and engagement indicators</p></div>
  861. <p>It also comes with a nice preintegration with <a href="">backtype</a>. This searches the social media buzz of the interwebs and reports activity as part of your report. When @izahoor, @theg, @irina_guseva, @cmsreport and @kevinc2003 were kind enough to retweet my horseshit blog post, I saw my dashboard get a bit busier and saw their link love appear shortly afterwards in the backtype console. Good stuff.</p>
  862. <div id="attachment_1745" class="wp-caption aligncenter" style="width: 310px"><a href=""><img class="size-medium wp-image-1745" title="chartbeatscreen2" src="" alt="" width="300" height="204" /></a><p class="wp-caption-text">Nice integration with backtype. Click for large image.</p></div>
  863. <p>It has an <a href="">API</a> and a bucket of prebuilt <a href="">widgets</a>. I haven&#8217;t had time to play with these, but I might add a widget here soon. The downside being, of course, it would pretty much always say &#8220;1 user currently viewing this page&#8221;. And that would be you.</p>
  864. <p>It gets better. chartbeat even monitors the health of your site. While I was testing, <a href="">my dickhead hosting company GoDaddy</a> had yet another embolism, and my site flatlined for about 5 minutes. But unlike the previous million times this happened, it didn&#8217;t die silenty. I got a nice email from chartbeat informing me of the tragedy. Also, it tells you how long a page took to load for each user. 20 seconds isn&#8217;t great, GoDaddy. And yes, it has a free iPhone app too.</p>
  865. <p><a href=""><img class="aligncenter size-medium wp-image-1751" title="cbiPhone" src="" alt="" width="200" height="300" /></a></p>
  866. <p>Because I&#8217;m a social media guru who understands transparancy and douchebaggery, I&#8217;ve shared my wonderful stats with the world. So have a look at <a href=";k=c59ec106fbe4b408ff964fea71bf65a9#">my chartbeat dashboard</a>.</p>
  867. <p>You do have to pay a small fee for all this goodness, but it is money well spent. Buy it. Finally, a huge nod to <a href="">@arctictony</a> for helping me out.</p>
  868. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  869. <wfw:commentRss></wfw:commentRss>
  870. <slash:comments>3</slash:comments>
  871. </item>
  872. <item>
  873. <title>Drupal, Lawsuits and a Peruvian Prostitute</title>
  874. <link></link>
  875. <comments></comments>
  876. <pubDate>Mon, 23 Aug 2010 20:42:15 +0000</pubDate>
  877. <dc:creator>Jon Marks</dc:creator>
  878. <category><![CDATA[Ramblings]]></category>
  879. <category><![CDATA[bastard]]></category>
  880. <category><![CDATA[con]]></category>
  881. <category><![CDATA[liar]]></category>
  882. <category><![CDATA[linkbait]]></category>
  883. <category><![CDATA[whore]]></category>
  885. <guid isPermaLink="false"></guid>
  886. <description><![CDATA[Sorry, so very sorry, dear reader. This isn't a real post. But it is research for a real post. You see, I'm test driving a new analytics package which, on first impressions, is awesome. Problem is, my blog doesn't get enough traffic to make any screenshots interesting. Which is why you are here.]]></description>
  887. <content:encoded><![CDATA[<blockquote class="dylan"><p>Hang on to your woman if you got one<br />
  888. Remember in El Paso, once, you shot one.<br />
  889. She may have been a whore, but she was a hot one<br />
  890. - BILLY</p></blockquote>
  891. <p>Sorry, so very sorry, dear reader. This isn&#8217;t a real post. But it is research for <a href="">a real post</a>. You see, I&#8217;m test driving a new analytics package which, on first impressions, is awesome. Problem is, my blog doesn&#8217;t get enough traffic to make any screenshots interesting. Which is why you are here.</p>
  892. <p>So, before you leave, browse around and read some shit. It&#8217;s all in the interest of science. Retweet it, leave a comment, tell your friends and make my screenshots the busiest darn screenshots any analytics review ever had. If you&#8217;re very very lucky, you might even notice your visit in a picture in my next post.</p>
  893. <p><a href=""><img class="aligncenter size-full wp-image-1731" title="linkbait" src="" alt="" width="476" height="214" /></a></p>
  894. <p>Let&#8217;s see if 1337 Twitter followers are worth anything. I&#8217;m serious. I&#8217;ve got elite followers. And I&#8217;m sure I&#8217;ll lose a whole bunch of them pretty damn soon.</p>
  895. <p><strong>UPDATE</strong>: You can read the real blog post now &#8211; <a href="">It Can All Change In a ChartBeat</a>. And I only lost 2 Twitter followers. Fuck &#8216;em.</p>
  896. <p><a href=""><img class="aligncenter size-full wp-image-1737" title="l337" src="" alt="" width="636" height="178" /></a></p>
  897. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  898. <wfw:commentRss></wfw:commentRss>
  899. <slash:comments>6</slash:comments>
  900. </item>
  901. <item>
  902. <title>Painting the Analytics World Blue</title>
  903. <link></link>
  904. <comments></comments>
  905. <pubDate>Fri, 13 Aug 2010 21:18:37 +0000</pubDate>
  906. <dc:creator>Jon Marks</dc:creator>
  907. <category><![CDATA[Ramblings]]></category>
  908. <category><![CDATA[adobe]]></category>
  909. <category><![CDATA[Analytics]]></category>
  910. <category><![CDATA[apple]]></category>
  911. <category><![CDATA[coremetrics]]></category>
  912. <category><![CDATA[google]]></category>
  913. <category><![CDATA[ibm]]></category>
  914. <category><![CDATA[omniture]]></category>
  915. <category><![CDATA[unica]]></category>
  916. <category><![CDATA[webtrends]]></category>
  918. <guid isPermaLink="false"></guid>
  919. <description><![CDATA[We've got some more BlueWashing going on. IBM announced today that they're acquired analytics and marketing vendor Unica for $480 million. It seems like a lot of cash to me, but then again IBM have got plenty and what do I know. I do know it follows quite shortly after they bought pure analytics vendor CoreMetrics.]]></description>
  920. <content:encoded><![CDATA[<blockquote class="dylan"><p>I already assumed<br />
  921. That we&#8217;re in the felony room<br />
  922. But I ain&#8217;t a judge, you don&#8217;t have to be nice to me<br />
  923. But please tell that<br />
  924. To your friend in the cowboy hat<br />
  925. You know he keeps on sayin&#8217; ev&#8217;rythin&#8217; twice to me<br />
  926. - SHE&#8217;S YOUR LOVER NOW</p></blockquote>
  927. <p>We&#8217;ve got some more BlueWashing going on. <a href="">IBM announced today</a> that they&#8217;re acquired analytics and marketing vendor Unica for $480 million. It seems like a lot of cash to me, but then again IBM have got plenty and what do I know. I do know it follows quite shortly after they bought pure analytics vendor CoreMetrics.</p>
  928. <p style="text-align: center;"><a href=""><img class="aligncenter size-full wp-image-1723" title="ibm_unica_coremetrics" src="" alt="" width="456" height="152" /></a></p>
  929. <p>The &#8220;<a href="">Farewell to Coremetrics and Web Analytics as you knew it</a>&#8221; post from the Unica blog (two months ago) is quite interesting in retrospect:</p>
  930. <blockquote><p>Now, IBM’s acquisition of Coremetrics follows suit as IBM folds Coremetrics into Websphere with the likely intention of making it part of the Websphere eCommerce technology stack.</p>
  931. <p>With no major standalone contenders remaining in the market (WebTrends had signaled their interest in getting acquired) prospective web analytics buyers must evaluate the core competencies of the parent company in order to determine the best match for their current and future needs.</p>
  932. <p><strong>IBM does NOT appear to be making a play for a broader analytics offering</strong></p></blockquote>
  933. <p>The wise seem to be saying that IBM isn&#8217;t actually going to bother marketing either Unica or CoreMetrics, but rather just add them into the already vast IBM Suite. Which effectively mean they&#8217;re being withdrawn from the Analytics battlefield. If that is the case, then the three players that will be slugging it out will be Adobe Omniture, Google Analytics and WebTrends. And although WebTrends are alledgely not trying to put themselves up for sale, I suspect they might be gobbled up quite soon. Maybe AAPL will feel left out of an Adobe vs Google slugfest, and buy WebTrends just to join the fracas. Maybe we should count Nedstat too, but I don&#8217;t see much of them. Or have they already been bought?</p>
  934. <p>I&#8217;m the kind of guy that likes to believe the <a href="">IBM &lt;-&gt; HAL</a> thing (although Arthur denies it), and I&#8217;ve got this vision of poor IBM acquired vendors trying to wriggle free of the corporation. For no good reason, let&#8217;s end on this:</p>
  935. <blockquote><p>Dave Bowman: Open the pod bay doors, HAL.<br />
  936. HAL: I&#8217;m sorry, Dave. I&#8217;m afraid I can&#8217;t do that.</p></blockquote>
  937. <p><a href=""><img class="aligncenter size-full wp-image-1725" title="2001 SPACE ODYSSEY" src="" alt="" width="450" height="250" /></a></p>
  938. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  939. <wfw:commentRss></wfw:commentRss>
  940. <slash:comments>5</slash:comments>
  941. </item>
  942. <item>
  943. <title>My Midlife Crisis Catalyst</title>
  944. <link></link>
  945. <comments></comments>
  946. <pubDate>Sat, 07 Aug 2010 20:23:48 +0000</pubDate>
  947. <dc:creator>Jon Marks</dc:creator>
  948. <category><![CDATA[Ramblings]]></category>
  949. <category><![CDATA[This Blog]]></category>
  950. <category><![CDATA[civilization]]></category>
  951. <category><![CDATA[games]]></category>
  953. <guid isPermaLink="false"></guid>
  954. <description><![CDATA[A friend of mine just reintroduced me to my favourite game of all time. A curse on all of his houses. Civilization Revolution is out on iOS and, the bad news is, it is as good and addictive as ever. I don't play games any more, trying to balance my time between my kids, my job, my blog and the odd bit of sleep. That's all about to go to hell.]]></description>
  955. <content:encoded><![CDATA[<blockquote class="dylan"><p>Come you masters of war<br />
  956. You that build all the guns<br />
  957. You that build the death planes<br />
  958. You that build the big bombs<br />
  959. - MASTERS OF WAR</p></blockquote>
  960. <p>A friend of mine just reintroduced me to my favourite game of all time. A curse on all of his houses. <em><a href="">Civilization Revolution</a></em> is available on iOS and, the bad news is, it is as good and addictive as ever. It&#8217;s actually been around for almost a year, but I was blissfully unaware. I don&#8217;t play games any more, trying to balance my life between my kids, my job, my drinking, my blog and the odd bit of sleep. That&#8217;s all about to go to hell.</p>
  961. <p>I&#8217;ve given it a try and it rocks. I feel like I&#8217;m 18 again when all I had to do was play <em>Civilization I</em>, go out and get drunk, play some more, drinks some more, write some pretty easy university maths exams, and play even more. But two decades later, I&#8217;m told I have &#8220;responsibilities&#8221;. I&#8217;ve got a bad feeling that this week the kids are going to go feral, my wife will leave me, the fridge will fester, and I&#8217;ll get fired.</p>
  962. <p><a href=""><img class="aligncenter size-full wp-image-1712" title="Civilization_for_iPhone" src="" alt="" width="480" height="320" /></a></p>
  963. <p>But a man has gotta do what a man has gotta do. The game won&#8217;t beat itself on Emperor level, you know. Those asshat Greeks need to be taught a lesson, the shifty Aztecs can&#8217;t be trusted, and Ghengis Khan is really, really pissing me off. So until I&#8217;ve sorted that out, you won&#8217;t be seeing much on this blog. £3.99 is a small price to pay for your life to fall apart. <a href="">Buy it</a>, you know you want to.</p>
  964. <p>[<b>UPDATE</b>]: The iPhone version went FREE the day after I flushed £3.99 down the bog. Makes my time-stealing, money-stealing friend that ruined my life even more of a ballsack. At least the rest of you can have your midlife crisis for free.</p>
  965. <p><a href=""><img class="aligncenter size-full wp-image-1713" title="CivFullMap" src="" alt="" width="480" height="320" /></a></p>
  966. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  967. <wfw:commentRss></wfw:commentRss>
  968. <slash:comments>12</slash:comments>
  969. </item>
  970. <item>
  971. <title>Warning: Acquisitions May Cause Dizziness, Vomiting, Nausea and Diarrhea</title>
  972. <link></link>
  973. <comments></comments>
  974. <pubDate>Wed, 04 Aug 2010 21:41:00 +0000</pubDate>
  975. <dc:creator>Jon Marks</dc:creator>
  976. <category><![CDATA[Ramblings]]></category>
  977. <category><![CDATA[autonomy]]></category>
  978. <category><![CDATA[interwoven]]></category>
  979. <category><![CDATA[mental]]></category>
  980. <category><![CDATA[open text]]></category>
  981. <category><![CDATA[rant]]></category>
  982. <category><![CDATA[reddot]]></category>
  983. <category><![CDATA[vignette]]></category>
  985. <guid isPermaLink="false"></guid>
  986. <description><![CDATA[Where there is smoke, there is fire. In this case, it'll be a shitstorm of a fire that'll consume everything useful in it's path. A bit like a Scorched Earth Campaign of Content Management. Of course I'm talking about the Autonomy/Open Text speculation, which isn't actually going to happen. Surely.]]></description>
  987. <content:encoded><![CDATA[<blockquote class="dylan"><p>All the tired horses in the sun<br />
  988. How&#8217;m I supposed to get any ridin&#8217; done? Hmm.<br />
  989. - ALL THE TIRED HORSES</p></blockquote>
  990. <p>Where there is smoke, there is fire. In this case, it&#8217;ll be a shitstorm of a fire that&#8217;ll consume everything useful in it&#8217;s path. A bit like a <a href="">Scorched Earth</a> Campaign of Content Management.</p>
  991. <p>Of course I&#8217;m talking about the Autonomy/Open Text speculation <a href="">here</a> (@hakana), <a href="">here</a> (@ldallasBMOC) and <a href="">here</a> (@piewords). In truth, the few rumours are, according to the crowds, highly unlikely to have any substance so this whole post is a waste of time. Apart from photos of CEOs in bed with hookers, no-one in Twitterville can produce a single good reason for it that I can swallow. But if this post even slightly reduces the miniscule chance of this joke of a deal materialising, it&#8217;s time well spent.</p>
  992. <div id="attachment_1702" class="wp-caption aligncenter" style="width: 345px"><a href=""><img class="size-full wp-image-1702" title="BadEngineering" src="" alt="" width="335" height="287" /></a><p class="wp-caption-text">The whole is less than the sum of the parts</p></div>
  993. <p>Onward. It&#8217;s pretty clear there is no way that this deal could make a new sale more likely. The number of different CMS and search products The Firm would have warrants the invention of a new Collective Noun. How about a Gaggle of Products? Or Confusion of Products. Or Mindfuck of Products? Should some poor customer go through a vendor selection exercise and pick Opentonomytext, they&#8217;d need to go through another one to pick the product. Ain&#8217;t gonna happen.</p>
  994. <p>And the poor existing customers. Following the Open Text/Vignette deal, many poor customers are still wondering whether or when their product will be discontinued. They&#8217;re playing Russian Roulette with about 2 bullets in the chamber. If this deal happens, they&#8217;ll have about 4 bullets. Some will jump ship, so the whole idea of creating a maintenance revenue cash cow doesn&#8217;t make sense either. In simple maths terms: (Autonomy Maintenance 2011) + (Open Text Maintenance 2011) &lt; (Opentonomytext Maintenance 2011).</p>
  995. <p>Spare a thought for the search engineers at Vignette. They OEM&#8217;ed Autonomy as their search for years. &#8220;Best of Breed&#8221;, they all cried. Then arch-rival Interwoven was aquired by Autonomy. &#8220;We&#8217;re not paying our arch rival cash every time we sell a product&#8221;, they  cried. &#8220;Autonomy is a piece of shit. Let&#8217;s embed the Open Text search engine.&#8221; So they did. Hopefully they didn&#8217;t delete the code, cause they may be flipping it back pretty soon.</p>
  996. <p>And spare a thought for yours truly. I&#8217;ve pushed my MS Paint skills to the limit creating the <a href="">Super Spliced Open Text Logo</a>. I think the only way I could make a logo for the new beast is on a <a href="">Möbius strip</a>, and I don&#8217;t have any lying around.</p>
  997. <p><a href=""><img class="aligncenter size-full wp-image-1700" title="Super Spice Dollars" src="" alt="" width="447" height="126" /></a></p>
  998. <p>Now I&#8217;m not saying that the road ahead for either company is paved with gold. But they&#8217;ve both got some good products, some great people and a fair bit of cash. If they roll up their sleeves and innovate, they might just be okay. If they keep playing Pass The Parcel with products that develop more slowly than tectonic plates, they&#8217;re toast. Wait! Hold on a second! What&#8217;s that putrid smell? Oh, look, it&#8217;s an an elephant graveyard. And elephants don&#8217;t make good software. Especially dead ones.</p>
  999. <p>P.S. Remember, this isn&#8217;t actually going to happen. Surely. They&#8217;re gonna buy someone else. Answers on a postcard.</p>
  1000. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1001. <wfw:commentRss></wfw:commentRss>
  1002. <slash:comments>3</slash:comments>
  1003. </item>
  1004. <item>
  1005. <title>A Fine Day For Adobe</title>
  1006. <link></link>
  1007. <comments></comments>
  1008. <pubDate>Wed, 28 Jul 2010 08:56:26 +0000</pubDate>
  1009. <dc:creator>Jon Marks</dc:creator>
  1010. <category><![CDATA[Future of CMS]]></category>
  1011. <category><![CDATA[Ramblings]]></category>
  1012. <category><![CDATA[adobe]]></category>
  1013. <category><![CDATA[alfresco]]></category>
  1014. <category><![CDATA[boobs]]></category>
  1015. <category><![CDATA[CMS]]></category>
  1016. <category><![CDATA[day]]></category>
  1017. <category><![CDATA[flash]]></category>
  1018. <category><![CDATA[java]]></category>
  1019. <category><![CDATA[livecycle]]></category>
  1020. <category><![CDATA[spain]]></category>
  1021. <category><![CDATA[wcm]]></category>
  1023. <guid isPermaLink="false"></guid>
  1024. <description><![CDATA[Finally, finally, an acquisition I think I understand. Adobe have just announced they're buying Day Software (press release) for about USD $240 million - just slightly less than OTEX paid for Vignette. Adobe's re-entry into the CMS game is well overdue.]]></description>
  1025. <content:encoded><![CDATA[<blockquote class="dylan"><p>No, there&#8217;s nothin&#8217; you can send me, my own true love,<br />
  1026. There&#8217;s nothin&#8217; I wish to be ownin&#8217;.<br />
  1027. Just carry yourself back to me unspoiled,<br />
  1028. From across that lonesome ocean.<br />
  1029. - BOOTS OF SPANISH LEATHER</p></blockquote>
  1030. <p>Finally, finally, an acquisition I think I understand. <a href="">Adobe </a>have just announced they&#8217;re buying <a href="">Day Software</a> (<a href="">press release</a>) for about USD $240 million &#8211; just slightly less than <a href="">OTEX paid for Vignette</a>. Adobe&#8217;s re-entry into the CMS game is well overdue. Some might argue that the Creative Suite tools are becoming more CMS like.  They dabbled briefly in it when they aquired Macromedia (remember Contribute, anyone?) and the Product Formally Known As Stellent comes from this line.</div>
  1031. <div>This aquisition makes sense from both sides. Kudos to the senior Day team (Erik, David, Kevin, Roy and others) for making Day so attractive. And from Adobe&#8217;s perspective I think it had to be either Day or Alfresco. There aren&#8217;t many independents left, and a Java based technology fits best with them. Many were surprised it wasn&#8217;t Alfresco due to the recent love affair between the two of them. The wise <a href="">ECM Architect, Jeff Potts</a>, says it best so I quote him here:</p>
  1032. <blockquote><p>
  1033. Honestly, I thought Adobe would acquire Alfresco by the end of last year and I was surprised when it didn’t happen. They had done a big OEM deal making Alfresco part of LiveCycle and they did a gigantic Alfresco implementation as part of standing up Adobe’s site. Heck, Adobe even hosted Alfresco’s community event back in 2008. All small potatoes in the grand scheme of things, I know, but I can’t help but feel like the proud parent who’s daughter brought home a keeper, only to find out the guy’s been dating a hottie from Switzerland the whole time.</p></blockquote>
  1034. <p>I must admit I&#8217;m also partly saddened by the news. I rather liked having a few smaller, more nimble independent players. The bigger guys all seem to be getting sidetracked by M&#038;A activity and posturing, and innovation seems to have ground to a halt. I can&#8217;t even begin to get my head around the impending clusterfuck that would be an <a href="">Autonomy Interwoven and</a> <a href="">Open Text merger</a>. If there is any truth to that rumour, put on a hard hat, run for cover and sell your shares in both as quickly as humanly possible. But more on that later perhaps.</p>
  1035. <p>I&#8217;m guessing that operationally this merger will affect Day very little, if any, in the short term. Hopefully it just gives them a  bit more money and clout. A few big questions spring to mind, and hopefully we will get clarity on them soon:</p>
  1036. <ul>
  1037. <li>Day has a good track record contributing to open source projects, particularly the Apache ones. Hopefully this continues.</li>
  1038. <li>Will Adobe have any intentions of integrating the Day products with existing Adobe ones, specifically Adobe Content Server and Adobe LiveCycle Enterprise Suite? I hope it is the end of ColdFusion</li>
  1039. <li>Will Day integrate even more closely with Adobe&#8217;s other big recent purchase &#8211; Omniture?</li>
  1040. <li>Day&#8217;s big event, Ignite, promises <a href="">iPads to all</a>. I hope the Adobe &#8211; Apple squabbles don&#8217;t interfere with anything.</li>
  1041. <li>I hope Day doesn&#8217;t ONLY focus on &#8220;technologies that create and deliver rich online and offline experiences leveraging the ubiquity of Flash and PDF&#8221;. I wonder what the latest Day employee, @kasthomas, makes of this.</li>
  1042. <li>Speaking of which, there is a huge amount going on in the publishing industry at the moment around tablets and magazines and shit. Adobe have been in the thick ofthings with the wildly successful Wired App, and CMS is going to be a big part of this. But I&#8217;m not allowed to talk about this right now, am I?</li>
  1043. </ul>
  1044. <p>Day and Flash have always been close. I remember debating with David whether Flash should be considered a first class citizen of the web. Bigoted me thinks it is a second class citizen. See point 7 in <a href="">David&#8217;s slide deck</a> below:</p>
  1045. <p><a href=""><img class="aligncenter size-full wp-image-1687" title="Day Trends" src="" alt="" width="580" height="415" /></a></p>
  1046. <p>In closing, I think it&#8217;s also really important to note that I&#8217;m writing this from a beach in Lanzarote. It hasn&#8217;t been easy to divert my attention from the Spanish Sun, Spanish Sea, Spanish Sangria and Spanish Boobies Bouncing Around, but yours truly belives it is crucial to keep you all abreast of the latest in CMS developments so has taken a hit for the team to write this up. Signing out, and see you all back on the soggy island for <a href="">#LastThursdayCMS</a> tomorrow night &#8230;</p>
  1047. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1048. <wfw:commentRss></wfw:commentRss>
  1049. <slash:comments>13</slash:comments>
  1050. </item>
  1051. <item>
  1052. <title>The Cloud – Not A Crock of Shit</title>
  1053. <link></link>
  1054. <comments></comments>
  1055. <pubDate>Mon, 21 Jun 2010 21:44:22 +0000</pubDate>
  1056. <dc:creator>Jon Marks</dc:creator>
  1057. <category><![CDATA[Ramblings]]></category>
  1059. <guid isPermaLink="false"></guid>
  1060. <description><![CDATA[It was just over a year ago when a younger, more naive Jon declared the The Cloud is a Crock of Shit. Well, I'm a little wiser now and I'm overjoyed to report that, in fact, it isn't. Cloud Computing is very real, and something you need to know about.]]></description>
  1061. <content:encoded><![CDATA[<blockquote class="dylan"><p>Even though a cloud&#8217;s white curtain in a far-off corner flashed<br />
  1062. An&#8217; the hypnotic splattered mist was slowly lifting<br />
  1063. Electric light still struck like arrows, fired but for the ones<br />
  1064. Condemned to drift or else be kept from drifting<br />
  1065. - CHIMES OF FREEDOM</p></blockquote>
  1066. <p>It was just over a year ago when a younger, more naive Jon declared the <a href="">The Cloud is a Crock of Shit</a>. Well, I&#8217;m a little wiser now and I&#8217;m overjoyed to report that, in fact, it isn&#8217;t. Cloud Computing is very real, and something you need to know about. I HEART clouds.</p>
  1067. <p style="text-align: center;"><a href=""><img class="aligncenter size-medium wp-image-1676" title="heart_cloud" src="" alt="" width="240" height="240" /></a></p>
  1068. <p>In my defense, when I wrote my blog post a year ago, 98% of the time the phrase &#8220;The Cloud&#8221; was used it was by people that didn&#8217;t have a clue what it meant. This has now dropped to 44% which means that, more often than not, you should listen to people that say it. Sadly, the number is still about 85% for people with the word &#8220;Sales&#8221; or &#8220;Business&#8221; on their business cards, so continue to ignore them. And the<a href=""> wikipedia entry</a>, while improved, is still is desparate need of an update.</p>
  1069. <h2>Public Clouds</h2>
  1070. <p>So what is Cloud Computing? There are <a href="">lots</a> <a href="">of</a> <a href="">definitions</a> <a href="">out</a> <a href="">there</a>. But let&#8217;s distill the essence of Cloud Computing by listing things that Cloud Computing is that good old Hosted Services (*aas) and Grid/Utility Computing are NOT. They are:</p>
  1071. <table border="0">
  1072. <tbody>
  1073. <tr>
  1074. <th></th>
  1075. <th>Cloud Computing</th>
  1076. <th>Grid/Utility Computing</th>
  1077. <th>Hosted *aas</th>
  1078. <th>Your Server Room</th>
  1079. </tr>
  1080. <tr>
  1081. <td><strong>Infrastructure Services &#8211; offers a wide variety of platform services</strong></td>
  1082. <td>YES</td>
  1083. <td>NO</td>
  1084. <td>NO</td>
  1085. <td>YES</td>
  1086. </tr>
  1087. <tr>
  1088. <td><strong>Multi-tenancy &#8211; resources shared by a vast set of users</strong></td>
  1089. <td>YES</td>
  1090. <td>SOMETIMES</td>
  1091. <td>SOMETIMES</td>
  1092. <td>NO</td>
  1093. </tr>
  1094. <tr>
  1095. <td><strong>Usage Based Pricing &#8211; very fine grained</strong></td>
  1096. <td>YES</td>
  1097. <td>SOMETIMES</td>
  1098. <td>NO</td>
  1099. <td>NO</td>
  1100. </tr>
  1101. <tr>
  1102. <td><strong>Scalability &#8211; ramped up (with no cap) or down in near real time</strong></td>
  1103. <td>YES</td>
  1104. <td>SOMETIMES</td>
  1105. <td>NO</td>
  1106. <td>NO</td>
  1107. </tr>
  1108. <tr>
  1109. <td><strong>Programmability &#8211; provisioning can be accessed via software</strong></td>
  1110. <td>YES</td>
  1111. <td>NO</td>
  1112. <td>NO</td>
  1113. <td>NO</td>
  1114. </tr>
  1115. <tr>
  1116. <td><strong>Virtualisation &#8211; Machines are virtual, not physical</strong></td>
  1117. <td>MAYBE</td>
  1118. <td>MAYBE</td>
  1119. <td>MAYBE</td>
  1120. <td>MAYBE</td>
  1121. </tr>
  1122. </tbody>
  1123. </table>
  1124. <p>Firstly, you&#8217;ll notice that the concept of virtualisation is nothing to do with Cloud Computing. It&#8217;s an orthogonal concern. I like to think of a Cloud Computing platform a bit like a Java<a href=",_Enterprise_Edition"> JEE App Server</a>. The App Server provides a Java Application ways to access resources like storage, memory, caching, queuing, messaging and more &#8211; all with a standard API. A Cloud Computing API offers access to all of this, and more. Plus an API to allow the programmer to provision more resources. However, unlike the JEE example, the APIs to different cloud providers isn&#8217;t yet standard. But this is what people like <a href="">The Open Cloud Consortium</a> and <a href="">Unified Cloud Interface Project</a> are working on.</p>
  1125. <p>But I talked about this <a href="">last time</a>. Back then, however, I didn&#8217;t have a clue what kind of APIs they were trying to standardise. Now I&#8217;m no expert in this area, after all I was one of the Great Cloud Unwashed a meagre year ago. So the table below that I&#8217;ve thrown together to illustrate Cloud Capability no doubt has plenty of errors and ommissions. So please correct me via the comments and I&#8217;ll update it. If something like this already exists somewhere in the interwebitutes, I couldn&#8217;t find it.</p>
  1126. <table border="0">
  1127. <tbody>
  1128. <tr>
  1129. <th>CAPABILITY</th>
  1130. <th>Microsoft Azure</th>
  1131. <th>Amazon Web Services (AWS)</th>
  1132. <th>Google App Engine (GAE)</th>
  1133. </tr>
  1134. <tr>
  1135. <td><strong>Infrastructure Provisioning</strong></td>
  1136. <td>Windows Azure</td>
  1137. <td>Amazon Elastic Compute Cloud (Amazon EC2)</td>
  1138. <td>n/a &#8211; You just get the App Engine</td>
  1139. </tr>
  1140. <tr>
  1141. <td><strong>NoSQL Database</strong></td>
  1142. <td>Azure Table Services</td>
  1143. <td>Amazon SimpleDB</td>
  1144. <td>App Engine Data Store (BigTable + GFS)</td>
  1145. </tr>
  1146. <tr>
  1147. <td><strong>Relational Database</strong></td>
  1148. <td>SQL Azure</td>
  1149. <td>Amazon Relational Database Service (Amazon RDS) &#8211; MySQL</td>
  1150. <td>n/a</td>
  1151. </tr>
  1152. <tr>
  1153. <td><strong>Blob/Doc Storage</strong></td>
  1154. <td>Azure Blob Storage</td>
  1155. <td>Amazon Simple Storage Service (Amazon S3)</td>
  1156. <td>App Engine Data Store (Google File System)</td>
  1157. </tr>
  1158. <tr>
  1159. <td><strong>Caching</strong></td>
  1160. <td>Azure Cache</td>
  1161. <td>n/a</td>
  1162. <td>memcached</td>
  1163. </tr>
  1164. <tr>
  1165. <td><strong>Queuing</strong></td>
  1166. <td>Azure Queue Services</td>
  1167. <td>Amazon Simple Queue Service (Amazon SQS)</td>
  1168. <td>Task Queues</td>
  1169. </tr>
  1170. <tr>
  1171. <td><strong>Messaging / Notifications</strong></td>
  1172. <td>n/a</td>
  1173. <td>Amazon Simple Notification Service (Amazon SNS)</td>
  1174. <td>App Engine Mail</td>
  1175. </tr>
  1176. <tr>
  1177. <td><strong>Data Processing</strong></td>
  1178. <td>n/a</td>
  1179. <td>Amazon Elastic MapReduce (Hadoop)</td>
  1180. <td>Google MapReduce</td>
  1181. </tr>
  1182. <tr>
  1183. <td><strong>Payment</strong></td>
  1184. <td>n/a</td>
  1185. <td>Amazon Flexible Payments Service (Amazon FPS)</td>
  1186. <td>n/a (Google Checkout not part of GAE)</td>
  1187. </tr>
  1188. <tr>
  1189. <td><strong>CDN</strong></td>
  1190. <td>n/a</td>
  1191. <td>Amazon CloudFront</td>
  1192. <td>n/a</td>
  1193. </tr>
  1194. <tr>
  1195. <td><strong>Public Datasets</strong></td>
  1196. <td>Codename &#8220;Dallas&#8221;</td>
  1197. <td>Amazon Public Data Sets</td>
  1198. <td>n/a</td>
  1199. </tr>
  1200. <tr>
  1201. <td><strong>Back Office</strong></td>
  1202. <td>
  1203. <div id="_mcePaste">Office Live Workspace</div>
  1204. <div>Business Productivity Online Standard Suite (BPOS)</div>
  1205. </td>
  1206. <td>n/a</td>
  1207. <td>Google Apps (Docs, etc)</td>
  1208. </tr>
  1209. </tbody>
  1210. </table>
  1211. <p>Very random aside &#8211; if you don&#8217;t know what memcached does, read the best ever overview of a technology ever written &#8211; <a href="">An Adventure In Learning memcached</a>.</p>
  1212. <p>Once you grock the Cloud Computing model, it becomes clear that this model introduces many questions around security and privacy. I&#8217;m getting rather weary of people saying they don&#8217;t like the idea of putting data on cloud services (and *aaS services like Google Docs and others). They&#8217;re statistically far more secure than internal networks. There are also interesting commercial models and legal questions but, seeing this blog isn&#8217;t Jon On Commerce or Jon On The Law, I&#8217;ll leave those alone for now.</p>
  1213. <h2>Virtual Private Clouds</h2>
  1214. <p>So we know what a Public Cloud is. And it all makes sense, right? But what about Virtual Private Clouds. That was the question, from Ian Truscott, that made me write this post.</p>
  1215. <p><a href=""><img class="aligncenter size-medium wp-image-1660" title="virtualprivatecloud" src="" alt="" width="300" height="94" /></a></p>
  1216. <p>Well, Amazon offer their own <a href="">Virtual Private Cloud service</a>. In essence, this gives you a VPN bewteen your local network and a dedicated resources on the Amazon Web Services. You can then treat your Amazon instances as if they were part of your local network. In addition to the standard AWS fees, you also pay for each hour that your VPN is in place, and for the data transferred. I&#8217;ve stolen their image so I don&#8217;t have to draw my own knock-off which wouldn&#8217;t be anywhere near as pretty:</p>
  1217. <p><a href=""><img class="aligncenter size-medium wp-image-1664" title="AmazonVPC" src="" alt="" width="300" height="205" /></a></p>
  1218. <p>My colleague <a href="">@justincormack</a> got me looking into <a href="">Eucalyptus </a>- a product which allows you to create your own physical Private Cloud &#8211; entirely hosted by you. This works in almost the opposite way to the Amazon VPC Service. You use your own hardware, and install their software over the top. However, they also support the Amazon EC2 APIs, which allows you to administer your cloud as you would an Amazon Cloud and, even better, move resources between your cloud and Amazon&#8217;s. So you see, Ian, Private Clouds and Virtual Private Clouds are real and more than just hosting.</p>
  1219. <p>But enough of my blabbering. To keep abreast of all things cloud, follow these peeps on Twitter. They keep me in the know:</p>
  1220. <ul>
  1221. <li>Christofer Hoff (<a href="">@Beaker</a>)</li>
  1222. <li>James Urquhart (<a href="">@jamesurquhart</a>)</li>
  1223. <li>steve clayton (<a href="">@stevecla</a>)</li>
  1224. <li>Joe Drumgoole (<a href="">@jdrumgoole</a>)</li>
  1225. </ul>
  1226. <p>And as I said earlier, please comment with corrections to my Cloud Capability Table. I&#8217;m positive it is strewn with errors. Help me!</p>
  1227. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1228. <wfw:commentRss></wfw:commentRss>
  1229. <slash:comments>7</slash:comments>
  1230. </item>
  1231. <item>
  1232. <title>Ostriches, Cheapskates, Charlatans, Old Dogs and Hippies</title>
  1233. <link></link>
  1234. <comments></comments>
  1235. <pubDate>Wed, 26 May 2010 21:30:10 +0000</pubDate>
  1236. <dc:creator>Jon Marks</dc:creator>
  1237. <category><![CDATA[Ramblings]]></category>
  1239. <guid isPermaLink="false"></guid>
  1240. <description><![CDATA[Paywalls are in the air. The Times have just launched their new site, and more will follow. No-one is quite sure how many people are going to cough up their cash for the content - we'll just have to wait and see. For today, let's just try to put the people that won't pay into neat little boxes.]]></description>
  1241. <content:encoded><![CDATA[<blockquote class="dylan"><p>They say that patriotism is the last refuge<br />
  1242. To which a scoundrel clings.<br />
  1243. Steal a little and they throw you in jail,<br />
  1244. Steal a lot and they make you king.<br />
  1245. - SWEETHEART LIKE YOU</p></blockquote>
  1246. <p>Paywalls are in the air. <a href="">The Times</a> have just launched their new site, and more will follow. No-one is quite sure how many people are going to cough up their cash for the content &#8211; we&#8217;ll just have to wait and see. For today, let&#8217;s just try to put the people that won&#8217;t pay into neat little boxes. Let me know where you fit in, if there are any big groups I&#8217;ve forgotten, or if you think this is just plain old horseshit. Here goes nothing &#8211; meet the Ostriches, Cheapskates, Charlatans, Old Dogs and Hippies.</p>
  1247. <h2>The Characters</h2>
  1248. <p style="text-align: center;"><a href=""><img class="aligncenter size-large wp-image-1650" title="LittleBoxes" src="" alt="" width="655" height="134" /></a></p>
  1249. <p>The <strong>Ostriches </strong>don&#8217;t particularly care about news. They don&#8217;t buy newspapers and don&#8217;t care much for newspaper sites. They&#8217;ll clearly never pay for editorial content as it isn&#8217;t something they need. &#8216;Nuff said.</p>
  1250. <p><strong>Cheapskates</strong> have a price point of $0.00. Given the choice between a crap sprocket for $0.00 versus a pretty decent sprocket at $0.01, they&#8217;d take the crap one. While they acknowledge that the Times, for example, might have better quality editorial than other sites, there is no way in hell they&#8217;d pay for it. You&#8217;ll hear them often in the current debates &#8211; if site X charges me, I&#8217;ll get my fix from site Y. Cheapskates also only read free print newspapers.</p>
  1251. <p>The <strong>Charlatans </strong>wouldn&#8217;t pay online for anything either, but for different reasons. Hell, if I get my films, TV shows, music, eBooks and prawn for free from BitTorrent or Rapidshare, why in heaven&#8217;s name would I pay for news? There are a lot of charlatans out there. Even yours truly has occasionally downloaded something for backup purposes before I&#8217;ve got around to buying the product. Ironically, the last music I actually paid for were the tunes for my son&#8217;s second birthday, which was a pirate party. And yes, I steal images from Google Images without proper attribution, for which I am deeply ashamed.</p>
  1252. <p><strong>Old Dogs</strong> are more honest than Charlatans and happily pay for content they consider valuable. Paying for a film, music album, eBook or their niche prawn collection is normal practice for these guys. They&#8217;d probably even buy digital editions of magazines, because they&#8217;re using to paying for print subscriptions and magazine websites have never offered a decent free alternative. However, they are horrified by the idea of paying for newspaper content only because, in recent times, they&#8217;ve got used to getting the content for free from the websites. Had the newspapers never had free sites, they might not find themselves in the pickle they&#8217;re currently in as there are a lot of Old Dogs out there who certainly don&#8217;t learn new tricks easily.</p>
  1253. <p>Then we have the <strong>Hippies</strong>. They wouldn&#8217;t pay as it violates their moral code. These tree huggers believe in Open Standards, Open Source, Open Data, Free Love, Free Beer, Free Interwebs and Free Content. Ideologically speaking, I&#8217;m pretty closely aligned with this bunch, and I certainly look like a Hippie. I&#8217;m completely with them on Open Standards and Open Source, both of which can happily co-exist with paid for revenue models. Open Data and Paywalls aren&#8217;t compatible, but the point of the Open Data movement is making freely available <em>factual data</em> which is compiled using the <em>tax-payers money</em>. It isn&#8217;t about devaluing content produced by hard working individuals or companies.</p>
  1254. <h2>Some afterthoughts</h2>
  1255. <p>The great @McBoof has a bit of all of these characters in his DNA. However, I really really hope that the paywalls work and quality journalism gets the funding it needs and deserves to flourish. The main alternative, ad revenue, is stinky. The lion&#8217;s share goes to the search engines, aggregators and shitty content farms. The next alternative is &#8220;changing the way newspapers produce content&#8221;, which means you&#8217;ll be reading crap like this blog instead of professionals that can actually form coherent thoughts and do proper research.</p>
  1256. <p>There is a lot more to chat about. If paid-for journalism fails, what&#8217;ll go next? Music is already struggling, and films are taking a small beating from the Charlatans. Paid-for prawn is on the decline, with dating sites overtaking them in revenue. In 5 or 10 years time, will we all only be watching amateur home movies or free blockbusters with even more product placement that we have already?</p>
  1257. <p>And we also need to chat about the clear shift from &#8220;buying&#8221; to &#8220;renting&#8221; (or <a href="">ownership vs access</a>) . But seeing I&#8217;m always accused of rambling on for too long, I&#8217;ll leave it at that and talk about the rest later. Hell, I&#8217;ve got so much interesting stuff to share with you guys, I might just put up my own paywall.</p>
  1258. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1259. <wfw:commentRss></wfw:commentRss>
  1260. <slash:comments>12</slash:comments>
  1261. </item>
  1262. <item>
  1263. <title>Global CMS Geekery</title>
  1264. <link></link>
  1265. <comments></comments>
  1266. <pubDate>Thu, 20 May 2010 19:37:17 +0000</pubDate>
  1267. <dc:creator>Jon Marks</dc:creator>
  1268. <category><![CDATA[Events]]></category>
  1269. <category><![CDATA[Ramblings]]></category>
  1270. <category><![CDATA[Beer]]></category>
  1271. <category><![CDATA[CMS]]></category>
  1272. <category><![CDATA[cmswatch]]></category>
  1273. <category><![CDATA[gilbane]]></category>
  1274. <category><![CDATA[last thursday]]></category>
  1276. <guid isPermaLink="false"></guid>
  1277. <description><![CDATA[Good news. CMS Geeks are getting tanked up all over the world, and it's spreading. If you live in/travel to one of these areas, join your groups and tell your friends. A few cities with a visible CMS presence haven't joined in yet. I'm talking to you Stockholm and Copenhagen. And Western Europe could use a couple. Australia, New Zealand, South Africa and India need to represent too.]]></description>
  1278. <content:encoded><![CDATA[<blockquote class="dylan"><p>You said you were going&#8217; to Frisco, stay a couple of months.<br />
  1279. I always liked San Francisco, I was there for a party once.<br />
  1280. - MAYBE SOMEDAY</p></blockquote>
  1281. <p>Good news. CMS Geeks are getting tanked up all over the world, and it&#8217;s spreading. We all drink and blabber on the last Thursday on every month, unless a conference or something means we should move the date for an uber-event. Here is a quick summary of where we are.</p>
  1282. <p><a href=""><img class="aligncenter size-full wp-image-1639" title="CMS Geek Beer Map" src="" alt="CMS Geek Beer Map" width="586" height="560" /></a></p>
  1283. <p><strong>London</strong> (<a href="">MeetUp</a>, <a href="">LinkedIn</a>) - The original, a.k.a. <em>#LastThursdayCMS</em>. Thanks to Kenton and the other guys at Squiz for starting it. Been going a few years now, and had many celebrity visits. We will have lots of nice photos once our most recent celebrity visitor, @theresaregli, figures out how to download from her camera.</p>
  1284. <p><strong>New York</strong> (<a href="">LinkedIn</a>) &#8211;  Follow this one on <em>#CMSGeekUpNYC</em>. There have been a few meetings, with another big one coming soon. Irina (@irina_guseva) has taken the baton here.</p>
  1285. <p><strong>San Francisco</strong> (<a href="">MeetUp</a>, <a href=";gid=2997890">LinkedIn</a>) - The first one is TONIGHT (20 May 2010), moved to coincide with Gilbane SF. The Mad Monks (@pmonks) is your guy for this one, and it&#8217;s on <em>#CMSGeekUpSF</em>. Hoping for some photos soon.</p>
  1286. <p><strong>Amsterdam</strong> - The first event is tonight, and they&#8217;re using <em>#CMSGeekUpAMS</em>. The SDL Tridion folks will be there in force and you may see a Hippo or two. With the @erikmhartman event in town, it&#8217;s likely to grow. Don&#8217;t be put off by the stupidly small beers they serve in Amsterdam. Just drink more.</p>
  1287. <p><strong>Boston</strong> - Yet to have a meeting, but the intentions are good. Threatening to organise is @natea. This should get big with many vendors based in the Boston area. Not sure we have a hashtag yet.</p>
  1288. <p><strong>Paris </strong>(<a href="">MeetUp</a>, <a href="">LinkedIn</a>) &#8211; Just created! First event is on Monday 14 June, after which is becomes Last Thursdays. Created by @adeforsan and @elieauvray, and you can follow it on #CMSGeekupParis. Expect free drinks from Nuxeo, Jahia and others.</p>
  1289. <p><strong>Geneva </strong>(<a href="">MeetUp</a>) &#8211; We&#8217;re &#8220;spreading like cholera&#8221;. A new joiner, set up by @scroisier. Looking forward to hearing about their first event.</p>
  1290. <p>So if you live in/travel to one of these areas, join your groups and tell your friends. A few cities with a visible CMS presence haven&#8217;t joined in yet. I&#8217;m talking to you Stockholm and Copenhagen. And Western Europe could use a couple. Australia (Yuval, you listening?), New Zealand, South Africa and India need to represent too.</p>
  1291. <p>Start spreading the word and creating those groups. Finally, feel free to map a better map than my horrorshow.</p>
  1292. <div id="attachment_1632" class="wp-caption aligncenter" style="width: 610px"><a href=""><img class="size-full wp-image-1632" title="Celebrity Guest In London" src="" alt="" width="600" height="450" /></a><p class="wp-caption-text">Celebrity Guest In London</p></div>
  1293. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1294. <wfw:commentRss></wfw:commentRss>
  1295. <slash:comments>17</slash:comments>
  1296. </item>
  1297. <item>
  1298. <title>GoDaddy, GoDaddy, you bastards, I’m through</title>
  1299. <link></link>
  1300. <comments></comments>
  1301. <pubDate>Tue, 18 May 2010 20:56:10 +0000</pubDate>
  1302. <dc:creator>Jon Marks</dc:creator>
  1303. <category><![CDATA[Ramblings]]></category>
  1304. <category><![CDATA[This Blog]]></category>
  1306. <guid isPermaLink="false"></guid>
  1307. <description><![CDATA[I've been on GoDaddy a long time, and got pretty annoyed by the speed and reliability of the service. And now they've been hacked too. I'm angry.]]></description>
  1308. <content:encoded><![CDATA[<blockquote class="dylan"><p>
  1309. Your daddy walks in wearin&#8217;<br />
  1310. A Napoleon Bonaparte mask<br />
  1311. Then you ask why I don&#8217;t live here<br />
  1312. Honey, do you have to ask?<br />
  1313. - ON THE ROAD AGAIN</p></blockquote>
  1314. <p>It was only a matter of time. It seems some hacker group wanted to take down my site. Probably a Chinese military faction, a bunch of Free Content Tree Hugging Hippies, or someone I whipped in some youth chess tournament. Naturally, I was prepared for this shit so ensured my site was running the latest everything, and was more secure than Fort Knox &#8211; safe from ground attacks or air assaults.</p>
  1315. <p>But, it turns out, not safe from burrowing from below. These sneaky hackers realised my site was rock solid, so they took out the whole of GoDaddy instead. My blog was injected with evil PHP script which redirected my legions of adoring fans to malware pages. Apologies to the thousands of other bloggers on GoDaddy who were innocent victims of this malicious, round-about attack on Jon On Tech.</p>
  1316. <p>Fortunately, GoDaddy accepted complete responsibility for the situation, and their tech support really understood the problem and helped people quickly and effectively. NOT. Actually, they continually blamed non-patched software and their tech support people wouldn&#8217;t know they were being penetrated until the poker came out of one of their eye sockets. I hate those guys.</p>
  1317. <p>I&#8217;ve done some temporary fix (which you can find <a href="">here</a>) that goes through all the files on your system and removes the evil PHP. However, it&#8217;s only temporary. Me, and thousands of others, are completely at the mercy of the script-kiddies that currently can do pretty much anything to the GoDaddy servers. I might already be part of a BotNet. It seems to be some Linux Shared Hosts problem that is affecting other hosting companies too. If one account on the host is compromised, all the accounts are toast. So the Jon on Tech ship is floating, but leaky. Not to mention as slow and flaky as always. So why do I still live on GoDaddy? Cause I haven&#8217;t had time to get the fuck off it yet. But I plan to.</p>
  1318. <p>Here is what my home page looked like while fixing the problem. I stole the image from Google. Seems other people have the same sentiments as I do.</p>
  1319. <p><a href=""><img class="aligncenter size-full wp-image-1619" title="GoDaddySuck" src="" alt="" width="500" height="345" /></a></p>
  1320. <p>Thanks to <a href="">@roekens</a> who alerted me to the problem. It&#8217;s probably only him and my mother that read my blog, and Mommy dearest wouldn&#8217;t know Malware from Tupperware. As usual, I started this post with a Bob Dylan lyric. But let me end with the last stanza from a poem by the great (if slightly unbalanced) <a href="">Sylvia Plath</a> which sums up my #GoDaddy feelings nicely right now:</p>
  1321. <blockquote><p>There&#8217;s a stake in your fat black heart<br />
  1322. And the villagers never liked you.<br />
  1323. They are dancing and stamping on you.<br />
  1324. They always knew it was you.<br />
  1325. Daddy, daddy, you bastard, I&#8217;m through<br />
  1326. DADDY &#8211; SYLVIA PLATH</p></blockquote>
  1327. <p>P.S. Please let me know if anything dodgy happens again, like you get redirected to some pr0n or anti-virus rubbish. However, don&#8217;t be alarmed if the site is slow or times out. That&#8217;s just GoDaddy&#8217;s usual service. </p>
  1328. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1329. <wfw:commentRss></wfw:commentRss>
  1330. <slash:comments>8</slash:comments>
  1331. </item>
  1332. <item>
  1333. <title>E is for Enterprise</title>
  1334. <link></link>
  1335. <comments></comments>
  1336. <pubDate>Thu, 06 May 2010 19:44:28 +0000</pubDate>
  1337. <dc:creator>Jon Marks</dc:creator>
  1338. <category><![CDATA[Ramblings]]></category>
  1339. <category><![CDATA[CMS]]></category>
  1340. <category><![CDATA[ECM]]></category>
  1341. <category><![CDATA[ejb]]></category>
  1342. <category><![CDATA[enterprise]]></category>
  1343. <category><![CDATA[naming]]></category>
  1344. <category><![CDATA[wcm]]></category>
  1346. <guid isPermaLink="false"></guid>
  1347. <description><![CDATA[Here we go again. Peter (@pmonks) and Laurence (@piewords) are at it again. The current enormously important discussion topic is whether the 'E' makes any sense in the term ECM. Well, it doesn't.
  1348. ]]></description>
  1349. <content:encoded><![CDATA[<blockquote class="dylan"><p>We heard the Sermon on the Mount and I knew it was too complex,<br />
  1350. It didn&#8217;t amount to anything more than what the broken glass reflects.<br />
  1351. When you bite off more than you can chew you pay the penalty,<br />
  1352. Somebody&#8217;s got to tell the tale,<br />
  1353. I guess it must be up to me.<br />
  1354. - UP TO ME</p></blockquote>
  1355. <p>Here we go again. Peter (<a href="">@pmonks</a>) and Laurence (<a href="">@piewords</a>) are at it again. The current enormously important discussion topic is whether the &#8216;E&#8217; makes any sense in the term ECM.</p>
  1356. <p><a href=""><img class="aligncenter size-full wp-image-1612" title="Pie and Monks" src="" alt="" width="400" height="319" /></a></p>
  1357. <div>I think everyone that matters agrees that Enterprise Content Management defines a problem domain, not a kind of product. I&#8217;ve never heard anyone use the term ECMS, and hope that I never do. But Content Management defines a problem domain too, and I don&#8217;t like the idea that Content Management is a subset of Enterprise Content Management at all. Or should it be the other way round &#8211; ECM is a subset of CM? If either case is true, we need a name for the bit that isn&#8217;t identical. How about some set theory to help.</div>
  1358. <p>The idea that WCM + ECM = CM is bollocks. I do agree that ECM = WCM + RM + DM + some other things. But what does CM equal? I&#8217;m going with Peter here. ECM = CM and the &#8216;E&#8217; needs to go. If there is a good reason to keep the E, do we also need EDM, ERM and E-EveryThingElse?</p>
  1359. <p>In <a href="">Pie&#8217;s blogpost</a>, he lists some important characteristics that form the essense of ECM. However, they all hold true for CM too. They really differentiate between ECM/CM and WCM.</p>
  1360. <p>So let&#8217;s have a quick look at the word &#8220;Enterprise&#8221;. Here are some uses:</p>
  1361. <ul>
  1362. <li>An Enterprise is an organisation. When used in a product name, it normally means stuff that happens behind the firewall. For example, Yammer is an Enterprise Twitter. I&#8217;m not sure anyone thinks that ECM is for internal stuff (including partners and suppliers) and CM is for stuff you share with the world. Or do they?</li>
  1363. <li>Enterprise License &#8211; this usage is similar to the above. It&#8217;s an all you can eat for your organisation, that starts expensive and gets worse.</li>
  1364. <li>Enterprise Architect &#8211; I&#8217;m not sure what this means exactly. It&#8217;s not something I&#8217;ve ever wanted on my business card. Technical Architect or Solutions Architect work just fine.</li>
  1365. <li>Enterprise Java Beans &#8211; Now that was a fuck up, wasn&#8217;t it? It really just means bulky and complex &#8211; the opposite of lean and simple. Ask any of the guys at Vignette who are trying to make core changes to the product. Newer, simpler technologies have bitch-slapped EJB&#8217;s all over the place. It feels to me like the E in ECM and the E in EJB are the same thing. It&#8217;s the E that makes me scared.</li>
  1366. </ul>
  1367. <p>Interesting aside: CMSWatch have recently <a href="">renamed the Enterprise Tier product category</a> in their report to &#8220;Complex Enterprise Platforms&#8221;. The use of the word Complex here is particularly intriguiging. In my simple mind, Complex is always a bad thing in a product, even when the problem domain has complex problems. The product&#8217;s aim in life should be to hide that complexity from everyone. I wonder if the fact that all of the platforms classified by CMS Watch as complex (Autonomy Interwoven, EMC/Documentum, IBM, Open Text/Vignette, Oracle) are J2E based means anything (Interwoven has Perl and other stuff thrown in too). While we&#8217;re on it, 5 of the 6 Upper Tier products are Java too, except for Tridion which is a .NET/Java/COM mashup.</p>
  1368. <p>Here is the truth &#8211; you&#8217;ll only hear the words &#8220;Free&#8221; and &#8220;Enterprise&#8221; in the same sentence from an economist, never a CMS salesman. And Enterprises are by their very nature big and slow. The closest thing to an Agile Enterprise that you&#8217;re likely to see is Captain James T. Kirk taking a sharp left while evading those pesky Klingons. These days, Enterprise is a mindset which implies Complex. And Complex is Bad. Please, Lord, help me keep things simple and take away that E.</p>
  1369. <p><a href=""><img class="aligncenter size-full wp-image-1608" title="Starship Enterprise" src="" alt="" width="450" height="288" /></a></p>
  1370. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1371. <wfw:commentRss></wfw:commentRss>
  1372. <slash:comments>18</slash:comments>
  1373. </item>
  1374. <item>
  1375. <title>Superspliced Open Text Logo Updated</title>
  1376. <link></link>
  1377. <comments></comments>
  1378. <pubDate>Tue, 27 Apr 2010 19:44:31 +0000</pubDate>
  1379. <dc:creator>Jon Marks</dc:creator>
  1380. <category><![CDATA[Ramblings]]></category>
  1381. <category><![CDATA[logo]]></category>
  1382. <category><![CDATA[open text]]></category>
  1383. <category><![CDATA[reddot]]></category>
  1384. <category><![CDATA[vignette]]></category>
  1386. <guid isPermaLink="false"></guid>
  1387. <description><![CDATA[Open Text's recent acquisition of NStein means it is time to update the super-spliced Open Text logo that first made it's appearance in the article When CMS Genes Won’t Splice, inspired by the aquisition of Vignette. So here it is in all of it's glory, with a nice Red N added.]]></description>
  1388. <content:encoded><![CDATA[<blockquote class="dylan"><p>She promised that she&#8217;d be right there with me<br />
  1389. When I paint my masterpiece.<br />
  1390. - WHEN I PAINT MY MASTERPIECE</p></blockquote>
  1391. <p>Open Text&#8217;s recent <a href="">acquisition of NStein</a> means it is time to update the super-spliced Open Text logo that first made it&#8217;s appearance in the article <a href="">When CMS Genes Won’t Splice</a>, inspired by the aquisition of Vignette. So here it is in all of it&#8217;s glory, with a nice Red N added:</p>
  1392. <p><a href=""><img class="aligncenter size-full wp-image-1597" title="Open Text logo including Nstein" src="" alt="" width="447" height="133" /></a></p>
  1393. <p>Feel free to use it all over the interwebs. That means you <a href="">Miss Guseva</a> &#8211; you promised.</p>
  1394. <p>Now I need OTEX to buy some companies with an &#8216;e&#8217; in the logo. Are escenic, EPiServer or Ektron for sale, anyone? The companies gobbled into the logo are, for those that care:</p>
  1395. <ul>
  1396. <li>RedDot</li>
  1397. <li>Obtree C4</li>
  1398. <li>NStein</li>
  1399. <li>Gauss</li>
  1400. <li>Vignette</li>
  1401. <li>Hummingbird</li>
  1402. </ul>
  1403. <p>And, dear Open Text, please don&#8217;t sue me if this is illegal or brand tampering or anything else.</p>
  1404. <p><em>Colophon: MS Paint, and nothing but MS Paint.</em></p>
  1405. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1406. <wfw:commentRss></wfw:commentRss>
  1407. <slash:comments>8</slash:comments>
  1408. </item>
  1409. <item>
  1410. <title>CMS Vendor Navel Gazing</title>
  1411. <link></link>
  1412. <comments></comments>
  1413. <pubDate>Mon, 19 Apr 2010 21:12:16 +0000</pubDate>
  1414. <dc:creator>Jon Marks</dc:creator>
  1415. <category><![CDATA[Ramblings]]></category>
  1416. <category><![CDATA[CMS]]></category>
  1417. <category><![CDATA[wcm]]></category>
  1418. <category><![CDATA[wordpress]]></category>
  1420. <guid isPermaLink="false"></guid>
  1421. <description><![CDATA[Is it possible to take five crucial CMS features and rate them in order of importance. It should be. But will anyone play?]]></description>
  1422. <content:encoded><![CDATA[<blockquote class="dylan"><p>You can either go to the church of your choice<br />
  1423. Or you can go to Brooklyn State Hospital<br />
  1424. You&#8217;ll find God in the church of your choice<br />
  1425. You&#8217;ll find Woody Guthrie in the Brooklyn State Hospital<br />
  1426. And though it&#8217;s only my opinion<br />
  1427. I may be right or wrong<br />
  1428. You&#8217;ll find them both<br />
  1429. In the Grand Canyon<br />
  1430. At sundown<br />
  1431. - LAST THOUGHTS ON WOODY GUTHRIE</p></blockquote>
  1432. <p>Forgive me, WordPress, for I have sinned. It&#8217;s been 8 weeks since my last blog post. And in that time <a href="">many</a> <a href="">people</a> <a href="">have</a> <a href="">slandered</a> <a href="">WordPress</a>, accusing it of not being a Web Content Management (WCM) platform at all. But that&#8217;s not important right now.</p>
  1433. <p>What is important is the main reason for my 8 week lapse &#8211; the arrival of my very own WCM &#8211; Willow Coco Marks, born 19 Feb and smiling ever since. So I&#8217;m now the proud owner of two darling little sproglets. And no-one would ever dare to ask me which of my children I love more. That would be horrible. It would be like asking a CMS vendor to take five super important features decide which they love the most. No-one who has seen <a href=",9171,924815-8,00.html">Streep</a> bawling her eyes out in <a href="'s_Choice_(film)">Sophie&#8217;s Choice</a> would go there.</p>
  1434. <p><a href=""><img class="aligncenter size-full wp-image-1588" title="Woody Guthrie" src="" alt="" width="400" height="316" /></a></p>
  1435. <p>So, here is the deal. I challenge any CMS vendor to rate these in order of priority:</p>
  1436. <ul>
  1437. <li><strong>E</strong>ditors &#8211; A user interface that is a editor or publisher&#8217;s wet dream</li>
  1438. <li><strong>P</strong>erformance - The fastest, most stable and scalable CMS in the world</li>
  1439. <li><strong>F</strong>eatures &#8211; The richest set of features any CMS could dream of offering</li>
  1440. <li><strong>D</strong>evelopers &#8211; An open, standard, extensible product that makes developers salivate</li>
  1441. <li><strong>W</strong>ebsite &#8211; A product that can give you a kick-ass website, really really quickly</li>
  1442. </ul>
  1443. <p>Yes, yes, yes, we know they are all important. But not equally important to you. For example, would you choose a proprietary format if it made the editor interface better? Would you add the feature the developers all want if it affected performance?</p>
  1444. <p>So, dear vendors, have a long hard introspective and submit your answers in the comments in the form E P F D W (assuming you like the random order I listed them in) with the first being most important and the last less important than the other four. And no, there isn&#8217;t a right answer.</p>
  1445. <p>Who wants to play?</p>
  1446. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1447. <wfw:commentRss></wfw:commentRss>
  1448. <slash:comments>24</slash:comments>
  1449. </item>
  1450. <item>
  1451. <title>McBoof’s New Job</title>
  1452. <link></link>
  1453. <comments></comments>
  1454. <pubDate>Mon, 15 Feb 2010 21:21:39 +0000</pubDate>
  1455. <dc:creator>Jon Marks</dc:creator>
  1456. <category><![CDATA[Ramblings]]></category>
  1457. <category><![CDATA[This Blog]]></category>
  1458. <category><![CDATA[job]]></category>
  1459. <category><![CDATA[murdoch]]></category>
  1460. <category><![CDATA[news corp]]></category>
  1462. <guid isPermaLink="false"></guid>
  1463. <description><![CDATA[Okay, this is getting stupid now. In order to end the horseshit on #mcboofsnewjob (thanks @pmonks) and the worst poll ever (thanks @jameshoskins), here is the official statement.]]></description>
  1464. <content:encoded><![CDATA[<blockquote class="dylan"><p>So all you newsy people, spread the news around,<br />
  1465. You c&#8217;n listen to m&#8217; story, listen to m&#8217; song.<br />
  1466. You c&#8217;n step on my name, you c&#8217;n try &#8216;n&#8217; get me beat,<br />
  1467. When I leave New York, I&#8217;ll be standin&#8217; on my feet.<br />
  1468. - HARD TIMES IN NEW YORK TOWN</p></blockquote>
  1469. <p>Okay, this is getting stupid now. In order to end the horseshit on <a href="">#mcboofsnewjob</a> (thanks @pmonks) and the <a href="">worst poll ever</a> (thanks @jameshoskins), here is the official statement.</p>
  1470. <p><em><strong>I&#8217;m the Lead Architect on a high profile <a href="">News Corp</a> project. It covers many areas that I&#8217;m deeply interested in, and many of my technology sweet spots.</strong></em></p>
  1471. <p>Now leave me in peace. Speculate away, but I&#8217;m not going to be talking about this one much I&#8217;m afraid. Move along, folks. Nothing to see here.</p>
  1472. <p>P.S. If you&#8217;re a genius looking for a job, hunt me down on LinkedIn. Especially if I know you already.</p>
  1473. <p><a href=""><img class="aligncenter size-full wp-image-1569" title="news_corp" src="" alt="" width="532" height="436" /></a></p>
  1474. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1475. <wfw:commentRss></wfw:commentRss>
  1476. <slash:comments>14</slash:comments>
  1477. </item>
  1478. <item>
  1479. <title>Goodbye LBi, Hello Mayhem</title>
  1480. <link></link>
  1481. <comments></comments>
  1482. <pubDate>Thu, 11 Feb 2010 14:20:02 +0000</pubDate>
  1483. <dc:creator>Jon Marks</dc:creator>
  1484. <category><![CDATA[Agency]]></category>
  1485. <category><![CDATA[Ramblings]]></category>
  1486. <category><![CDATA[Beer]]></category>
  1487. <category><![CDATA[change]]></category>
  1488. <category><![CDATA[LBi]]></category>
  1490. <guid isPermaLink="false"></guid>
  1491. <description><![CDATA[A change is as good as a holiday, they say. Well, after ten brilliant years at the company now known as LBi, it's time for a change. I wasn't looking for anything, but an opportunity  came along that, had I turned it down, I'd probably regret forever.]]></description>
  1492. <content:encoded><![CDATA[<blockquote class="dylan"><p>Yes, to dance beneath the diamond sky with one hand waving free,<br />
  1493. Silhouetted by the sea, circled by the circus sands,<br />
  1494. With all memory and fate driven deep beneath the waves,<br />
  1495. Let me forget about today until tomorrow.<br />
  1496. - MR. TAMBOURINE MAN</p></blockquote>
  1497. <p>A change is as good as a holiday, they say. Well, after ten brilliant years at the company now known as LBi, it&#8217;s time for a change. I wasn&#8217;t looking for anything, but <a href="">an opportunity came along</a> that, had I turned it down, I&#8217;d probably regret for the rest of my life. More on this <a href="">here</a>; I plan to keep this blog going strong &#8211; time and lawyers permitting.</p>
  1498. <p>To all my LBi colleagues, thanks for the wonderful times, the beers and the things you&#8217;ve taught me. You&#8217;ve got an awesome gig going, and the road ahead looks rosy. In particular, thanks to the exec for their vision and guidance, the technical architects for all their wisdom, and my development teams for fucking up <em>far </em>less projects than the industry average.</p>
  1499. <p>To the Dream Team (@mislip, @laurajaybee, @dacrumb, @skinnybouffant and @shakster), congrats on a job well done and I&#8217;ll be watching a certain site with eager anticipation. And a huge huge thanks to my boss, Mark, for keeping me honest for the last few years.</p>
  1500. <p>To end my Paltrow-esque blubbering &#8211; to all my wonderful, well-informed clients that read this blog, thanks for letting me go near your projects, and for making most of the work a pleasure.</p>
  1501. <p>We&#8217;ll always have<a href=""> The Pride</a>. It&#8217;s been real.</p>
  1502. <p><strong>P.S.</strong> If anyone wants my old job (the best job at the best agency in London), mail [email protected] for the attention of Mark Agar and the subject &#8220;I want Jon&#8217;s old job&#8221;. I&#8217;m serious.</p>
  1503. <p><a href=""><img class="aligncenter size-medium wp-image-1536" title="ScrewYouGuys" src="" alt="" width="261" height="300" /></a></p>
  1504. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1505. <wfw:commentRss></wfw:commentRss>
  1506. <slash:comments>38</slash:comments>
  1507. </item>
  1508. <item>
  1509. <title>#cmshaiku 2010 Results</title>
  1510. <link></link>
  1511. <comments></comments>
  1512. <pubDate>Wed, 10 Feb 2010 12:12:35 +0000</pubDate>
  1513. <dc:creator>Jon Marks</dc:creator>
  1514. <category><![CDATA[Events]]></category>
  1515. <category><![CDATA[Ramblings]]></category>
  1516. <category><![CDATA[Beer]]></category>
  1517. <category><![CDATA[botnet]]></category>
  1518. <category><![CDATA[CMS]]></category>
  1519. <category><![CDATA[erlang]]></category>
  1520. <category><![CDATA[gilbane]]></category>
  1521. <category><![CDATA[Haiku]]></category>
  1522. <category><![CDATA[poetry]]></category>
  1523. <category><![CDATA[vote]]></category>
  1525. <guid isPermaLink="false"></guid>
  1526. <description><![CDATA[Time up. The votes have been tallied, checked and verified by our independent auditors. Let's announce all of our winners.]]></description>
  1527. <content:encoded><![CDATA[<blockquote class="dylan"><p>Trails of troubles,<br />
  1528. Roads of battles,<br />
  1529. Paths of victory,<br />
  1530. I shall walk.<br />
  1531. - PATHS OF VICTORY</p></blockquote>
  1532. <p>The votes have been tallied, checked and verified by our independent auditors. With over 250 tweets to the <a href="">#cmshaiku hashtag</a> and 114 votes in the Grand Winner category, it&#8217;s been more popular than expected. Time to announce the<a href=""> #cmshaiku 2010</a> winnners. The worthy Grand Winner from Cheryl McKinnon (who knows a thing or two about legacy vendors and legal):</p>
  1533. <blockquote><p>Legacy vendors<br />
  1534. want to play haiku too but<br />
  1535. poems stuck in legal</p></blockquote>
  1536. <p><a href=""><img class="aligncenter size-full wp-image-1545" title="cmshaikuwinners" src="" alt="" width="400" height="417" /></a></p>
  1537. <p>I&#8217;ve always suspected that Peter Monks is actually a Bot written in Erlang, but he proved me wrong. He&#8217;s actually a BotNet with a powerful Poetry Plugin. Sadly, his Distributed Denial of Justice attack meant that poor Kathy Brown&#8217;s masterpiece was pushed into third. Philippe came a close fourth, although yours truly thinks his was probably the most inspired entry.</p>
  1538. <p>Cheryl (Self Promotion) and Peter&#8217;s (Random) legions of voters meant they also won their categories. Embarassingly I won the Product category by a country mile. Laurence Hart won the General section, and Paul Carvill won the Despair section. I fear I did Philippe (@proops) a disservice by including both his genius open source haiku and my fork in the same category, thus splitting the vote.</p>
  1539. <p>So, I owe <a href="">Cheryl</a>, <a href="">Peter</a>, <a href="">Kathy</a>, <a href="">Laurence </a>and <a href="">Paul </a>beers. You&#8217;ll receive your prizes next time we happen to be in a bar together. All liability for events occuring after drinking said beer falls squarely on the drinker. Kathy can tell you what happened last time I bought her a beer &#8230;</p>
  1540. <p>If you need a bit more poetry in your life, you can follow all the entrants using <a href="">this Twitter list</a>.  Also, a special shout to Tim Walters for laughing in the face of the <a href="">Forrester personal brand building embargo</a>.</p>
  1541. <p>Lastly, make sure you get your copy of the book from our friends at <a href=""><span style="text-decoration: line-through;">Gilbane</span> </a><a href="">Outsell</a>.</p>
  1542. <p>And please, I beg, tweet /  haiku should inspiration / find you! For the book.</p>
  1543. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1544. <wfw:commentRss></wfw:commentRss>
  1545. <slash:comments>6</slash:comments>
  1546. </item>
  1547. <item>
  1548. <title>#cmshaiku 2010 Beer Contest</title>
  1549. <link></link>
  1550. <comments></comments>
  1551. <pubDate>Fri, 05 Feb 2010 17:25:52 +0000</pubDate>
  1552. <dc:creator>Jon Marks</dc:creator>
  1553. <category><![CDATA[Events]]></category>
  1554. <category><![CDATA[Ramblings]]></category>
  1555. <category><![CDATA[Beer]]></category>
  1556. <category><![CDATA[CMS]]></category>
  1557. <category><![CDATA[Haiku]]></category>
  1558. <category><![CDATA[poetry]]></category>
  1559. <category><![CDATA[vote]]></category>
  1561. <guid isPermaLink="false"></guid>
  1562. <description><![CDATA[It's the biggest competition to hit the web in a long time - The 2010 CMS Haiku Beer Contest. We created the fourth worst poetry in history, caused the CEO of Sun to resign, and inspired a prize for the Gilbane Conference in San Francisco.]]></description>
  1563. <content:encoded><![CDATA[<blockquote class="dylan"><p>Took an untrodden path once, where the swift don&#8217;t win the race,<br />
  1564. It goes to the worthy, who can divide the word of truth.<br />
  1565. - I AND I</p></blockquote>
  1566. <p>It&#8217;s the biggest competition to hit the web in a long time &#8211; The 2010 CMS Haiku Beer Contest. We created the fourth worst poetry in history, caused the CEO of Sun to resign, and inspired a prize for the <a href="">Gilbane Conference in San Francisco</a>. <strong>If I have forgotten you, please leave your entry in the comments</strong>. You can still make the book.</p>
  1567. <p><a href=""><img class="aligncenter size-full wp-image-1502" title="HaikuHighlights" src="" alt="" width="578" height="119" /></a></p>
  1568. <p>But enough of that, it&#8217;s time to pick the winners. Due to the overwhelming response, I&#8217;ve divided the best into six categories of five. Please vote in each category. Voting closes on Feb 10. I&#8217;m buying beers for all the winners.</p>
  1569. <script type='text/javascript' language='javascript' charset='utf-8' src=''></script><noscript> <a href=''>View Poll</a></noscript>
  1570. <script type='text/javascript' language='javascript' charset='utf-8' src=''></script><noscript> <a href=''>View Poll</a></noscript>
  1571. <script type='text/javascript' language='javascript' charset='utf-8' src=''></script><noscript> <a href=''>View Poll</a></noscript>
  1572. <script type='text/javascript' language='javascript' charset='utf-8' src=''></script><noscript> <a href=''>View Poll</a></noscript>
  1573. <script type='text/javascript' language='javascript' charset='utf-8' src=''></script><noscript> <a href=''>View Poll</a></noscript>
  1574. <script type='text/javascript' language='javascript' charset='utf-8' src=''></script><noscript> <a href=''>View Poll</a></noscript>
  1575. <p>There were many other fine entries. Sadly, a few good ones didn&#8217;t meet the strict traditional <a href="">5/7/5 syllable rule</a>. We decided that an @ or a # <em>could </em>count as a syllable, but didn&#8217;t have to.</p>
  1576. <p>Happy voting, and watch this space for the winners.</p>
  1577. <pre><a href=""><img class="aligncenter size-medium wp-image-1501" title="Gilbane San Fransisco Haiku Prize" src="" alt="" width="240" height="359" /></a></pre>
  1578. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1579. <wfw:commentRss></wfw:commentRss>
  1580. <slash:comments>9</slash:comments>
  1581. </item>
  1582. <item>
  1583. <title>Why the iPad Makes Murdoch Right</title>
  1584. <link></link>
  1585. <comments></comments>
  1586. <pubDate>Wed, 27 Jan 2010 21:20:11 +0000</pubDate>
  1587. <dc:creator>Jon Marks</dc:creator>
  1588. <category><![CDATA[Ramblings]]></category>
  1589. <category><![CDATA[Apple Inc.]]></category>
  1590. <category><![CDATA[flash]]></category>
  1591. <category><![CDATA[iPad]]></category>
  1592. <category><![CDATA[IPhone]]></category>
  1593. <category><![CDATA[murdoch]]></category>
  1594. <category><![CDATA[newscorp]]></category>
  1595. <category><![CDATA[paywall]]></category>
  1596. <category><![CDATA[publishing]]></category>
  1598. <guid isPermaLink="false"></guid>
  1599. <description><![CDATA[My thoughts on the iPad, why it will be good for the publishing industry, and why people will pay for content on it.]]></description>
  1600. <content:encoded><![CDATA[<blockquote class="dylan"><p>Where were you when it started<br />
  1601. Do you want it for free<br />
  1602. What was it you wanted<br />
  1603. Are you talking to me?<br />
  1604. - WHAT WAS IT YOU WANTED?</p></blockquote>
  1605. <p>Right. It&#8217;s the iPad and, <a href="">obvious jokes</a> aside, I think the device is going to revolutionise more than just reading on the toilet.</p>
  1606. <p>Here&#8217;s the thing &#8211; the iPad is just too damn beautiful for shit content. I think this is the best thing that has happened to publishing for a long long time. People will pay for content on this baby, and on other devices that follow. Be assured, they will follow, just like they followed the iPhone. I wouldn&#8217;t disrespect my iPad (that someone is sure to send me as a gift) by reading machine-generated advertorial crap on it. I want to read good content written by people that are paid to write. And I&#8217;d be happy to pay a small fee for this &#8211; for books, newspapers, magazines, video and the hybrids of these that are going to emerge.</p>
  1607. <p><a href=""><img class="aligncenter size-full wp-image-1487" title="iPad" src="" alt="" width="436" height="528" /></a></p>
  1608. <p>We recently saw a lot of people <a href="">paying for the Guardian iPhone App</a>, although I don&#8217;t understand how a one-off payment for content is sustainable. We need a way to do in-app recurring payments, which should be relatively easy. <a href="">Murdoch&#8217;s threat </a>to remove News Corp content from Google and start charging for it makes more and more sense. And all you people that scream about content being free &#8211; consider the BBC web site for a second. They produce wonderful content, which is paid for by every citizen in the UK as part of our taxes, and I don&#8217;t think many people begrudge them this.</p>
  1609. <p>There will also be people that scream &#8220;Damn You, @McBoof. How could you write about the joys Open Data and Open Standards then embrace a Paywall. Judas!&#8221;. To those I say, &#8220;Trust Me, Open does not always mean Free&#8221;. More on this another time.</p>
  1610. <p>A last thought on the iPad. The fact that it doesn&#8217;t have a camera doesn&#8217;t bother me at all. The lack of Flash is a small issue, but I don&#8217;t like Flash much. No USB port sadly &#8211; the device is still too closed for me. And it <em>needs </em>to multitask, and I got the impression from what I&#8217;ve seen so far that it doesn&#8217;t. That sucks a bit. Still, I want one.</p>
  1611. <p>Let&#8217;s close on a video from 2006 (thanks to <a href="">@halvorson</a>):</p>
  1612. <p style="text-align: center;"><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="344" codebase=",0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value=";hl=en_GB&amp;fs=1&amp;" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="425" height="344" src=";hl=en_GB&amp;fs=1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
  1613. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1614. <wfw:commentRss></wfw:commentRss>
  1615. <slash:comments>28</slash:comments>
  1616. </item>
  1617. <item>
  1618. <title>An Incomplete Directory of Open Standards</title>
  1619. <link></link>
  1620. <comments></comments>
  1621. <pubDate>Sun, 10 Jan 2010 15:04:58 +0000</pubDate>
  1622. <dc:creator>Jon Marks</dc:creator>
  1623. <category><![CDATA[Future of CMS]]></category>
  1624. <category><![CDATA[Ramblings]]></category>
  1625. <category><![CDATA[Application Layer]]></category>
  1626. <category><![CDATA[cmis]]></category>
  1627. <category><![CDATA[CMS]]></category>
  1628. <category><![CDATA[Hypertext Transfer Protocol]]></category>
  1629. <category><![CDATA[Internet protocols]]></category>
  1630. <category><![CDATA[JCP]]></category>
  1631. <category><![CDATA[OASIS]]></category>
  1632. <category><![CDATA[Open standard]]></category>
  1633. <category><![CDATA[portal]]></category>
  1634. <category><![CDATA[Standard]]></category>
  1635. <category><![CDATA[Technology/Internet]]></category>
  1636. <category><![CDATA[W3C]]></category>
  1637. <category><![CDATA[WebDAV]]></category>
  1638. <category><![CDATA[World Wide Web Consortium]]></category>
  1640. <guid isPermaLink="false"></guid>
  1641. <description><![CDATA[During the panel discussion at the recent British Computer Society Open Source event, there was discussion (and confusion) about Open Source versus Open Standards. I was asked "So, can you give us some examples of Open Standards". I rattled off a few, but I thought I'd add a few more here. ]]></description>
  1642. <content:encoded><![CDATA[<blockquote class="dylan"><p>Through this open world I&#8217;m about to ramble,<br />
  1643. Through ice and snows, sleet and rain,<br />
  1644. I&#8217;m about to ride that mornin&#8217; railroad,<br />
  1645. P&#8217;raps I&#8217;ll die on that train.<br />
  1646. - MAN OF CONSTANT SORROW</p></blockquote>
  1647. <p>During the panel discussion at the recent <a href="">British Computer Society Open Source event</a>, there was discussion (and confusion) about Open Source versus Open Standards. I was asked &#8220;So, can you give us some examples of Open Standards&#8221;. I rattled off a few, but I thought I&#8217;d add a few more here. There is a lot more to be said on the topic, but a good place to start is to list the standards that I think are important.</p>
  1648. <p>If I get the time, I plan to turn this into a nice diagram that is much more easily digestible. If there are important standards that I&#8217;ve forgotten about that anyone interested in web sites should know about, please let me know in the comments. I&#8217;d avoided worrying about file formats (e.g. PNG, MPEG, PDF). And REST isn&#8217;t a standard &#8211; it is an architectural style that was developed in parallel with the HTTP/1.1 protocol. I&#8217;m sure there are many many important ones I&#8217;ve left out though.</p>
  1649. <p>This is a long and boring post with a record-breaking number of acronyms. So maybe you should stop reading now.</p>
  1650. <h2>The Internet Plumbing</h2>
  1651. <p>These standards are the plumbing of the Internet. Like the sewers under a big city, they are impossible to change and will be there forever. They&#8217;re infrastructure. Some people are saying Twitter has already become infrastructure, but I&#8217;m not convinced about that yet. These standards are split into layers &#8211; the link layer is about physical connection to a network and include standards such as Ethernet. The Internet layer routes packets of information across one or more network using the <a title="Internet protocol" href="">Internet protocol (IP)</a>. The Transport Layer is responsible for the reliable delivery of messages, and uses standards such as TCP or UDP. Finally, the Application Layer provides higher level application specific protocols such as DNS, HTTP (and <a title="WebDav" href="">WebDAV</a>) for web servers, FTP, SMTP for mail servers, NTP for time servers, <a title="LDAP" href="">LDAP</a> for user directories and so on. But I&#8217;m not here to talk about any of these. I want to talk about the standards that sit on top of these, specifically for web pages.</p>
  1652. <h2>Making Web Pages</h2>
  1653. <div id="attachment_1449" class="wp-caption aligncenter" style="width: 391px"><a href=""><img class="size-medium wp-image-1449" title="First 10 Years of the W3C" src="" alt="" width="381" height="151" /></a><p class="wp-caption-text">First 10 Years of the W3C - Click for large version</p></div>
  1654. <p>Let&#8217;s start with the standards we know and love that make up web pages. Of course we have <a href="">HTML 4</a>, <a href="">XHTML</a> and the eagerly awaited <a title="status is WD" href="">HTML 5</a>. We make our HTML pretty using <a href="">Cascading Style Sheets (CSS)</a> and we interact with the page using the <a href="">Document Object Model (DOM)</a>, which has a large number of associated standards. Note AJAX is not a standard, despite what you might hear. The <a title="status is LCWD" href="">XMLHttpRequest</a> DOM API (which can be used to implement AJAX) is currently a last call working draft and may be a W3C standard soon. Another client side standard, <a href="">Scalable Vector Graphics (SVG)</a> never really took off and probably never will.</p>
  1655. <p>So we have standards to make interactive web pages that may or may not be semantically rich. But the world would be a better place if these pages can be accessed by as many people as possible. So we have accessibility standards as part of the Web Accessibility Initiative (<a title="WAI" href="">WAI</a>). These include <a title="status is REC" href="">Web Content Accessibility Guidelines (WCAG)</a> for your web page and the imminent <a title="status is WD" href="">Accessible Rich Internet Applications (WAI-ARIA)</a>.</p>
  1656. <p>Excellent! Our HTML is neat, we&#8217;ve styled it, and all humans can interact with it. But what about the machines? They don&#8217;t understand our badly structured markup. If we want machines to be able to understand the content, we need to engage with the semantic web standards and <a href="">Resource Description Framework (RDF)</a>. The UK public sector is keen on <a title="status is WD" href="">HTML+RDFa</a> although this is not a W3C standard yet. You can query your RDF data set using <a href="">SPARQL</a> and define your ontology (formal representation of concepts and relations between them) using the <a href="">Web Ontology Language (OWL, not WOL)</a>. While we&#8217;re at it, a related and very succesful standard which touches my world is the <a title="Dublin Core Metadata Standard" href="">Dublin Core Metadata Standard</a>, which is an <a title="ISO standard" href="">ISO standard</a>. I like this <a id="u.9y" title="good introduction to Semantic Web standards" href="">good introduction to Semantic Web standards</a> if you want to read more.</p>
  1657. <h2>The Biggest Standard of the Naughties</h2>
  1658. <p><a href="">Extensible Markup Language (XML)</a> is a hugely successful standard. If you judge the success of a standard by its adoption (which I do), it was the Hit of the Decade. <a href="">XML Schema (XSD)</a> has replaced the ill-thought-out DTD standard for defining XML structures. Other child standards include the node selection language <a href="">XPath</a> and query language <a href="">XQuery</a>. <a href="">XSL Transformations (XSLT)</a> is my favourite templating language. <a href="">XML Inclusions (XInclude)</a> joins XML documents together. They&#8217;ve also given us <a href="">XForms</a> to collect data &#8211; sadly it hasn&#8217;t taken off as I&#8217;d have liked.</p>
  1659. <p>Also XML related, the Web Services Standards have given us a wonderful way to make remote services play together. The Holy Trinity behind Web Services are <a href="">SOAP</a> (previously Simple Object Access Protocol) to define the message formats, <a href="">Web Services Description Language (WSDL)</a> to give service descriptions and <a title="Universal Description, Discovery and Integration (UDDI)" href="">Universal Description, Discovery and Integration (UDDI)</a> to find the services. UDDI is actually an OASIS specification, not W3C, but it fits better here.</p>
  1660. <h2>OASIS standards</h2>
  1661. <div>All of the standards mentioned so far are open, and unless otherwise stated, are looked after by the <a href="">World Wide Web Consortium (W3C)</a> and the <a title="Internet Engineering Task Force (IETF)" href="">Internet Engineering Task Force (IETF)</a>. These guys look after the Web as we know it. However, there are other standards bodies that create open standards that are more application specific, and some bodies that create standards which might not be considered truly open. Below are some of the important ones.</div>
  1662. <p><a title="OASIS" href="">OASIS</a> (Organization for the Advancement of Structured Information Standards), in their own words, &#8220;drives the development, convergence and adoption of open standards for the global information society&#8221;. The OASIS standards that touch my world include, in no particular order:</p>
  1663. <div>
  1664. <ul>
  1665. <li><a href="">Content Management Interoperability Services (CMIS)</a> &#8211; Okay, so this isn&#8217;t actually a standard yet, but it is well on the way. It will allow for interoperability between Content Repositories</li>
  1666. <li><a href="">Web Services for Remote Portlets (WSRP)</a> &#8211; Allows portals to include remote portlets. This is probably going to lose to the newer, simpler portlet/widget ideas.</li>
  1667. <li>
  1668. <div><a href="">Universal Description, Discovery and Integration (UDDI)</a> &#8211; mentioned earlier. The third pillar of Web Services</div>
  1669. </li>
  1670. <li><a href="">Security Assertion Markup Language (SAML)</a> &#8211; Used for exchanging authentication and authorization data between security domains. I think this will also lose to newer protocols.</li>
  1671. <li>
  1672. <div><a href="">Darwin Information Typing Architecture (DITA)</a> &#8211; A presentation neutral component-oriented XML content standard, which competes with another OASIS standard, <a href="">DocBook</a>, which I know very little about.</div>
  1673. </li>
  1674. <li>
  1675. <div><a title="eXtensible Resource Descriptor Sequence (XRDS)" href="">eXtensible Resource Descriptor Sequence (XRDS)</a> &#8211; An XML format for discovery of metadata about a resource. Actually part of another standard, but that&#8217;s just details.</div>
  1676. </li>
  1677. </ul>
  1678. <p><a href=""><img class="aligncenter size-medium wp-image-1471" title="StandardsBodies" src="" alt="" width="300" height="98" /></a></p>
  1679. <div>
  1680. <h2>Authentication and Private Data Portability</h2>
  1681. </div>
  1682. <div>OASIS tends to focus on fairly large, complex standards which are always at risk from smaller standards which are often easier to implement so have less of a barrier to adoption. The standards that I think will beat SAML include <a title="OpenID" href="">OpenID</a> which has taken the web by storm recently and <a title="OAuth" href="">OAuth</a>. OpenID (under the <a title="OpenID Foundation" href="">OpenID Foundation</a>) is a web single sign-on protocol similar to SAML. OAuth (now under the IETF) allows a site to request private user data from another site. Both OpenID and OAuth above rely of XRDS. While we&#8217;re talking about users and social networks, other important not-quite-standards are listed below. A great article to learn more about these is the &#8220;<a href="">Overlap of identity technologies</a>&#8221; worked example from Google.</div>
  1683. <ul>
  1684. <li>
  1685. <div><a title="OpenSocial" href="">OpenSocial</a> (Google) &#8211; for building social applications (widgets) and share data across networks</div>
  1686. </li>
  1687. <li>
  1688. <div><a id="ntxr" title="Friend of a Friend" href="">Friend of a Friend</a> (FOAF) &#8211; defines an open technology for connecting social Web sites and the people in them. It uses RDF and OWL.</div>
  1689. </li>
  1690. <li>
  1691. <div><a id="hmsa" title="Portable Contents" href="">Portable Contents</a> &#8211; for moving your social graph around the internet with you</div>
  1692. </li>
  1693. </ul>
  1694. <h2>Content Repository Access, and Java Community Standards</h2>
  1695. <div>CMIS is a Content Repository access standard. Another very successful repository standard you all know well is SQL, which has been a standard with both the <a title="American National Standards Institute" href="">American National Standards Institute</a> (ANSI) and the <a title="International Organization for Standardization" href="">International Organization for Standardization</a> (ISO) for over 20 years. File system standards haven&#8217;t seen the same joy, with most major operating systems using their own standard.</div>
  1696. <div>Another open content repository standard is the <a id="vv90" title="Java Content Repository" href="../2009/11/26/cmis-jcr-and-osgi-for-idiots/">Java Content Repository</a> (JCR) from the <a id="v-xy" title="Java Community Process" href="../2009/11/26/cmis-jcr-and-osgi-for-idiots/">Java Community Process</a> (JCP) Programme. Now while these standards are Java language focussed, they are still open. JCP standards are defined in Java Specification Requests (JSRs), of which there are other 300. Some important, well adopted JCP standards include:</div>
  1697. <ul>
  1698. <li>
  1699. <div>JSR 170 and 283 for the Java Content Repository</div>
  1700. </li>
  1701. <li>
  1702. <div>JSR 168 and 286 for Java Portlet Specification</div>
  1703. </li>
  1704. <li>JSR 53, 152 and 245 for various versions of <a title="Java Servlet" href="">Java Servlet</a> and <a title="JavaServer Pages" href="">JavaServer Pages</a> (JSP)</li>
  1705. <li>
  1706. <div>
  1707. <div>JSR 314 for <a title="JavaServer Faces" href="">JavaServer Faces</a> (JSF)</div>
  1708. </div>
  1709. </li>
  1710. <li>
  1711. <div>
  1712. <div>JSR 255 for <a title="Java Management Extensions" href="">Java Management Extensions</a> (JMX)</div>
  1713. </div>
  1714. </li>
  1715. </ul>
  1716. <h2>Syndication</h2>
  1717. <div>
  1718. <div>For syndication we have <a id="g5d5" title="RSS" href="">RSS</a>, which is looked after by the <a title="RSS Advisory Board" href="">RSS Advisory Board</a> (the guy that fixes my boiler is on it) and <a id="gafp" title="AtomPub" href="">AtomPub</a>, which is an IETF standard. An extension to these, <a id="vuoy" title="PubSubHubbub" href="">PubSubHubbub</a>, is a Google project which added near-realtime notification to RSS and AtomPub. My boiler guy thinks this <a id="vsym" title="specification has holes" href="">specification has holes</a>. For outlines, we have OPML (Outline Processor Markup Language). For example, here is <a href="">my blogroll as OPML</a>.</div>
  1719. </div>
  1720. <h2>Things that start with Open</h2>
  1721. <p>I thought I&#8217;d end with some things I like that aren&#8217;t actually standards, but use the word Open in their title.</p>
  1722. <ul>
  1723. <li><a id="l_:r" title="OpenSearch" href="">OpenSearch</a> &#8211; A set of formats designed to make sharing search results easier</li>
  1724. <li><a href="">OpenStreetMap</a> &#8211; Creates and provides free geographic data such as street maps to anyone who wants them. This is more about Open Data than Open Standards, but anyway.</li>
  1725. <li><a id="zo9o" title="OpenCalais" href="">OpenCalais</a>- A service that semantically parses your content and identifies people, events, places and more. I used the WordPress plugin <a id="oa.:" title="Tagaroo" href="">Tagaroo</a> on this blog for fun. Only basic use is free, though. Probably doesn&#8217;t really belong here. However, below is a screenshot that shows Tagaroo suggesting tags and images for this blog post. The power of semantic analysis.</li>
  1726. </ul>
  1727. <p><a href=""><img class="aligncenter size-full wp-image-1447" title="Tagaroo WordPress Plugin" src="" alt="" width="709" height="525" /></a><span class="status action"><strong> </strong></span></p>
  1728. </div>
  1729. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1730. <wfw:commentRss></wfw:commentRss>
  1731. <slash:comments>98</slash:comments>
  1732. </item>
  1733. <item>
  1734. <title>BCS Open Source Presentation</title>
  1735. <link></link>
  1736. <comments></comments>
  1737. <pubDate>Thu, 07 Jan 2010 10:31:50 +0000</pubDate>
  1738. <dc:creator>Jon Marks</dc:creator>
  1739. <category><![CDATA[Events]]></category>
  1740. <category><![CDATA[This Blog]]></category>
  1741. <category><![CDATA[bcs]]></category>
  1742. <category><![CDATA[open source]]></category>
  1743. <category><![CDATA[Presentation software]]></category>
  1744. <category><![CDATA[prezi]]></category>
  1746. <guid isPermaLink="false"></guid>
  1747. <description><![CDATA[As I write this, we're kicking of the BCS Event - Public Funds in the UK: Open Source for Document and Content Management? I'll write more about the event afterwards, but I thought I'd share my presentation.
  1749. I did this using Prezi, which I really enjoyed. First time I've used it - apologies if it makes you feel sick. And it probably doesn't make any sense without me talking over it. Probably doesn't make sense then either, but anyway.]]></description>
  1750. <content:encoded><![CDATA[<blockquote class="dylan"><p>I don&#8217;t build up illusion &#8217;til it makes me sick,<br />
  1751. I ain&#8217;t afraid of confusion no matter how thick.<br />
  1752. - MOST OF THE TIME</p></blockquote>
  1753. <p>As I write this, we&#8217;re kicking off the BCS Event &#8211; <a href="">Public Funds in the UK: Open Source for Document and Content Management</a>? I&#8217;ll write more about the event afterwards, but I thought I&#8217;d share my presentation.</p>
  1754. <p>I assumed I&#8217;d be stoned if I used PowerPoint at an Open Source event, so I did this using <a href="">Prezi</a>, which I really enjoyed. First time I&#8217;ve used it &#8211; apologies if it makes you feel sick. And it probably doesn&#8217;t make any sense without me talking over it. Probably doesn&#8217;t make sense then either, but anyway.</p>
  1755. <p style="text-align: center;"><object id="prezi_rmga5cq2iplv" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="550" height="550" codebase=",0,40,0"><param name="name" value="prezi_rmga5cq2iplv" /><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="bgcolor" value="#ffffff" /><param name="flashvars" value="prezi_id=rmga5cq2iplv&amp;lock_to_path=1&amp;color=ffffff&amp;autoplay=no" /><param name="src" value="" /><embed id="prezi_rmga5cq2iplv" type="application/x-shockwave-flash" width="550" height="550" src="" flashvars="prezi_id=rmga5cq2iplv&amp;lock_to_path=1&amp;color=ffffff&amp;autoplay=no" bgcolor="#ffffff" allowscriptaccess="always" allowfullscreen="true" name="prezi_rmga5cq2iplv"></embed></object></p>
  1756. <p>You can see the presentation online here: <a href=""></a></p>
  1757. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1758. <wfw:commentRss></wfw:commentRss>
  1759. <slash:comments>14</slash:comments>
  1760. </item>
  1761. <item>
  1762. <title>Don’t Look Back – Zeitgeist 2009</title>
  1763. <link></link>
  1764. <comments></comments>
  1765. <pubDate>Thu, 31 Dec 2009 19:48:03 +0000</pubDate>
  1766. <dc:creator>Jon Marks</dc:creator>
  1767. <category><![CDATA[This Blog]]></category>
  1768. <category><![CDATA[Analytics]]></category>
  1769. <category><![CDATA[google]]></category>
  1770. <category><![CDATA[wordpress]]></category>
  1771. <category><![CDATA[zeitgeist]]></category>
  1773. <guid isPermaLink="false"></guid>
  1774. <description><![CDATA[Baaaah. I said I wouldn't write this post, and a few people advised me not to. But, dear readers, some of you begged for it. More importantly, I'm doing it for me as a record. So if you don't like these Blog Year In Review posts, stop reading now. Bye bye, and Happy New Year.]]></description>
  1775. <content:encoded><![CDATA[<blockquote class="dylan"><p>She&#8217;s got everything she needs,<br />
  1776. She&#8217;s an artist, she don&#8217;t look back.<br />
  1777. - SHE BELONGS TO ME</p></blockquote>
  1778. <p>Baaaah. I said I wouldn&#8217;t write this post, and a few people advised me not to. &#8220;Don&#8217;t Look Back!&#8221; they cried. But, dear readers, some of you begged for it. More importantly, I&#8217;m doing it for me (<a href="">thanks Finnur</a>) as a record. So if you don&#8217;t like these Blog Year In Review posts, stop reading now. Bye bye, and Happy New Year.</p>
  1779. <h2>The Numbers</h2>
  1780. <p>I finally started this blog in March 2009. The main reasons were a) I was up most of the night anyway due to baby&#8217;s sleeping habits and b) I was forced to take some holiday in March. I was never expecting anyone to read it, so a huge huge thank you to those that did, and helped me get some traffic love juice. I also got lucky with my timing as the infamous CMS Vendor Meme started just when I did. In 10 months, I&#8217;ve done:</p>
  1781. <ul>
  1782. <li>Real Life beers with about 30 or 40 people I&#8217;d never have met if I didn&#8217;t start this blog. You know who you are.</li>
  1783. <li>According to Alexa, a mere 700,000 sites are more popular than mine. I&#8217;ve got a Page Rank of 5, although these don&#8217;t mean anything any more.</li>
  1784. <li>65 blog posts (34 in the long gone super-keen first 3 months). So averaging 1.5 posts per week. Each post has lyrics from a <em>different </em>Bob Dylan song. I&#8217;m aiming for 100 before a theme change.</li>
  1785. <li>571 comments (just over 8 per post). Probably 100 of these are from me!</li>
  1786. <li>5,224 spam comments that Akismet has saved me from</li>
  1787. <li>21,700 visits, or 45,500 page views, according to Google Analytics</li>
  1788. </ul>
  1789. <p>My biggest day ever was about 400 visits. A shitty weekend is about 30. The traffic numbers have actually stayed reasonably constant since I started, although the frequency of new posts has dropped enormously.</p>
  1790. <p><a href=""><img class="aligncenter size-full wp-image-1414" title="Traffic for 2009" src="" alt="" width="695" height="155" /></a></p>
  1791. <h2>Most Underrated</h2>
  1792. <p>These are the 5 posts I liked most that never even made the Top 20. Please read them and tell all your friends. The poor guys never stood a chance.</p>
  1793. <table border="0">
  1794. <tbody>
  1795. <tr>
  1796. <th>BLOG POST</th>
  1797. <th>SUMMARY</th>
  1798. <th>BOB DYLAN SONG INTRO</th>
  1799. </tr>
  1800. <tr>
  1801. <td><a href="">Six Seminal Concerts, or What I&#8217;ve Learned About Blogging</a></td>
  1802. <td>Social Media lessons from rock concerts</td>
  1803. <td>LIKE A ROLLING STONE</td>
  1804. </tr>
  1805. <tr>
  1806. <td><a href="">When CMS Genes Won’t Splice</a></td>
  1807. <td>Options for Open Text CMS Roadmap</td>
  1808. <td>HIGHWAY 61 REVISITED</td>
  1809. </tr>
  1810. <tr>
  1811. <td><a href="">Don’t Make Monoliths</a></td>
  1812. <td>A little story about Asterix and the Monoliths</td>
  1813. <td>NORTH COUNTRY BLUES</td>
  1814. </tr>
  1815. <tr>
  1816. <td><a href="">Which Comes First: the Crew or the CMS?</a></td>
  1817. <td>Thoughts on corruption in vendor selection exercises</td>
  1819. </tr>
  1820. <tr>
  1821. <td><a href="">The CMS Word on the Tweet</a></td>
  1822. <td>Thoughts on how the term CMS means different things to different people</td>
  1824. </tr>
  1825. </tbody>
  1826. </table>
  1827. <h2>Most Read</h2>
  1828. <p>Here is the obligatory Top 10 by traffic. I&#8217;ve used number of <em>unique </em>visits as my metric.</p>
  1829. <table border="0">
  1830. <tbody>
  1831. <tr>
  1832. <th>UNIQUE VISITS</th>
  1833. <th>BLOG POST</th>
  1834. <th>SUMMARY</th>
  1835. <th>BOB DYLAN SONG INTRO</th>
  1836. </tr>
  1837. <tr>
  1838. <td>2,049</td>
  1839. <td><a href="">Follow Forty Twitter CMS Gurus In Three Clicks</a></td>
  1840. <td>Bit of a gimmick, but nice and viral as it turned out.</td>
  1841. <td>WHEN THE SHIP COMES IN</td>
  1842. </tr>
  1843. <tr>
  1844. <td>1,454</td>
  1845. <td><a href="">OMG! Open Text buy Grandpa Vignette</a></td>
  1846. <td>First impressions on the unexpected Open Text acquisition of Vignette. The only blog post I wrote at work (sorry, boss!), so I was one of the first.</td>
  1847. <td>OH, SISTER</td>
  1848. </tr>
  1849. <tr>
  1850. <td>1,170</td>
  1851. <td><a href="">Celebrity CMS Deathmatch &#8211; The Aftermath</a></td>
  1852. <td>CMS Vendor Meme Commentary &#8211; after it all ended.</td>
  1853. <td>IDIOT WIND</td>
  1854. </tr>
  1855. <tr>
  1856. <td>899</td>
  1857. <td><a href="">What has the Ministry of Magic Quadrants got against me?</a></td>
  1858. <td>Rant about Gartner&#8217;s new WCM Magic Quadrant</td>
  1859. <td>BOB DYLAN&#8217;S 115TH DREAM</td>
  1860. </tr>
  1861. <tr>
  1862. <td>819</td>
  1863. <td><a href="">A Collaborative Google Wave Blog Post</a></td>
  1864. <td>The Motley Crew writes a post in one hour with Wave</td>
  1865. <td>TOMBSTONE BLUES</td>
  1866. </tr>
  1867. <tr>
  1868. <td>794</td>
  1869. <td><a href="">CMIS, JCR and OSGi for Idiots</a></td>
  1870. <td>A diagram outlining JCR, CMIS and OSGi</td>
  1871. <td>IT’S ALL OVER NOW, BABY BLUE</td>
  1872. </tr>
  1873. <tr>
  1874. <td>672</td>
  1875. <td><a href="">Will Vignette Give Open Text Food Poisoning?</a></td>
  1876. <td>More thoughts on the world-shaking OTEX-VIGN acquisition</td>
  1877. <td>MIXED UP CONFUSION</td>
  1878. </tr>
  1879. <tr>
  1880. <td>636</td>
  1881. <td><a href="">The Cloud &#8211; A Crock of Shit</a></td>
  1882. <td>My thoughts on the non-existent cloud, the hype, and the standards</td>
  1883. <td>KNOCKIN&#8217; ON HEAVEN&#8217;S DOOR</td>
  1884. </tr>
  1885. <tr>
  1886. <td>628</td>
  1887. <td><a href="">Celebrity CMS Deathmatch &#8211; The Beginning</a></td>
  1888. <td>CMS Vendor Meme Commentary &#8211; Part I</td>
  1890. </tr>
  1891. <tr>
  1892. <td>592</td>
  1893. <td><a href="">Brain Teasers For The Pub</a></td>
  1894. <td>Ten brain teasers to think about over a beer</td>
  1895. <td>SILENT WEEKEND</td>
  1896. </tr>
  1897. </tbody>
  1898. </table>
  1899. <h2>Best Traffic Sources</h2>
  1900. <p>Here is just a summary of where the traffic came from. Again, a massive thanks to those that lowered the tone of their sites by linking to me.</p>
  1901. <ul>
  1902. <li>25% of my traffic was from search engines. Google is the only one that matters sending about 95% of these.</li>
  1903. <li>30% of the traffic was &#8220;direct&#8221;. I never bothered to set up tracking from Tweets but I&#8217;d bet the majority of these came from Twitter clients like Seesmic or Tweetdeck. Which means I get much more traffic from Twitter than Google. The other 45% of the traffic is from referring sites.</li>
  1904. <li>Twitter was my top referrer by miles, with 25% of my direct visits.</li>
  1905. <li>Second, third and fourth were all very close &#8211;, and Eighth went to</li>
  1906. <li>FaceBook, LinkedIn and Delicious made the Top 20.</li>
  1907. <li>The blogs in the Top 20 referrers were <a href=""></a> (6), <a href=""></a> (7),   <a href=""></a> (9), <a href=""></a> (13), <a href=""></a> (14), <a href=""></a> (15), <a href=""></a> (17), <a href=""></a> (19) and <a href=""></a> (20)</li>
  1908. </ul>
  1909. <p>Well, that&#8217;s that. If for some reason you&#8217;re interested in a stat I didn&#8217;t share, ask in the comments. Be excellent to each other, and I&#8217;ll see you on the other side of the noughties for that beer. It&#8217;s been real.</p>
  1910. <p><a href=""><img class="aligncenter size-full wp-image-1425" title="Don't Look Back" src="" alt="" width="340" height="475" /></a></p>
  1911. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1912. <wfw:commentRss></wfw:commentRss>
  1913. <slash:comments>7</slash:comments>
  1914. </item>
  1915. <item>
  1916. <title>Six Seminal Concerts, or What I’ve Learned About Blogging</title>
  1917. <link></link>
  1918. <comments></comments>
  1919. <pubDate>Wed, 23 Dec 2009 10:56:17 +0000</pubDate>
  1920. <dc:creator>Jon Marks</dc:creator>
  1921. <category><![CDATA[Ramblings]]></category>
  1922. <category><![CDATA[This Blog]]></category>
  1923. <category><![CDATA[Beer]]></category>
  1924. <category><![CDATA[blogging]]></category>
  1925. <category><![CDATA[dylan]]></category>
  1926. <category><![CDATA[music]]></category>
  1927. <category><![CDATA[social media]]></category>
  1928. <category><![CDATA[twitter]]></category>
  1930. <guid isPermaLink="false"></guid>
  1931. <description><![CDATA[Being a blogging newbie, I learnt a shitload this year which, it transpires, was well understood by the Social Media gurus I've loved for years. So, ladies and gentlemen, I bring you their wisdom from 1965 - 1970, the years I should have lived in. I'll take my lessons from Lennon, Dylan, Hendrix, Page, Jagger or Morrison over social media whore @GuyKawasaki or ego-blogger @Scobleizer any day of the week.]]></description>
  1932. <content:encoded><![CDATA[<blockquote class="dylan"><p>You never turned around to see the frowns on the jugglers and the clowns<br />
  1933. When they all come down and did tricks for you<br />
  1934. You never understood that it ain&#8217;t no good<br />
  1935. You shouldn&#8217;t let other people get your kicks for you<br />
  1936. - LIKE A ROLLING STONE</p></blockquote>
  1937. <p>End of the decade again. Everyone is writing the Obligatory Reflection and/or Prediction stuff again. So I ain&#8217;t going to write one of those. However, being a blogging newbie, I learnt a shitload this year which, it transpires, was well understood by the Social Media gurus I&#8217;ve loved for years. So, ladies and gentlemen, I bring you their wisdom from 1965 &#8211; 1970, the years I should have lived in. I&#8217;ll take my lessons from <a href="">Lennon</a>, <a href="">Dylan</a>, <a href="">Hendrix</a>, <a href="">Page</a>, <a href="">Jagger </a>or <a href="">Morrison </a>over social media whore <a href="">@GuyKawasaki</a> or ego-blogger <a href="">@Scobleizer</a> any day of the week.</p>
  1938. <h3>Lesson #1: It&#8217;s Noisy Out There, So Make a Bigger Noise</h3>
  1939. <p><strong>The Beatles, New York, NY, August 15 1965</strong></p>
  1940. <p>The <a href="'_1965_U.S._tour#The_Shea_Stadium_show">Beatles concert at Shea Stadium</a> broke records all over the place, with over 55,000 people attending. And Beatlemania was at its peak, so the crowd was going mental. The noise in the stadium was, according to Lennon, &#8220;louder than God&#8221;. No-one in the stadium could really hear any of the music. And, as it turned out, nor could the band. So eventually Lennon just started banging the keyboard with his elbows just to make some sound that people could actually hear.</p>
  1941. <p>It&#8217;s noisy as hell in the blogosphere too. Most blogs don&#8217;t get read. If you want people to notice you, you need to make a noise. Start banging your keyboard with your elbows.</p>
  1942. <p><a href=""><img class="aligncenter size-medium wp-image-1355" title="The Beatles" src="" alt="" width="300" height="198" /></a></p>
  1943. <h3>Lesson #2: Experiment, but Don&#8217;t Pander to the Crowds</h3>
  1944. <p><strong>Bob Dylan, Newport Folk Festival, Newport, RI, July 25 1965</strong></p>
  1945. <p>As some of you might know, I&#8217;ve got a soft spot for Bob. I love his older acoustic gems. So I might have been one of the sheep who were upset when, at the<a href=""> Newport Folk Festival</a>, Dylan plugged in his guitar and backing band, and mixed it up a bit. At a concert in Manchester the following year, we had the famous <a href="">Judas Incident</a>. Details are still sketchy, but let&#8217;s go with the romantic version. Dylan starts playing some electric tunes, and during a gap between songs <a href="">someone </a>shouts &#8220;Judas&#8221;. Dylan replied with the rather cryptic &#8220;<em>I don&#8217;t believe you, you&#8217;re a liar</em>&#8220;, before turning to his band instructing them to <em>&#8220;play it fucking loud</em>!&#8221; And they did, belting out an awesome version of Like A Rolling Stone. The &#8220;rock&#8221; albums which followed (<a href="">Highway 61 Revisited</a> and <a href="">Blonde on Blonde</a>) are two of my favourites, and they both went platinum nice and quickly.</p>
  1946. <p>So, like Bob, I&#8217;ve tried to experiment. Do different things, and see what your readers like. Don&#8217;t just keep doing what you think they like. Branch out a bit for potential new readers. Sometimes you can go a bit far, though. I&#8217;m really struggling to understand a world in which Bob could release such an <a href="">embarrassing Christmas album</a>. Maybe time will prove everyone wrong here too.</p>
  1947. <p><a href=""><img class="aligncenter size-medium wp-image-1357" title="Dylan" src="" alt="" width="300" height="195" /></a><a href=""></a><a href=""></a><a href=""></a></p>
  1948. <h3>Lesson #3: Controversy Breeds Traffic</h3>
  1949. <p><strong>Jimi Hendrix, Monterey, CA, 16 June 1967</strong></p>
  1950. <p>When The Jimi Hendrix Experience were booked at the <a href="">Monterey Pop Festival</a>, they were huge in England, but largely unknown in the US.  Some of the biggest names in pop at the time were performing &#8211; The Animals, Beach Boys, The Mamas &amp; Papas and more. However, it&#8217;s Hendrix that is remembered. He closed his set with an insane version of &#8220;Wild Thing&#8221;, which ended with Jimi dousing his guitar in lighter fluid, setting it on fire and smashing the shit out of it. Surprise, surprise &#8211; people remembered that and the buzz helped propel him to stardom in the USA too.</p>
  1951. <p>In the blogosphere, more controversial posts generate far more interest. It can be really boring reading the same things over and over again where everyone agrees with each other. Have (or make up) strong opinions, play Devil&#8217;s Advocate and encourage debate around your posts. If these debates prove that you were completely wrong, admit you were an idiot, thank the crowds for teaching you something, and buy another guitar.</p>
  1952. <p><img class="aligncenter size-medium wp-image-1358" title="JimiHendrix" src="" alt="" width="300" height="198" /></p>
  1953. <h3>Lesson #4: Talk About What You Know, Your Way</h3>
  1954. <p><strong>Led Zeppelin, Boston, MA, 23 January 1969</strong></p>
  1955. <p>The famous Boston Tea Party concert. The birth of head banging. Zeppelin only had one 70-minute album under their belt at the time , but they played for over 4.5 hours. In the words of bassist <a href="">John Paul Jones</a>:</p>
  1956. <blockquote><p>There were kids actually banging their heads against the stage. I&#8217;ve never seen that at a gig before or since, and when we finally left the stage we&#8217;d played for four and a half hours &#8230; I suppose it was then that we realized just what Led Zeppelin was going to become.</p></blockquote>
  1957. <p>Most of the concert was rambling, brilliant improvisation. They mashed up their existing songs, mixed in some covers and generally went with the flow. The band knew each other, they knew their craft, and just kept making shit up.</p>
  1958. <p>For bloggers, there&#8217;s nothing wrong with rambling and improvising. I&#8217;ve discovered that I can&#8217;t really plan blog posts, and I can&#8217;t write short ones. If Led Zep can get away with it, so can I. And I prefer reading posts that have a little personality thrown in.</p>
  1959. <p><img class="aligncenter size-medium wp-image-1359" title="LedZeppelin" src="" alt="" width="300" height="164" /></p>
  1960. <h3>Lesson #5: Shit Happens, Live With It</h3>
  1961. <p><strong>Rolling Stones, Hyde Park, England, 5 July 1969</strong></p>
  1962. <p>The <a href="">Hyde Park Free Concerts</a> are legendary. As are the Rolling Stones. Two days before their scheduled appearance, band mate Brian Jones was found dead in his swimming pool, another victim of &#8220;death by misadventure&#8221;. Admittedly Jones hadn&#8217;t been playing with the band for a month, but the Hyde Park Concert was scheduled to be his replacement&#8217;s first live gig. So the concert turned into a Brian Jones memorial. Jagger opened the set by reading a section from <a href="">Adonais</a>, a poem by Shelley. Over 250,000 people were there.</p>
  1963. <p>By all accounts, the performance itself was pretty crap. But the lesson here is that bad things happen, and you need to be flexible and deal with them. I&#8217;ve written some blog posts that are ridiculously bad and I&#8217;ve been tempted to delete the bastard things. BJ Fogg said on Twitter <em>&#8220;<a href="">I regret 20% of what I tweet</a></em>&#8220;. I&#8217;m probably about the same. But you can&#8217;t do anything about it. Get over it, learn, and move on.</p>
  1964. <p><img class="aligncenter size-medium wp-image-1360" title="RollingStones" src="" alt="" width="300" height="198" /></p>
  1965. <h3>Lesson #6: A Network is About Quality, not Quantity</h3>
  1966. <p><strong>Jim Morrison, Miami, FL, 1969</strong></p>
  1967. <p>Aaah, the <a href="">Miami Incident</a>. Now this didn&#8217;t actually happen exactly like it did in <a href="">the movie</a>, but I prefer that version. The story goes something like this. Morrison was really struggling with his self-created sex-symbol rocker image. He arrived at the concert much more drunk than usual (and usual was pretty damn drunk). He stumbled to the mic, and started rambling &#8211; a few versus of his poetry, but mostly utter nonsense. The crowd was getting uneasy, and Jim was getting annoyed with his followers that didn&#8217;t understand him. He started calling them idiots, culminating in the often quoted (though not 100% accurate) &#8220;<em>You&#8217;re all a bunch of fuckin&#8217; slaves!</em>&#8221;</p>
  1968. <p>What am I getting at here? Well, Morrison had been collecting &#8220;followers&#8221; for years, and then decided he didn&#8217;t like them. Hordes of people hanging on his every word, but completely useless to him. They no longer understood what he thought he was. It&#8217;s a bit like Twitter really. The important thing is not how many followers you have &#8211; an army of SEO spammers or porn bots or follow-me-follow-you-gurus is no use to man or beast. You want people that care. Jim said it far better a year later in one of his poems &#8211; <em>A Feast Of Friends</em> a.k.a <em>The Severed Garden</em>. Admittedly he&#8217;s talking about death, but it works for Twitter too:</p>
  1969. <blockquote><p>I will not go<br />
  1970. Prefer a Feast of Friends<br />
  1971. To the Giant Family.</p></blockquote>
  1972. <p><a href=""><img class="aligncenter size-medium wp-image-1356" title="Doors" src="" alt="" width="300" height="235" /></a></p>
  1973. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  1974. <wfw:commentRss></wfw:commentRss>
  1975. <slash:comments>11</slash:comments>
  1976. </item>
  1977. <item>
  1978. <title>Visions of Jon: WCM is for Losers</title>
  1979. <link></link>
  1980. <comments></comments>
  1981. <pubDate>Wed, 16 Dec 2009 22:24:19 +0000</pubDate>
  1982. <dc:creator>Jon Marks</dc:creator>
  1983. <category><![CDATA[Ramblings]]></category>
  1984. <category><![CDATA[CMS]]></category>
  1985. <category><![CDATA[ECM]]></category>
  1986. <category><![CDATA[monolith]]></category>
  1987. <category><![CDATA[names]]></category>
  1988. <category><![CDATA[standards]]></category>
  1989. <category><![CDATA[wcm]]></category>
  1991. <guid isPermaLink="false"></guid>
  1992. <description><![CDATA[The mystics at CMS Watch have been throwing the bones again and have released their 2010 Technology Predictions, including "Enterprise Content Management and Document Management will go their separate ways". Pie responded with "Enterprise Content Management and WCM will go their separate ways." But I've got my own thoughts.]]></description>
  1993. <content:encoded><![CDATA[<blockquote class="dylan"><p>Ain&#8217;t it just like the night to play tricks when you&#8217;re tryin&#8217; to be so quiet?<br />
  1994. We sit here stranded, though we&#8217;re all doin&#8217; our best to deny it<br />
  1995. - VISIONS OF JOHANNA</p></blockquote>
  1996. <p>The end of the decade is nigh, and the mystics at CMS Watch have been throwing the bones again. They&#8217;ve released their very interesting <a href="">2010 Technology Predictions</a>. The first of these caught my eye:</p>
  1997. <blockquote><p>CMS Watch: Enterprise Content Management and Document Management will go their separate ways</p></blockquote>
  1998. <p>I don&#8217;t agree with the terminology here. In my world, Document Management is one of the pillars of Enterprise Content Management. Enterprise Content Management is not a technology, it&#8217;s a business problem. Documents are one of the types of content the Enterprise needs to manage. So they can&#8217;t really go their separate ways. The wise <a href="">Pie responded</a> quickly to this prediction with an alternative:</p>
  1999. <blockquote><p>Pie: Enterprise Content Management and WCM will go their separate ways.</p></blockquote>
  2000. <p>Now this I agree with more than the CMS Watch version.  Parts of ECM include Document Management, Records Management, Collaboration, Imaging, Workflow and all that good stuff. It is these pillars that allow a business to <strong>manage </strong>their <strong>content</strong>. The end game of all of these technologies is content sitting in a repository that can be easily found and consumed. The includes all the fun with versions, security, compliance and anything else you&#8217;d want to do with it. But it does not include setting up web based delivery channel that exposes some of this content. WCM should not be considered part of ECM.</p>
  2001. <p>Now Pie also acknowledges that his prediction isn&#8217;t going to happen, although it should. My prediction is even less lightly to happen, but here it is anyway:</p>
  2002. <blockquote><p>Jon: Enterprise Content Management is well defined. The term WCM is horseshit, unnecessary and should take a long walk off a short pier.</p></blockquote>
  2003. <p>I can already see the news headlines: <em>LONDON, 2009 &#8211; SHOCK HORROR! WCM Geek Demands Death of term WCM</em>. But it&#8217;s true. I&#8217;m of the camp that wished the term WCM would cease to exist.</p>
  2004. <p>The W is meant to stand for Web, which makes people think Web Site. But it also includes Mobile, Kiosks, TV and various other HTML based delivery channels. Many vendors are trying to deliver their WCM content to print channels too. I want any product that ends in &#8220;CM&#8221; to focus on content creation and management. As Pie said, this content should be accessed via an API or repository standard. A Content Management System should be an extensible <strong><em>application </em></strong>that works pretty well out of the box. The kind of standard these systems care about include data/process standards (for example <a href="">DITA</a>, <a href="">BPEL</a>, or <a href="">Dublin Core</a>) and repository access standards (for example <a href="">JCR </a>or <a href="">CMIS</a>).</p>
  2005. <p><a href=""><img class="aligncenter size-full wp-image-1340" title="Walk The Plank" src="" alt="Walk The Plank" width="470" height="329" /></a></p>
  2006. <p>The other half of the coin is the delivery <em><strong>framework</strong></em>. These are called Web Publishing Tools (WPT) in <a href="">NPR&#8217;s COPE</a> and <a href="">Presentation Management Systems (PMS)</a> by Peter Monks. Things like <a href="">Struts</a>, <a href="">Spring Web</a>, <a href="">ASP.NET MVC</a>, <a href="">Ruby on Rails</a> and many many more are all delivery frameworks. So are Portals. They let you manage authentication, URLs, site structure, templates, layouts, page composition, personalisation, aggregation and more. They understand standards like JSON, AJAX libraries, Web Services,  SAML, OAuth, OpenID, Open Social, Portlets, Gadgets, WSRP, and so on and so on. They let you call any API to bring in content or functionality from any source.</p>
  2007. <p>Of course you can use these technologies to power sites that aren&#8217;t &#8220;content managed&#8221; at all.  They should treat CMS driven content components, SoCo powered UGC components, DAM powered media components and anything else that can sit on a web site as equals. Interestingly, it isn&#8217;t uncommon to see &#8220;Web Content Management Systems&#8221; used to power sites that that aren&#8217;t really content managed. Take something like Drupal &#8211; it&#8217;s often simply used as a delivery framework without any content modules. I&#8217;ve launched sites running on .NET &#8220;WCM&#8221; systems that have never intended to have any content changed post launch. In these examples, the WCM product is being used purely as a good delivery framework.</p>
  2008. <p>But sadly, my prediction it isn&#8217;t going to happen. I&#8217;m just going to have to keep thinking of a WCMS as a tightly coupled hybrid of a content management system and a delivery framework. On the plus side, I&#8217;ll continue to make money out of poor customers that think a &#8220;WCM migration/replacement&#8221; doesn&#8217;t involve a complete site rewrite as they&#8217;re throwing the delivery baby out with the content bath water. Losers.</p>
  2009. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2010. <wfw:commentRss></wfw:commentRss>
  2011. <slash:comments>51</slash:comments>
  2012. </item>
  2013. <item>
  2014. <title>Spot The Difference – The 2010 CMS Watch Vendor Map</title>
  2015. <link></link>
  2016. <comments></comments>
  2017. <pubDate>Wed, 02 Dec 2009 23:31:34 +0000</pubDate>
  2018. <dc:creator>Jon Marks</dc:creator>
  2019. <category><![CDATA[Ramblings]]></category>
  2020. <category><![CDATA[analysts]]></category>
  2021. <category><![CDATA[CMS]]></category>
  2022. <category><![CDATA[cmswatch]]></category>
  2023. <category><![CDATA[dam]]></category>
  2024. <category><![CDATA[ECM]]></category>
  2025. <category><![CDATA[jboss]]></category>
  2026. <category><![CDATA[opentext]]></category>
  2027. <category><![CDATA[oracle]]></category>
  2028. <category><![CDATA[soco]]></category>
  2029. <category><![CDATA[sun]]></category>
  2030. <category><![CDATA[vendor]]></category>
  2031. <category><![CDATA[vignette]]></category>
  2032. <category><![CDATA[vyre]]></category>
  2034. <guid isPermaLink="false"></guid>
  2035. <description><![CDATA[As everyone knows, I think the CMS Watch Content Techonology Vendor Map is awesome. They've just released the 2010 version. The main differences between this and the 2009 version are highlighted.]]></description>
  2036. <content:encoded><![CDATA[<blockquote class="dylan"><p>Here&#8217;s to Cisco an&#8217; Sonny an&#8217; Leadbelly too,<br />
  2037. An&#8217; to all the good people that traveled with you.<br />
  2038. Here&#8217;s to the hearts and the hands of the men<br />
  2039. That come with the dust and are gone with the wind.<br />
  2040. - SONG TO WOODY </p></blockquote>
  2041. <p> As everyone knows, I think the CMS Watch Content Techonology Vendor Map is awesome. They&#8217;ve just released the 2010 version. As far as I can tell, the main differences between this and <a href="">the 2009 version </a>are shown below:</p>
  2042. <p> <a href=""><img class="aligncenter size-full wp-image-1323" title="2010SpotTheDiff" src="" alt="2010SpotTheDiff" width="746" height="558" /></a></p>
  2043. <p>Get the high res version from the <a href="">CMS Watch site</a>. </p>
  2044. <p> So, what&#8217;s changed? Firstly, the big mergers and acquisitions:</p>
  2045. <ul>
  2046. <li>Adobe decided to buy Omniture for reasons I haven&#8217;t figured out yet. It&#8217;s made the map more topologically tricky.</li>
  2047. <li>OpenText has <a href="">gobbled up Vignette</a>, removing another of the big dots</li>
  2048. <li>Oracle has <a href="">bought SUN</a>, which hasn&#8217;t changed much since Oracle had a few of everything already.</li>
  2049. <li>JBoss and eXo have <a href="">merged Portal platforms</a></li>
  2050. <li>ClearStory is now <a href="">The FeedRoom</a>, who have been recently acquired by <a href="">KIT digital</a>.</li>
  2051. </ul>
  2052. <p>New Kids On The Map:</p>
  2053. <ul>
  2054. <li>Vyre isn&#8217;t new, but it&#8217;s now recognised as a DAM product too. This was <a href="">discussed last time</a>. <a href="">OpenCms </a>has made the WCM big time, along with <a href="">Hannon Hill</a>, <a href="">Telerik </a>and <a href="">Omniupdate</a>.</li>
  2055. <li><a href="">Mark Logic </a>storms onto the XML Component Management line after creating quite a buzz in the last few months. <a href="">Quark </a>is on there too, Revolutionizing Publishing. Again.</li>
  2056. <li><a href="">Cisco&#8217;s new tools </a>get them onto the Social and Collab line. It&#8217;s busy there though &#8211; they&#8217;re joined by Salesforce (the Daddy), <a href="">Yammer </a> (like Twitter for the Enterprise), <a href="">MindTouch </a>(Open Source Enterprise Networking Platform) and <a href="">KickApps</a> (another community builder).</li>
  2057. <li>Three ECM platforms I know nothing about: <a href="">Fabasoft</a>, <a href="">DocuWare </a>and <a href="">Objective</a>.</li>
  2058. </ul>
  2059. <p>And finally:</p>
  2060. <ul>
  2061. <li>FaceBook has gone. Maybe not enterprise enough. Which is probably why Twitter isn&#8217;t on either.</li>
  2062. <li>Poor EPiServer still hasn&#8217;t made it onto the SoCo line, even though they&#8217;ve got a very mature Community product</li>
  2063. <li>SAP still isn&#8217;t considered a CMS, which is fine by me.</li>
  2064. </ul>
  2065. <p>So that&#8217;s that. A 300 page report costs about the same as an overpaid consultant researching badly for a couple of days to prepare that disappointing Google-fleeced document you were embarrassed to show your boss. It&#8217;s a no brainer. <a href="">Buy the reports</a>. All of them. They rock.</p>
  2066. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2067. <wfw:commentRss></wfw:commentRss>
  2068. <slash:comments>6</slash:comments>
  2069. </item>
  2070. <item>
  2071. <title>CMIS, JCR and OSGi for Idiots</title>
  2072. <link></link>
  2073. <comments></comments>
  2074. <pubDate>Thu, 26 Nov 2009 15:42:42 +0000</pubDate>
  2075. <dc:creator>Jon Marks</dc:creator>
  2076. <category><![CDATA[Ramblings]]></category>
  2077. <category><![CDATA[Beer]]></category>
  2078. <category><![CDATA[chemistry]]></category>
  2079. <category><![CDATA[cmis]]></category>
  2080. <category><![CDATA[CMS]]></category>
  2081. <category><![CDATA[felix]]></category>
  2082. <category><![CDATA[jackrabbit]]></category>
  2083. <category><![CDATA[jcr]]></category>
  2084. <category><![CDATA[osgi]]></category>
  2085. <category><![CDATA[sling]]></category>
  2087. <guid isPermaLink="false"></guid>
  2088. <description><![CDATA[I had the chance to drink beer and talk shit with the great David Nüscheler, which inspired me to draw a picture all about JCR, CMIS and OSGi. ]]></description>
  2089. <content:encoded><![CDATA[<blockquote class="dylan"><p>The empty-handed painter from your streets<br />
  2090. Is drawing crazy patterns on your sheets.<br />
  2091. - IT&#8217;S ALL OVER NOW, BABY BLUE</p></blockquote>
  2092. <p>Every now and again, certain tumultuous events coincide that makes us feel insignificant. A bit like a total solar eclipse, which is a rare and humbling thing. This week three seemingly unconnected occurances came to pass which made me stop and think. Firstly, <a href="">CMIS was mentioned in the New York Times</a>. Yes, <em>the </em>New York Times. Secondly, Jeff Potts released his &#8220;<a href="">Getting Started with CMIS</a>&#8221; tutorial. And, finally, I had the chance to drink beer and talk shit with the great <a href="">David Nüscheler</a>.</p>
  2093. <p>So, to honour all of this, I drew a picture.</p>
  2094. <p>Why, you may ask. Well, after chatting to David, I felt inspired to think (and blog) more about the <a href="">JCR</a>, <a href="">CMIS </a>and <a href="">OSGi</a>. But while doing my cursory research (that&#8217;s a strong word for what I do, but anyway), I discovered that there were quite a few things I knew nothing about, and a few products that I&#8217;d never heard of. I also coined the word Dignorance in honour of my newly found knowledge gaps.</p>
  2095. <p><a href=""><img class="aligncenter size-medium wp-image-1304" title="Dignorance" src="" alt="Dignorance" width="300" height="134" /></a></p>
  2096. <p>So here is a small version of the picture. Click for a large one, or <a href="">download it as PDF</a>. Do whatever you want to with it. If you think it is useful, or think it needs fixing, leave comments here or get in touch. I&#8217;m sure it&#8217;s completely wrong all over the place. If you want the original Visio drawing to play with, let me know.</p>
  2097. <p><a href=""><img class="aligncenter size-medium wp-image-1349" title="JCRCMISOverview_v1.4" src="" alt="JCRCMISOverview_v1.4" width="205" height="300" /></a></p>
  2098. <p>Next time I come to your office, I except to see this printed as A3 and stuck on your wall.</p>
  2099. <p><strong>UPDATE 18 Dec 2009</strong>: I&#8217;ve written an article on CMS Wire which explains some of this. Have a look:</p>
  2100. <p><a href=""></a></p>
  2101. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2102. <wfw:commentRss></wfw:commentRss>
  2103. <slash:comments>37</slash:comments>
  2104. </item>
  2105. <item>
  2106. <title>Brave Vendors, Cruel Judges and Me</title>
  2107. <link></link>
  2108. <comments></comments>
  2109. <pubDate>Sat, 14 Nov 2009 23:00:52 +0000</pubDate>
  2110. <dc:creator>Jon Marks</dc:creator>
  2111. <category><![CDATA[Ramblings]]></category>
  2112. <category><![CDATA[23video]]></category>
  2113. <category><![CDATA[CMS]]></category>
  2114. <category><![CDATA[espirit]]></category>
  2115. <category><![CDATA[jboye]]></category>
  2116. <category><![CDATA[kapow]]></category>
  2117. <category><![CDATA[microsoft]]></category>
  2118. <category><![CDATA[sitecore]]></category>
  2119. <category><![CDATA[terminalfour]]></category>
  2120. <category><![CDATA[webidol]]></category>
  2122. <guid isPermaLink="false"></guid>
  2123. <description><![CDATA[I promised I'd scribble something about the Web Idol Competition at JBoye 09. The competition involved 6 vendors each presenting a fast paced 7 minute demo to the crowds, mimicking something like Pop Idol. The judging is done by an "expert" panel of 3 judges who offer inane commentary. The audience vote holds all the power over the final outcome. I was lucky enough to be asked to be one of the three judges on the panel.]]></description>
  2124. <content:encoded><![CDATA[<blockquote class="dylan"><p>These be seven curses on a judge so cruel:<br />
  2125. That one doctor will not save him,<br />
  2126. That two healers will not heal him,<br />
  2127. That three eyes will not see him.<br />
  2128. That four ears will not hear him,<br />
  2129. That five walls will not hide him,<br />
  2130. That six diggers will not bury him<br />
  2131. And that seven deaths shall never kill him.<br />
  2132. - SEVEN CURSES</p></blockquote>
  2133. <p>Better late than never. I promised I&#8217;d scribble something about the <a href="">Web Idol Competition at JBoye 09</a>. The competition involved 6 vendors each presenting a fast paced 7 minute demo to the crowds, mimicking something like Pop Idol. The judging is done by an &#8220;expert&#8221; panel of 3 judges who offer inane commentary. The audience vote holds all the power over the final outcome.</p>
  2134. <p>I was lucky enough to be asked to be one of the three judges on the panel. Teaching me the ropes were <a href="">Erik Hartman</a>, a grandfather of Content Management, and <a href="">Sara Redin</a> of JBoye. The night before, I was out drinking with a Dutch guy called Erik and was enormously impressed by how much he knew about all the CMS products out there. Idiot that I am, I didn&#8217;t put two and two together and only realised that he was <em>the</em> Erik when I sat next to him on the panel. I&#8217;ve been a fan of his for ten years.</p>
  2135. <p>Anyway, the participating vendors (in the order they presented, from our right to left in the picture) were <a href="">Microsoft</a>, <a href="">e-Spirit</a>, <a href="">Kapow</a>, <a href="">TERMINALFOUR</a>, <a href="">23 Video</a> and <a href="">Sitecore</a>. So 4 content management vendors, a content migration vendor and a video startup.</p>
  2136. <p><a href=""><img class="aligncenter size-medium wp-image-1289" title="WedIdol1" src="" alt="WedIdol1" width="300" height="199" /></a></p>
  2137. <p>First up was <strong>Microsoft</strong>, presenting a Web <a href="">Content Management</a> interface in <a href="">SharePoint 2010</a>. I think it is a massive improvement over the monster that is MOSS 2007, but my fellow judges didn&#8217;t think much of it. The much hated Ribbon interface (as featured in the new versions of MS Office) received scorn. The demo didn&#8217;t show anything profound. While it is true that we didn&#8217;t see anything that other systems haven&#8217;t been doing for years, at least it brings SharePoint into the ballpark. I&#8217;ve been violently opposed to the idea of using MOSS for public facing sites, but the new version might warrant a rethink.</p>
  2138. <p>While we&#8217;re on this, those of you that saw <a href="">Steve Ballmer&#8217;s discussion with Tom Rizzo</a> in October 2009 must have had their ear&#8217;s prick when they heard this:</p>
  2139. <blockquote><p>We have a lot of customers using SharePoint in Internet sites, and with the capabilities of 2010, we expect to see that explode. But it wasn&#8217;t the initial design point for SharePoint.</p></blockquote>
  2140. <p>Wait, Steve, did I hear you right? After The Righteous have been fighting (and losing) the SharePoint For Public Facing Sites for many a long year, you suddenly say that Internet Sites were not a design goal of the initial SharePoint. No shit. But why couldn&#8217;t you have saved everyone a whole lot of pain and said this when MOSS was released. And if, in 5 years time, you end up saying the same thing about SharePoint 2010, I think I&#8217;ll kick you in the starboard testicle.</p>
  2141. <p>Next up was<strong> e-Spirit</strong>, showing off the <a href="">FirstSpirit </a>CMS. e-Spirit aren&#8217;t a vendor I know much about. They&#8217;re really big in Germany, and are trying to get into other markets. I actually quite like the interface we were shown, although it does look rather complicated. It&#8217;s always hard to judge as we were show the interface as seen by an administrator. Maybe it&#8217;s simpler if you&#8217;re logged in as a lesser mortal. The drag-and-drop of multiple objects looked rather nice. That said, the demo didn&#8217;t go well at all. The connection to the interwebs was very slow which screwed the demo badly (my comment about everything being run on local machines was wrong). And the choice of things to show wasn&#8217;t great either.</p>
  2142. <p>Third on was <strong>Kapow</strong>, doing a content migration demo. I thought the demo was decent, taking content from the conference site and sticking it into SiteCore. However, I suspect that most of the audience probably weren&#8217;t sure what they were seeing. For me, the demo was a lot more interesting than the rather dry Kapow presentation the night before. They showed the web interface for scripted remote control of a browser for migrating content. If I understood it correctly, it&#8217;s a bit like the <a href="">Selenium IDE</a>. Seeing as I&#8217;m more a fan of coding/scripting than pointing/clicking, it didn&#8217;t do much for me. I&#8217;m sure there is a scripting interface too, but we never saw it. I know the <a href="">Vamosa </a>product suite far better than I know Kapow, and the demo I saw didn&#8217;t allow me to compare the two.</p>
  2143. <p><strong>TERMINALFOUR </strong>was fourth. <a href="">Piero </a>showed a nice solid demo of the interface with a bit of WebDAV thrown in, but again nothing profound. Later that beer-fuelled evening, Janus introduced Piero to someone from the Danish digital agency <a href="">727 </a>online, and we all spent the next half an hour talking shite about 727 landing on TERMINALFOUR. You probably had to be there.</p>
  2144. <p>Fifth was <strong>23 Video</strong>, a startup that also produced the video for the conference. While the previous four demos were feature showcases, this demo was scenario based, which the judges preferred. But as the judges are all CMS geeks not Video Sharing Sites geeks, there weren&#8217;t too many questions. For example, my company uses the <a href="">YouTube API</a> and <a href="">Viddler</a> at the moment. The demo didn&#8217;t convince me to consider changing. I&#8217;d also have loved to see a video upload, but I guess the restrictive conference bandwidth probably meant they were clever to avoid this.</p>
  2145. <p>Last were defending champions <strong>SiteCore</strong>, presented by the defending champion <a href="">Lars Birkholm Petersen</a>. This was probably the most feature poor seven minutes of all of them. The whole demo consisted of creating a form with a CAPTCHA, and trying to fill in the form. There was a peak at the newly released Online Marketing Suite. They cleverly did not ever actually show the SiteCore interface which some of you will know also contains an Office-style ribbon.</p>
  2146. <p>However, it was a brilliantly presented featureless demo. Lars had hats representing conference organiser <a href="">Janus</a>, and CMS Analyst <a href="">Adriaan Bloem</a> (who wasn&#8217;t at the conference because he wasn&#8217;t capable of passing the CAPTCHA). He told a great story and got lots of laughs from everyone. You can watch the all the demos below.</p>
  2147. <p style="text-align: center;">
  2148. <p><object style="width: 510px; height: 287px;" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="510" height="287" codebase=",0,40,0"><param name="FlashVars" value="album%5fid=528666&amp;autoPlay=0" /><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="" /><param name="flashvars" value="album%5fid=528666&amp;autoPlay=0" /><embed style="width: 510px; height: 287px;" type="application/x-shockwave-flash" width="510" height="287" src="" allowscriptaccess="always" allowfullscreen="true" flashvars="album%5fid=528666&amp;autoPlay=0"></embed></object></p>
  2149. <p>The results:</p>
  2150. <ul>
  2151. <li>3rd &#8211; TERMINALFOUR</li>
  2152. <li>2nd &#8211; 23 Video</li>
  2153. <li>1st &#8211; Sitecore, defending their title</li>
  2154. </ul>
  2155. <p>Unsurprisingly, the votes went according to the quality and style of the demo, not according to what was actually demoed. And the best demo certainly won. But none of the vendors showed any profound features. Throughout the conference everyone was talking about The Next Big Thing, Social Media, Engagement, Web 3.5, etc, etc. Yet all the CMS vendors simply showed their content entry forms! If I&#8217;d had a vote, I think I&#8217;d have voted for Microsoft (shock, horror!) based on a Most Improved Award mentality.</p>
  2156. <p>The whole event was great fun. The other two judges were mean &#8211; Erik being the hardest to please. I&#8217;m told that Erik looks like a kitten compared to <a href="">Tony Byrne</a>, who makes vendors cry. Finally, I often wonder how important the &#8220;sizzle&#8221; factor is in demos that are part of formal RFPs. I hope the buyers judge on more than the audiences at Web Idol do.</p>
  2157. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2158. <wfw:commentRss></wfw:commentRss>
  2159. <slash:comments>6</slash:comments>
  2160. </item>
  2161. <item>
  2162. <title>Don’t Make Monoliths</title>
  2163. <link></link>
  2164. <comments></comments>
  2165. <pubDate>Wed, 11 Nov 2009 12:46:53 +0000</pubDate>
  2166. <dc:creator>Jon Marks</dc:creator>
  2167. <category><![CDATA[Agency]]></category>
  2168. <category><![CDATA[Ramblings]]></category>
  2169. <category><![CDATA[architecture]]></category>
  2170. <category><![CDATA[planning]]></category>
  2171. <category><![CDATA[procurement]]></category>
  2173. <guid isPermaLink="false"></guid>
  2174. <description><![CDATA[This was the main point of my JBoye Presentation. A few people have asked me what I mean by this. So I figured I'd write a little story instead about the technical, project management and procurement monoliths that have been giving me a headache recently.]]></description>
  2175. <content:encoded><![CDATA[<blockquote class="dylan"><p>Come gather &#8217;round friends<br />
  2176. And I&#8217;ll tell you a tale<br />
  2177. Of when the red iron pits ran plenty.<br />
  2178. - NORTH COUNTRY BLUES</p></blockquote>
  2179. <p>Asterix was worried. Once again he&#8217;d woken up with his bed surrounded by water. It appeared that the melting polar ice caps were leading to a rise in the sea level, which was threatening to flood the whole of Armorica. The only solution would be to move the entire town further inland, and they&#8217;d run out of magic potion. He got up, got dressed, and went to find Overcomplix, the town&#8217;s architect. When he found him, Overcomplix looked worried too.</p>
  2180. <p>&#8220;So, Overcomplix, how are the plans to migrate the village inland progressing?&#8221;, inquired Asterix. &#8220;To be honest&#8221;, replied Overcomplix, &#8220;not very well. You see, when we designed this village, we opted for a tightly coupled, fully integrated architecture. The town hall is joined to the market by solid iron girders, and all of the houses are tightly welded to the market. If we could move one building at a time, we&#8217;d be okay. But if we try to separate them, the whole village will fall apart. I think Gantchartix is working on a plan, though.&#8221;</p>
  2181. <p>&#8220;That&#8217;s no good at all&#8221;, sighed Asterix. &#8220;I&#8217;ll talk to Gantchartix, but it sounds like we&#8217;ve built a monolith. Let me find Obelix. He&#8217;s helped us out of tight spots before.&#8221;</p>
  2182. <p style="text-align: center;"><a href=""><img class="aligncenter" title="asterix-obelix" src="/wp-content/uploads/2009/11/asterix-obelix-188x300.gif" alt="asterix-obelix" width="188" height="300" /></a></p>
  2183. <p>When Asterix found Gantchartix, he was surrounded by Microsoft Project Plans and grinning from ear to ear. &#8220;I&#8217;ve created a masterpiece&#8221;, smiled Gantchartix. &#8220;The village is saved. All we need to do is get one hundred thousand doves and connect them to the village with pieces of rope. Then, all the doves need to lift off at exactly the same moment, fly inland a bit, and land at exactly the same time. If one of them mistimes it, the village will fall apart. But look at my project plan &#8211; it&#8217;s perfect.&#8221;</p>
  2184. <p>Asterix wasn&#8217;t convinced. Once again, Gantchartix was living inside his plan instead of reality. &#8220;That sounds like a Big Bang approach to me, Gantchartix. Those never work. Your plan is a monolith. I really need to speak to Obelix. He has experience with these things.&#8221;</p>
  2185. <p>All this worrying had made Asterix hungry. He decided to visit Procurafix to grab a bite to eat.</p>
  2186. <p>&#8220;Sorry, Asterix, we don&#8217;t have any food,&#8221; explained Procurafix. &#8220;We are in the  middle of evaluating responses to our Supply Everything To Armorica RFP. The lawyers are embroiled in a battle over the Boar Hunting Rights clause, so the process might take a while yet. Rather annoyingly, this probably means we won&#8217;t have grain or water for a while either. It&#8217;s a single contract for everything.&#8221;</p>
  2187. <p>&#8220;That is annoying&#8221;, said Asterix. &#8220;In fact, your process sounds rather like another monolith. I&#8217;ll see if Obelix can move it forward. He is good at that.&#8221;</p>
  2188. <p style="text-align: center;"><a href=""><img class="aligncenter" title="Building A Monolith" src="/wp-content/uploads/2009/11/asterixandobelix2.jpg" alt="Building A Monolith" width="300" height="300" /></a></p>
  2189. <p>Obelix seemed to be the only one that could bypass Procurafix&#8217;s rules as when Asterix found him he was feasting on nuts and oysters. Asterix explained the sad state of affairs, and asked Obelix for help.</p>
  2190. <p>&#8220;Sorry, Asterix. I&#8217;m afraid I have some bad news. The Goths have offered me a much higher day rate as part of an extremely attractive package. Effective immediately, I&#8217;m working for them. You&#8217;re on your own.&#8221;</p>
  2191. <p>&#8220;Oh no! We&#8217;re doomed,&#8221; cried Asterix. &#8220;We should never have made those fucking monoliths.&#8221;</p>
  2192. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2193. <wfw:commentRss></wfw:commentRss>
  2194. <slash:comments>74</slash:comments>
  2195. </item>
  2196. <item>
  2197. <title>My JBoye09 Fix WCM Presentation</title>
  2198. <link></link>
  2199. <comments></comments>
  2200. <pubDate>Wed, 04 Nov 2009 13:19:55 +0000</pubDate>
  2201. <dc:creator>Jon Marks</dc:creator>
  2202. <category><![CDATA[Events]]></category>
  2203. <category><![CDATA[Ramblings]]></category>
  2204. <category><![CDATA[CMS]]></category>
  2205. <category><![CDATA[cmswatch]]></category>
  2206. <category><![CDATA[jboye]]></category>
  2208. <guid isPermaLink="false"></guid>
  2209. <description><![CDATA[Just finished my "Inconvenient truths and unsolved industry challenges" session at JBoye09, with Janus Boye and Jarrod Gingras of CMS Watch. You can download the slide deck as a 2MB PDF here
  2210. ]]></description>
  2211. <content:encoded><![CDATA[<blockquote class="dylan"><p>In the dime stores and bus stations,<br />
  2212. People talk of situations,<br />
  2213. Read books, repeat quotations,<br />
  2214. Draw conclusions on the wall.<br />
  2215. Some speak of the future,<br />
  2216. My love she speaks softly,<br />
  2217. She knows there&#8217;s no success like failure<br />
  2218. And that failure&#8217;s no success at all<br />
  2219. - LOVE MINUS ZERO/NO LIMIT</p></blockquote>
  2220. <p>Just finished my &#8220;<a href="">Inconvenient truths and unsolved industry challenges</a>&#8221; session at <a href="">JBoye Aarhus 09</a>, with <a href="">Janus Boye</a> (the organiser) and <a href="">Jarrod Gingras</a> of CMS Watch. The session was fairly lively, and the <a href="">#fixwcm</a> hashtag was nice and busy. Over 300 tweets so far, and it&#8217;s still going strong. Keep the discussion going. If you&#8217;re at the conference, grab me for some beers over the next couple of nights.</p>
  2221. <div id="__ss_2475374" style="width: 425px; text-align: left;"><a style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;" title="J Boye20091103 V1.2" href="">J Boye20091103 V1.2</a><object style="margin:0px" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="355" codebase=",0,40,0"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value=";stripped_title=j-boye20091103-v12" /><param name="allowfullscreen" value="true" /><embed style="margin:0px" type="application/x-shockwave-flash" width="425" height="355" src=";stripped_title=j-boye20091103-v12" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
  2222. <div style="font-size: 11px; font-family: tahoma,arial; height: 26px; padding-top: 2px;">View more <a style="text-decoration:underline;" href="">documents</a> from <a style="text-decoration:underline;" href="">Jon Marks</a>.</div>
  2223. </div>
  2224. <p>You can download the slide deck as a 2MB PDF here:<br />
  2225. <a href=""></a></p>
  2226. <p>The slides probably don&#8217;t make any sense without my commentary. In fact, they probably don&#8217;t make any sense with it.</p>
  2227. <p><a href=""><img class="aligncenter size-medium wp-image-1237" title="JBoyeMug" src="" alt="JBoyeMug" width="299" height="300" /></a></p>
  2228. <p>I know a few people have blogged about the session. So far I&#8217;m aware of:</p>
  2229. <ul>
  2230. <li>Janus Boye &#8211; <a title="Permanent Link to Rethink web content management" rel="bookmark" href="">Rethink web content management</a></li>
  2231. <li>Jarrod Gingras, CMS Watch &#8211; <a href="">Is WCM fundamentally broken?</a></li>
  2232. <li>Irina Guseva, CMS Wire -<a href=""> #jboye09 Web Content Management: Inconvenient Truths and Industry Challenges</a></li>
  2233. <li>Ron Miller , FierceCM &#8211; <a href="">Is the vendor solely responsible for WCM project failure? </a></li>
  2234. <li>Michael Kowalski- <a href="">Hey everybody, let’s #fixwcm right now!</a></li>
  2235. <li>Yuval Ararat &#8211; <a rel="bookmark" href="">What went wrong? #fixwcm!</a></li>
  2236. <li>Vern Imrich &#8211; <a href="">Get the most out of a WCMS Trial, Test, or Proof of Concept (POC)</a> (Sales Pitch Alert!)</li>
  2237. <li>Ian Truscott &#8211; <a href="">Does WCM Really Need a Fix?</a></li>
  2238. <li>James Hoskins &#8211; <a href="">#fixwcm &#8211; some thoughts from the front line</a></li>
  2239. <li>Seth Gottlieb &#8211; <a href="">The world&#8217;s worst WCMS</a></li>
  2240. <li>Bryan Ruby, CMS Report &#8211; <a href="">When WCM is no longer fun</a></li>
  2241. <li>Philippe Parker &#8211; <a href="">Something rotten in WCM</a></li>
  2242. <li>Tristan Renaud &#8211; <a href="">Fixing the WCM: don’t forget your crampons, your rope and your guide</a></li>
  2243. <li>Lokesh Pant &#8211; <a href="">Who should #fixwcm?</a></li>
  2244. </ul>
  2245. <p>And thanks to the kind people that took the photos I stole without credit from Google. Sadly, I stole them from stolen sources so really don&#8217;t know who to credit. Finally, here&#8217;s a taster of some of the many tweets that came in:</p>
  2246. <ul>
  2247. <li><strong>bjfogg </strong>OH in #jboye09 session: If we can name things better, we can put standards around them #fixwcm</li>
  2248. <li><strong>RussellNelson </strong>#fixwcm 1 happy cms customer in a room of 20 &#8211; that meets my definition of something that is broken</li>
  2249. <li><strong>jameshoskins </strong>#fixwcm not all the buyers fault &#8211; WCM vendors need to focus on long standing pain points as much as those business winning new features</li>
  2250. <li><strong>tednyberg </strong>Often times when companies switch #WCM often I think it&#8217;s a sign of dissatisfaction with the implementer, not necessarily the #CMS. #fixwcm</li>
  2251. <li><strong>sigdestad </strong>#fixwcm Dare to say no to the customer &#8211; Good advices some times require courage</li>
  2252. <li><strong>adrianmateljan </strong>Are the likes of @cmswatch diverting us from the real implementation issues? Perhaps #agencywatch would be more appropriate? #fixwcm</li>
  2253. <li><strong>theresaregli </strong>@janusboye says a big part of education is finding people who are trusted #jboye09 #fixwcm</li>
  2254. <li><strong>irina_guseva</strong> If you’re waiting for #WCM vendors to wake up and fix the problems, it is unrealistic, says @janusboye #fixwcm #jboye09</li>
  2255. <li><strong>yuvalararat </strong>Guys the products are fine the way we implement and the way clients envision the system is the failure, Kill the sales guys #fixwcm</li>
  2256. </ul>
  2257. <div id="_mcePaste" style="overflow: hidden; position: absolute; width: 1px; height: 1px; top: 599px; left: -10000px;">bjfogg OH in #jboye09 session: If we can name things better, we can put standards around them #fixwcm<br />
  2258. RussellNelson #fixwcm 1 happy cms customer in a room of 20 &#8211; that meets my definition of something that is broken<br />
  2259. jameshoskins #fixwcm not all the buyers fault &#8211; WCM vendors need to focus on long standing pain points as much as those business winning new features<br />
  2260. tednyberg Often times when companies switch #WCM often I think it&#8217;s a sign of dissatisfaction with the implementer, not necessarily the #CMS. #fixwcm<br />
  2261. sigdestad #fixwcm Dare to say no to the customer &#8211; Good advices some times require courage<br />
  2262. adrianmateljan Are the likes of @cmswatch diverting us from the real implementation issues? Perhaps #agencywatch would be more appropriate? #fixwcm<br />
  2263. theresaregli @janusboye says a big part of education is finding people who are trusted #jboye09 #fixwcm<br />
  2264. irina_guseva If you’re waiting for #WCM vendors to wake up and fix the problems, it is unrealistic, says @janusboye #fixwcm #jboye09<br />
  2265. yuvalararat Guys the products are fine the way we implement and the way clients envision the system is the failure, Kill the sales guys #fixwcm</div>
  2266. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2267. <wfw:commentRss></wfw:commentRss>
  2268. <slash:comments>4</slash:comments>
  2269. </item>
  2270. <item>
  2271. <title>Let’s #fixwcm Before The Wheels Come Off</title>
  2272. <link></link>
  2273. <comments></comments>
  2274. <pubDate>Sun, 01 Nov 2009 23:25:29 +0000</pubDate>
  2275. <dc:creator>Jon Marks</dc:creator>
  2276. <category><![CDATA[Agency]]></category>
  2277. <category><![CDATA[Events]]></category>
  2278. <category><![CDATA[Ramblings]]></category>
  2279. <category><![CDATA[This Blog]]></category>
  2280. <category><![CDATA[CMS]]></category>
  2281. <category><![CDATA[cmswatch]]></category>
  2282. <category><![CDATA[jboye]]></category>
  2283. <category><![CDATA[standards]]></category>
  2285. <guid isPermaLink="false"></guid>
  2286. <description><![CDATA[How many WCM implementations leave customers grinning from ear to ear? The statistics make sad reading. But if so many projects don’t meet expectations, who is to blame? Is it the vendor, either because of a crappy product or dodgy practice? Or the implementer that eats your budget while making a beautiful product smell real bad? Or are the customers naive, unrealistic or worse?]]></description>
  2287. <content:encoded><![CDATA[<blockquote class="dylan"><p>Standing next to me in this lonely crowd,<br />
  2288. Is a man who swears he&#8217;s not to blame.<br />
  2289. All day long I hear him shout so loud,<br />
  2290. Crying out that he was framed.<br />
  2291. - I SHALL BE RELEASED</p></blockquote>
  2292. <p>How many WCM implementations leave customers grinning from ear to ear? The statistics make sad reading. But if so many projects don&#8217;t meet expectations, who is to blame? Is it the vendor, either because of a crappy product or dodgy practice? Or <a id="aso:" title="the implementor that eats your budget" href="../2009/04/24/sitatm-milking-the-client/">the implementer that eats your budget</a> while making a beautiful product smell real bad? Or are the customers naive, unrealistic or worse?</p>
  2293. <p>On Wednesday morning, the <a id="udhx" title="Web Content Management Track" href="">Web Content Management Track</a> of the <a id="v0cw" title="Greatest Web Conference in the World" href="">Greatest Web Conference in the World</a> kicks off. The opening session, &#8220;Inconvenient truths and unsolved industry challenges &#8220;, has a rather unambitious aim &#8211; to solve the world&#8217;s WCM problems. A bit like WCM World Peace. On the panel we&#8217;ll have <a href="">Janus Boye</a> himself representing the customer viewpoint, <a href="">Jarrod Gingras</a> of CMS Watch representing the analyst massive, and <a id="qlda" title="little old me" href="">little old me</a> defending the honour of the implementers.</p>
  2294. <p><a href=""><img class="aligncenter size-medium wp-image-1222" title="Tweet4" src="" alt="Tweet4" width="300" height="187" /></a></p>
  2295. <p>The topics are sure to be varied, and our <a id="ov8q" title="esteemed moderator" href="">esteemed moderator</a> will be sourcing questions from the crowd, and from Twitter. We&#8217;ll be using the hashtag <a id="o854" title="#fixwcm" href="">#fixwcm</a> so be sure to set up your Twitter search now, and get involved in the discussions. Apart from blaming each other for multiple disasters, some other issues we might be covering include:</p>
  2296. <ul>
  2297. <li>Does the term WCM even make sense these days?</li>
  2298. <li>Are there too many vendors out there, and will we see consolidation?</li>
  2299. <li>Can buyers navigate the marketplace themselves?</li>
  2300. <li>Why do so many projects fall on their face?</li>
  2301. <li>Will Open Source vendors dominate in the future?</li>
  2302. <li>Do you need hard requirements to select a CMS, or is it a philosophical decision?</li>
  2303. <li>Are more Web / Content Standards the answer to our prayers?</li>
  2304. <li>Why are the Requests for Proposal always so bad?</li>
  2305. </ul>
  2306. <p><a href=""><img class="aligncenter size-medium wp-image-1219" title="Tweet1" src="" alt="Tweet1" width="300" height="169" /></a><br />
  2307. You can start shaping the session <em>right now</em> by tweeting your thoughts using our <a id="f80k" title="#fixwcm" href="">#fixwcm</a> hashtag. We want to hear why you think WCM is broken, and what the biggest challenges are. Or if you just want a 140-character rant about a horrorshow of a project, that&#8217;ll be fun too.</p>
  2308. <p>Join us live on Twitter on Wednesday 4th November between 10:30 and 12:00 CET to throw in some curveballs. And if, for some reason, you&#8217;re attending the conference but choose to attend one of the competing parallel sessions (like the great <a href="">Kristina Halvorson</a>,<a href=""> Bob Boiko</a>,   <a href="">Jane McConnell</a> or <a href="">Shawn Shell</a> &#8211; it&#8217;s a tough pool), you can still participate on Twitter at the same time!</p>
  2309. <p><a href=""><img class="aligncenter size-medium wp-image-1218" title="Tweet2" src="" alt="Tweet2" width="300" height="169" /></a><br />
  2310. See you in person or in the Twittersphere. It&#8217;s going to be cold as hell in Aarhus, but the discussions are sure to get heated.</p>
  2311. <p>P.S. If you think the main WCM problem is the design of the content repository, it looks like @pmonks, @justincormack, @micycle and others might have it fixed before our session starts. Hope they&#8217;ll share their findings live! The Content Tree is Dead. Long Live the Content Graph.</p>
  2312. <p><a href=""><img class="aligncenter size-medium wp-image-1221" title="Tweet3" src="" alt="Tweet3" width="300" height="186" /></a></p>
  2313. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2314. <wfw:commentRss></wfw:commentRss>
  2315. <slash:comments>9</slash:comments>
  2316. </item>
  2317. <item>
  2318. <title>A Collaborative Google Wave Blog Post</title>
  2319. <link></link>
  2320. <comments></comments>
  2321. <pubDate>Fri, 23 Oct 2009 15:53:29 +0000</pubDate>
  2322. <dc:creator>Jon Marks</dc:creator>
  2323. <category><![CDATA[Ramblings]]></category>
  2324. <category><![CDATA[This Blog]]></category>
  2325. <category><![CDATA[collaboration]]></category>
  2326. <category><![CDATA[google]]></category>
  2327. <category><![CDATA[wave]]></category>
  2329. <guid isPermaLink="false"></guid>
  2330. <description><![CDATA[It's almost 17:00 on a Friday afternoon, and I've just spent the last hour trying to write a blog post on Google Wave with The Motley Crew. Rather than say any more, read the post we made. I've embedded the wave below for those that have a Wave account, and the full blog text is at the bottom.]]></description>
  2331. <content:encoded><![CDATA[<blockquote class="dylan"><p>Now I wish I could write you a melody so plain<br />
  2332. That could hold you dear lady from going insane<br />
  2333. That could ease you and cool you and cease the pain<br />
  2334. Of your useless and pointless knowledge<br />
  2335. - TOMBSTONE BLUES</p></blockquote>
  2336. <p>It&#8217;s almost 17:00 on a Friday afternoon, and I&#8217;ve just spent the last hour trying to write a blog post on Google Wave with The Motley Crew. Rather than say any more, read the post we made. I&#8217;ve embedded the wave below for those that have a Wave account, and the full blog text is at the bottom, and hopefully repeated on the blogs of <a href="">Irina</a>, <a href="">Justin</a>, <a href="">Ian </a>and more. Maybe even CMS Watch if Adriaan can twist Tony&#8217;s arm!</p>
  2337. <h1>The Wave</h1>
  2339. <div id="waveframe-1"  style="width:100%;height:500px;"  ></div>
  2340. <script type="text/javascript">
  2342. add_wave("waveframe-1",{
  2343. bgcolor:"#dddddd",
  2344. color:"black",
  2345. font:"",
  2346. font_size:"1em",
  2347. width:"100%",
  2348. height:"500px",
  2349. server:"",
  2350. id:"!w+UrMQrNA0D" });
  2352. </script>
  2353. <h1>Things We Hate About Content Management</h1>
  2354. <p>- By The Motley Crew</p>
  2355. <p>It was a lovely Friday morning/afternoon, and we were Waving. The experiment initiated by McBoof (yes, that one) brought together 6 CMS folks from around the world. The event gathered together analysts, journalists, vendors, system integrators toWave on a topic that was decided at that very moment. We had one hour (in between conference calls and other job thingys) to pick a topic and Wave it.</p>
  2356. <p>A little collab on what exactly to Wave about later, we decided to do &#8220;a mindmap of things we find annoying in CMSs.&#8221; To up the ante, we also decided to take the original bullet points (deemed &#8220;too easy&#8221;) and convert the whole thing toprose. Was the tool given really up to the task? Were our minds flexible enough to wrap around this kind of realtime collaboration?</p>
  2357. <p>In the beginning &#8212; we blame the tool <img src='' alt=';)' class='wp-smiley' />  &#8212; we were Drowning, not Waving. We (almost) didn&#8217;t fight about <span style="background-color: yellow;"> </span>edits. We almost didn&#8217;t step on each other&#8217;s toes. All in all, it turned out to be a fun and productive collaborative exercise. Read on to see for yourself.</p>
  2358. <h2>Cosmetic Issues</h2>
  2359. <p>There really should be a CMS UI fashion police. As there should be a Magic Quadrant for shoes and handbags. Why? Well, there&#8217;s a couple of issues.</p>
  2360. <p>For instance, sloppy, non-designed design. You know the kind of thing that has not been thought about and reworked and made to feel right. The sort of thing coders do if you don&#8217;t force them. But at the same time, over-designed interfaces can be just as bad: the designers and developers really need to be on speaking terms.</p>
  2361. <p>When building a system that works, you can&#8217;t have the development team in the basement on a sustenance of Jolt coding away into the night, and the designers in the penthouse in turtleneck sweaters sipping espressos. Too many CMS designs end up being programmer vs. end-user friendly. And this is not the best way to charm away those marketing and web content folks.</p>
  2362. <p>Developers and designers need to talk to each other and essentially, both should talk to users &#8211; not just eat your own dogfood &#8211; but listen to what dogs like to eat. A developer or UI designer are not content editors, marketers or knowledge and information workers.</p>
  2363. <p>Some vendors say that the agonizingly and depressingly black UI backgrounds are hip and modern. Well, they are not, really. Who told you that? Especially if you add a Star Trek theme to it and sprinkle in some stars and cosmic swirls, because if Apple does it, it must be cool right? Not pointing any fingers, but I would quit if I were a content manager having to spend my 9-5 staring into the &#8220;black hole&#8221; of some of the CMS UIs that are out there on the market.</p>
  2364. <p>Even pop-ups seem less annoying when compared to dark UIs. Which brings us onto&#8230;</p>
  2365. <h2>Interface Issues</h2>
  2366. <p>Interfaces need a comfortable lived in feel. Content management is something people work with every day, it is their interface to their job. You meet people who hate the interface, and that makes their work a heap of pain. I have seen people who describe the 44 clicks it takes to insert an image. You have a responsibility to these people, to make them love the content and make the tool disappear.</p>
  2367. <p>We all hate it when the interface does something on its own that ruins your context. E.g. a page refresh, or in Wave the jumping around of the scrolled window in some cases <img src='' alt=';-)' class='wp-smiley' />  Or the lack of an easy way to bookmark, so you can reference someone to the content. Remember people will be collaborating and need to send links around. Make sure the UI is a proper web application with URLs. And why do tasks that are easy to describe and often repeated in exactly the same way still take more than a few clicks? (Or maybe even dozens of clicks.) With bonus points for forcing users to use dialogs or tabs to enter mandatory information. Remember people do not have all the information in the right order.</p>
  2368. <p>Also, we need sane conflict merges. Check in and check out is too extreme for most uses. But people want to edit offline still. Of course Wave doesn&#8217;t have an offline: Google thinks this problem is going away, it&#8217;s real time so there are never conflicts (that&#8217;s defined in the XML protocol; it&#8217;s quite interesting if you are that way geeky). Does Google have the right answer here? Well, the Motley Crew is struggling here, and some browsers lost sync during this experiment.</p>
  2369. <p>&#8220;Power users&#8221; (those who use it all day long) of CMSs needed to have a &#8220;Desktop&#8221; experience. What does Desktop Experience mean? Well, it doesn&#8217;t really have to be on the desktop &#8212; these days it is perfectly possible to get very close to a hitherto Desktop experience in a browser or similar. these are qualities:  very low latency from action to response, no page refreshes, modal and modal-less dialog boxes as appropriate, &#8220;push&#8221; notification.</p>
  2370. <h2>Architectural Issues</h2>
  2371. <p>Architectural issues of the wave overtook any architectural issues of Content Management Systems. The fact that we authored this entire article in a single blip didn&#8217;t help, and slowed everything down enormously. McBoof learned the hard way that he really need a new laptop and spent most of the session giving his machine CPR. Next time we&#8217;ll do each paragraph in its own blip to stop FireFox going down like a Led Zeppelin.</p>
  2372. <p>Monolithic systems. Build it out of pieces that the client can not use all of. Obviously your pieces may work together better, but there should be components. Do not try to reinvent all kinds of wheel. &#8220;Best of breed,&#8221; though, is just another weasel marketing idea, as if systems are pinnacles not about meeting requirements.</p>
  2373. <p><span><span> </span></span></p>
  2374. <p>Marketeers are adroit at using the term Best Practice to position Their Way as the only way that a particular matter can be solved. (Many of us live in that netherland of having to pedal that point of view, but it is a falsehood that the careful buyer should try to see through.)I think this devalues genuine best practice, vendors should cite references</p>
  2375. <p><span> </span></p>
  2376. <p>Most often a marketeer&#8217;s Best Practice view is the <span style="font-style: italic;">only </span>one they subscribe to as their product development has paddled up the wrong stream and cannot or won&#8217;t reverse their architectural design (probably because of the cost of doing so). This intransigence most often causes a product to doom itself. (Think of IBM and The Mainframe Is The Only Way To Do Serious Business).</p>
  2377. <p>Who really still believes that there is a place in this world for Flash or Java Applet based Rich Text Editors? TinyMCE, FCKeditor and others are filling the gap left by Ektron when they bit the hand that feeds and entered the CMS market. Ephox is trying to spread, but I find it difficult to come up with an excuse to use an Applet over HTML with javascript these days. Stick with the standard.</p>
  2378. <h2><span style="font-weight: bold;">Bu</span><span style="font-weight: bold;">siness Issues</span></h2>
  2379. <p>Where you are buying into something that you may very well need to change or integrate with there is strong benefit in considering Open Source. Open Source used to frighten commercial software companies but we have come along way on that road to understand that commercial organisation can operate in an Open Source world and benefit. This does not necessarily mean that their prized system needs to be fully opened up, but taking the <span style="font-style: italic;">spirit </span>of it to mean that you are completely open to people seeing and learning from your code how it operates.</p>
  2380. <p>Exactly what you need to see opened up varies.  In a CMS there may be a subsystem that stores the content or one that allows a Rich Text Editor. These arguably don&#8217;t need to be opened up, but when a CMS ships with modules for, for example, an RSS feed widget, calendaring tool, prebuilt webforms, users who then want a variation on this module can benefit from seeing how the &#8220;pros&#8221; did it, they can then use it as a starting point for their own different implementation.</p>
  2381. <p>We really don&#8217;t need vendors that pay lip service to the buzzwords. When they think the new CMS buzzword &#8220;engagement&#8221; is just a screenshot of Google Analytics. Or when they add an image picker and call itDAM . And a cross-over between WCM and ECM? Don&#8217;t think WCM is like ECM and it&#8217;s about organizing content, not about effectively communicating with the audience. And don&#8217;t think that if you organize the content, you canaut <span> </span>omatically communicate effectively.</p>
  2382. <p>Completely different, but equally frustrating, is procurement (and the procedures that go with it.) Procurement folk don&#8217;t recognise the importance of user adoption to the success of the project &#8212; of the black background and all the UI issues pointed out previously. If a CMS is procured according to procedure, the selection is a success to them. But those same rules are often a recipe for ignoring what the users really need.</p>
  2383. <p>At the same time, budgets that aren&#8217;t transparent are an issue &#8211; customer and vendor should be able to have a sensible grown up conversation. As a customer, of course you want good value, but how cheap are you?But to vendors: many licensing models don&#8217;t make any sense, and force you to do stupid things. People are scared to have that conversation &#8211; the best architectural fit first I say, lets figure out an appropriate license around that.</p>
  2384. <h2>Conclusion</h2>
  2385. <p>So much hatred rolled up into a tight little ball of anti-CMS rage. Who would have expected it from such a respected bunch of CMS folk. We hate the designs, the interfaces, the architectures and the business. Time for a beer/wine? Wave good bye!<span><br />
  2386. </span></p>
  2387. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2388. <wfw:commentRss></wfw:commentRss>
  2389. <slash:comments>24</slash:comments>
  2390. </item>
  2391. <item>
  2392. <title>Reflections on EPiServer London Day</title>
  2393. <link></link>
  2394. <comments></comments>
  2395. <pubDate>Thu, 15 Oct 2009 09:50:11 +0000</pubDate>
  2396. <dc:creator>Jon Marks</dc:creator>
  2397. <category><![CDATA[Events]]></category>
  2398. <category><![CDATA[Ramblings]]></category>
  2399. <category><![CDATA[Beer]]></category>
  2400. <category><![CDATA[CMS]]></category>
  2401. <category><![CDATA[EPiServer]]></category>
  2402. <category><![CDATA[google]]></category>
  2403. <category><![CDATA[hangover]]></category>
  2404. <category><![CDATA[interwoven]]></category>
  2405. <category><![CDATA[marketing]]></category>
  2406. <category><![CDATA[partners]]></category>
  2407. <category><![CDATA[sitecore]]></category>
  2408. <category><![CDATA[tridion]]></category>
  2409. <category><![CDATA[upgrade]]></category>
  2411. <guid isPermaLink="false"></guid>
  2412. <description><![CDATA[So I managed to get to the EPiServer Customer and Partner Day in London. The main goodies on the roadmap are the new Marketing Arena, and EPiServer 6.]]></description>
  2413. <content:encoded><![CDATA[<blockquote class="dylan"><p>Well, early in the mornin&#8217;<br />
  2414. &#8216;Til late at night,<br />
  2415. I got a poison headache,<br />
  2416. But I feel all right.<br />
  2417. - PLEDGING MY TIME</p></blockquote>
  2418. <p>I managed to get to the <a href="">EPiServer Customer and Partner Day</a> in London on Tuesday. I presented there <a href="">last year</a>, but this year could relax and go to lots of sessions. There were over 250 people, a big increase. They&#8217;re doing rather nicely in the UK, and everywhere else. They claim to have launched 500 new sites in the last three months. Personally, I hate the number of sites metric. I wish vendors would use number of new clients. For a nice, general overview of the day read <a href="">James&#8217; blog post</a>. I&#8217;m just going to ramble a bit as usual.</p>
  2419. <p><a href=""><img class="aligncenter size-medium wp-image-1193" title="Mingling is fun" src="" alt="Mingling is fun" width="300" height="225" /></a></p>
  2420. <p>EPiServer are still moving extremely quickly, which I talked about <a href="">six months ago at the Swedish event</a>. The main goodies on the roadmap are the new Marketing Arena, and EPiServer 6. And I stayed till far too late and still have a headache two days later, but that&#8217;s a story for another time.</p>
  2421. <h2>Yams, Yams everywhere</h2>
  2422. <p>Yes, we&#8217;ve got Yet Another Marketing Suite. Hot on the heels of  <a href=";source=web&amp;ct=res&amp;cd=1&amp;ved=0CAsQFjAA&amp;;ei=NDHWSvWWPIb54AbGuancDA&amp;usg=AFQjCNHgENEoy9T_eBWambaKX_HcozmzWg&amp;sig2=uviQBUUswcl_8CabFGn-Gw">SiteCore&#8217;s Online Marketing Suite</a>, <a href="">Tridion&#8217;s Unified Online Marketing Suite</a> and <a href="">Autonomy/Interwoven&#8217;s Optimized Landing Page Solution</a>, our friends at EPiServer showed off their new <a href="">Marketing Arena</a>. EPiServer&#8217;s product has four main prongs (each sold separately, batteries included):</p>
  2423. <h3>Campaign Monitor and Optimiser (CMO)</h3>
  2424. <p>The CMO has two parts. The <strong>Landing Page Optimiser (LPO)</strong> performs A/B Testing and has a nice interface. It is an entry level product that doesn&#8217;t include demographic information in the A/B testing which, for me, is something they need to introduce before I&#8217;d consider using it. The tool needs to be able to say, for example, &#8220;Page A performs best for US customers and Page B for European customers&#8221;. It also doesn&#8217;t perform <a href="">Multivariate Testing</a> but who know what the future holds. It provides basic web analytics, but wouldn&#8217;t claim to complete with a niche analytics product. In summary, it&#8217;s a nice entry level tool.</p>
  2425. <p><a href=""><img class="aligncenter size-medium wp-image-1188" title="CMO_BigScreen" src="" alt="CMO_BigScreen" width="300" height="183" /></a></p>
  2426. <p>The second part, <strong>EPiServer SEO</strong>, performs good static analysis of your site and provides friendly instructions about how to improve your searchability based on the ever-changing rules of the search engines. It does all the things it should, looking at sematic code quality as well as content quality. It summarises this into a single number (your Digital Visibility) in a similar way to <a href="">WebSite Grader</a>. It&#8217;s a hosted service maintained by a third party. I wish I&#8217;d known about this before an we could have tried to set up a partnership with LBi instead &#8211; we have <a href="">a service that&#8217;s very similar</a>.</p>
  2427. <p>One thing I don&#8217;t like is the fact EPiServer SEO also has basic web tracking, to provides things like Heat Maps showing where users focus. Other parts of the CMO already have script based tracking. Two products doing this is one too many. And another trend I don&#8217;t like &#8211; black seems to be the new white. CMO has a shiny black background on their new &#8220;funky&#8221; product, while everything else is still white. Vignette did it with their Rich Media product. What&#8217;s wrong with white backgrounds anyway?</p>
  2428. <h3>B2B Adapt</h3>
  2429. <p>This is cool. Using an enhanced version of the <a href="">Dun &amp; Bradstreet company database</a>, it maps the visitor&#8217;s IP address to their company&#8217;s <a href="">Standard Industrial Classification</a> (SIC) code. From this, the product can tell the vertical industry of the company, the number of employees and even the annual turnover. These attributes are then fed into the rules engine to allow you to target different content to the revelant people. For example, you could show a very different pages to a small Swedish fishing company and a large US pharma. This is a hosted service which contains both the up-to-date database of companies as well as the rules.</p>
  2430. <p>I&#8217;d really like to use a service like this simply to get the demographic information and then put it to use in my own evil ways. However, I&#8217;m told this isn&#8217;t legal. There are strict (and somewhat quirky) rules around how company demographic information can be used.</p>
  2431. <h3>B2B Prospect</h3>
  2432. <p>This is a lower-cost option using the same technology as B2B Adapt. It simply provides a report of the companies that visited your site, including contact details and other useful things.</p>
  2433. <h2>From Zero to Hero</h2>
  2434. <p>Those of you that are wise in the EPiWays will recognise a few of the features mentioned above. EPiServer have a really really strong development community and an extensible API, so third parties are continually adding modules and features. They&#8217;ve just taken the first step towards an EPiAppStore with the release of the <a href="">EPiServer Extra directory</a> which includes free and commercial modules created by EPiServer and third parties. Many of these modules are now in the main product. Some of the extras that have made the big time include:</p>
  2435. <ul>
  2436. <li><a href="">dropit </a>- Their X3 add-on has become <a href="">EPiServer Composer</a>, part of the Create+ package.</li>
  2437. <li> <a href="">Meridium</a> &#8211; Their <a href="">ImageVault</a> DAM add-on is also part of Create+ (and they stayed late and had lots of beer)</li>
  2438. <li><a href="">Ottoboni </a>- Their InteractiveScene is in <a href="">Create+</a> too.</li>
  2439. <li><a href="">Online Services</a> &#8211; <a href=";lang=44">XTractor </a>for EPiServer has become EPiServer SEO.</li>
  2440. <li><a href="">Enecto </a>- The adaptivecontent and prospectfinder are <a href="">B2BAdapt </a>and <a href="">B2BProspect </a>respectively.</li>
  2441. <li>EPiTrace &#8211; this is now bundled in the Marketing Arena.</li>
  2442. </ul>
  2443. <p><a href=""><img class="aligncenter size-full wp-image-1184" title="AllTheEPiMore" src="" alt="AllTheEPiMore" width="439" height="145" /></a></p>
  2444. <p>I really like this model, by the way. All the most of the integrations are loosely coupled, and using partners like this allows the EPiServer guys to focus on the core.</p>
  2445. <h2>What&#8217;s in EPiServer 6</h2>
  2446. <p>The other big news is, of course, the arrival of EPiServer 6. Technically, this isn&#8217;t a massive change and the upgrade from 5.x promises to be trivial. As @rogerwirz pointed out in his closing presentation, it&#8217;s more of an &#8220;editorial training upgrade&#8221; than a technical one. I loved the comedy-act demo from @sunnaster and @mathel, sucking Tweets into the new Dynamic Data Store. I&#8217;m slightly uneasy about the Dynamic Data Store &#8220;Big Table&#8221; architecture, but I think this is because I&#8217;m old-school and fear change. But don&#8217;t get fooled into believing that this is anything like Google&#8217;s <a href="">BigTable </a>which  isn&#8217;t an RDBMS and wouldn&#8217;t pass the <a href="">ACID</a> test. The EPiServer &#8220;Big Table&#8221; really is just a big bastard of a SQL table which sounds pretty hard to index. But I&#8217;m sure they&#8217;ve got it right. Something to talk to Roger about next time he&#8217;s in town.</p>
  2447. <p>I liked the demo of the new Dashboard (and how to write extensions for it) from @epirach and @bevan_souster. This Dashboard is based on the new <a href="">EPiServer CMS Shell framework</a> and provides good Portalesque features. However, I think it also overlaps enormously with many of the features of EPiServer Composer. So much overlap, in fact, that keeping both technologies alive doesn&#8217;t make sense. If I was a betting man (which I am) I&#8217;ll wager the heart of EPiServer Composer will be ripped out and replaced with a shiny new one in one (or at most two versions) time. At least I hope so.</p>
  2448. <p>Some other new features of EPiServer 6 which excite me:</p>
  2449. <ul>
  2450. <li>Completely browser compatibility on the editorial site</li>
  2451. <li>Complete mirroring rewrite, which is a very good thing</li>
  2452. <li>Access rights on page types</li>
  2453. <li>Access rights on languages</li>
  2454. <li>Drag and drop page tree ordering</li>
  2455. </ul>
  2456. <h2>Final Thoughts</h2>
  2457. <p>The thing I like most about EPiServer is their geekiness and honesty. For example, in the keynote, they happily admit which products are simply OEM&#8217;ed partner products. Some competitors will wax lyrical about how <em>their </em>product has won Award XYZ, which happened before they even OEM&#8217;ed it.  The final presentation was a tech demo that everyone was forced to watch. I did hear some less-technical people saying that some of the presentations aren&#8217;t slick and &#8220;marketeer&#8221; enough. Which is great. Keep it up I say.</p>
  2458. <p>But please use a shorter hashtag than <a href="">#episerverdayuk09</a> next year.</p>
  2459. <div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">Dun &amp; <em>Bradstreet</em></div>
  2460. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2461. <wfw:commentRss></wfw:commentRss>
  2462. <slash:comments>5</slash:comments>
  2463. </item>
  2464. <item>
  2465. <title>Web in a Box, or Mix and Match?</title>
  2466. <link></link>
  2467. <comments></comments>
  2468. <pubDate>Wed, 23 Sep 2009 08:22:45 +0000</pubDate>
  2469. <dc:creator>Jon Marks</dc:creator>
  2470. <category><![CDATA[Ramblings]]></category>
  2471. <category><![CDATA[CMS]]></category>
  2472. <category><![CDATA[EPiServer]]></category>
  2473. <category><![CDATA[procurement]]></category>
  2474. <category><![CDATA[sitecore]]></category>
  2475. <category><![CDATA[standards]]></category>
  2477. <guid isPermaLink="false"></guid>
  2478. <description><![CDATA[CMS RFPs seem to want everything these days. But should you buy a single one-stop-shop product that does everything, or assemble together a set of best-of-breed products?]]></description>
  2479. <content:encoded><![CDATA[<blockquote class="dylan"><p>Never bein&#8217; able to separate the good from the bad,<br />
  2480. Ooh, I can&#8217;t stand it, I can&#8217;t stand it,<br />
  2481. It&#8217;s makin&#8217; me feel so sad.<br />
  2482. - DEAD MAN, DEAD MAN</p></blockquote>
  2483. <p><a href="">ACME Corporation</a> have decided to launch a web presence to support their thriving cartoon supply business . They hire you as the brand new big technical cheese to realise their vision. And this vision, as usual, includes everything: Content Management, of course; Search so that you can find the products; a Community to provoke discussion about new product design; Digital Asset Management to store the images and blueprints of the products; Analytics to track down who is interesting in committing nefarious deeds; CRM to improve the way they deal with their prospects; and mapping software to track Road Runners. And something to glue these all together. So, Mr Big Cheese, what are you going to do: buy a single one-stop-shop product that does everything, or assemble together a set of best-of-breed products?</p>
  2484. <div id="attachment_1112" class="wp-caption aligncenter" style="width: 490px"><a href=""><img class="size-full wp-image-1112" title="acme_full" src="" alt="The ACME Corporation Web Site" width="480" height="410" /></a><p class="wp-caption-text">The ACME Corporation Web Site</p></div>
  2485. <h2>What do the RFPs say customers want?</h2>
  2486. <p>The majority of the <a href="">CMS Vendor Selection RFP</a>s that I see demand feature ticking around search, analytics, SoCo, DAM and all the rest. They ask for it all. These RFPs are geared towards procuring a single product that does everything. Most also all assume that the Content Management System will also be the delivery layer and ask for many delivery layer features. A pure-play decoupled CMS wouldn&#8217;t stand a chance. If the scoring was done purely on the features lists, a portal would often beat a CMS. The vendor presentations tend to focus more on the features of the canned demonstration site they all have than on the CMS back end.</p>
  2487. <h2>What does the research say customers want?</h2>
  2488. <p>The research doesn&#8217;t agree completely with this. The recent <a href="">eConsultancy CMS Survey</a> showed that more customers want best-of-breed suppliers over a one-stop shop, especially for companies with more than 100 employees.</p>
  2489. <div>
  2490. <dl id="attachment_1111" style="width: 712px;">
  2491. <dt><a href=""><img title="BestofBreedorOnestop" src="" alt="When selecting a CMS vendor, which do you prefer? (from Squiz/eConsultancy report)" width="702" height="465" /></a></dt>
  2492. <dd>When selecting a CMS vendor, which do you prefer? (from Squiz/eConsultancy report)</dd>
  2493. </dl>
  2494. </div>
  2495. <h2>What is the strategy of the vendors?</h2>
  2496. <p>Well, they all seem to heading towards the one-stop-shop solution. Sure, they&#8217;ll release new features to their core product. But more and more, they seem to be differentiating by moving into other areas. CMS vendors, in particular, are packaging in social/collaboration software, search software, shopping baskets and payment modules, basic DAM and the kitchen sink. Everyone is producing their own Analytics and MVT software. For example, SiteCore recently announced their <a href="">Online Marketing Suite</a> and EPiServer called with their <a href="">Marketing Arena</a> . Seeing as most of these features really sit at the delivery layer, not the content management layer, the number of <a href="">pure decoupled CMS vendors is on the decline</a>. There is a <a href="">huge amount of M&amp;A activity</a> at the high end of the market as everyone tries to cover all the bases.</p>
  2497. <p>So, the strategy of the vendors seems to be on diversification. Gut feeling would imply that finding a niche, or focussing on improving the core CMS would be front of mind. Not so, they&#8217;re all playing &#8220;RFP feature ticking&#8221;. They all bang on about being &#8220;open&#8221; and supporting open standards, while at the same time singing about their proprietary, tight integration between their newly aquired products. For example, a typical conversation:</p>
  2498. <blockquote><p>Me: So, Mr Vendor X, why do you think we&#8217;d use your new Analytics|Search|Community product over the one we currently use?<br />
  2499. Vendor: Because our one has a &#8216;much deeper integration with our product&#8217; and &#8216;understands our product&#8217;  better.</p></blockquote>
  2500. <p>There are problems with this as I see it, some of which include:</p>
  2501. <ul>
  2502. <li>everyone is building monoliths</li>
  2503. <li>as parts of the system become obsolete, and it becomes harder to take advantage of unexpected future goodies</li>
  2504. <li>you really are at the mercy of a single vendor</li>
  2505. </ul>
  2506. <h2>What does the future hold?</h2>
  2507. <p>I would have expected the fact that standards are improving to mean that we&#8217;d have more focussed best-of-breed vendors that allow you to plug their product in to any CMS &#8211; the nice Lego-block style architecture diagram. However, currently it looks like we&#8217;re heading the other way, which really depresses me. We might even be buying the Google CMS Appliance before long.</p>
  2508. <p>If it continues at this rate, our friends at <a href="">CMS Watch</a> might need to consolidate all their lovely reports into the &#8220;Web In A Box&#8221; report quite soon &#8230;</p>
  2509. <img src="" height="1" width="1" alt=""/>]]></content:encoded>
  2510. <wfw:commentRss></wfw:commentRss>
  2511. <slash:comments>21</slash:comments>
  2512. </item>
  2513. </channel>
  2514. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda