Tuesday, September 13, 2005

High expectations for PDC05 concerning SharePoint and MCMS

I was going over my postings of 2005, just checking all the stuff I wanted to see in next versions of SharePoint:

SharePoint v3.0 and other speculations (Posting: 2005/06)

Bill has put together some insights about Office 12 and SharePoint Portal Server v3.0 - of course he knows more, he just can't tell us.

Here are some of the things I'm betting on (or hoping for ...):
  • SharePoint and CMS will merge together into one product, I guess SharePoint will be the main component and CMS will be available to plug into SharePoint. This model will more or less ressemble the model that IBM uses with their IBM workplaces

  • There will be more extensive support for workflow out of the box, my guess is that they will base it on the Biztalk rule engine - which works pretty good- and add extra webparts for administering human workflow on top. Although you can never rule out that Microsoft will finally acquire one of their workflow partners, be it K2.Net or Captaris

  • IBF will be integrated into Visual Tools for Office and will be further pushed as a way of integrating different systems - a statement I heard today "IBF is the next generation smart tags". Development with 1.5 has already become a lot easier but especially the Office side - smart tag recognizer still isn't easy enough

  • Integration of features of the newly acquired Groove product set into Office 12 - I especially like the Mobile Workspace for SharePoint. Although there are still some serious limitations which need to be solved - See Limitations in using Groove to Offline SharePoint

  • Possibility to publish InfoPath forms on your SharePoint Portal Server through InfoPath Server - clients do not need a full blown version of InfoPath anymore

  • Full localization of the SharePoint environment - it will be possible to change languages at runtime - this information will be dependent on the user who logs into your portal

  • Single document security (This is definitely a must - we have done a huge project based on SharePoint which needed single document security and I can assure you, it is not easy ...) with further enhancements to Rights Management Server

  • Lots of emphasis on charting, scorecards and data analysis - Maestro will use SharePoint as its main UI

  • Full integration with lots and lots of different Microsoft products and solutions, SQL Reporting Services, Project Server, Team Foundation Server, Biztalk,...

  • SharePoint will be RSS enabled out of the box - it will possible to create RSS driven alerts on all items in SharePoint

  • More consistency in the way that SharePoint uses site definitions - admin and user facing pages should both rely on the same server controls to render their content. For those of you who have been playing with AlternateCSS and AlternateHeader now what I'm talking about

  • A plugin for VS.Net to edit site definitions - we know that CAML isn't going away, but at least provide us with better tools...

  • Better integration of WSS and SPS - it would be quite nice that when a site gets deleted it also automatically gets unlisted from the site directory

  • More options to troubleshoot SharePoint search - this is one huge black box for the moment and quite troublesome if you encounter problems

  • Support for 64-bit (of course since this is a common engineering criteria)
  • Update 23 june:I just read this article by Kay Slagman and it pointed me to another thing - mobile support for SharePoint. I don't think this is a must however, ...

  • Update 23 june:Support for database replication - especially when you have SharePoint Portal Servers in different locations, this is a must

  • SPSvNext wishlist (Posting: 2005/02)

    A couple of days ago, Heather published a prediction and wish list for the next version of SharePoint.
    Things she mentionned on her wishlist:
    (1) Late-Bound Security - people hate seeing links that they don't have privileges for
    (2) Better Search Interface - the SPS search engine is great; the interface for entering queries and seeing results is terrible
    (3) Better Customization Tools - You shouldn't have to manually alter CSS and XML files to expose additional functionality
    (4) No more DOS - template publishing should be cleaner... the current generation doesn't know how to use DOS...

    Ok, lets add my wishlist ... (Everybody feel free to add your own in the comments)
    (1) Possibility to attach events to every type of list and not only to the document library
    (2) Real multilanguage scenarios both on Portal as on the site level - come on Bill, just take a look at websphere and learn... ;-)
    (3) Give us single document security
    (4) More integration between the Portal and the WSS sites
    (5) An easier way to develop custom site definitions
    (6) Make it possible to develop webparts like normal usercontrols (this one will probably be done...)
    (7)A different licensing model - create license models which don't need the extra investment in CALS.
    (8)Possibility to replicate data between SharePoint Servers in different geographical locations

    Overview of most important IW postings of 2005 - expectations, speculations and ranting:
  • MCMS and SharePoint architectures merging

  • First glimpse of Office 12

  • SharePoint v3.0 and other speculations

  • MCMS V.Next and MCMS SP2

  • Rumors about CMS and SPS merging

  • SPSvNext wishlist

  • Connected systems, Office 2003, InfoPath and XML

  • Workflow in Office 12

  • Rumors about K2.Net and Microsoft merging denied...

  • WinOE workflow prepared for Whidbey, Longhorn and Office 12 in 2006

  • Workflow solutions on Microsoft Platform

  • mscms

    No comments: