Categories
Technology Weblogging

Wordform: Release

I’m reaching a burn out point in trying to enhance and support Wordform (and get it ready for a release) and do enough work to pay the bills. At this time, I’m working 15+ hours a day, and it’s taking a toll.

What I’ll most likely do is release bits of the tool as extensions to WordPress. That way more people can use the functionality, and I’ll be able to focus on specific pieces of development.

If things lighten up, and I feel comfortable I have enough time to provide decent support, I’ll release the application.

Categories
Technology Weblogging

Rewriting metadata layer

I’ve decided that the current implementation of the metadata layer is unworkable. Too vulnerable, and becoming too cumbersome for developers to work with.

Additionally, since it has a significant overhead, and not everyone is interested in it, I’m pulling it out as an integrated component and adding it as a drop-in infrastructure that takes advantage of the plugin architecture, as well as adding some of my own extensibility hooks.

The advantage, aside from decreasing the size of the default Wordform install, not to mention removing a security vulnerability, is that the infrastructure can have different backend engines — not just RAP (RDF API for PHP), which I’ll still be using as the first semantic drop-in. This is a response for those who are interested in using Redland and its PHP interface, rather than RAP.

Just goes to show that for every cloud there is sunshine — the new infrastructure will be superior to the existing one, but I may not have pursued it if I hadn’t had problems with security–which is something I just won’t compromise on.

Categories
Weblogging

Wordform: Rewriting metadata lawyer

Recovered from the Wayback Machine.

I’ve decided that the current implementation of the metadata layer is unworkable. Too vulnerable, and becoming too cumbersome for developers to work with.

Additionally, since it has a significant overhead, and not everyone is interested in it, I’m pulling it out as an integrated component and adding it as a drop-in infrastructure that takes advantage of the plugin architecture, as well as adding some of my own extensibility hooks.

The advantage, aside from decreasing the size of the default Wordform install, not to mention removing a security vulnerability, is that the infrastructure can have different backend engines — not just RAP (RDF API for PHP), which I’ll still be using as the first semantic drop-in. This is a response for those who are interested in using Redland and its PHP interface, rather than RAP.

Just goes to show that for every cloud there is sunshine — the new infrastructure will be superior to the existing one, but I may not have pursued it if I hadn’t had problems with security–which is something I just won’t compromise on.

Categories
Technology Weblogging

CVS Check-in

In order to help faciliate code walk throughs for those who are willing to help examine the Wordform source code for security and other problems, I’ll be looking at checking this code into SourceForge CVS in the next couple of days. I’ll probably also re-release the source code then–without the metadata extensions, until these are vetted out as secure.

Boy, I’m tired. Between the small jobs I’ve had from webloggers and which have helped me make it through this month (bless their souls) and the work on this, I haven’t had a break from code for almost two weeks. Need a break.

Categories
Weblogging

Wordform: CVS Check In

Recovered from Wayback Machine.

In order to help faciliate code walk throughs for those who are willing to help examine the Wordform source code for security and other problems, I’ll be looking at checking this code into SourceForge CVS in the next couple of days. I’ll probably also re-release the source code then–without the metadata extensions, until these are vetted out as secure.

Boy, I’m tired. Between the small jobs I’ve had from webloggers and which have helped me make it through this month (bless their souls) and the work on this, I haven’t had a break from code for almost two weeks. Need a break.