<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why we went with the .WS TLD</title>
	<atom:link href="/blog/2012/08/why-we-went-with-the-ws-tld/feed/" rel="self" type="application/rss+xml" />
	<link>https://vesica.ws/blog/2012/08/why-we-went-with-the-ws-tld/</link>
	<description>- Taking museum and art collections to the cloud</description>
	<lastBuildDate>Sun, 19 May 2013 12:16:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Sree</title>
		<link>https://vesica.ws/blog/2012/08/why-we-went-with-the-ws-tld/comment-page-1/#comment-1478</link>
		<dc:creator>Sree</dc:creator>
		<pubDate>Sun, 19 May 2013 12:16:00 +0000</pubDate>
		<guid isPermaLink="false">https://vesica.ws/blog/?p=499#comment-1478</guid>
		<description>Currently .ws is preferable for Pro &amp; Experts as because its the only domain TLD, which belongs to less limitation than others. So is .ws you are safe enough to get niche web threats and limitation. We can say .ws has near to ZERO Limitation of use comparing with others (and even .com/.net)</description>
		<content:encoded><![CDATA[<p>Currently .ws is preferable for Pro &amp; Experts as because its the only domain TLD, which belongs to less limitation than others. So is .ws you are safe enough to get niche web threats and limitation. We can say .ws has near to ZERO Limitation of use comparing with others (and even .com/.net)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chatterchit</title>
		<link>https://vesica.ws/blog/2012/08/why-we-went-with-the-ws-tld/comment-page-1/#comment-1454</link>
		<dc:creator>Chatterchit</dc:creator>
		<pubDate>Wed, 05 Sep 2012 13:24:00 +0000</pubDate>
		<guid isPermaLink="false">https://vesica.ws/blog/?p=499#comment-1454</guid>
		<description>Thank you. I appreciate your engagement.</description>
		<content:encoded><![CDATA[<p>Thank you. I appreciate your engagement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asif N</title>
		<link>https://vesica.ws/blog/2012/08/why-we-went-with-the-ws-tld/comment-page-1/#comment-1453</link>
		<dc:creator>Asif N</dc:creator>
		<pubDate>Tue, 04 Sep 2012 12:50:00 +0000</pubDate>
		<guid isPermaLink="false">https://vesica.ws/blog/?p=499#comment-1453</guid>
		<description>Fair enough - I said official version, not justification. The information about TLDs qualifies why we chose .ws. The &quot;Hegelian&quot; opening was meant to set context for the information provided because a general explanation is not really necessary (unless someone asks). And now that you have, let me restate why we chose .ws.

1. .COM was not available
2. .WS is a widely accepted as a gTLD domain for both marketing as well as technical SEO purposes (this is where some of the irrelevant ramble may help) 
3. It does not restrict us to any particular platforms (like .mobi does, for instance)
4. Unlike any other ccTLDs or sTLDs that are marketed or accepted by major search engines as gTLDs, .WS is and should be more stable because of the affiliate with Global Domains International

Thank you for your feedback - I will add the information to make the article too.</description>
		<content:encoded><![CDATA[<p>Fair enough &#8211; I said official version, not justification. The information about TLDs qualifies why we chose .ws. The &#8220;Hegelian&#8221; opening was meant to set context for the information provided because a general explanation is not really necessary (unless someone asks). And now that you have, let me restate why we chose .ws.</p>
<p>1. .COM was not available<br />
2. .WS is a widely accepted as a gTLD domain for both marketing as well as technical SEO purposes (this is where some of the irrelevant ramble may help)<br />
3. It does not restrict us to any particular platforms (like .mobi does, for instance)<br />
4. Unlike any other ccTLDs or sTLDs that are marketed or accepted by major search engines as gTLDs, .WS is and should be more stable because of the affiliate with Global Domains International</p>
<p>Thank you for your feedback &#8211; I will add the information to make the article too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chatterchit</title>
		<link>https://vesica.ws/blog/2012/08/why-we-went-with-the-ws-tld/comment-page-1/#comment-1452</link>
		<dc:creator>Chatterchit</dc:creator>
		<pubDate>Tue, 04 Sep 2012 11:32:00 +0000</pubDate>
		<guid isPermaLink="false">https://vesica.ws/blog/?p=499#comment-1452</guid>
		<description>Thank you for your reply.

Actually, it was you yourself who framed this piece as a justification, by beginning what otherwise is (indeed) an information piece with a Hegelian-type dialectical opening structure [your conversation with a friend &quot;....who really could not understand the reason we run Vesica on the .ws TLD ... he was adamant that we can and only should use .COM. This has, of course, come up in the past ...&quot;]. This dialectical device inherently means your &quot;antithesis&quot; is framed as a justification.

But justification or information, that&#039;s neither here nor there. The point is most of the piece is simply information  about TLDs (quite right there); and yet the piece is titled &quot;Why we went with the .WS TLD&quot;  so your readers would therefore have a rightful expectation of coming away with an understanding about why you chose it. (I don&#039;t, I&#039;m afraid, and I&#039;ve read it a couple of times to see if I missed something.)</description>
		<content:encoded><![CDATA[<p>Thank you for your reply.</p>
<p>Actually, it was you yourself who framed this piece as a justification, by beginning what otherwise is (indeed) an information piece with a Hegelian-type dialectical opening structure [your conversation with a friend "....who really could not understand the reason we run Vesica on the .ws TLD ... he was adamant that we can and only should use .COM. This has, of course, come up in the past ..."]. This dialectical device inherently means your &#8220;antithesis&#8221; is framed as a justification.</p>
<p>But justification or information, that&#8217;s neither here nor there. The point is most of the piece is simply information  about TLDs (quite right there); and yet the piece is titled &#8220;Why we went with the .WS TLD&#8221;  so your readers would therefore have a rightful expectation of coming away with an understanding about why you chose it. (I don&#8217;t, I&#8217;m afraid, and I&#8217;ve read it a couple of times to see if I missed something.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asif N</title>
		<link>https://vesica.ws/blog/2012/08/why-we-went-with-the-ws-tld/comment-page-1/#comment-1451</link>
		<dc:creator>Asif N</dc:creator>
		<pubDate>Sun, 02 Sep 2012 00:26:00 +0000</pubDate>
		<guid isPermaLink="false">https://vesica.ws/blog/?p=499#comment-1451</guid>
		<description>I think you misunderstood. None of this is a justification - it&#039;s all just information. We don&#039;t have to justify anything.</description>
		<content:encoded><![CDATA[<p>I think you misunderstood. None of this is a justification &#8211; it&#8217;s all just information. We don&#8217;t have to justify anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chatterchit</title>
		<link>https://vesica.ws/blog/2012/08/why-we-went-with-the-ws-tld/comment-page-1/#comment-1450</link>
		<dc:creator>Chatterchit</dc:creator>
		<pubDate>Sat, 01 Sep 2012 12:10:00 +0000</pubDate>
		<guid isPermaLink="false">https://vesica.ws/blog/?p=499#comment-1450</guid>
		<description>After a mildly irrelevant ramble about TLDs, that&#039;s a bit of a feeble justification at the end of the piece for why you chose .ws.</description>
		<content:encoded><![CDATA[<p>After a mildly irrelevant ramble about TLDs, that&#8217;s a bit of a feeble justification at the end of the piece for why you chose .ws.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
