It became apparent over the last couple of days that we're going to need to start to add OCS support in a couple of key areas to ensure that the content that you are producing is intelligible for the "unintended use" by others.
Categories is a great example of this. Due to a template bug, it probably hasn't occurred to you yet that we're actually generating unique RSS 0.91 feeds for each folder you've created. You can check it out by going directly to:
http://[yourblogurl]/blog/[categoryname]/rblog.xml
We're definitely changing the name of the RSS file, so don't get attached to it, but you get the picture.
This creates a huge amount of disorganization in the system for aggregators - mainly because Blogware allows you to prevent a post from bubbling up (ie - prevent it from moving up the hierarchy of folders into parent folders). When you do so, you have created a dynamic in which readers and aggregators will not always be inclined to simply browse your main blogware page to see what's new - in some cases, they will be forced to read down into other categories to get a full picture of what you've posted. This is a problem for aggregators because they aren't reading from your website and don't have the benefit of your navigation structure.
OCS can ameliorate this problem to a certain degree. We will soon be writing out a blogware.ocs file into the root directory of your blogware so that aggregators can take a directory level view of the folders that you've created and choose which "folders" they wish to aggregate from.
One of the nice side-effects of supporting OCS within Blogware is that we'll be able to use it the primitives for other purposes - like letting you share your blogrolls as OCS directories.
Neat.
All of this is coming shortly. If you have any thought regarding other uses of OCS, please drop me a note or leave a comment.