<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/sla">
<title>Public marks with tag sla</title>
<description>Public marks with tag sla</description>
<link>http://blogmarks.net/marks/tag/sla</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/JMF/mark/1057477618"/>
<rdf:li resource="http://blogmarks.net/api/user/bl5189e0/mark/2520409"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/2658152"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/2658153"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/2658154"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/2658155"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/2658157"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/2658160"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/JMF/mark/1057477618">
<title>Amazon.comAmazon S3 / Amazon S3 SLA</title>
<link>http://www.amazon.com/gp/browse.html?node=379654011</link>
<description></description>
<dc:date>2007-10-09T15:17:05Z</dc:date>
<dc:author>JMF</dc:author>
<dc:subject>amazon, s3, sla</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.amazon.com/gp/browse.html?node=379654011"><img border="0" src="http://blogmarks.net/screenshots/2007/10/09/3f89cbe440a0d0c6b20a472103526517.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.amazon.com/gp/browse.html?node=379654011">Amazon.comAmazon S3 / Amazon S3 SLA</a></h4>
 
by <a href="http://blogmarks.net/user/JMF">JMF</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/amazon">amazon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/s3">s3</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057477618">Copy</a> | 
<a href="http://blogmarks.net/link/2470816">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/bl5189e0/mark/2520409">
<title>99 99 Webhosting Sla Uptime</title>
<link>http://www.critical-hosting.info/99-99-webhosting-sla-uptime/</link>
<description></description>
<dc:date>2007-03-25T20:52:30Z</dc:date>
<dc:author>bl5189e0</dc:author>
<dc:subject>99, webhosting, sla, uptime, critical, hosting</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.critical-hosting.info/99-99-webhosting-sla-uptime/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.critical-hosting.info/99-99-webhosting-sla-uptime/">99 99 Webhosting Sla Uptime</a></h4>
 
by <a href="http://blogmarks.net/user/bl5189e0">bl5189e0</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/99">99</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webhosting">webhosting</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/uptime">uptime</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/critical">critical</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hosting">hosting</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2520409">Copy</a> | 
<a href="http://blogmarks.net/link/2069151">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/2658152">
<title>Getting ready for SLAs</title>
<link>http://www.networkworld.com/newsletters/nsm/2002/01366109.html</link>
<description>
      While it is true that organizations should try to establish service-level agreements as soon as possible, it is a serious mistake to begin the process before your organization is ready. If you are considering negotiating SLAs, you need to make sure you are prepared.

Before you can negotiate an SLA, it is essential that there be a solid management infrastructure in place. That means all of the management functions are there, in some form, for each of the resources used to deliver the service.
    </description>
<dc:date>2006-10-15T14:14:51Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>service, méthodologie, sla</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.networkworld.com/newsletters/nsm/2002/01366109.html"><img border="0" src="http://blogmarks.net/screenshots/2006/10/15/dac52abc83a1de53baa8fcb9779d4f42.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.networkworld.com/newsletters/nsm/2002/01366109.html">Getting ready for SLAs</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">
      While it is true that organizations should try to establish service-level agreements as soon as possible, it is a serious mistake to begin the process before your organization is ready. If you are considering negotiating SLAs, you need to make sure you are prepared.

Before you can negotiate an SLA, it is essential that there be a solid management infrastructure in place. That means all of the management functions are there, in some form, for each of the resources used to deliver the service.
    </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/service">service</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/m%25C3%25A9thodologie">méthodologie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2658152">Copy</a> | 
<a href="http://blogmarks.net/link/1181343">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/2658153">
<title>SLM is not SLA</title>
<link>http://www.networkworld.com/weblogs/management/002516.html</link>
<description>
      The acronyms SLM (service-level management) and SLA (service-level agreement) are not synonymous. SLM, among accomplishing other goals, can help enterprise network managers automatically track how well service providers deliver on their SLAs. And SLAs, really just written contracts, serve as an insurance policy for companies getting Internet, network or application services from an external service provider or carrier.
    </description>
<dc:date>2006-10-15T14:12:44Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>doc, service, sla</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.networkworld.com/weblogs/management/002516.html"><img border="0" src="http://blogmarks.net/screenshots/2006/10/15/9f6c846a596f33894bdb5b5bffbc0b06.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.networkworld.com/weblogs/management/002516.html">SLM is not SLA</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">
      The acronyms SLM (service-level management) and SLA (service-level agreement) are not synonymous. SLM, among accomplishing other goals, can help enterprise network managers automatically track how well service providers deliver on their SLAs. And SLAs, really just written contracts, serve as an insurance policy for companies getting Internet, network or application services from an external service provider or carrier.
    </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/doc">doc</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/service">service</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2658153">Copy</a> | 
