<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>marcellus &#187; api</title>
	<atom:link href="http://blog.marcellus.tv/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.marcellus.tv</link>
	<description>the marcellus blog</description>
	<lastBuildDate>Thu, 04 Feb 2010 03:11:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>API</title>
		<link>http://blog.marcellus.tv/api/</link>
		<comments>http://blog.marcellus.tv/api/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 12:33:09 +0000</pubDate>
		<dc:creator>Preetam</dc:creator>
				<category><![CDATA[miscellaneous]]></category>
		<category><![CDATA[api]]></category>

		<guid isPermaLink="false">http://blog.marcellus.tv/?p=146</guid>
		<description><![CDATA[A number of you have asked us over the last few days, if there is a Marcellus API.
Which tells us:

Setting up a classy workflow is still a problem

upload, content management, customization, and publishing are fundamental challenges for many


The work flow needs to be ubiquitous

it&#8217;s one thing to use workflow on Marcellus. It&#8217;s quite another to [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fblog.marcellus.tv%2Fapi%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fblog.marcellus.tv%2Fapi%2F" height="61" width="51" /></a></div><p>A number of you have asked us over the last few days, if there is a Marcellus API.</p>
<p>Which tells us:</p>
<ul>
<li><strong>Setting up a classy workflow is still a problem</strong>
<ul>
<li>upload, content management, customization, and publishing are fundamental challenges for many</li>
</ul>
</li>
<li><strong>The work flow needs to be ubiquitous</strong>
<ul>
<li>it&#8217;s one thing to use workflow on Marcellus. It&#8217;s quite another to be able to access the same workflow on YOUR website</li>
</ul>
</li>
<li><strong>Scale and economics are SERIOUS considerations</strong>
<ul>
<li>And therefore, a reliable cloud infrastructure is a huge blessing for online video</li>
</ul>
</li>
</ul>
<p>So, to answer your questions:</p>
<ul>
<li>We ARE working on the Marcellus API. With a little luck, we&#8217;ll have it ready for you by Christmas of this year.</li>
<li>Before the API arrives, we&#8217;ll be launching a community video platform: <span style="color:#99cc00;"><strong>mia</strong></span>. You can read more about it at <a href="http://www.marcellus.tv/mia" target="_blank">http://www.marcellus.tv/mia</a></li>
</ul>
<p>We&#8217;re keeping <span style="color:#99cc00;"><strong>mia </strong><span style="color:#000000;">a little hush-hush for a bit. Not because it&#8217;s a big secret that we want to hide, but because we&#8217;re trying to figure out what feature set to launch it with. So, if you have ideas/thoughts on what you&#8217;d like to see when we launch, just place a comment on here, or write to us. </span></span></p>
<p><span style="color:#99cc00;"><span style="color:#000000;">We are: buzz (at) marcellus (dot) tv</span></span></p>
<p><span style="color:#99cc00;"><span style="color:#000000;"><br />
</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.marcellus.tv/api/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
