<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for POCKET</title>
	<link>http://pocket.jiscinvolve.org</link>
	<description>Project on Open Content Knowledge Exposition and Teaching</description>
	<pubDate>Mon, 01 Dec 2008 19:39:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.5</generator>

	<item>
		<title>Comment on POCKET materials: Interoperability issues by IAN iBBOTson</title>
		<link>http://pocket.jiscinvolve.org/2008/10/30/pocket-materials-interoperability-issues/#comment-1828</link>
		<dc:creator>IAN iBBOTson</dc:creator>
		<pubDate>Tue, 25 Nov 2008 15:58:30 +0000</pubDate>
		<guid>http://pocket.jiscinvolve.org/2008/10/30/pocket-materials-interoperability-issues/#comment-1828</guid>
		<description>Hiya... Wilbert suggested that it might be worth us catching up at #cetis08 for a chat about how transcoder might help in this regard? If you see me around, please holler or get wilbert/scott to introduce us?

Cheers,
Ian.</description>
		<content:encoded><![CDATA[<p>Hiya&#8230; Wilbert suggested that it might be worth us catching up at #cetis08 for a chat about how transcoder might help in this regard? If you see me around, please holler or get wilbert/scott to introduce us?</p>
<p>Cheers,<br />
Ian.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on POCKET materials: Interoperability issues by Wilbert</title>
		<link>http://pocket.jiscinvolve.org/2008/10/30/pocket-materials-interoperability-issues/#comment-1658</link>
		<dc:creator>Wilbert</dc:creator>
		<pubDate>Tue, 18 Nov 2008 23:31:19 +0000</pubDate>
		<guid>http://pocket.jiscinvolve.org/2008/10/30/pocket-materials-interoperability-issues/#comment-1658</guid>
		<description>Hello there,

Sorry that you have found content interoperability so poor with your VLE. As the existence of the open standards content player building block indicates, it wasn't really designed to take standard content as is, unfortunately. 

Short of installing that building block, the one and only thing that might be worth trying is to convert the IMS content packages to SCORM 1.2 using the CETIS transcoder. I wouldn't hold my breath, though.

We would like to develop the transcoder in such a way that it can also convert standard packages to a format BB will understand, which would save other people the bother you went through. In the mean time, perhaps it's easiest to just link to the unit in the OpenLearn site...</description>
		<content:encoded><![CDATA[<p>Hello there,</p>
<p>Sorry that you have found content interoperability so poor with your VLE. As the existence of the open standards content player building block indicates, it wasn&#8217;t really designed to take standard content as is, unfortunately. </p>
<p>Short of installing that building block, the one and only thing that might be worth trying is to convert the IMS content packages to SCORM 1.2 using the CETIS transcoder. I wouldn&#8217;t hold my breath, though.</p>
<p>We would like to develop the transcoder in such a way that it can also convert standard packages to a format BB will understand, which would save other people the bother you went through. In the mean time, perhaps it&#8217;s easiest to just link to the unit in the OpenLearn site&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RSP: Repository Services Day 23 April 2008 by Corinne</title>
		<link>http://pocket.jiscinvolve.org/2008/04/30/rsp-repository-services-day-23-april-2008/#comment-947</link>
		<dc:creator>Corinne</dc:creator>
		<pubDate>Mon, 27 Oct 2008 14:17:36 +0000</pubDate>
		<guid>http://pocket.jiscinvolve.org/2008/04/30/rsp-repository-services-day-23-april-2008/#comment-947</guid>
		<description>You write very well.</description>
		<content:encoded><![CDATA[<p>You write very well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on OSS Watch Workshop 20 October 2008 by Ross Gardler</title>
		<link>http://pocket.jiscinvolve.org/2008/10/22/oss-watch-workshop-20-october-2008/#comment-868</link>
		<dc:creator>Ross Gardler</dc:creator>
		<pubDate>Wed, 22 Oct 2008 19:51:19 +0000</pubDate>
		<guid>http://pocket.jiscinvolve.org/2008/10/22/oss-watch-workshop-20-october-2008/#comment-868</guid>
		<description>Thanks for your report from the OSS Watch workshop - such feedback is always useful for us in planning future events.

I'd like to make a couple of observations:

You say: "The JISC is flexibility but at the end of the project the original objectives need to be met." However, in the welcome from Matthew Dovey (JISC Programme Director)  it was stated that the JISC are happy to consider changing objectives over the course of a project if this become be necessary. Don't be afraid of talking to your programme managers if you feel a change is needed.

Secondly, you say that the second session fed back saying "Building a community means that you can’t control it". Actually, what was said was that if you build a community you may *choose* not to control it. Gianugo made this point during his presentation when he said (to paraphrase) "you will only loose control when you are no longer interested and other members of the community have more energy/interest than you". With a suitable governance model in place there is no reason why you should ever lost control, unless you lose interest.

For more on governance models see http://wiki.oss-watch.ac.uk/GovernanceModel</description>
		<content:encoded><![CDATA[<p>Thanks for your report from the OSS Watch workshop - such feedback is always useful for us in planning future events.</p>
<p>I&#8217;d like to make a couple of observations:</p>
<p>You say: &#8220;The JISC is flexibility but at the end of the project the original objectives need to be met.&#8221; However, in the welcome from Matthew Dovey (JISC Programme Director)  it was stated that the JISC are happy to consider changing objectives over the course of a project if this become be necessary. Don&#8217;t be afraid of talking to your programme managers if you feel a change is needed.</p>
<p>Secondly, you say that the second session fed back saying &#8220;Building a community means that you can’t control it&#8221;. Actually, what was said was that if you build a community you may *choose* not to control it. Gianugo made this point during his presentation when he said (to paraphrase) &#8220;you will only loose control when you are no longer interested and other members of the community have more energy/interest than you&#8221;. With a suitable governance model in place there is no reason why you should ever lost control, unless you lose interest.</p>
<p>For more on governance models see <a href="http://wiki.oss-watch.ac.uk/GovernanceModel" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/wiki.oss-watch.ac.uk');">http://wiki.oss-watch.ac.uk/GovernanceModel</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
