iKOZ

At the welcoming party for this year’s GnomeDex, I caught up with the excellent John Hartman who I’ve met before at GnomeDex and in Second Life. He interviewed me for AlphaGeek TV

He wanted to know all about the Twitteromance between Efisia (my now fiancee!) and I

So, I talk about aaaaaall that and then cover a load of things like Second Life blogging and using trees of media to manage podcast networks and build the Web 3.0 concept of ‘Social Multimedia Networking‘ using OPML.

[youtube=http://youtube.com/watch?v=8rYOslqQcm0]

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.

Wow! There seems to be no stopping me now! I’m on a roll!

Another podcast for ye.

Today I talk about OPML PLUS RSS TO THE POWER OF USERS and what I am trying to do to make life easier. Also thoughts on the perfect podcast device and mobiles in podcasting.

[audio=http://media.libsyn.com/media/agentkosso/kozcast3.mp3]

DOWNLOAD PODCAST MP3 HERE

Subscribe here

Dave 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

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)

The Samsung SPH-M8110 

Windows Mobile app reads RSS feeds and allows OPML in and out
posted by kosso using NOKLOG : [permalink]