Treedia Powers Motorola and Podcast.com Partnership

Well, finally after a few months preparation, along with the rest of the development of podcast.com I can talk about the exciting news that podcast.com, powered by the system we call the Treedia Feed Management Platform is to be partnering with Motorola on delivering podcasts to their forthcoming smartphones, including the the MOTO Z8 ‘MotoRizr’.

We will be providing Motorola with a managed set of podcast directory folders which their applications can access and navigate the structure of through the use of OPML managed by the Treedia system. The current structure of the system and soon, more information will be available at motorola.podcast.com

The Treedia system’s name derives from the simple idea that any media can be distributed via RSS feeds held together by OPML directory folder structures which were easy to grow and manipulate.

It’s a tree of media. Treedia!

Through the use of very simple OPML files utilizing the ‘include’ type attribute, the Motorola application can drill down and list the podcasts on the device.

Soon, I will be providing a more thorough explanation of just how simple if is for anyone to create a way to navigate this data and also the power of networking available to social media networks, given easy tools to manage the data in a way we all understand already as computer users – folders. Of any ‘depth’.

And let’s not forget that RSS feeds and the like don’t have to ‘simply’ deliver podcasts. Audio or video. They could just as easily deliver updates on a multitude of things. Leveraging the awesome opportunity available to us thanks to OPML inclusion, we can begin to connect and share our appreciation of and presentation of our media in ways we haven’t even though of yet.

But they will all be connected by a ‘semantic path’ and also by the ‘curator’ of the folders and directories and their FOAF file, for example. Not only that, but each user will be able to share their playlists of what they are listening to at the time in a variety of formats, including RSS, XSPF and M3U.

Through these playlist formats and the OPML data available for each user (and each folder), it makes it easy for us to create simple widget user interfaces for just about any connected media platform there is. Simple and easy.

Naturally, users will be able to subscribe to each other’s playlists and folders. See when these change and are updated. All thanks to simple XML based technology.

I’m still wrapping up some loose ends and doing some long overdue bits of clean up on the site and documentations and tutorials, but soon we should be able to open up the doors to a limited amount of people to begin with, pretty soon!

Stay tuned! Stay subscribed! Much more exciting news to come! 🙂

Also in the news is the new next-generation RAZR-2 from Motorola.

OPML Reading/Listening/Viewing ‘Lists’ and ‘Trees’ = ‘Treedia’

OPML webDave on Scripting News and Mike over on Techcrunch post their views of OPML used for ‘reading lists’.

This is an important discussion and one close my heart. I commented over on Dave’s (wordpress) blog , but I thought I’d add to it over here:

Re: OPML lists and ‘trees’ – etc expect some along these lines soon:

The system developed behind podcast.com enables just that, it’s just that naturally with podcast.com we are only interested in feeds with audio or video enclosures.

So, podcast.com is a ‘client’ of this larger system which will be able to support all types of ‘types’ – all supporting OPML inclusion.

I don’t think you should call them ‘lists’ – I think ‘trees’ is more descriptive. ‘Reading trees’. People can either ‘climb’ up then to find the ‘fruit’ (content) they want, or they could wait for the most popular to drop into their lap. Also through looking through ‘leaves’ (tags) they can be sure of following the right branches, as they ‘climb’ up the tree, deep and deeper into the directory/tree. (’directree’? ;) )

OPML is the tree
FEEDS are the vines
TAGS are the leaves
ITEMS/ENCLOSURES are the fruit.

The coolest thing about OPML inclusion, is you could think of it like climbing up a tree, going along a branch, and then ‘zap’, you’re in another tree. Like magic. Painless. Rewarding. ;)

Telepordata?

Semantics. Taxonomy. Folksonomy.

Now that’s what I call a ’social media network’ ;)

I hope to be able to let some users in to try out the system in the next 4 weeks.

Then people could create something like : http://my.podcast.com/kosso , which is my ‘listening tree’/ podcast folders/ ‘tree of sound’

One reason why I think there are more OPML ‘lists’ than ‘trees’ out there is that there are too few tools out there to effectively manage an OPML file. Your apps have been the best to date (once we got the rss attributes sorted)

I mean managing OPML folders/nodes effectively, over import/export of ‘flat’ lists. So many systems eith dont ‘do’ folders or destroy them on import/export.

Also, I think we really need to evangelise the concept of ‘OPML subscription’ .
OPML files are so often used as static files to import/export bunches of feeds. It is indeed great for backup in that sense. But I believe that ‘OPML Subscription CONNECTS’ all these trees/branches out there. When one branch changes on one tree – if there is an ‘inclusion’ (think of it like a shortcut/symbolic link to a folder) then the other will be able to reflect that if one was to climb that branch.

