Tech, start by presuming this will require a SharPoint Server. PT seems to be wondering about this--the extent to which it is dependent on other apps or servers, but he got a noncomittal answer from MS. The very fact that MS doesn't know whether or not it can be a stand-alone app is disconcerting.
Second, if your company uses developed Outlook forms you can understand what this will be doing. Disconcerting element number 2: MS is obviously moving away from attaching this functionality to Exchange Server.
Third, if you aren't doing document management using a server, there is no need for SharePoint... similar functionality exists in Outlook (but is more difficult to develop for and the data store is crappy)... but still, is available.
Fourth, building spreadsheets and word docs and other materials into these forms (or XDocs) will be a waste of time if you are not heavily implementing XDocs/SharePoint in the first place; you can still do it with OLE or other methods--i.e. HTML, XML.
Five, if it is dependent on a specialized server, why use XML data as your data store? I would prefer a true datastore than a tagged language. If it isn't primarily a data entry/storage system but is also related to electronic documents and archival documents, I'd prefer the pdf solution.... rather than .doc files or scanned documents.
My conclusion: MS is trying to add value to SharePoint due to poor implementation and slow adoption of document management services by grafting on a form tool... They had tried to do the same thing with Outlook/Exchange several years back, but this implementation will be superior. Although superior, this will still depend on adopting centralized Document Management Servers (read: expensive) and an educated user base. MS has no idea what this is yet (as mentioned PT says they will not confirm or deny that this will be dependent on other apps or servers... which in and of itself wouldn't even mean that there was a "real" dependency on these apps, just a "MS" one) which means to me that it will be somewhat messy, unmanageable, and interdependent on a whole array of variable products.... meanwhile all of this can be done today, maybe not as prettily and in a single package, but it can be done already.
...which is a plus for MS--they may get more people adopting Doc Mgmt because they want to use the forms, people using the forms because they are using Doc Mgmt, or convince corp.s using Outlook Forms to buy into SharePoint/XDocs, but for the consumer, this will probably mean more options, strung together, each one not delivering in some way that you may want them to...
This post was edited by sodajerk on Wednesday, October 09, 2002 at 19:42.
|