Are you in the Groove? If not, check out this tutorial from Microsoft.
Groove is an interesting concept, though I'm not sure how well it will catch on. It reminds me of a P2P app. If I were to compare it to Google Office (my term) I would differentiate it as a centralized v. distributed model. Google is a web-based, web-stored centralized provider, whereas Groove is a web-based, locally stored and replicated solution. With Google there is concern over file ownership and potential privacy issues, while Groove appears to bypass that by ensuring that only members of a Groove workspace have access to these files as they are stored on each authorized user's machine and are allowed to sync their changes to the rest of their team.
Very cool! A must see for anyone trying to understand the Vista Information Processing Chain. MSOffice applications become the user interfaces to Office Groove. Compare this to the stuck in side the browser efforts of Google, Yahoo, and SalesForce.com. The passing of document based (MOOXML and MOOXML Binary InfoSet) information between MSOffice 2007 (Word, Excel, PowerPoint), the Exchange/SharePoint Hub, and the Office Groove collaboration and workflow hub is seamless, fluid, easy and perfect fidelity.
The only catch is that everyone in the workflow must have licensed access to the entire Vista Stack of desktop, server and device systems. Can Office Groove users exchange ODF documents that might have XForms or Jabber based data bindings to an Oracle Transaction Processign System? I doubt it. Best to switch the backend infrastructure to MS SQL. Hint hint hint Oracle!
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.
Page Comments
Groove is an interesting concept, though I'm not sure how well it will catch on. It reminds me of a P2P app. If I were to compare it to Google Office (my term) I would differentiate it as a centralized v. distributed model. Google is a web-based, web-stored centralized provider, whereas Groove is a web-based, locally stored and replicated solution. With Google there is concern over file ownership and potential privacy issues, while Groove appears to bypass that by ensuring that only members of a Groove workspace have access to these files as they are stored on each authorized user's machine and are allowed to sync their changes to the rest of their team.
The only catch is that everyone in the workflow must have licensed access to the entire Vista Stack of desktop, server and device systems. Can Office Groove users exchange ODF documents that might have XForms or Jabber based data bindings to an Oracle Transaction Processign System? I doubt it. Best to switch the backend infrastructure to MS SQL. Hint hint hint Oracle!
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.