We have now published tutorial and session descriptions for our Fall conference (November 28-30, 2006 Westin Copley Place, Boston MA) and registration is also now open. Speaker details will be added soon.
Conference track descriptions:
http://gilbaneboston.com/06/ConferenceProgram.html
Conference session descriptions:
http://gilbaneboston.com/06/Conference-Sessions.html
Pre-conference tutorial descriptions:
http://gilbaneboston.com/06/Conference-Tutorials.html
Complete conference schedule:
http://gilbaneboston.com/06/Conference-Grid.html
Author: Frank Gilbane (Page 63 of 74)
Industry colleague, consultant, and Content Management Bible author Bob Boiko is teaching an intensive two-day workshop, “Taming the Content Beast: Content Strategy and Modeling for IT Professionals” in Washington DC September 18th and 19th. Bob is an incredible presenter and will keep you engaged while you’re learning. More info.
We have now published tutorial and session descriptions for our Fall conference (November 28-30, 2006 Westin Copley Place, Boston MA) and registration is also now open. Speaker details will be added soon.
Conference track descriptions:
Conference session descriptions:
Pre-conference tutorial descriptions:
Complete conference schedule:
Registration:
Note: The CTO blog content has been integrated into this blog. This post is only still here because we’re picky about these things, and the old permalink need a place to go.
——
What is the CTO Blog?
The content technology CTO Blog is hosted by the Gilbane Group as a service to the content and information technology community. The purpose of the blog is to facilitate ongoing discussion and debate on technologies, approaches and architectures relevant to enterprise content applications. (Note: Obviously the blog is live, but it won’t be officially launched until late August or Early September.)
Why have we created it?
CTOs have a wealth of critical information about technologies that is not always accessible to enterprise customers. When it is, it is often filtered through marketing or PR staff. CTOs also have demanding jobs, and have limited time available to meet with each other with customers, or with other industry influencers. Some CTOs have their own blogs, but in many cases these are not widely read. This blog is intended to encourage communication both between vendor CTOs and between enterprise customer CTOs and vendor CTOs. We have been asked by multiple CTOs to provide this channel.
Who can contribute?
Any CTO is welcome, and anyone who has an equivalent role. If you are not sure whether it makes sense for you, ask us at: ctoblog@gilbane.com. We understand that small companies might have a founding CEO who acts as the CTO (me, for example), and large companies may have multiple senior technology strategists that in effect act as CTOs for divisions. We invite all vendors, enterprise customers, system integrators, and analyst and consulting firms to participate. Anyone may comment on blog postings.
What topics will be covered?
Any topics relevant to enterprise applications and content technologies are welcome. We have set up a starter list of categories at https://gilbane.com/ctoblog/ that suggests the range. Our contributors will help us expand this list. This is a business/technical blog and not intended for personal, political or other types of content.
How can you become an author?
Send an email to ctoblog@gilbane.com if you would like to contribute to the blog, or if you have questions about doing so. If you meet our CTO or equivalent criteria you will be set-up as an author and listed as such on the blog. Each author has full posting and commenting permissions, and also will have a direct link to all their own posts (of the form “https://gilbane.com/ctoblog/firstname_lastname.html). If you don’t have a blog, this might be all you need.
What if I already have a blog?
Chances are there will be content that makes sense for your own blog that might not make sense here, and possibly vice versa. In any case, relevant cross-posting is OK.
Are there minimum contribution requirements?
No. Nor are there maximum limits. You can post just once or every day.
- What other rules are there?
Submissions by anyone “representing” approved contributors (for example, PR folks) are not allowed. Anyone is able to comment. - There will be very little moderating. However no personal attacks, “flaming”, or uncivilized posting will be allowed.
- No pure marketing or sales content is allowed, but it is fine to talk about products and their existing and planned functionality, and even to argue for a particular approach, strategy, or philosophy.
- The CTO Blog has a creative Commons license associated with it that only restricts commercial use, so, for example, re-posting to or from your own or other blogs is fine.
Is this a Gilbane Group platform?
Only physically, in that we host it and moderate it. Our own opinions may be found in comments or on our analyst blog at https://gilbane.com/blog/.
The conference schedule for our Fall Content Management Technologies event, November 28-30 at the Westin Copley in Boston, is available at: . Topics to be covered in-depth include:
* Web Content Management (WCM)
* Enterprise Content Management (ECM)
* Collaboration, Enterprise Wikis & Blogs
* Enterprise Search & Search-based Applications
* Enterprise Digital Rights Management (eDRM)
* Automated Publishing
* Enterprise User Case Studies
Conference track descriptions are available at:
Speakers and complete session descriptions coming soon.
I could have sworn they already announced this, but in any case it was inevitable. The whole controversy is now simply not all that interesting. IT organizations need to understand the translation issues, but choosing one format over another is just not that big a deal. Many organizations have more complex issues to deal with, like integrating XML content from custom applications or other enterprise apps that don’t map to either ODF or Open XML directly. We have lots more background on this.
Forrester has published one of their “Wave Evaluations” on blogging platforms. Charlene Li has a summary of the report along with the associated Wave graphic on her blog. The full report is available for sale at Forrester. Note that this report does not cover Wikis, although some of the platforms covered also have Wiki functionality. As we have suggested before, in the enterprise space, the line between blog and wiki platforms blurs in many cases. This is of course truer for collaboration and intranet-oriented deployments than for outward facing, e.g., PR-oriented communication.
As Tim Bray says “Wow”. Here is the announcement post with a huge number of comments. This is discouraging. As I have argued before, we need the kinds of capabilities WinFS was striving for to make the next leap in managing information. I remain skeptical that database platforms are a sufficient solution for effective object management – they may be the necessary next step, but they are certainly not the ultimate answer.
There are no doubt many easier, shorter-term ways to get return on software development than a radically different operating system, but hopefully at some point there will be sufficient recognition by all the software infrastructure vendors that working together to build a modern OS would be worth it. On the other hand, perhaps what has happened to WinFS is really a sign that the days of huge operating systems are numbered. The problems are really bigger than any one platform. What kind of cross-platform infrastructure is feasible to accomplish the fluid, granular and meaningful interchange of content and behavior we know we need? This is a more interesting question than whether WinFS itself is dead.
UPDATE: There is a lot of commentary out there, but as usual Jon Udell has a view worth reading.
