<?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: &#8220;OPEN&#8221; really? &#8230; I mean Really?</title>
	<atom:link href="http://silona.org/open-really-i-mean-really/2009/11/02/feed/" rel="self" type="application/rss+xml" />
	<link>http://silona.org/open-really-i-mean-really/2009/11/02/</link>
	<description>silona's central identity</description>
	<lastBuildDate>Wed, 14 Jul 2010 03:06:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Silona</title>
		<link>http://silona.org/open-really-i-mean-really/2009/11/02/comment-page-1/#comment-78</link>
		<dc:creator>Silona</dc:creator>
		<pubDate>Mon, 02 Nov 2009 22:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://silona.org/open-really-i-mean-really/2009/11/02/#comment-78</guid>
		<description>I wasn&#039;t trying to say that citability is the same as &quot;open&quot; nor am I interested in yolking the terms together. I was using citability as a good example of how things should be done.  It is why I created a new term that wasn&#039;t in the dictionary. 

 Instead I was saying we need to be careful about how we formulate our terms as terms like &quot;open&quot; because can be used improperly as Adobe and Facebook are doing.

Though I do agree with you that the way to save &quot;open&quot; is to make sure it is bonded to another term.  Like OpenBanking can mean something specific as OpenSource does (though often disputed.)  And I need to get on it in regards to defining that.  Though I do have doubts about OpenBanking as a term because of how undefined the word &quot;open&quot; is...

Adobe is claiming (in Adverts that are DC specific so I&#039;m not surprised you haven&#039;t seen them) that they do &quot;Open Govt&quot; and that is what I am referring too.  http://blogs.adobe.com/adobeingovernment/2009/04/open_government_in_action.html  

It is not that they are wrong.  It is just not how a group of us in the Govt 2.0 word have been using the term.</description>
		<content:encoded><![CDATA[<p>I wasn&#8217;t trying to say that citability is the same as &#8220;open&#8221; nor am I interested in yolking the terms together. I was using citability as a good example of how things should be done.  It is why I created a new term that wasn&#8217;t in the dictionary. </p>
<p> Instead I was saying we need to be careful about how we formulate our terms as terms like &#8220;open&#8221; because can be used improperly as Adobe and Facebook are doing.</p>
<p>Though I do agree with you that the way to save &#8220;open&#8221; is to make sure it is bonded to another term.  Like OpenBanking can mean something specific as OpenSource does (though often disputed.)  And I need to get on it in regards to defining that.  Though I do have doubts about OpenBanking as a term because of how undefined the word &#8220;open&#8221; is&#8230;</p>
<p>Adobe is claiming (in Adverts that are DC specific so I&#8217;m not surprised you haven&#8217;t seen them) that they do &#8220;Open Govt&#8221; and that is what I am referring too.  <a href="http://blogs.adobe.com/adobeingovernment/2009/04/open_government_in_action.html" rel="nofollow">http://blogs.adobe.com/adobeingovernment/2009/04/open_government_in_action.html</a>  </p>
<p>It is not that they are wrong.  It is just not how a group of us in the Govt 2.0 word have been using the term.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jrep</title>
		<link>http://silona.org/open-really-i-mean-really/2009/11/02/comment-page-1/#comment-77</link>
		<dc:creator>jrep</dc:creator>
		<pubDate>Mon, 02 Nov 2009 20:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://silona.org/open-really-i-mean-really/2009/11/02/#comment-77</guid>
		<description>Are you getting a little ahead of yourself? &quot;Open&quot; is an adjective; it has meaning only when conjoined with some noun. To take the Adobe example, I&#039;ve seen them recently say &quot;open source&quot; about some of their code, and so far a I can tell, the &quot;source&quot; in question really is &quot;open.&quot; I haven&#039;t seen them claim that PDF itself is &quot;open,&quot; did I miss that? And I certainly haven&#039;t seen them claim that &quot;everyone who ever uses PDF anywhere is open with their data.&quot;

On the other hand, I&#039;ve also seen them, like many, using the phrase &quot;open API,&quot; lately, and I have rather more reservations about that. I think most people who use the phrase mean &quot;you can connect to my web API,&quot; and maybe even &quot;I&#039;ve documented it for you.&quot; They don&#039;t tend to mean &quot;you can help define the API&quot; (some do, but not all, and I don&#039;t think Adobe does, since we&#039;re using that example). As an open sourcerer, I&#039;d rather the &quot;open&quot; adjective be held to something in the &quot;you can contribute&quot; neighborhood, but I did also live through the 80&#039;s era of &quot;open standards,&quot; which were at best only slightly communitarian, and mostly just meant &quot;not IP-encumbered.&quot;

Now &quot;citability&quot; is somewhere in the same corner of the cosmos as &quot;open,&quot; but I think it would be a shame to yoke the two. Citability is actually a much stronger word, with a reasonably fair chance of making sense, all by itself, right out of the gate, without conjoined nouns or lengthy explanations. It&#039;s pretty clear that PDF is not presently &quot;citable&quot; (for example, because it&#039;s not internally addressable). That&#039;s worth some discussion, but trying to retrofit those notions to the &quot;open&quot; moniker seems counterproductive, but if we do it, it would still need that noun ... &quot;open reference points,&quot; or something like that.</description>
		<content:encoded><![CDATA[<p>Are you getting a little ahead of yourself? &#8220;Open&#8221; is an adjective; it has meaning only when conjoined with some noun. To take the Adobe example, I&#8217;ve seen them recently say &#8220;open source&#8221; about some of their code, and so far a I can tell, the &#8220;source&#8221; in question really is &#8220;open.&#8221; I haven&#8217;t seen them claim that PDF itself is &#8220;open,&#8221; did I miss that? And I certainly haven&#8217;t seen them claim that &#8220;everyone who ever uses PDF anywhere is open with their data.&#8221;</p>
<p>On the other hand, I&#8217;ve also seen them, like many, using the phrase &#8220;open API,&#8221; lately, and I have rather more reservations about that. I think most people who use the phrase mean &#8220;you can connect to my web API,&#8221; and maybe even &#8220;I&#8217;ve documented it for you.&#8221; They don&#8217;t tend to mean &#8220;you can help define the API&#8221; (some do, but not all, and I don&#8217;t think Adobe does, since we&#8217;re using that example). As an open sourcerer, I&#8217;d rather the &#8220;open&#8221; adjective be held to something in the &#8220;you can contribute&#8221; neighborhood, but I did also live through the 80&#8242;s era of &#8220;open standards,&#8221; which were at best only slightly communitarian, and mostly just meant &#8220;not IP-encumbered.&#8221;</p>
<p>Now &#8220;citability&#8221; is somewhere in the same corner of the cosmos as &#8220;open,&#8221; but I think it would be a shame to yoke the two. Citability is actually a much stronger word, with a reasonably fair chance of making sense, all by itself, right out of the gate, without conjoined nouns or lengthy explanations. It&#8217;s pretty clear that PDF is not presently &#8220;citable&#8221; (for example, because it&#8217;s not internally addressable). That&#8217;s worth some discussion, but trying to retrofit those notions to the &#8220;open&#8221; moniker seems counterproductive, but if we do it, it would still need that noun &#8230; &#8220;open reference points,&#8221; or something like that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
