Cross-document messaging
Group items tagged
HTML5 data communications - 1 views
-
-
Sounds like the core of a 1992 Windows Desktop Productivity "Compound Document" model. Applications need to message, exchange and link data. In 1992, the key technologies embedded in a compound document were DDE, OLE, ODBC, scripts and macros. Later on, ActiveX and COM was added. Today the MSOffice desktop productivity environment links into the MS-Live Productivity Cloud or the BPOS - SharePoint private cloud with a raft of WPF-SilverlightX stuff. Good to see the Open Web fighting back with their own compound document model.
-
-
Sharepoint Site Configuration - 0 views
Sharepoint Upgrading - 0 views
Sharepoint 2010 Rating Feature - 0 views
Microsoft preps Office 365 document management tool for lawyers | Network World - 2 views
-
The product apparently has a special search engine that can be accessed from within Outlook and Word, and it offers functionality to “track or pin” frequently used documents and “matters,” those issues related to managing a law practice. Emails can be dropped into the appropriate context from Outlook, and documents retain their metadata, permissions and version control as they’re stored and shared.
-
"Microsoft has developed a document management add-on for Office 365 intended for lawyers, signaling a possible interest by the company in creating vertical-industry tools for the suite. Featured Resource Presented by Riverbed Technology 10 Common Problems APM Helps You Solve Practical advice for you to take full advantage of the benefits of APM and keep your IT environment Learn More Microsoft announced the product, called Matter Center for Office 365, Monday, saying it's in limited preview and available via a beta program to which customers can apply. The company provided few details about how the product works and what features it has, focusing instead on the fact that it is closely integrated with Office 365. Customers will be able to use Matter Center from within the suite's interface and components, like the Word and Excel apps, the SharePoint Online collaboration server and the OneDrive for Business cloud storage service. Matter Center has been designed to let lawyers and other legal professionals "easily find, organize and collaborate on files" within Office 365, instead of having to use a separate document management product. It remains unclear whether Matter Center will have all the security, compliance, retention and search functionality of full-featured document management products already used in legal settings."
-
Big barrier in that vertical market; law firms are required by Bar disciplinary rules to protect the confidentiality of client files. Unless Microsoft implements end to end encryption for Office 365 so that it's nigh impossible for the NSA et ilk to gain access to the plain text and rewrites its end user license to guarantee confidentiality of customer files, MSFT will get only the unwary law offices to use Office 365.
What will it be for ODF? Continuation of limited interop? Or a transition to Universa... - 0 views
-
-
Preserving metadata! Preserving application specific information. Preserving "unknown" information inside of a document
-
-
Unless we add conformance requirements for the preservation of metadata and processing instructions, the less featureful apps will never be able to round-trip documents with the more featureful apps. Our language should require that. Personally, I believe that the software-as-an-end-point client-side office suites are dinosaurs at the end of their era. They are being finished off by a thousand cuts as users spend less and less time using them and more and more time using other apps, such as web apps. ODF either develops methods for interoperability among all apps or it will die along with the office suites. E.g., Microsoft knows this and is busily migrating its Office development budget across the Sharepoint/Exchange server hubs to the network. Meanwhile, this TC fiddles with preserving the 1995 software-as-an-endpoint vision.
-
Marbux is clearly at the top of his game here as he hammers the interoperability issue.
Q&A: Calif. CIO Steers Clear of Ideology on File Formats - 0 views
-
We’re trying to view it as a straight business decision. What are the costs associated with one approach over another? Does it serve all of our business needs? If it doesn’t serve a business need, how do we satisfy that business need? We’re trying to view this just as a plain-vanilla, nonpartisan, nonideological issue.
-
A mus tread. Carol Sliwa of ComputerWorld intervies Clark Kelso, California CIO. ODF is the main issue, with clark casting all his answers in the context of business decisions. Carol o fcourse is asking the best questions of any journalist alive.
Keep in mind that ComputerWorld and the Boston globe filed for the Freedom of Information Act to be invoked in Massachusetts. They got access to all the eMail, documnetation, and conferencing notes concerning ODF and Microsoft. Carol's interview with Louis Gutierrez last week was filled with the same hard questions Clark Kelso fielded so deftly.
The "committee" Clark Kelso has set up to look at these issues is headed by Bill Welty, the CIO of the California Air Resources Board. Bill is a long time opensource - Linux guy, but will be the firs tto admit that Microsoft is the only vendor providing a means of getting everything inot XML. And that's the heart of any SOA strategy, "First, get everything into XML".
With a 500 million MSOffice desktop bound business process headstart, Microsoft has the extreme advantage in this much needed migration to XML.
They now have their own proprietary application and platform bound version of XML; MOOXML (Microsoft OfficeOpenXML) heading for international standardization at ISO.
They now have their XML Hub in place; the Exchange4/SharePoint Hub. This is also an essential part of any SOA strategy. You've got to have an XML Hub where the XML information streams and service connection to legacy black box systems can be piped into, managed and resolved. The XML must also provide an end user interface to these information flows. One that converges and integrates information, documents, data, and workflows into an easy to manage and participate in interface. The E/S Hub excells at this because it covers the fundamentals of eMail, messaging, portal, calendar, scheduling, c
Microsoft Suffers Latest Blow As NIST Bans Windows Vista - Technology News by Informati... - 0 views
-
In a new setback to Microsoft's public sector business, the influential National Institute of Standards and Technology has banned the software maker's Windows Vista operating system from its internal computing networks, according to an agency document obtained by InformationWeek.
-
Excuse me! Excuse me! Does the right hand know what the left hand is doing?
NiST, the National Institute of Standards and Technology, is authorized by the USA Department of Commerce.
Years ago, in conjunction with the Department of Defense (WWI), the Dept of Commerce joined with two manufacturing consortia to form ANSI. Int eh aftemath of WWII and the formation of ISO/IEC, the US Congress, at the behest of the Department of Commerce, authorized the NiST subdiary. NiST then authorized (and continues to oversee) ANSI to take on the USA representation at ISO/IEC.
ANSI in turn authorized INCITS to take on the ISO/IEC document processing specific standardization issues. It is INCiTS that represents the citizens on the ISO/IE SCT 1 workgroups (wk1) responsible for both ISO 26300 (OpenDocument - ODF) and Ecma 376 (MOOX).
Okay, so now we have the technical staffers at NiST refusing to allow purchases of Vista, MSOffice 2007 and IE 7.0. What's going on? And why is this happenign near everywhere at this exact same moment in time?
The answer is that this is clearly plan B.
Plan A was to force Microsoft to enable MSOffice native use of ODF. The reasoning here is that governments could force Microsoft to implement ODF, the monopolist control over desktops would be broken, and the the threat of MS leveraging that monnopoly into servers, devices and Internet systems be averted.
The key to this plan A was to mandate purchase requirements comply with Open Standards. And not just any "Open Standards". Microsoft had previously demonstrated how easy it was to use ECMA as rubber stamp for standards proposals that were anything but open. This is why in August of 2004 the EU asked the OASIS ODF Technical Committee to submit ODF to ISO/IEC. ISO had not yet been corrupted in the same way as the hapless money hungry ECMA.
Plan A was going along
Microsoft playing three card monte with XML conversion, with Sun as the "outside man" w... - 0 views
-
In a highly informative post to his Open Stack blog Wednesday, Edwards explains how three key features are necessary for organizations to convert to open formats. These are: Conversion Fidelity - the billions of binaries problem Round Trip Fidelity - the MSOffice bound business processes, line of business integrated apps, and assistive technology type add-ons Application Interop - the cross platform, inter application, cross information domain problem
-
Dana Blankenhorn posted this article back in March of 2007. It was right at the time when the OASIS ODF TC and Metadata XML/RDF SC (Sub Committee) were going at it hammer and tong concerning three very important file format characteristics needed to fulfill a real world interoperability expectation:
.... Compatibility - file format level interop -
::: backwards compatibility / compatibility with existing file formats, including the legacy of billions of binary Microsoft documents
....... Interoperability - application level interop-
:::::: application interoperability including interop with all Microsoft applications
INTERVIEW: Craig Mundie -- Microsoft's technology chief, taking over from Bill Gates - 0 views
-
In this exclusive interview with APC, Mundie says the notion of all software delivered entirely through the web browser is now widely recognised as being 'popular mythology'. He also stakes the claim that Google's existence and success was contingent on Microsoft creating Windows. He talks about what's coming down the pipeline for future versions of Windows, and his belief that Windows can get still more market share than it has today. He also discusses the issues around the recent controversy over the Office Open XML file format.
-
So Vista is in its diffusion cycle and until there is enough of it out there, you won't really see the developer community come across.
-
Uh, the diffusion we really should be focused on involves the OOXML plug-in for MSOffice, IE 7.0, MSOffice 2007, and the Exchange/SharePoint Hub.
The Exchange/SahrePoint juggernaught is now at 65% marketshare, with Apache servers in noticeable decline.
So it seems the improtant "diffusion" is going forward nicely. The exploitation of the E/S Hub has also started, and here the Microsoft deelopers have an uncahllenged advantage. Most of the business processes being migrated to the E/S Hub are coming off the MSOffice bound desktop. Outsiders to the MS Stack do not have the requisite access to the internals that drive these MSOffice bound business processes, so they have little hope of getting into the "exploitation" cycle.
This aspect was on full display at the recent Office 2.0 Conference in San Francisco. The only way a O2 provider can position their service as a collaborative addon to existing business processes is to have some higher level of interop-integration into those processes beyond basic conversion to HTML.
Most O2 operatives struggle to convince the market that an existing business process can be enhanced by stepping outside the process and putting the collaboration value elsewhere. While this approach is disruptive and unfriendly, it tends to work until a more integrated, more interoperable coolaboration value becomes available.
And that's the problem with O2. Everyone is excited over the new collaboration possibilities, but the money is with the integration of collaborative computing into existing business processes. This is a near impossible barrier for non Microsoft shops and would be competitors. If you're Microsoft though, and you control existing formats, applications and processes, the collaboration stuff is simple value added on. It's all low hanging fruit that Microsoft can get paid to deliver while O2 players struggle to f
-
-
So far, we have delivered about 60 million copies. That would represent about six per cent of the global Windows install base. So it has probably got to get up another few percentage points before you will start to see a big migration of the developer community.
-
What is he talking about? Does a developer write to Vista? Or do they write to MS Stack ready .NET - OOXML-Smart Documents, XAML, Silverlight stuff?
-
- ...2 more annotations...
-
Great inteview, i'll comment as i make my way down the page. Hopefully others will do the same.
The Merging of SOA and Web 2.0: 3 - 0 views
-
SOA is not about connecting things but, rather, enabling business processes and continual change. The goal is to allow users to build applications out of services, Bloomberg said. "We're really talking about service automation," Bloomberg said. "Service-oriented business applications [SOBAs] are composite applications [made up] of services that implement a business process."
-
Good SOA thinking!
-
-
the SOA world is we're reaching the services tipping point—from a focus on building services to consuming services. This has given rise to the mashup. A mashup is a flexible composition of services within a rich user interface environment."
-
Bloomberg is on fire here!
-
-
"This is where the information assets and people productivity issues come together,"
-
But does IBM have a stategy for SOA that includes Lotus Notes? Or will the MS Exchange/SharePoint OOXML juggernaut knock out the enterprise collaboration king?
-
But can they implement ODF? South African Government Adopts ODF (and not OOXML) - 0 views
-
That said, it goes on to acknowledge that “there are standards which we are obliged to adopt for pragmatic reasons which do not necessarily fully conform to being open in all respects.
-
So, South Africa was watching closely the failed effort in Massachusetts to implement ODF? And now they are determined to make it work? Good thing they left themselves a "pragmatic" out; "there are standards which we are obliged to adopt for pragmatic reasons which do not necessarily fully conform to being open in all respects."
Massachusetts spent a full year on an ODF implementation Pilot Study only to come to the inescapable conclusion that they couldn't implement ODF without a high fidelity "round trip" capable ODF plug-in for MSOffice. In May of 2006, Pilot Study in hand, Massachusetts issued their now infamous RFi, "the Request for Information" concerning the feasibility of an ODF plug-in clone of the MS-OOXML Compatibility Pack plug-in for MSOffice applications. At the time there was much gnashing of teeth and grinding of knuckles in the ODf Community, but the facts were clear. The lead dog hauling the ODf legislative mandate sleigh could not make it without ODf interoperability with MSOffice. Meaning, the rip out and replace of MSOffice was no longer an option. For Massachusetts to successfully implement ODf, there had to be a high level of ODf compatibility with existing MS documents, and ODf application interoperability with existing MS applications. Although ODf was not designed to meet these requirements, the challenge could not have been any more clear. Changes in ODf would have to be made. So what happened?
Over a year later,
What Might Hurt ODF? And It Is Not Another Office Format | iface thoughts - Flock - 0 views
-
A while back the OpenDocument Foundation folded up, withdrawing its support for the ODF in favor of CDF. The reason for the switch is buried in the details of ODF community’s denial to be fully interoperable with Microsoft Office, which might have helped in migrating to ODF without affecting the processes. So, there was something bigger here playing it up. Matt Assay notes that Microsoft Sharepoint might kill ODF more than anything else. It is the process stupid! People want to move to ODF, but without having to re-engineer their business processes.
Getting the (Share)Point About Document Formats [LWN.net] - Gly Moody - 0 views
-
The OpenDocument Foundation was formed in 2005, with the mission "to provide a conduit for funding and support for individual contributors to participate in ODF development" at the standards body OASIS. So, at a time when backing for the ODF format seems to be gaining in strength around the world, eyebrows were naturally raised when Sam Hiser, the Foundation's Vice President and Director of Business Affairs, wrote on October 16 that it was no longer supporting ODF:
open...: Oh, Tell Me the Truth About...the ODF Bust-Up - 0 views
-
Oh, Tell Me the Truth About...the ODF Bust-Up The recent decision by the OpenDocument Foundation to shift its energies away from ODF to CDF has naturally provoked a lot of rather exaggerated comment. I wrote a piece for LWN.net (now out from behind the paywall) exploring what exactly was going on, and found out that there are bigger issues than simply document interoperability at play.It turns out to be all about Microsoft's Sharepoint - software that I am beginning to see as one of the most serious threats to open source today. Read it and be very afraid.
Brian Jones: Open XML Formats : Mapping documents in the binary format (.doc; .xls; .pp... - 0 views
-
The second issue we had feedback on was an interest in the mapping from the binary formats into the Open XML formats. The thought here was that the most effective way to help people with this was to create an open source translation project to allow binary documents (.doc; .xls; .ppt) to be translated into Open XML. So we proposed the creation of a new open source project that would map a document written using the legacy binary formats to the Open XML formats. TC45 liked this suggestion, and here was the TC45 response to the national body comments: We believe that Interoperability between applications conforming to DIS 29500 is established at the Office Open XML-to- Office Open XML file construct level only.
-
And here i was betting that the blueprints to the secret binaries would be released the weekend before the September 2nd, 2007 ISO vote on OOXML! Looks like Microsoft saved the move for when they really had to use it; jus tweeks before the February ISO Ballot Resolution Meetings set to resolve the Sept 2nd issues. The truth is that years of reverse engineering have depleted the value of keeping the binary blueprints secret. It's true that interoperability with MSOffice in the past was near entirely dependent on understanding the secret binaries. Today however, with the rapid emergence of the Exchange/SharePoint juggernaught, interop with MSOffice is no longer the core issue. Now we have to compete with E/S, and it is the E/S interfaces, protocols and document API's and dependencies tha tmust be reverse engineered. The E/S juggernaught is now surging to 70% or more of the market. These near monopoly levels of market penetration is game changing. One must reverse engineer or license the .NET libraries to crack the interop problem. And this time it's not just MSOffice. Today one must crack into the MS Stack whose core is tha tof MSOffice <> E/S. So why not release the secret binary blueprints? If that's the cost of getting the application, platform and vendor specific OOXML through ISO, then it's a small price to pay for your own international standard.
-
-
Well well well. We knew that IBM had access to the secret binary blueprints back in 2006. Now we know that Sun ALSO had access!
And why is this important? In June of 2006, Massachusetts CIO Louis Gutierrez asked the OpenDocument Foundation's da Vinci Group to work with IBM on developing the da Vinci ODF plug-in clone of Microsoft's OOXML Compatibility Pack plug-in. When we met with IBM they were insistent that the only way OASIS ODF could establish sufficient compatibility with MSOffice and the billions of binary documents would be to have the secret blueprints open.
Even after we explained to IBM that da Vinci uses the same internal conversion process that the OOXML plug-in used to convert binaries, IBM continued to insist that opening up the secret binaries was a primary objective of the OASIS ODF community.
For sure this was important to IBM and Sun, but the secret binaries were of no use to us. da Vinci didn't need them. What da Vinci needed instead was a subset of ODF designed for the conversion of those billions of binary documents! A need opposed by Sun.
Sun of course would spend the next year developing their own ODF plug-in for MSOffice. But here's the thing: it turns out that Sun had complete access to the secret binary blueprints dating back to 2006!!!!!!
So even though IBM and Sun have had access to the blueprints since 2006, they have been unable to provide effective conversions to ODF!
This validates a point the da Vinci group has been trying to make since June of 2006: the problem of perfecting a high fidelity conversion between the billions of binaries and ODF has nothing to do with access to the secret binary blueprints. The real issue is that ODF was NOT designed for the conversion of those binary documents.
It is true that one could eXtend ODF to achieve the needed compatibility. But one has to be very careful before taking this ro
Notes on Breaking the Web to Ride the Fifth Wave - 1 views
-
garyedwards's Discussions Breaking the Web Talkback: Google: OOXML 'insufficient and unnecessary'
-
Somehow i got involved in this discussion and ended up posting a number of comments explaining the how and why behind Microsoft's push for ISO approval of MS-OOXML. I have been working on a paper titled, "Breaking the Web to Ride the Great Wave". Breaking the Web is what will happen once ISO approves MS-OOXML. The MIcrosoft Stack of Web Servers (Exchange, SharePoint, MS-SQL Server) are integrated into the MSOffice-Outlook desktop. The MS desktop dominates much of the document workflows and business processes of the commercial world. ISO approval of the MSOffice specific MS-OOXML will legitamize MSOffice as an editor of standardized web ready docuemnts. But how MS-OOXML docuemnts become "Web REady" is tricky. In the December 2007 MSOffice SDK beta, we see how this is done. The SDK provides a conversion component for the quick high fidelity conversion of MS-OOXML documents to XAML. XAML is a proprietary part of the WPF (Windows Presentation Foundation) layer of the .NET framework, and is easily paried with Silverlight. Sometimes XAML is referred to as "fixed/flow". XAML is an MS proprietary replacement for the W3C's (X)HTML. Billions of MSOffice docuemnts will make their way to the Web using this SDK converter. The path for transitioning the monopolist hold on desktop business processes to the monopolist stack of web servers is set with this converter. ISO approval of MS-OOXML will enable Microsoft to dodge brining their desktop editor into compliance with advancing W3C standards such as (X)HTML, CSS 3, XForms, SVG and RDF. Instead of these open standards, transitioning business processes will be locked into MS only dependencies; XAML, Silverlight, WinForms, and Smart Tags. The breaking of the web results in a consumer/business cloud dependent on MS proprietary technologies that are out of the reach of Firefox, Apache, Java, and Adobe technologies. Google won't be able to penetrate the business stack, and will be kept very busy trying to defen
Infocon 4 - DOD bars use of HTML e-mail, Outlook Web Access - 0 views
-
Wow, Outlook and Web OutLook eMail hit Infocon 4 and are banned by the DOD. The MS Exchange/ShrePoint Hub has been on a tear, with governments worldwide leading the way. And now this? Government mandates to use ODF on the desktop did not stop governmen
-
Wow, Outlook and Web OutLook eMail hit Infocon 4 and are banned by the DOD. The MS Exchange/ShrePoint Hub has been on a tear, with governments worldwide leading the way. And now this? Government mandates to use ODF on the desktop did not stop governmen
-
Wow, Outlook and Web OutLook eMail hit Infocon 4 and are banned by the DOD. The MS Exchange/ShrePoint Hub has been on a tear, with governments worldwide leading the way. And now this? Government mandates to use ODF on the desktop did not stop governmen
digg - The Future of Microsoft Lock-in - 0 views
-
hey great comment!
-
hey great comment!
-
hey great comment!
‹ Previous
21 - 40 of 54
Next ›
Showing 20▼ items per page
"....One of the more interesting characters in the recent standards battles has been Gary Edwards: he was a member of the original ODF TC in 2002 which oversaw the creation of ODF 1.0 in 2005, but gradually became more concerned about large vendor dominance of the ODF TC frustrating what he saw as critical improvements in the area of interoperability. This compromised the ability of ODF to act as a universal format."
"....Edwards increasingly came to believe that the battleground had shifted, with the SharePoint threat increasingly needing to be the focus of open standards and FOSS attention, not just the standalone desktop applications: I think Edwards tends to see Office Open XML as a stalking horse for Microsoft to get its foot back in the door for back-end systems....."
"....Edwards and some colleagues split with some acrimony from the ODF effort in 2007, and subsequently see W3C's Compound Document Formats (CDF) as holding the best promise for interoperability. Edwards' public comments are an interesting reflection of an person evolving their opinion in the light of experience, events and changing opportunities...."
".... I have put together some interesting quotes from him which, I hope, fairly bring out some of the themes I see. As always, read the source to get more info: ..... "