<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Paul Browning on Ariadne</title>
    <link>http://www.ariadne.ac.uk/authors/paul-browning/</link>
    <description>Recent content in Paul Browning on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 29 Apr 2004 23:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/authors/paul-browning/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Through the Web Authoring Tools</title>
      <link>http://www.ariadne.ac.uk/issue/39/browning/</link>
      <pubDate>Thu, 29 Apr 2004 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/39/browning/</guid>
      <description>The Web is over ten years old but it has yet to realise the vision of its founder - &#39;.... it should be possible for grandma to take a photo of grandchildren and put it on the web immediately and without fuss ....&#39;[1]. The Web, for most of its users, remains a read-only medium.
The &#39;Universal Canvas&#39; is a term introduced by Microsoft; two definitions are [2]:
It builds upon XML schema to transform the Internet from a read-only environment into a read/write platform, enabling users to interactively create, browse, edit, annotate and analyze informationA surface on which we view, but also create and edit, words and tables and charts and picturesCentral to the concept of the Universal Canvas is the idea of the write-enabled or &#39;Two-way-Web&#39; [3].</description>
    </item>
    
    <item>
      <title>Six MLEs: More Similar Than Different</title>
      <link>http://www.ariadne.ac.uk/issue/36/browning/</link>
      <pubDate>Tue, 29 Jul 2003 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/36/browning/</guid>
      <description>The JISC-funded programme &amp;lsquo;Building Managed Learning Environments (MLEs) in HE&amp;rsquo; [1] was of three years&amp;rsquo; duration and concluded in July 2003. The aim of the programme was to explore developments that test, evaluate, and prove (or in some circumstances disprove) the generic deployment of technology in support of improved learning. The programme has developed good practice and shared ideas and experiences across FE and HE sectors. The specific objectives were to:</description>
    </item>
    
    <item>
      <title>Content Management Systems: Who Needs Them?</title>
      <link>http://www.ariadne.ac.uk/issue/30/techwatch/</link>
      <pubDate>Fri, 25 Jan 2002 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/30/techwatch/</guid>
      <description>Content management? That’s what librarians do, right? But we’ve already got a library management system (LMS) – why should we consider a content management system (CMS)?
The second initial is perhaps misleading – “manipulation” rather than “management” might better summarise the goals of a CMS. Content creation and content re-purposing are fundamental aspects which tend to lie outside the current LMS domain.
Actually, from the point of view of workflow (and to lesser extent content re-purposing), the CMS and LMS have much in common.</description>
    </item>
    
    <item>
      <title>ZOPE: Swiss Army Knife for the Web?</title>
      <link>http://www.ariadne.ac.uk/issue/25/zope/</link>
      <pubDate>Sat, 23 Sep 2000 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/25/zope/</guid>
      <description>MotivationI would be surprised if most people don&amp;rsquo;t feel a sense of achievement when they author their first Web page. It&amp;rsquo;s the first thing you ever made which potentially the rest of the world can see. Others learn about your new skill and before you know it you&amp;rsquo;ve become the departmental webperson and are buried in an avalanche of other people&amp;rsquo;s content to &amp;ldquo;put on the Web&amp;rdquo;.
The chore of document conversion and the burden of information maintenance quickly dispel the euphoria of your first experience of authoring for the Web.</description>
    </item>
    
  </channel>
</rss>