<a href="http://blogmarks.net/link/1181341">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/2658154">
<title>Template: Internal Service Level Agreement (Short-Form)</title>
<link>http://www.nextslm.org/internalsla_short.html</link>
<description>
      This template provides a general description of the intent of the service level agreement (SLA) as well as the owners, approval and review process, and a definition of the terms used in the document. Customize this template by filling in all italicized text.
    </description>
<dc:date>2006-10-15T14:57:27Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>service, doc, sla</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.nextslm.org/internalsla_short.html"><img border="0" src="http://blogmarks.net/screenshots/2006/10/15/957e1cfe18c782af027081944707e13d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.nextslm.org/internalsla_short.html">Template: Internal Service Level Agreement (Short-Form)</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">
      This template provides a general description of the intent of the service level agreement (SLA) as well as the owners, approval and review process, and a definition of the terms used in the document. Customize this template by filling in all italicized text.
    </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/service">service</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/doc">doc</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2658154">Copy</a> | 
<a href="http://blogmarks.net/link/1181322">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/2658155">
<title>Template: Internal Service Level Agreement</title>
<link>http://www.nextslm.org/internalsla.html</link>
<description>
      This template provides a general description of the intent of the service level agreement(SLA) as well as the owners, approval and review process, and a definition of the terms used in the document. Customize this template by filling in all italicized text.
    </description>
<dc:date>2006-10-15T14:58:09Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>doc, service, sla</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.nextslm.org/internalsla.html"><img border="0" src="http://blogmarks.net/screenshots/2006/10/15/ecb638ad058ac521f471d97210b754a2.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.nextslm.org/internalsla.html">Template: Internal Service Level Agreement</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">
      This template provides a general description of the intent of the service level agreement(SLA) as well as the owners, approval and review process, and a definition of the terms used in the document. Customize this template by filling in all italicized text.
    </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/doc">doc</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/service">service</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2658155">Copy</a> | 
<a href="http://blogmarks.net/link/1181321">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/2658157">
<title>Le Service Level Agreement ou SLA</title>
<link>http://www.droit-technologie.org/1_2.asp?actu_id=844</link>
<description>
      Le Service Level Agreement ou SLA est une expression anglaise qui peut être traduite par « Accord de Niveau de Service » ou par « Engagement de Service », ou encore plus simplement « Convention de Service ».

Le SLA est le contrat ou la partie du contrat spécifiant l’ensemble des niveaux de services à fournir par le prestataire informatique au(x) client(s). Il s’agit d’un engagement formel et contraignant, établi entre un prestataire et son (ses) client(s).
    </description>
<dc:date>2006-10-15T02:02:17Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>méthodologie, doc, sla, service</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.droit-technologie.org/1_2.asp?actu_id=844"><img border="0" src="http://blogmarks.net/screenshots/2006/10/16/d422929a1d5703886629695b451e4859.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.droit-technologie.org/1_2.asp?actu_id=844">Le Service Level Agreement ou SLA</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">
      Le Service Level Agreement ou SLA est une expression anglaise qui peut être traduite par « Accord de Niveau de Service » ou par « Engagement de Service », ou encore plus simplement « Convention de Service ».

Le SLA est le contrat ou la partie du contrat spécifiant l’ensemble des niveaux de services à fournir par le prestataire informatique au(x) client(s). Il s’agit d’un engagement formel et contraignant, établi entre un prestataire et son (ses) client(s).
    </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/m%25C3%25A9thodologie">méthodologie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/doc">doc</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/service">service</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2658157">Copy</a> | 
<a href="http://blogmarks.net/link/1180798">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/2658160">
<title>Service Level Agreement Zone</title>
<link>http://www.sla-zone.co.uk/</link>
<description>
      A service level agreement is a document which defines the relationship between two parties: the provider and the recipient.

This is clearly an extremely important item of documentation for both parties. If used properly it should:

    * Identify and define the customer’s needs
    * Provide a framework for understanding
    * Simplify complex issues
    * Reduce areas of conflict
    * Encourage dialog in the event of disputes
    * Eliminate unrealistic expectations
...
    </description>
<dc:date>2006-10-15T00:59:35Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>sla, hosting, doc</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.sla-zone.co.uk/"><img border="0" src="http://blogmarks.net/screenshots/2006/10/16/6139a1d30e3b85cba88f6fd4384412b1.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.sla-zone.co.uk/">Service Level Agreement Zone</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">
      A service level agreement is a document which defines the relationship between two parties: the provider and the recipient.

This is clearly an extremely important item of documentation for both parties. If used properly it should:

    * Identify and define the customer’s needs
    * Provide a framework for understanding
    * Simplify complex issues
    * Reduce areas of conflict
    * Encourage dialog in the event of disputes
    * Eliminate unrealistic expectations
...
    </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sla">sla</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hosting">hosting</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/doc">doc</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2658160">Copy</a> | 
<a href="http://blogmarks.net/link/1180786">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>