The trees are ALIVE! So subscribe to them! Watch them grow ;) Feed them, prune them and ‘graft’ ‘cuttings’ to their branches.

We like to call it ‘treedia‘ 🙂

Clearly for this to work, we also need well defined standards to make sure the data out there is well-formed – or we’re screwed ;) but let’s not make the same mistake the web browsers did, by just displaying html if it was broken or not.

I feel like doing another podcast ;)

‘Codecasting’

Over on Scripting News, Dave Winer has been talking about the concept of ‘codecasting’ whereby instead of audio or video being sent via an RSS enclosure, a software update for the receiving app could be downloaded and installed.

This is very much like the way that all Dave’s Frontier-based applications have updated for some time, I believe.

I have been suggesting alternate uses for the RSS enclosure for some time myself. But also leveraging the very nature and characteristics of OPML and RSS too.

I think that the distributed media network model provided by an approach of ‘OPML plus RSS to the Power of Users’ – as in development at podcast.com ) could also power a software documentation system. I have also suggested this could also power the perfect forum software, but more on that in another post)

Imagine a directory where all the top level folders were software vendors. The next level would be software languages and applications.

Then the next level, drilling into the folder (via OPML inclusion) would be the language/software API itself. A list of each method/verb etc. These could even be categorised prior to this list, depending on the software it is documenting.

Each method/verb link in this OPML list would link to an RSS feed. IE: Every function available has its own RSS feed. The title of the feed is the name of the verb, the description is the description of the function being documented, with an example.

Then every RSS feed item below it is actually the user/developer generated content – the cool snippets of code – the wisdom – the experience : the BEST bits. 🙂 Look at PHP.net and see that often the most useful information on each function page is actually the list of submitted comments below the official instructions. Also see Macromedia/Adobe’s LiveDocs. Most APIs have a tree like structure which OPML lends itself to building very easily.

Touching briefly on the concept that OPML alone could power forum applications, then the depth of communication and knowledge available for future groks is incredible.

And the best thing being is that all this would be ‘WELL-FORMED’ data. It could document almost any software language ever made.

ps: I am suggesting all this to the owners of software.com – for like podcast.com, I believe that generic domains should do what they ‘have a duty to do‘. Anything else, and they are merely squatters trying to make a fast buck. (imho)

Samsung WiBro with RSS button!


This WiMAX enabled device from Samsung has an app called ‘My Feeds’ in it, which reads your RSS feed subscriptions. Also supports OPML import/export. Not podcasts yet though. But a great big RSS button! 🙂
posted by kosso using NOKLOG : [permalink]

UPDATE: I think it’s hilarious that some people question the authenticity of this image. I really have better things to do than to PShop phones 😉

There’s a better photo on the post above with the rest of the original photos of it, with shots of the application it kicks off.

UPDATE: Peter Rojas from Engadget has picked up on this, as has Dave on Scripting News, who has rather less to say apart from making cheeky graphics with punctuation ;p (_!_)

UPDATE2: Peter Rojas has confirmed the model as the SPH-M8110

More discussion on this via TechMeme

NOKLOG.COM : Mobile Multimedia Publishing

Presenting NOKLOG.COM!!! 🙂

So, what else have I been working on? Well, some of you will already know about the BlogHUD system I built for Second Life users, which lets them post messages and articles to a blogging system. It will also crosspost the post to your external blog too (WordPress, Blogger, Typepad, etc) – as well as send on any images you take to your flickr account.

Well, all this is really a model for a simple web application for mobiles which I started think about and testing back in 2004 called ‘camoby’. I used it to post articles of gadgets back to the BBC News website while I was out at CeBit in ’04. The editor back in London watched my RSS feed for things he liked for the site, then republished them on the BBC news site like a blog (one of their first, actually!)

So, the camoby system has evolved – as have I. Since learning many new skills since then,I was able to sit here in my hotel room in Boston/Cambridge yesterday and build the whole proof-of-concept system at noklog.com. (This will probably move to another domain eventually, as more manufacturers allow this very useful feature)

NOKLOGNOKLOG is a mobile publishing system, optimised for mobile browsers which support the oft-requested file upload form tag. (input type=file) Nokia’s Symbian Series60 web browser and Sony Ericsson’s phones with the Symbian UIQ browsers have supported this for a while. No need to build and install more apps on the phone. It all goes via the web. Sweet! it also works with the connected Archos devices (PMA430 and 604WiFi).

The difference with this and the camoby system is that I can now support ALL media types which the handset can produce. Ie: Images, Audio and Video. Once uploaded, the user can choose to publish/post the media to the main noklog.com blog, when the server then processes the image to a sensible jpeg size (with branding / watermark) and transcodes audio (.amr, .wav etc) to mp3 for podcasts and flash players AND now also video – .mp4, .3gp etc will get transcoded to the ubiquitous Flash video format (.flv) to use in a webbased Flash player, a la YouTube. No reason why I can’t transcode to MPEG4 H.263 for iPods and PSP too. It’s easy once you know how 😉

