|
|
|
25 May 2005
Standard Form for MicroContent
l.m.orchard replies to a worry that one would get a plugin for each MicroContent type. He suggest that with GreaseMonkey one could have a single form for all blogging systems.
It all depends how you look at MicroContent. If you see it as just a blog-entry with some extra mark-up, I guess that you are OK.
If you take it however to a more fundamental level and add extra fields to your database storage, then you must have another solution. Ideally you would specify at the creation moment of your item what kind of item you want to create. And then the appropriate fields to fill are presented. This is however only possible if your system supports multiple MicroContent types per blog. I guess you would need a XML-database for this.
If only a single MicroContent type is allowed per blog, you must create a separate blog for each MicroContent type. At blog-creation moment you must now specify the kind of blog you want to create. This method is compatible with a relation database. This is by the way the approach I have taken.
And finally you can revert to the solution that is proposed on 0xDECADBAD.
And a XSD-file for each MicroContent type might prevent the proliferation of plugins, etc for each blog-system.