Microsoft Office Online
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
Bookmark History
Saved by 4 people (0 private), first by anonymouse user on 2007-01-11
- Jchall00 on 2008-04-29 - Tags collaboration , technology , LAMD , FLM , flexibleworking
- Philiphuang on 2007-06-25 - Tags groove , office , 官方
- Garyedwards on 2007-01-18 - Tags collaboration , exchange , hubs , integration , mooxml , msoffice , sharepoint , xml
- Edventures on 2007-01-11 - Tags 2007 , groove , microsoft , msoffice2007 , office , tutorial , video


Public Comment
on 2007-01-11 by edventures
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.
on 2007-01-18 by garyedwards
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!