marc canter gave a talk about microcontent to the berkman weblog group this evening (remotely over a free webx.com trial). it was most excellent, and while i had an idea what would be coming, i was still surprised by the scope of marc’s vision. this is something oscom should support, as it offers a migration path from content silos to new applications and services based on top of open source content. marc is evangelizing his ideas on a tucows-sponsored tour in Q1 2005.
Michael Radwin knows what he is talking about: HTTP Caching and Cache-busting for Content Publishers. highly recommended.
Daisy is a comprehensive content management application framework, consisting of a standalone repository server accessible through HTTP/XML and a high-level (remote) Java API, and an extensive Daisy browsing and editing DaisyWiki application. Daisy is licensed under the commercially-friendly Apache License 2.0.
motivated by danese cooper who named oscom 3 (and yours truly) as an influence to push corporate blogging at sun, we’d like to expand the number of feeds we carry on planet oscom. if you are a developer or user of cms (or of underlying technologies, such as mysql, php or apache) we’d like to hear from you.
so it turns out that one of the proposals we received for oscom.4 was a scam from someone in nigeria to get a visa to switzerland and then disappear.. i was wondering about the low quality of that particular proposal.
Koranteng Ofosu-Amaah ported the halfbrain browser productivity applications to mozilla as part of his work at ibm. his post gives the necessary background to understand the state of rich web applications. (via loosely coupled i am thinking, maybe we should have someone from WHATWG at oscom.4?
If standards conscious designers already follow conventions, then the stage is set. So I decided to look at forty designers’ sites to see what conventions were being used in common page elements like headers and banners, navigation, content and footers. Here’s what I found.
it makes a lot of sense to standardize on common container names like header, content, navigation. this allows to share CSS across sites and create a nice CSS skin repository. bergie, who pointed me to this, seems to agree. maybe OSCOM should set up a set of “recommended div elements” and start a CSS repository that uses them?
The RFP for OSCOM.4 (Sept. 29 – Oct 1, Zurich, Switzerland) is now available. The theme of OSCOM.4 is “Cross-Pollination”. This will be a conference with assistance from the Apache Software Foundation for the ApacheTracks content. The conference will have 4 tracks:
- OSCOM Technical / Community Track
- OSCOM Business / Legal Track
- ApacheTrack 1
- ApacheTrack 2
i went and added more feeds to the planet oscom aggregator. for now, top-level feeds are oscom-related or main project feeds. i also created sub categories:
- integrate sub categories into main navigation
- list names of aggregated people
- add more project feed lists (as OPML preferrably)