<?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: On Content Management, Standards &amp; Practices.</title>
	<atom:link href="http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/</link>
	<description>ZOMGWTFHAI</description>
	<lastBuildDate>Tue, 15 Jun 2010 00:36:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tracy Welles</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8365</link>
		<dc:creator>Tracy Welles</dc:creator>
		<pubDate>Fri, 21 Aug 2009 06:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8365</guid>
		<description>Good write up Adam. I couldn&#039;t agree more.</description>
		<content:encoded><![CDATA[<p>Good write up Adam. I couldn&#8217;t agree more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Innis</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8336</link>
		<dc:creator>Dale Innis</dc:creator>
		<pubDate>Fri, 07 Aug 2009 20:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8336</guid>
		<description>Sadly the Lab has a bit of a history of making a proposal, asking for feedback, saying very little in the face of huge Resident outcry, and then implementing the original proposal with a few small tweaks, without addressing the biggest concerns that people had (see Zindra, for instance).  We can hope that in this case they&#039;re actually a bit less wedded to this particular proposal, and open to major suggestions.  Hope springs eternal.  :)</description>
		<content:encoded><![CDATA[<p>Sadly the Lab has a bit of a history of making a proposal, asking for feedback, saying very little in the face of huge Resident outcry, and then implementing the original proposal with a few small tweaks, without addressing the biggest concerns that people had (see Zindra, for instance).  We can hope that in this case they&#8217;re actually a bit less wedded to this particular proposal, and open to major suggestions.  Hope springs eternal.  <img src='http://www.adamfrisby.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Llewellyn</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8335</link>
		<dc:creator>Marcus Llewellyn</dc:creator>
		<pubDate>Fri, 07 Aug 2009 19:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8335</guid>
		<description>As a content creator in both Second Life and OSgrid, I wasn&#039;t particularly thrilled about this Content Roadmap. Their brainstorming meetings must be mired in trivia and confusion.

I suspect that tagging content with the grid on which it was created is an attempt to address intergrid licensing. But it&#039;s a lame one, and your suggestion of an explicit export permission is an excellent one. Linden Lab&#039;s solution requires eyeballs and manual work on behalf of grid/simulator operators. An export permission can simply be implemented in software. It also effectively nulls the debate about export checks on full permission objects versus creator owned ones.

As for the inventory thing, I didn&#039;t get the impression that Linden Labs intends to bar mass inventory export. If they do, they&#039;re being damn silly. What they say on the blog post is, &quot;most of us are not the intellectual property owners of **all** [emphasis mine] content in our inventory,&quot; meaning that exporters simply ought to check permissions in an inventory export. Why they could not just say this is beyond me; it seems blindingly obvious.

I do *like* the idea of my content having my user name preserved as the creator. Although I routinely give stuff away, the one and only thing I ever request is an attribution as the originator of the work. Very BSD/MIT license-like.</description>
		<content:encoded><![CDATA[<p>As a content creator in both Second Life and OSgrid, I wasn&#8217;t particularly thrilled about this Content Roadmap. Their brainstorming meetings must be mired in trivia and confusion.</p>
<p>I suspect that tagging content with the grid on which it was created is an attempt to address intergrid licensing. But it&#8217;s a lame one, and your suggestion of an explicit export permission is an excellent one. Linden Lab&#8217;s solution requires eyeballs and manual work on behalf of grid/simulator operators. An export permission can simply be implemented in software. It also effectively nulls the debate about export checks on full permission objects versus creator owned ones.</p>
<p>As for the inventory thing, I didn&#8217;t get the impression that Linden Labs intends to bar mass inventory export. If they do, they&#8217;re being damn silly. What they say on the blog post is, &#8220;most of us are not the intellectual property owners of **all** [emphasis mine] content in our inventory,&#8221; meaning that exporters simply ought to check permissions in an inventory export. Why they could not just say this is beyond me; it seems blindingly obvious.</p>
<p>I do *like* the idea of my content having my user name preserved as the creator. Although I routinely give stuff away, the one and only thing I ever request is an attribution as the originator of the work. Very BSD/MIT license-like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Frisby</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8332</link>
		<dc:creator>Adam Frisby</dc:creator>
		<pubDate>Thu, 06 Aug 2009 23:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8332</guid>
		<description>@Tateru: I partly suspected it was more proposal than actual change, but the way it was written, and the fact that I know Linden has asked the Meerkat developers to implement those three already, seems to imply it is closer to policy than proposal.

@Ari: No, this isn&#039;t old policy - those three standards/suggestions are very very new. Second Inventory was built using its current IP mechanism because LL wouldnt provide any clarification - ultimately, I think they did a good job.

As far as copyright infringement goes, yes - I agree I think it will continue; but I do think there are practical ways of stopping it - just many will be unconscionable to the majority of smaller content creators.</description>
		<content:encoded><![CDATA[<p>@Tateru: I partly suspected it was more proposal than actual change, but the way it was written, and the fact that I know Linden has asked the Meerkat developers to implement those three already, seems to imply it is closer to policy than proposal.</p>
<p>@Ari: No, this isn&#8217;t old policy &#8211; those three standards/suggestions are very very new. Second Inventory was built using its current IP mechanism because LL wouldnt provide any clarification &#8211; ultimately, I think they did a good job.</p>
<p>As far as copyright infringement goes, yes &#8211; I agree I think it will continue; but I do think there are practical ways of stopping it &#8211; just many will be unconscionable to the majority of smaller content creators.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ari Blackthorne</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8331</link>
		<dc:creator>Ari Blackthorne</dc:creator>
		<pubDate>Thu, 06 Aug 2009 20:31:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8331</guid>
		<description>Huh.

It&#039;s not a &quot;change&quot; in Linden Lab&#039;s &quot;content management policy&quot;. It&#039;s a reiteration and clarification. Linden Lab has been saying these exact same things since I can remember, and I can remember back as far as Spring, 2006.

It is enough to prevent pirates plagiarizing creators&#039; work on any grid? No. Is it enough as much as a can be reasonably expected? I think so.

Linden Lab has control of Linden Lab assets and nothing else. All tools and methods employed by Linden Lab can and will only work on Linden lab grids. The simple fact of the matter is that plagiarism (sorry, I cannot &#039;swallow&#039; the &quot;theft&quot; word with regard to digital works) is going to happen no matter what because when someone wants to plagiarize, they will find a way to do it.

However, at least Linden Lab is making a good-faith effort to curb this as much as possible; which does two things: first, it help keep honest people honest and second is that it shows Linden Lab is serious about this stuff; within the confines of what they are able.</description>
		<content:encoded><![CDATA[<p>Huh.</p>
<p>It&#8217;s not a &#8220;change&#8221; in Linden Lab&#8217;s &#8220;content management policy&#8221;. It&#8217;s a reiteration and clarification. Linden Lab has been saying these exact same things since I can remember, and I can remember back as far as Spring, 2006.</p>
<p>It is enough to prevent pirates plagiarizing creators&#8217; work on any grid? No. Is it enough as much as a can be reasonably expected? I think so.</p>
<p>Linden Lab has control of Linden Lab assets and nothing else. All tools and methods employed by Linden Lab can and will only work on Linden lab grids. The simple fact of the matter is that plagiarism (sorry, I cannot &#8217;swallow&#8217; the &#8220;theft&#8221; word with regard to digital works) is going to happen no matter what because when someone wants to plagiarize, they will find a way to do it.</p>
<p>However, at least Linden Lab is making a good-faith effort to curb this as much as possible; which does two things: first, it help keep honest people honest and second is that it shows Linden Lab is serious about this stuff; within the confines of what they are able.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8324</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Wed, 05 Aug 2009 17:16:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8324</guid>
		<description>Maybe an interoperability standards group needs to be formed so that a reasonable list of guidelines can be created that are acceptable to all parties. 
That way platforms can be members of say the &#039;Content Interoperability Organization&#039; which allows:
a) legal copyright attribution fields(always visible, defaulted to date created on that platform and username of that user on that platform but changeable
b) copy/mod/transfer/export flags for programmable checking (others if needed)

And any others the group decided were necessary to make it less a minefield for platform operators.</description>
		<content:encoded><![CDATA[<p>Maybe an interoperability standards group needs to be formed so that a reasonable list of guidelines can be created that are acceptable to all parties.<br />
That way platforms can be members of say the &#8216;Content Interoperability Organization&#8217; which allows:<br />
a) legal copyright attribution fields(always visible, defaulted to date created on that platform and username of that user on that platform but changeable<br />
b) copy/mod/transfer/export flags for programmable checking (others if needed)</p>
<p>And any others the group decided were necessary to make it less a minefield for platform operators.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tateru Nino</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8323</link>
		<dc:creator>Tateru Nino</dc:creator>
		<pubDate>Wed, 05 Aug 2009 14:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8323</guid>
		<description>See also: http://www.massively.com/2009/08/05/a-second-life-roadmap-content-management-intellectual-property/</description>
		<content:encoded><![CDATA[<p>See also: <a href="http://www.massively.com/2009/08/05/a-second-life-roadmap-content-management-intellectual-property/" rel="nofollow">http://www.massively.com/2009/08/05/a-second-life-roadmap-content-management-intellectual-property/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tateru Nino</title>
		<link>http://www.adamfrisby.com/blog/2009/08/on-content-management-standards-practices/comment-page-1/#comment-8322</link>
		<dc:creator>Tateru Nino</dc:creator>
		<pubDate>Wed, 05 Aug 2009 14:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=391#comment-8322</guid>
		<description>If you read closely, those three items are suggestions. They&#039;re exhorting someone else to come up with a code &quot;Sort of like [these three things]&quot; and also to implement/gather buy-in for it.

They&#039;re not actually mandating any rules there at all. Just a warning that they&#039;ll spank people if things get out of hand somehow.</description>
		<content:encoded><![CDATA[<p>If you read closely, those three items are suggestions. They&#8217;re exhorting someone else to come up with a code &#8220;Sort of like [these three things]&#8221; and also to implement/gather buy-in for it.</p>
<p>They&#8217;re not actually mandating any rules there at all. Just a warning that they&#8217;ll spank people if things get out of hand somehow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
