<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:thr="http://purl.org/syndication/thread/1.0">
    <title>USL Technologies Blog</title>
    <link rel="self" type="application/atom+xml" href="//blog.usltechnologies.com/atom.xml" />
    <link rel="alternate" type="text/html" href="//blog.usltechnologies.com/" />
    <id>tag:typepad.com,2003:weblog-517091</id>
    <updated>2007-04-12T13:11:24+01:00</updated>
    
    <generator uri="http://www.typepad.com/">TypePad</generator>
<entry>
        <title>Webware</title>
        <link rel="alternate" type="text/html" href="//blog.usltechnologies.com/2007/04/webware.html" />
        <link rel="replies" type="text/html" href="//blog.usltechnologies.com/2007/04/webware.html" thr:count="1" thr:updated="2007-04-20T10:29:46+01:00" />
        <id>tag:typepad.com,2003:post-32808544</id>
        <published>2007-04-12T13:11:24+01:00</published>
        <updated>2007-04-12T13:11:24+01:00</updated>
        <summary>Phil Wainewright points to a good post by Paul McNamara about the fact that the term &quot;Software as a Service&quot; or Saas as it is commonly referred to, is simply a bad term for a new wave of technologies since...</summary>
        <author>
            <name>richardoc</name>
        </author>
        <category term="Web/Tech" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="//blog.usltechnologies.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://blogs.zdnet.com/SAAS/?p=307">Phil Wainewright</a> points to a good post by <a href="http://www.cogblog.com/cogblog/2007/03/saas_this_is_no.html">Paul McNamara</a> about the fact that the term &quot;Software as a Service&quot; or Saas as it is commonly referred to, is simply a bad term for a new wave of technologies since it dwells on the past by referring to the term <em>software.</em></p>

<p>Paul recommends the term <em>Webware</em> as a replacement.</p>

<p>I fully agree that a new description is needed, as most non-technical people simply don't get the whole Saas thing - there is too much of a blurred line between what was there a few years ago, and what is available now.</p>

<p>I like the term webware, but I have reservations about it - the first thing that sprung to my mind when I read it was similar sounding terms - Spyware, malware, etc. I get the feeling that end-users would think of the same terms and view the term webware in a negative light.</p>

<p>Hopefully I'm wrong though as its a nice term</p>

<p>USL - Providers of <a href="http://www.usltechnologies.com/partners.htm">webware for web-designers</a>!</p></div>
</content>



    </entry>
<entry>
        <title>5 reasons why EditBureau is software on demand</title>
        <link rel="alternate" type="text/html" href="//blog.usltechnologies.com/2006/10/5_reasons_why_e.html" />
        <link rel="replies" type="text/html" href="//blog.usltechnologies.com/2006/10/5_reasons_why_e.html" thr:count="1" thr:updated="2006-12-23T22:03:20+00:00" />
        <id>tag:typepad.com,2003:post-13672421</id>
        <published>2006-10-26T17:57:49+01:00</published>
        <updated>2006-10-26T17:57:49+01:00</updated>
        <summary>Why is EditBureau categorised as software on-demand, and what&#39;s that whole on-demand thing about anyway? 1. You don&#39;t install EditBureau - its a service. And I hear you say... &quot;But I don&#39;t install any web application - I just run...</summary>
        <author>
            <name>richardoc</name>
        </author>
        <category term="Web/Tech" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="//blog.usltechnologies.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>Why is EditBureau categorised as software on-demand, and what's that whole on-demand thing about anyway?<br /><strong><br />1. You don't install EditBureau - its a service.</strong></p>

<p>And I hear you say... &quot;But I don't install any web application - I just run it in my browser&quot; ...</p>

<p>...True, but with any web application, it has to run somewhere, on some server, usually your own server. Especially in relation to Content Managament Systems (CMS), which usually always must be installed on your website, in some shape or form, and you usually pay a consultant or provider to perform this installation.</p>

<p>EditBureau on the other hand, runs as a web service - we run it for you, but yet it allows you to manage your website, where-ever its hosted.</p>

<p><strong>2. But there must be some integration, or changes to my website required?</strong></p>

<p>Nope, nothing.</p>

<p>Just enter a few pieces of information on a <a href="http://www.usltechnologies.com/trial.htm">signup form</a>, and get a free username and password instantly by email. No delays.</p>

<p><strong>3. What about a setup fee, or high up-front cost?</strong></p>

<p>Nope, nothing there either, in fact all accounts come with a free 48 hour trial. </p>

<p><strong>4. So there must be some really high purchase fee, or annual subscription?</strong></p>

<p>No, you can opt to purchase a subscription for a relatively in-expensive annual
fee, that's not going to break the bank. 3-4 updates by a technical
person would usually cover the total cost for EditBureau for a year of
unlimited updates.</p>

<p><strong>5. So you must lock me in, or have some way of preventing me from leaving the service?</strong></p>

<p>No, we hate that sort of thing. If you don't like it, you can leave. We don't change your site in any way. So if you don't want to renew, you don't have to. <strong>No catches.</strong></p>

<p>So there, in 5 brief points, you can gain an insight into why EditBureau is Saas, and why it is true value for money.<strong></strong></p></div>
</content>



    </entry>
<entry>
        <title>Welcome</title>
        <link rel="alternate" type="text/html" href="//blog.usltechnologies.com/2006/09/welcome.html" />
        <link rel="replies" type="text/html" href="//blog.usltechnologies.com/2006/09/welcome.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-12869504</id>
        <published>2006-09-18T08:57:35+01:00</published>
        <updated>2006-09-18T08:57:35+01:00</updated>
        <summary>Welcome to the new USL Technologies blog!</summary>
        <author>
            <name>richardoc</name>
        </author>
        
        
<content type="xhtml" xml:lang="en-US" xml:base="//blog.usltechnologies.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>Welcome to the new USL Technologies blog!</p></div>
</content>



    </entry>
 
</feed>

<!-- ph=1 -->