BUT, not only that – like the blogHUD system, users will also be able to share this content and extent its reach even further by crossposting to your own blogging system – if it supports XML-RPC / MetaWeblog / Blogger APIs or email publishing. There is also no reason why I couldn’t FTP the media to a host provider like Libsyn too!

This means that as well as sending you post to your blog, you can also send images on to your flickr account or even your YouTube or blip.tv account – AUTOMAGICALLY!!! W00t! (as they say!) heheh Also each user has their own ‘home’ page and RSS feed to share their mobile life. Aggretastic!

I’ll be improving this system over the next few days, as I stay out of the cold currently blowing over Massachusetts and add things like tagging etc.

NEXT – the killer metadata support will be the Geographical Latitude and Longitude data (geotagging) of where the media was taken or recorded. I simply cannot wait to get my hands on the Nokia N95 phone, with built-in GPS, to see how I can grb the position data and populate a form field or Javascript variable, while using the Series 60 browser. I hope that wont be too tricky. We shall see. This will let me add real world maps from Google and/or Yahoo! very easily to the site. Kind of like the idea I had for ‘Geepster.com‘ – another unfinished project 😉

Using Second Life and the blogHUD to model this system – as well as model my own abilities and support/iteration mechanisms has been a truly wonderful experience, One which I emplore any developer to try out. You will not regret it.

I’ll keep you posted when I can let some testers to NOKLOG in to try the system out. It shouldn’t be too long – because it’s simple! Just the way we like it 😉

Naturally, all this fits in perfectly with the podcast.com system I am creating, which is about to get a big overhaul to the new system upgrade I have nearly finished 🙂

Forums, Blogs, Threads, Comments… Structure!

Over on the Web2.0 Show blog, Darren Stuart asks ‘Are Blogs The New Forums?’

“Lets look at the function of a forum.

Users post messages for discussion. Users post messages discussing other messages. These discussions are normally in categorised in to sub forums.

Now lets look at the function of a Blog

A Blogger posts something interesting. Visitors post comments on the Blogger’s post. The Blogger’s posts are normally categorised and tagged.

As you can see the core functions of both Blogs and forums are almost identical.”

I totally agree! I too love forums. From usenet groups to phpBB. IMHO, the thread structure of forums are perfect for almost all communication and publication online.

Now pause for a moment to think and have a look at an OPML file 🙂

I often say that the only web software we (almost) ever needed was the remarkably influential ‘WWWBoard’ perl script, from a place called ‘Matt’s Script Archive‘. (I’m amazed it’s still there! – looking different though 😉 )I cut my coding teeth on that lot, years ago. Even hacked it make a flat-file content management system too 😉 WWWBoard was one of the earliest examples of an ‘open-source’ script that I ever encountered. Matt had other scripts too, for voting and the like. All very useful stuff. Until I found PHP 😉

Any post of anything online has certain basic attributes – a title, body text, author and date.

Having a post exist within the structure of a ‘thread’ – ‘a reply to reply’ or ‘a sub category of a sub category’ – the content immediately has context, reference, ‘a place’ – based on the details of its ‘parent’. It could be a comment to a post, a post on a forum, a reply to that post, a new user submitted script in code documenation, a comment on a comment on an area of a photo, a threaded discussion of experiences at a geographic location. Anything!

I’m actually working on something interesting in this area (I think!) – based around the upgrade to podcast.com which I am (still!) working on.

Let me say it again : It’s “OPML PLUS RSS TO THE POWER OF USERS!” 🙂

Do you catch my drift? 😉 Look up the tree!

Update: It looks like Dave Winer gets it too! !

The Well-Formed Web?


With well formed data, there’s no reason why not. 😉

Now, can we please work out the right way to *do* OPML please?

Basically:

If you want to point to a WEBSITE: use type=link and url=http://your.web.site.com

If you want to point to an RSS feed use type=rss and xmlUrl=htt://www.your.rss.feed.com/rss.xml

If you want to point to MORE OPML use type=include and url=http://www.you.opml.file.com/hoopla.opml

OK. So, you could argue that there might be better ways of doing/specifying it.
And what about htmlUrl, opmlUrl, atomUrl, foafUrl, rdfUrl, type=rdf, type=atom, type=application/pdf or whatever… I don’t know. Just DOCUMENT how you do it.

But what I do know is the sooner we agree and what is the right way to ‘do it’ – the better. 😀

IMHO.

Hey! Is my OPML Icon out of date?? :p

1 2 3 5