Wednesday, February 28, 2007

Three Stages of XML Migration and the Challenge to OpenDocument

  1. Conversion Fidelity - the billions of binaries problem
  2. Round Trip Fidelity - the MSOffice bound business processes, line of business integrated apps, and assistive technology type add-ons
  3. Application Interop - the cross platform, inter application, cross information domain problem

First it was the EU's controversial Valoris Report that centered on a fictional open standard XML universal file format known as “OpenDocument”. This was fictional open standard XML universal file format known as “OpenDocument”.

This was followed by the Massachusetts's pilot study and mandate for the real thing, the ISO/OASIS XML OpenDocument file format. The States of Texas and Minnesota weighed in with similar legislative proposals once again describing a open standard XML universal file format in measures that only the ISO/OASIS OpenDocument can measure up to.

And now comes the crusher. The State of California, touting what would be the world's eighth largest economy if it were a nation, steps forward into the breach with a legislative proposal describing in such detailed parameters what can only be the OpenDocument universal file format that one can almost see the butterfly tattoo on the specifications buttocks.

No doubt the great migration to XML is upon us, with XML universal file formats leading the way. Deciding to go with OpenDocument is the easy part.
Getting there is something else. A quote from Peter Quinn, the legendary CIO of Massachusetts who threw that great Commonwealth into the breach, says it all:
"Open document formats: I get it! But how do I get there? Discuss."
Sam Hiser has provided us with another fine commentary,“Open Standards Mandatory in Denmark”that's loaded with insight. He discusses the recent announcement by Denmark of their intentions to mandate support for two conflicting, contradictory, and irreconcilable XML file formats; the ISO/OASIS OpenDocument and the Microsoft Ecma Office Open XML proposal. For the life of me i don't see how mandating both ODF and OOXML will be helpful to any government. It's true that both are “XML” by design, but beyond that the promise and expectations of XML are broken by the proprietary application, platform and system specific dependencies that make up MS Ecma OOXML. In fact, the quality of XSL transformation filters between the two XML file formats is so bad it might as well be zero.

Although Microsoft assured Massachusetts that such a transformation would be trivial, nearly two years later they have nothing to show for their braggadocio.

Which means Denmark will be hoist on the petard of having their documents in two file formats that are not interchangeable. And except for the MSOffice ODF Plugins from Sun and the Foundation, application interoperability might as well be zero.

A Moving Target – MSOffice 2007 Plugin Architecture:

It's important to keep in mind that both daVinci and ACME 376, the Foundation's Plugins, were working fine in every beta release of MSOffice 2007, but broke in the final public version. I suspect Sun had the very same problem we did. It seems that Microsoft altered the system default for “zip” file format packages such that whenever a “zip” package like ODf is double clicked, the OOXML conversion engine automatically starts to convert the package to MSOffice 2007 in-memory-binary-representation. Of course, the OOXML conversion engine knows nothing about ODf. So the problem we now have is reverse engineering what looks to be a low level system “default” setting that loads the OOXML conversion engine instead of the daVinci conversion engine. Microsoft has a long history of dirty tricks and an ever moving APi, effectively protecting their monopoly from would be poachers and thieves, er “competitive application and service providers working the Windows – Vista platform”. And here we go again. This first act of aggressively blocking the ODf Plugins should signal governments loud and clear that moving into the Vista Stack of desktop, servers, devices and services is going to be the equivalent of exclusively mandating OOXML. We've known this to be the case in the past, the primary example being the Exchange/SharePoint Hub and developer platform which is optimized for MSOffice 2003 MSXML. So much so that the E/S Hub has to be considered an ODf killer. Yet even those governments exclusively mandating ODf are boldly going forward with E/S Hub purchases, totally unaware of the consequences. As i've said many times, Massachusetts is just one E/S Hub Court Docket System away from revoking their ODf requirement and standardizing on OOXML. (Watch carefully now, the hand is quicker than the eye; ViSTO 2005, which was released with MSOffice 2007, dropped support for MSXML entirely in favor of the MS version of OOXML. (i mention this because there is clear evidence that MOOXML, legacy MOOXML, and now MOOXL Binary InfoSet for Excel all include eXtensions and dependencies that differ from the Ecma 376 version submitted to ISO/IEC). Remember our Peter Quinn quote, "Open document formats: I get it! But how do I get there? Discuss.”? The simple truth is that the ODf Community is not providing the means to get to ODf. There is no bridge from the legacy installations of MSOffice and the billions of binary documents, to ODf ready applications and services.

Get to XML:

What most ODF-OOXML warriors forget is that the real issue for workgroup and workflow oriented consumers is getting their binary documents into XML. Which XML, ODf or OOXML, is a secondary consideration. The one thing everyone understands is that the way to connect important information domains, systems and architectures is through the skillful use of open XML and open Internet technologies. Important information domains and architectures includes:
  • Desktop Productivity Environments (the Office Suites)

  • Enterprise publication, content management and archive systems

  • SOA – Service Oriented Architectures

  • SaaS – Software as a Service systems

  • The Internet – Web 2.0 and beyond

You can't efficiently exchange information across these domains if it's trapped in application – platform specific and unstructured binary formats. Conversion fidelity requirements will break a binary bound exchange process every time. Even Microsoft realizes the need to move to XML, although they will of course strive to control that XML through continued use of application and platform specific dependencies and, artificially contrived implementation constraints.

XML Migration: The Three Stages

The problem as we saw in Massachusetts, Munich, and Bristol is that there are three stages of XML file format migration. The three stages for migrating to XML file formats are inextricably linked and must be tackled in exactly this order:
  1. Conversion Fidelity - the billions of binaries problem
  2. Round Trip Fidelity - the MSOffice bound business processes, line of business integrated apps, and assistive technology type add-ons
  3. Application Interop - the cross platform, inter application, cross information domain problem

Sadly, the ODf Community is near entirely focused on stage three, leaving the critically important first and second stages up to customers.

Interestingly, OOXML nails all three stages perfectly, with the proviso being that all interop applications be Microsoft application – platform specific. This is what they mean when they say, “interoperability by design”; applications designed to speak fluent OOXML, making exclusive internal use of .NET 3.0 system dependencies.

Note well that since the starting point of XML migration is that of MSOffice bound binaries and business processes, OOXML is today the only XML file format proposal that can perfectly answer all three stages of XML migration requirements. The OpenDocument Foundation does have three products in the works that are designed to also perfectly answer these same XML requirements, but the Foundations approach has met with considerable resistance, argument, doubt and continued outrage from the ODf Community at large. Note also that these three stages are only important to workgroup and workflowsituations – situations where MSOffice bound business processes are critical day to day to day operations. People who are involved in simple document exchange can easily move to ODf through an OpenOffice download and some simple conversion artifact fixes as documents are converted as needed. Workgroups and workflows require a very high level of round trip fidelity. Which is why mixed application environments present workgroups with an near insurmountable problem; even where the mix is limited to that of different MSOffice versions! Of course no one wants to see the life span of MSOffice eXtended indefinitely,which is exactly the conclusion most come too regarding the daVinci Plugin. daVinci makes it too too easy to stay with MSOffice since there is zero disruption to MSOffice bound business processes, line of business integrated apps, and the functioning of assistive technology add-ons. The ODf community doesn't realize three things.

  • First, it's an absolute real world requirement that the three stages of XML migration be met perfectly by any file format contestant.

  • Second, Microsoft has handed the ODf Community the opportunity of a lifetime regarding the most difficult stage for ODf; stage two, the migration of MSOffice bound business processes.

  • Third, consumers migrating to XML have no stomach, tolerance or funds for the highly disruptive and costly rip out and replace” approach most in the ODf community favor.

The Massachusetts RFi:

Massachusetts ITD deserves credit for figuring this out. The three stages are the reason behind their ODf Plugin for MSOffice RFi. Which is about as desperate a cry for help from the ODf Community as i've ever seen. There is no other way to describe the events in Massachusetts except to say that the ODf Community refused to listen, and worse, made no attempt whatsoever to understand the exact nature of problem consumers wanting to migrate to ODf face. Hence the unprecedented RFi (Request for Information). So what's going on here? It's the reality of being caught in the clutches of a monopolist for over ten years.

In 1995 Microsoft won the Office Suite application wars, with the next two years mopping up as they paved the way for the real crusher, MSOffice 97. The office suite wars were marked by the vicious marketing of comparative feature sets and competitive price inducements. The feature wars ended in 1995, were set by 1997, a time period during which a new movement had begun – the use of the ubiquitous MSOffice as a development platform for business processes, line of business integrated applications, and a proliferation of add-ons like those for assistive technologies.

In short, by 1997 it was no longer about “features”. It was all about MSOffice bound business processes. And the binding occurs at two levels; the MSOffice application layer, and the binary file format layer. This creates a binding trifecta of MSOffice, MS Binary Documents, MSOffice bound business processes.

The real battle today is over how to migrate or participate in the MSOffice bound business processes developed since 1995. This is the core of the problem every organization trying to migrate to ODf must confront. Massachusetts, to their everlasting credit, came up with a rather magical solution; the idea of using ODf Plugins for MSOffice to solve the problems of stages one and two. The stage three ODf problem of application interoperability is a work in progress, and i would direct everyone's attention to the ODf 1.2 progress ofthe three OASIS ODf sub committees; Accessibility, Open Formula, and Metadata RDF/XML. A great leap in application interop is brewing there, and expectations for ODf 1.2 run high with good reason.

The Problem With Rip Out and Replace:

Many people mistakenly believe that migrating to ODf is as easy as downloading for free OpenOffice 2.0. Which is true if your collaborative work is that of simple document exchange. For workgroups and workflows currently based on MSOffice bound business processes and binaries though, the disruptive and re engineering cost of moving those processes to ODf ready OpenOffice is impossibly high. While it's true that Novell is working on an automated means of converting bound business process VBA scripts to an OpenOffice footing, it's not there yet. But that's just a fraction of the problem. These business processes include compound documents for templates, forms, formula bound spreadsheets, and reports - often involving systems dependent data bindings. Rather than trying to unwind these MSOffice bound business processes and re write them to somehow become application independent and ODf ready, we believe there is another approach demanding consideration. Instead of migrating to an ODf ready desktop MSOffice alternative, we believe the ODf Community should instead be focused on the Microsoft migration of these same business processes to the OOXML enhanced Exchange/SharePoint/Groove Hub.

The Great Opportunity: The Vista Information Processing Chain

Briefly the greatopportunity is this: Microsoft has been very busy migrating those MSOffice bound business processes to the Exchange/SharePoint Hub, which will soon be joined with Groove Collaboration servers. XML Hubs are interesting in that they are an indispensable core to any SOA effort. The Hubs are a very effective point where access, aggregation and repurposing of XML services and information streams connecting to such things as backend data, transaction, inventory and billing processing or content –archival management systems. As a universal transformation layer able to connect to many disparate and purpose specific backend legacy systems, XML is unparalleled.

But what if these same XML Hubs are integrated as a way station connecting desktops and devices to Internet server systems as well as the legacy backends? And there my friends is the magic of an Exchange/SharePoint/Groove Hub. On the desktop side E/S Hubs integrate directly with the MSOffice productivity environment using OOXML (versions Ecma 376, MOOXML, legacy MOOXML, and MOOXML Binary InfoSet) as the both the XML container and transport. The E/S Hub provides the integration point where eMail, documents, workflows, project participants (people), and information resources (web services, XHRequest streams, media streams, and message streams) can be aggregated, sorted, re purposed, published, managed and scheduled. At the E/S Hub it's easy to bind data from MS SQL Server systems, MS CRM, MS ERP and MS Live to the portable OOXML document transport.

The most important point about XML Hubs is that migrating business processes to them always results in extraordinary productivity gains. Yes, the E/S Hub represents a new lock-in point for MSOffice bound workgroup customers. The immediate productivity gains however will far outweigh the long term cost of having your business lock-in to MS only applications and services for the next fifteen years. So where's the opportunity you ask?

By intercepting this migration at the head point, MSOffice, converting the documents to ODf, and provisioning ODf ready Hubs the ODf Plugins could potentially walk off with the entire monopoly base of over 500 million MSOffice bound desktops. The ODf Plugin route is infinitely cheaper in that there is no need for desktop upgrades. And, the cost of long term MS lock-in is completely negated.

The ODf Plugin alone however isn't enough - which is exactly why the Foundation began development of the lightweight, efficient and highly portable ODf InfoSet Engine and APi. We need ODf ready Hubs to complete the ODf Information Processing Chain alternative. ODf Hubs that can compete with E/S Hub Juggernaut.

C'mon Alfresco, Lotus, and Zimbra - the whole world is waiting.

One more thing about these ODf Hubs and ODf ready applications that span desktop, servers and device platforms. The Internet has ushered in a new world of universal connectivity, exchange and collaborative computing. Some ODf ready applications will be designed to participate in specific information processing chains, so they will be built to act as efficient routers of information.

Other applications will profess to be ODf ready, but continue to act in the legacy traditions of information end points - ignoring the ODf document needs as defined by other information processing chains; dropping objects and data binding mechanisms they don't understand or lack the feature sets needed to make use of. Or, they might add value by asserting application or platform specific dependencies that would otherwise corrupt the documents use in other information processing chains.

Application Interoperability

The problems of application interoperability are far more difficult for ODf than for OOXML because ODf was designed for a very different objective.

OOXML was designed exactly for MSOffice bound binary and business process compatibility, (stage I & II of the XML migration requirement) including application and platform specific dependencies.

ODf was designed to be an application and platform independent universal file format, dependent on open XML and other Internet technologies available to any application or service.

For ODf, proprietary or platform specific dependencies are an interop killer. For OOXML, proprietary and platform specific dependencies are the monopolists life blood of "interoperability by design”.

The world is going to move to XML, and from there to RDF/XML. That's a given. OOXML has the incredible advantage of meeting the three “migration to XML” requirements. But the migration comes at the cost of long term business process lock-in, with interoperability demands limiting applications and services to the Vista Stack of:

MSOffice <> OOXML <> IE <>ViSTO .NET <> E/S/G Hub <> MS Active Directory <> MS SQL Server <> MS CRM <> MS ERP <> MS Live etc. etc. etc.

The core of this chain is the MSOffice <> OOXML <> Exchange/SharePoint Hub

ODf can similarly meet the the three “migration to XML” requirements, and do so just as well as OOXML – in spite of MS claims otherwise. Although they anger and upset the rip out and replace bent ODf community crowd, the ODf plugins for MSOffice from Sun and the Foundation are the only way ODf can crack and perfect these critically important “migration to XML” requirements. Danes please take note!

And of course, there is today no ODf Stack or ODf information Processing Chain comparable to the one Microsoft has unleashed. Some great stuff cooking with Lotus Notes, but they are obviously lacking a strategy for stage I & II of the “migration to XML” requirements. Alfresco is hard charging, but they have that same problem. Zimbra and Google Hubs are still mired in the application as end points approach where they see conversion of documents as a one way process where continuing and persistent loss of fidelity and the dropping of feature related objects or bindings is the expected and unavoidable collateral damage cost, so get over it.

Meanwhile, the ISO/IEC consideration of Ecma 376 is a diversion from where the real action is; the optimized for MSOffice OOXML Exchange/SharePoint juggernaut.

It's high noon for XML. Do you know where your ODf information processing chain is?

~ge~

Notes: The OpenDocument Foundation is working on three products that we believe to be essential to the development of an ODf Information Processing Chain that can connect desktops, servers, devices and Internet systems transitioning information based on the highly interactive and collaborative portable XML document/data model/streaming media model.

These products are still in development. What follows are the design goals and objectives:

  • daVinci ODf 1.2 Plugin for MSOffice

  • InfoSet Engine & APi

  • Interop Wizard for OpenOffice

  • ACME 376 XML-RTF Plugin for MSOffice

The daVinci ODf 1.2 Plugin:

To the best of our knowledge, daVinci continues to be the only ODf plugin for MSOffice designed to work “internally”. What happens is that daVinci triggers the internal conversion process Microsoft uses to do MSOffice conversions.

DaVinci triggers the internal process, intercepting an undocumented internal super structure we call “MS Universal RTF”, for lack of a better name. This undocumented super structure accounts for the extraordinary near perfect conversion fidelity achieved by daVinci and demonstrated by the ACME 376 plugin.

We do not believe similar conversion fidelity results can be achieved by either the MCN XSL Translator plugin approach, or the traditional “external” binary file reverse engineering approach used by OpenOffice and the Sun ODf Plugin. Which is perhaps why Microsoft themselves use this same internal process to convert legacy MS binary documents to MS OOXML.

The daVinci conversion process follows this “internal” sequence (and it'sreverse):

imbr <> MS Universal RTF <> daVinci InfoSet <> ODf 1.2

imbr :: Microsoft in-memory-binary-representation which becomes a MS Binary (dump) on save (the reverse on load).

MS Universal RTF: This is a very special structure that MSOffice uses to do all conversions from imbr to MSXML, OOXML, and RTF (the RTF the rest of the world uses).

DaVinci InfoSet: A super InfoSet structure daVinci imposes on the MS Universal RTF structure.

ODf 1.2 :: daVinci maps from InfoSet to ODf 1.0 (first daVinci version) and ODf 1.2 to produce the ODf file. The mapping mechanism could be redirected to Chinese UOF or even a subset of OOXML with some work.

The ODf 1.2 metadata RDF/XML model provides daVinci with the descriptive flexibility needed to maintain a high level of interoperability. The first version of daVinci provided to Massachusetts in June of 2006 targeted ODf 1.0 and high interoperability with OpenOffice. This came at the expense of perfect conversion fidelity and much needed round trip fidelity with the legacy of billions of MS binary document. In essence, the 85% conversion fidelity one expects from OpenOffice was exactly the same conversion fidelity delivered by daVinci ODf 1.0.

ODf 1.2 enables daVinci to hit near perfect conversion fidelity without compromising on the high level of application interoperability users expect.

The ACME 376 plugin is available for public download and testing - (the ODf 1.2 metadata RDF/XML proposal will not be completed until April of 2007). Although ACME 376 perfects a XML encoding of RTF, it demonstrates the extraordinary near perfect conversion fidelity provided by the daVinci engine.

The daVinci Plugin design objectives includes these features:

  • daVinci plugin for MSWord, Excel and PowerPoint :: MSOffice versions 1998, 2000, XP Office, XP 2003 and 2007 (note- unexpected problems with final release of MSOffice 2007)

  • Accessibility Interface installed with daVinci (tagging graphic & media objects in MSOffice with ODf 1.1 accessibility eXtensions)

  • PDF/ODF w/Digital Signatures (XML-XForms sig model) :: a combination PDF/ODF file that can be read in Acrobat, but edited in any ODf ready application given proper digital rights :: excellent for data binding, transport and extraction

  • XForms Interface for MSOffice installed with daVinci

  • Enhanced document library storage search, re use, and re purposing through the advanced ODf 1.2 metadata RDF/XML model

  • Enhanced cross platform/cross information domain application

  • interoperability through the ODf 1.2 metadata RDF/XML model

InfoSet Engine & APi:

Based on our knowledge and experience of working with the MSOffice internal conversion process, we began development on a ODf InfoSet Engine with developers APi. The objective is to provide developers, IDE's, Server-Device-Desktop Application providers and cross platform run time engines with a complete ODf conversion and layout engine that is light weight, portable, and easy to embed. Work on the “layout” engine portion has not yet begun.

The Interop Wizard for OpenOffice:

This is a plugin for OpenOffice that enables workgroup user to set either the individual document or default document settings to provide perfect interop with MSOffice desktops.

The issue here is that mixed environment workgroups (ODf Plugin MSOffice & OpenOffice desktops) will face a near insurmountable problem of round trip fidelity corruption. This has nothing to do with file formats or conversion fidelity processing, and everything to do with an issue known as layout engine impedance mismatch.

OpenOffice has a very sophisticated and complex layout engine that is optimized for the advanced presentation and use of “styles”. MSOffice on the other hand has a comparatively simple layout engine design and does not attempt to do common presentation tasks such as “table within a table”.

The layout engine mismatch limits and defines certain feature sets that make it structurally impossible to map documents between the two application suites. The “structural” problems are well known, and fall into these five categories: lists, fields, sections, page breaks, and tables.

The Interop Wizard shuts off the advanced feature sets of OpenOffice, limiting functionality to mimic near exactly the structural features of MSOffice. When the wizard is on, the advanced features are not available unless the end user overrides the warning.

43 comments:

Anonymous said...

Don't want to distract from the critical message of the article, however any idea why my attempt to print this article (Linux + Firefox 2.0) only produces two pages?

Unknown said...

Hi Frank,

Try this link: Three Stages Of Migration

Hope that helps,
~ge~

Anonymous said...

Well, you've highlighted one of the reasons why I haven't been able to get started on Office Miniatures, why I'm still considering my options.

Since I became aware of Workflow Productivity apps as opposed to simple Desktop Office Productivity apps, I have been puzzling over the right balance to give to communications aspects of the software.

Workflow gives priority to communications, while office productivity gives a secondary importance.

I've been puzzling over this for some time - it's relatively simple to hack together an Office Productivity Suite, even a miniature version a la the MS WinCE-based MS Office version. It's a bit more complex to make a Workflow OPS, but rather more interesting.

Anonymous said...

Is there a roadmap for releasing daVinci/InfoSet? This year? 2008? And is any new report of the development planned for publication? It would be interesting to hear some news of this superb project.

Anonymous said...

Hi Gary

Quoting from the article:

"there is clear evidence that MOOXML, legacy MOOXML, and now MOOXL Binary InfoSet for Excel all include eXtensions and dependencies that differ from the Ecma 376 version submitted to ISO/IEC"

Some examples or a reference please?

cheers

Unknown said...

Hi Thomas,

There was an exacting roadmap for da Vinci/InfoSet provided to Louis Gutierrez and the Massachusetts ITD in August of 2006. Those plans came crashing down in October when Louis resigned.

The public reason given for Louis' sudden and unexpected resignation was that Mass ITD had their budget totally cut off. Which is true. Microsoft's vicious lobbying resulted in the budget committee ending their session without approving Louis' budget. Pretty bad situation for sure. Especially since many of the projects left hanging involved HomeLand Security!

Incredible how far Microsoft is willing to go to have their way and continue their control over document file formats.

The thing is, the budget committee went into recess in early August!

What happened in October just prior to Louis' resignation was that he was informed by IBM and Oracle that the ODF Community effort Louis had proposed to complete the da Vinci/InfoSet plugin project collapsed. This project would have resulted in both da Vinci and InfoSet becoming open sourced and freely available. Without a budget though, Louis had little choice but to turn to IBM and Oracle to organize benefactors and fund the ODF Community effort.

The failure of ODF in Massachusetts has had a world wide impact. We believe that IBM and Oracle did everythign possible to save ODF through the open sourcing and completion of da Vinci/InfoSet. The problem we believe was with Sun. And they were a critical component in Louis' plan.

Sun's dominance of the ODF TC and their ownership of the reference implementation, OpenOffice puts them at the center of all things ODF. There was simply no way to save ODF in Massachusetts without Sun's support and cooperation.

For one thing, the conversion of existing Microsoft documents, applications and processes to a highly interoperable version of ODF required a set of "Interoperability Enhancements" we called the ODF 1.2 iX enhancements. These had to be submitted and approved by the OASIS ODF TC, which is clearly dominated and directed by Sun.

There were three ODF 1.2 iX proposals that Mass ITD signed off on. The IX eXtensions dealt directly with enhancements to ODF needed for the "perfect" high fidelity round trip conversion process demanded by MSOffice bound workgroup-workflow business processes, line of business integrated apps, and low level assistive technology add-ons.

The other aspect important to Massachusetts is that they want ed to be able to gradually integrate OpenOffice desktops into these workflows. So not only did we need Sun's support for ODF iX at the OASIS TC level, but we needed them to implement the iX enhancements in OpenOffice. And implement iX in conformance with the da Vinci MSOffice constraints.

Sun of course does not like the implementation constraints imposed by a MSOffice bound workgroup-workflow. And who would? Nobody likes to limit their application features to clone MSOffice. But that is the cost of cracking into an MSOffice bound business process.

Our position was that once these business processes could be migrated to ODF ready server Hubs, then any OpenOffice desktop could fully participate in the process.

Sadly though, there are currently no ODF ready alternatives to the Exchange/SharePoint Hub. Microsoft started transitioning MSOffice bound business processes to Exchange a few years ago, but has been uncharacteristically quiet about the success these migrations have had. Note that the MSOffice <> Exchange/SharePoint migration is 100% a OOXML-Smart Documents affair!

We will wait for the September 2nd ISO vote on OOXML before deciding what to do with da Vinci/InfoSet. Most likely, if ISO does the unthinkable and approves OOXML as an international standard, there will be zero market demand for ODF converters like da Vinci.

We'll see soon enough. No matter what happens at ISO though, the problem of the ODF iX enhancements remains. Without them, it's impossible to convert existing documents, applications and processes to ODF with the round trip fidelity demanded by MSOffice bound business processes.

For California, Massachusetts and Denmark, the reality this lack of iX enhancements leaves is that, for all practical purposes, "ODF is impossible to implement".

There are those of the opinion that the ODF iX proposals were only for the commercial benefit of da Vinci. Sinc ethe first three iX proposals were signed off on by Massachusetts ITD and CIO Louis Gutierrez, this is a stretch. Add to this that we agreed to fully open source and freely distribute both da Vinci and InfoSet in return for the funding to complete this work (funding controlled by the benefactors with MASS ITD's Timothy Vaverchak as the Project Manager), and there's simply nothing left on the bones of this mistaken allegation.

There were five major iX proposals discussed and distributed to OASIS ODF TC-SC members. We contend that the iX proposals are a necessary and unavoidable enhancement to ODF needed by any and all parties interested in high fidelity - high interoperability conversion, translation and transformation between MS documents (binary and OOXML, applications and processes. The Cleverage Translator project needs these changes. If Microsoft were to join the ODF TC they would need these eXtensions. The iX proposals are fundamental to the problem of binary<>OOXML<>ODF conversion.

On November 20th, 2006, this opinion was verified by Novell. They submitted a clone of the Foundations iX proposals needed to perfect their effort to write an OOXML plugin converter for OpenOffice as part of the Micrsoft-Cleverage Translator Project!

Sadly, the ODF iX proposals have gotten zero traction and even less support at the OASIS ODF TC.

This reluctance to consider the needs of converters and translators working the difficult area Microsoft binary documents and bound business processes has served to "hold the door open for OOXML".

The only reason there is a real world need for OOXML is the conversion of existing documents, applications and processes to XML. without ODF iX, that XML is simply not going to be ODF. It's going to be OOXML. No matter what ISO does!

The sad part of this story is that at any time in the past five years, the ODF TC could have slammed the door shut on OOXML.

The iX proposals vary from a half page to two pages of needed enhancements.

There are some interesting bookends to this story. At the very first OASIS ODF TC meeting on December 14th, 2002, an effort was made to change the proposed charter Sun had written to include as a primary objective, "compatibility with existing file formats and interoperability with existing applications". This would of course include Microsoft file formats and applications. The proposal was cut to just "compatibility with existing file formats", but Sun opposed having a vote that day. Like many other interoperability - conformance issues, it was punted far into the future.

Fast forward to July of 2007 and consider the Sun-Bosak official position statement in support of ISO approval of OOXML (DIS 29500) as an international standard:

“We wish to make it completely clear that we support DIS 29500 becoming an ISO Standard and are in complete agreement with its stated purposes of enabling interoperability among different implementations and providing interoperable access to the legacy of Microsoft Office documents.”

There you go. If you want to know who held the door open for OOXML, look no further than these bookends.

Makes one wonder about Sun's opposition to iX, and their efforts to limit ODF interoperability to not include existing MS documents, applications and processes.

How do we come up with a da Vinci roadmap when there is this huge ODF crater - with Sun and Microsoft supporting OOXML on the other side?

What happened with that 2004 Sun - Microsoft deal anyway? The one where $2 Billion dollars changed hands? I wonder if Sun traded away the universal interoperability so many have worked so hard to achieve with ODF?

~ge~

Unknown said...

Hi Anony,

Hey, nice to see you again! Thanks for taking the time to inquire. We are preparing a comprehensive document describing exactly what your wondering about. The broad stroke answer however is simple and straightforward. In MSOffice 2003 - 2007 and with the Exchange/sharePoint Hub, Smart Document components replace VAB scripts, macros and OLE functions. Smart Documents is also the data binding - script binding, metadata model for MS OOXML documents. And you won't find Smart Document in any Ecma 376 references.

Platform and application specific dependencies like Smart Documents, XAML, and proprietary .NET 3.0 libraries are "optional" in Ecma 376. Just as the legacy "Win32" dependencies and proprietary file formats (like .wmv, .emf, .emf+, .vml and DrawingML) are "optional. The difference is that when your working with MSOffice 2003 or 2007, it's near impossible to not use these dependencies. It's not "optional" at the application level.

The OOXML plugin for Novell OpenOffice, and the upcoming Sun-Novell OOXML native version of OpenOffice, are both very clean implementations of OOXML. Proving that it is possible to implement Ecma 376 as it is written. But try doing that in MSOffice 2003 or 2007! Impossible! Besides, once you send any .doc attachment to an exchange/SharePoint Server, it gets automagically converted to Vista OOXML (the forward dependencies version of OOXML). MSOffice 2007 is incredibly able to work with both legacy OOXML dependencies and Vista future dependencies.

Anyway, we are working on an examples loaded document that should answer your questions. Thanks for asking.

~ge~

Anonymous said...

Hi,
I wrote a few words about this issue. I haven't translated it yet but Google makes a good/understandable job too. ;)

OpenDocument and Interoperability

Anonymous said...

Hi Gary

Please don't stop the development of daVinci/InfoSet/OOo Interop Wizard. Make it ready with the actual ODF 1.2 enhancements (whether or not the enhancements are sufficient).

Make it Open Source.

There is a market demand for another plug-in! The stopping of ISO's OOXML fast track has shown that.

Don't let all your work be futile.

Best regards
Thomas

Unknown said...

Hi Thomas,

Thanks for the link, and taking the time to comment! Your questions to Florian certainly generated some controversy. The truth is that in the past year Florian submitted for discussion no less than five ODF iX "interoperability enhancement" proposals to the OASIS ODF TC members. Three of these iX proposals were so critical to the effort to save ODF in Massachusetts that they were signed off on by CIO Louis Gutierrez and Timothy Vaverchak, the Massachusetts ITD project manager for the ODF da Vinci plug-in.

Following the resignation of Louis Gutierrez on October 4th, 2006, we stopped all ODF development on da Vinci and InfoSet. The failure of ODF in Massachusetts was certain to have world wide percussion, as every CIO we knew of was watching. And sure enough, within days we were hearing that, "ODF is impossible to implement." Meaning, if Massachusetts couldn't do it, no one could.

With our work on da Vinci-InfoSet in limbo, Florian joined Novell. His first task there was to write the OOXML plug-in for OpenOffice. A task which we now know was vital to the deal between Novell and Microsoft. Florian was also tasked with joining the Microsoft-CleverAge OOXML-ODF Translator effort.

On November 20th, 2006 Florian submitted his fourth iX "interoperability enhancement" proposal. The interesting thing with this iX is that, even though it was designed specifically to improve conversion fidelity related to the Novell OOXML OpenOffice plug-in and Translator project, the iX needs are the same as what da Vinci needed to save ODF in Massachusetts!

People need to think about that for a moment. There is lots of talk today about harmonization and/or convergence of OOXML-ODF, coming as it does in the aftermath of the September 2007 ISO vote rejecting OOXML. Many wonder if harmonization or convergence of the two file formats is technically possible? Yet here we have clear evidence from those who slog the trenches of conversion and translation of exactly what it takes! The ODF iX "interoperability enhancement" proposals represent both what is technically needed, and, a great opportunity for the OASIS ODF TC to deliver extraordinary value to a stressed marketplace.

The iX proposals deal with application specific feature sets and implementation model differentials between MSOffice and OpenOffice. The idea that either of these two file formats, OOXML or ODF, being application independent is ridiculous. ODF was just as much designed for OpenOffice's specific features and implementation methods as OOXML for MSOffice.

When your trying to convert existing documents, applications and processes to ODF, this problem becomes very real. da Vinci pushes the ODF sanctioned use of foreign elements and alien attributes as far as possible

to meet the real world challenge of converting existing documents, applications and processes to ODF. But it's not quite enough. For the love of five simple generic elements, which represent the easy path to iX "interoperability enhancements", ODF failed in Massachusetts. And we discontinued all efforts to perfect an ODF version of da Vinci and InfoSet.

The primary reason i believe the iX proposals will not be accepted by the OASIS ODF TC anytime in the near future is that nothing goes into ODF unless and until OpenOffice agrees to support and fully implement the feature. Nothing!!!

It will be very difficult for Sun to implement and support the iX enhancements in OpenOffice because they would have to re engineer much of the OpenOffice layout engine and current feature set implementations. This is a big job. And even though Sun and Novell are currently working together on a native OOXML file format capability in OpenOffice, they won't be able to do that without these changes to the OOo layout engine.

I expect at some point we will see the OASIS ODF TC approve the iX enhancements. But it won't be for the reason of enabling the world to convert their MS documents, applications and processes to ODF!

No, we'll see the iX proposals because Sun and Novell need them as part of their effort to provide native OOXML in OpenOffice! Meaning, the document compatibility between MS binaries and xml, and, ODF depends on establishing a document structure - implementation similarity at the application levels of OpenOffice and MSOffice.

So here we have the specter of Sun and Novell working together to make it easy and free for the world to move to OOXML. IMHO, this is not good for the future of the Internet.

I do have a private document called, The Plot To Limit ODF Interop" i would be willing to share with you. It's not quite ready yet for public distribution. Basically the document outlines two distinctly different groups of big vendors, each supporting the effort to limit ODF interoperability, but for very different and diametrically opposed reasons.

The OpenDocument Foundation seeks a Universal File format that is open, unencumbered, structured and completely in line with W3C HTML-XML-RDF technologies, application-platform-vendor independent, and with an acceptable governance not under the control or influence of big vendor consortia.

Our Universal File Format must solve three problems the world must overcome if we are to take back ownership of our information and information processes:


* ..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


*..Convergence - cross platform interop
the portable XML document promise of being able to move content/data/media rich document packages across desktop - server - device and Web information systems. Another way of expressing this would be the exchange of portable XML documents with data bindings across desktop productivity environments, enterprise publication-content-archive management systems, SaaS, SOA and Web 2.0


Unfortunately, ODF was not designed for any of these problems.

MS-OOXML was designed to solve these problems, with Microsoft providing a OOXML plug-in for MSOffice to make the conversion of existing documents, applications and processes to OOXML easy, free and as non disruptive as possible.

Unfortunately the MS-OOXML end game is not that of defending the MSOffice franchise from ODF. Look at the MS-OOXML design and the emerging MS Stack of desktop, server, device, and web information systems MS-OOXML targets. It couldn't possibly be any clearer. The target of OOXML is HTML! And the Web is the prize

If ODF is unable to solve these problems, which it was never designed for, do we sit by and watch our beloved Web embraced, extended and extinguished as a platform of universal access, exchange and collaborative computing?

There is no time to lose Thomas. If we can gear da Vinci to produce HTML+, we can turn the tables on Microsoft. The trick is to neutralize MSOffice with an HTML+ version of da Vinci, solve our three problems, and enable the forces of the open Internet to fight off this threat.

When ODF is ready to play big time convergence, we'll take another look. Of course. But right now the clock is ticking and ODF can't get the big job done.

Even if ISO continues to reject MS-OOXML, the MS Stack is coming hard. And MS-OOXML-Smart Tags is the stack specific language of accelerated interoperability and integration. ISO can't stop that. The core of the MS Stack, the Exchange/SharePoint developers hub already has 65% marketshare! MSOffice bound business processes are being migrated to the E/S Hub in volumes. ISO and the supposed battle between ODF and OOXML is a side show to what's really at stake.

Besides, there is plenty of evidence indicating that Microsoft knows full well that ODF 1.2, in it's current state, will not pass ISO approval! The MS-OOXML fury and volumes of comments has resulted in an interoperability high bar at ISO that ODF will not be able to leap. We could in fact end up with both OOXML and ODF having failed as International Standards!

Thanks for your concern and hard work Thomas.

~ge~

Reference Documents:

ACME 376 :: The ODF iX Proposals and the quest for a Universal File Format

Is Sun Friend or Foe?

Donnybrook: The OASIS ODf “List Enhancement Proposal” :: Vote Details

ODF 1.2 iX History .... the "Interoperability Enhancement" Proposals

Not in the Charter! Out of Scope! :: MINUTES OF THE OASIS OPEN OFFICE XML FORMAT TC MEETING DECEMBER 16TH, 2002

eWEEK's Tiffany Maleshefski,
Office Formats Fail to Communicate.

Why Can't We All Just Get Along? Response to Tiffany Comments

Universal Interop and the World According to Marbux

Universal Interop Now!
Proposal for an OpenDocument Interoperability Framework -- Part 1

Unknown said...

Thomas, there is one other thing i should mention. Well, actually there are many many other things, but i'll stick to this one.

There were three "governments" involved in the Massachusetts da Vinci trials; California, the EU-IDABC, and Massachusetts of course. They were unanimous on a
number of points of concern, especially that there be no proprietary eXtensions to ODF.

They also wanted interoperability with OpenOffice.org.

Well, why were at it, let's let it all hang out. In June of 2006, when we presented the first version of da Vinci (we actually had to do a complete re write), Louis Gutierrez had a budgetary problem, thanks to inspired Microsoft lobbying and dirty tricks. So he came up with the idea that da Vinci - InfoSet should be open sourced and a "ODF Community Project". We agreed to this with the terms that the "ODF Community" come up with the funding to complete the da Vinci project for Massachusetts. Louis turned to IBM and Oracle, who agreed to put together the core "benefactors" for this community. The August 2006 group of benefactors IBM and Oracle came up with included Google, Intel, Novell, Sun and of course, IBM - Oracle. Strangely, other companies such as Red Hat, Linspire, Canonical and CA were cut off the benefactors list.

In early October of 2006, Louis was notified by IBM and Oracle that the benefactors group could not be formed. Louis resigned shortly afterwards. The scuttlebutt that came back to us was that Sun refused to participate, opting instead to provide their own plug-in. This in spite of the fact that the trials demonstrated OpenOffice.org conversion fidelity was not good enough, and round tripping a non starter.

So saving ODF in Massachusetts involved three challenges.

The first is that we had to re write da Vinci to hit the same high fidelity "round trip" conversion the OOXML plug-in delivered.

Second, we had to pull of this "round trip" fidelity with OpenOffice.org in the interop mix.

Third, we had the ODF Community stuff to deal with.

The first challenge was thought to be impossible, but that turned out to be the only one we hit! The problem is that we needed the iX enhancements, and, OOo support of those iX enhancements.

The cooperation of Sun of course figures prominently in each challenge.

In July - early August of 2006 our CTO Florian Reuter submitted three ODF iX "interoperability enhancement" proposals to OASIS ODF members for discussion. These were signed off on by Louis Gutierrez and project manager Timothy Vaverchak. Two other iX proposals were submitted by Florian Reuter in November 2006 and February of 2007.

The reception of the iX "interoperability enhancements", including the changes to the Conformance Clause, was beyond discouraging. Many of my closest friends at OASIS even accused us of promoting iX for application specific - market splitting profit.

By April of 2007, i had had enough of Sun, OASIS and ODF. Given the problem set we seek to solve, there is no way we can implement ODF. It simply isn't designed to meet the three challenges of a universal file format; compatibility with existing documents, interoperability with existing applications, and the great convergence of desktop, server, device and web information systems. And there is no appetite or desire at OASIS to fix ODF. For us, the door was slammed shut.

We will however make one last contribution to ODF, which hopefully you'll see soon. There is an incredible problem for ODF 1.2 brewing at ISO. The MS-OOXML Donnybrook has raised the high bar, and ODF 1.2, in it's current state, cannot meet ISO "interoperability" demands. In fact, we found a secret ISO Directive issued in May of 2006, refusing a JTC1 - Sun request that an "interoperability" exception be granted for ODF 1.0!!!!

The OASIS ODF TC has never been made aware of this ISO Directive refusing to grant ODF an exception. So ODF 1.1 and ODF 1.2 have gapping show stopping holes. There is no way ODF 1.2 can be approved by ISO unless we fix the current Conformance Clause. Something Sun is quite reluctant to consider.

The February Ballot Resolution Committee may of may not be able to fix MS-OOXML. But shortly after this ISO effort, ODF 1.2 will come up for consideration.

Unless we do something now, there is the distinct possibility that both MS-OOXML and ODF 1.2 will end up being rejected by ISO! Leaving the marketplace without a standard.

And don't kid yourself. We kept this story quiet until after the September 2nd ISO vote on MS-OOXML.

~ge~

Unknown said...

広島 不動産
岡山 不動産
国際協力
高知 不動産
結婚相談所 東京
婚約指輪
結婚指輪
浮気調査
賃貸
募金

Anonymous said...

shanghai hotel
guangzhou hotel
shenzhen hotel
beijing hotel
china hotel
guangzhou hotel
shenzhen hotel
shanghai hotel
beijing hotel
回转支承
转盘轴承
slewing ring
slewing bearing
slewing bearings
slewing ring
slewing bearing
slewing bearings

Anonymous said...

The 3 stages of CMS: Boris Mann of Raincity Studios made a presentation on mid-February that just got posted on DigitalAssetManagementOrgUK (lots of nice educational links there, and some tools), and it does set out very clearly some principles and ideas, aimed at independent web developers, that are not just right but (for me) becoming articles of faith. It’s about the evolution of web sites into complex interconnected bits, and how best to make them. Sage, too.

Anonymous said...

名刺作成
格安 名刺
不動産
価格
価格比較
賃貸

Anonymous said...

杭州装修公司
杭州店面装修
杭州办公室装修
杭州装饰公司
杭州装饰公司

蜂王浆
芦荟
蜂胶
蜂王浆
芦荟
蜂胶

ball valve球阀
gate valve闸阀
angle valve角阀
bibcock水嘴
tap
Check valve
hot-water heating
fittings
苏州led
上海led
北京led
苏州电磁铁
苏州装修公司
苏州装饰公司
ats
ATS生产
ats
ATS开关

Anonymous said...

cマンション 買取 1戸建て 査定 1戸建て 買取 SEO対策 福岡 賃貸 車買取 自動車保険 バイク買取 美容整形 労働問題 収益物件不動産売却などにはマンション査定土地売買1戸建て売却が含まれる。 物件探しは広島 不動産 岡山 不動産 松山市 不動産 香川県 不動産 徳島 不動産 高知 不動産 高松 不動産をフルカバーしてます大手で 和歌山 富山 滋賀 石川 山梨 新潟 沖縄 大分 鹿児島 宮崎 熊本 高知

Anonymous said...

不動産 投資 新築マンション インプラント 広島 引越し マンション 売却 不動産 査定 不動産 売買 広島 賃貸 システム開発 土壌汚染 webシステム開発 土地 買取 不動産会社 ホームページ制作 賃貸 長野不動産富山不動産石川不動産福井不動産愛知不動産岐阜不動産三重不動産兵庫不動産滋賀不動産奈良不動産和歌山不動産鳥取不動産島根不動産山口不動産徳島不動産香川不動産愛媛不動産高知不動産佐賀不動産長崎不動産大分不動産宮崎不動産沖縄不動産 ホームページ制作 東京 原油 賃貸

Anonymous said...

pA片,A片,成人網站,成人漫畫,色情,情色網,情色,AV,AV女優,成人影城,成人,色情A片,日本AV,免費成人影片,成人影片,SEX,免費A片,A片下載,免費A片下載,做愛,情色A片,色情影片,H漫,A漫,18成人

a片,色情影片,情色電影,a片,色情,情色網,情色,av,av女優,成人影城,成人,色情a片,日本av,免費成人影片,成人影片,情色a片,sex,免費a片,a片下載,免費a片下載

情趣用品,情趣用品,情趣,情趣,情趣用品,情趣用品,情趣,情趣,情趣用品,情趣用品,情趣,情趣

A片,A片,A片下載,做愛,成人電影,.18成人,日本A片,情色小說,情色電影,成人影城,自拍,情色論壇,成人論壇,情色貼圖,情色,免費A片,成人,成人網站,成人圖片,AV女優,成人光碟,色情,色情影片,免費A片下載,SEX,AV,色情網站,本土自拍,性愛,成人影片,情色文學,成人文章,成人圖片區,成人貼圖

情色,AV女優,UT聊天室,聊天室,A片,視訊聊天室

Anonymous said...

toefl  
不動産投資
個別指導塾

Anonymous said...

toefl  
不動産投資
個別指導塾

Anonymous said...

会社設立
債務整理
ワンクリック詐欺
東京 マッサージ
薬剤師 求人
クレジットカード 海外旅行保険

Anonymous said...

アメリカンホームダイレクト: Estimates easily auto insurance risk-segmentation. Support for compensating the content on the website. Benefits are also available with special rates for hotel and leisure facilities, offering various services.

Anonymous said...

蜂王浆
芦荟
蜂胶

ball valve球阀
gate valve闸阀
angle valve角阀
bibcock水嘴
tap
Check valve
hot-water heating
fittings
苏州led
上海led
北京led
苏州电磁铁
苏州装修公司
苏州装饰公司
ats


双电源切换开关
双电源转换开关
双电源开关

乐清网站建设.
乐清网站推广.

Anonymous said...

名刺 ne2ying
ショッピングカート 3ying
探偵 感觉4ying
お見合いパーティー jepying

Anonymous said...

toefl
幼児教室
合宿 免許

Anonymous said...

免費a片卡通免費a片卡通免費a片卡通免費a片卡通免費a片卡通免費a片卡通免費a片卡通免費a片卡通免費a片卡通作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞作愛影片免費觀賞a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 a片看小電影頻道 免費av影片下載免費av影片下載免費av影片下載免費av影片下載免費av影片下載免費av影片下載免費av影片下載免費av影片下載免費av影片下載免費av影片下載a片短片試看a片短片試看a片短片試看a片短片試看a片短片試看a片短片試看a片短片試看a片短片試看a片短片試看a片短片試看免費 a 長片線上看aa片免費看微風論壇080哈啦聊天室6k聊天室成人聊天室上班族捷克論壇大眾論壇plus論壇080視訊聊天室520視訊聊天室尋夢園上班族聊天室成人聊天室上班族 a片a片影片免費情色影片免費a片觀看小弟第貼影片區免費av影片免費h影片試看 H漫 - 卡通美女短片小魔女貼影片免費影片觀賞無碼a片網美女pc交友相簿美女交友-哈啦聊天室中文a片線上試看免費電影下載區免費試看a短片免費卡通aa片觀看女優影片無碼直播免費性感a片試看日本AV女優影音娛樂網日本av女優無碼dvd辣妹視訊 - 免費聊天室美女交友視訊聊天室080免費視訊聊天室尋夢園聊天室080苗栗人聊天室a片下載日本免費視訊美女免費視訊聊天

Anonymous said...

看房子,買房子,建商自售,自售,台北新成屋,台北豪宅,新成屋,豪宅,美髮儀器,美髮,儀器,髮型,EMBA,MBA,學位,EMBA,專業認證,認證課程,博士學位,DBA,PHD,在職進修,碩士學位,推廣教育,DBA,進修課程,碩士學位,網路廣告,關鍵字廣告,關鍵字,廣告,課程介紹,學分班,文憑,牛樟芝,段木,牛樟菇,日式料理, 台北居酒屋,燒肉,結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,台北住宿,國內訂房,台北HOTEL,台北婚宴,飯店優惠,台北結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,住宿,訂房,HOTEL,飯店,造型系列,學位,牛樟芝,腦磷脂,磷脂絲胺酸,SEO,婚宴,捷運,學區,美髮,儀器,髮型,牛樟芝,腦磷脂,磷脂絲胺酸,看房子,買房子,建商自售,自售,房子,捷運,學區,台北新成屋,台北豪宅,新成屋,豪宅,學位,碩士學位,進修,在職進修, 課程,教育,學位,證照,mba,文憑,學分班,網路廣告,關鍵字廣告,關鍵字,SEO,关键词,网络广告,关键词广告,SEO,关键词,网络广告,关键词广告,SEO,台北住宿,國內訂房,台北HOTEL,台北婚宴,飯店優惠,住宿,訂房,HOTEL,飯店,婚宴,台北住宿,國內訂房,台北HOTEL,台北婚宴,飯店優惠,住宿,訂房,HOTEL,飯店,婚宴,台北住宿,國內訂房,台北HOTEL,台北婚宴,飯店優惠,住宿,訂房,HOTEL,飯店,婚宴,結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,台北結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,台北結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,台北結婚,婚宴場地,推車飲茶,港式點心,尾牙春酒,居酒屋,燒烤,美髮,儀器,髮型,美髮,儀器,髮型,美髮,儀器,髮型,美髮,儀器,髮型,小套房,小套房,進修,在職進修,留學,證照,MBA,EMBA,留學,MBA,EMBA,留學,進修,在職進修,牛樟芝,段木,牛樟菇,住宿,民宿,飯宿,旅遊,住宿,民宿,飯宿,旅遊,住宿,民宿,飯宿,旅遊,住宿,民宿,飯宿,旅遊,住宿,民宿,飯宿,旅遊,住宿,民宿,飯宿,旅遊,住宿,民宿,飯宿,旅遊,美容,美髮,整形,造型,美容,美髮,整形,造型,美容,美髮,整形,造型,美容,美髮,整形,造型,美容,美髮,整形,造型,美容,美髮,整形,造型,美容,美髮,整形,造型,設計,室內設計,裝潢,房地產,設計,室內設計,裝潢,房地產,設計,室內設計,裝潢,房地產,設計,室內設計,裝潢,房地產,設計,室內設計,裝潢,房地產,設計,室內設計,裝潢,房地產,設計,室內設計,裝潢,房地產,設計,室內設計,裝潢,房地產,進修,在職進修,MBA,EMBA,進修,在職進修,MBA,EMBA,進修,在職進修,MBA,EMBA,進修,在職進修,MBA,EMBA,進修,在職進修,MBA,EMBA,進修,在職進修,MBA,EMBA,進修,在職進修,MBA,EMBA

Anonymous said...

電報
op
iop
uy
ent
you
qwo
wer
to
for
live
hi
sky
per
cou
xie
wei
shi
look
enw
up
here
go
hom
hous
gucl
shunk
cona
netbol
saish
town
yeawo

Anonymous said...

=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=

Anonymous said...

Anonymous said...

Do you know that the mabinogi gold, and do you want to know? In the game many palyers need the mabinogi money to up their levels. so they often search where can buy the cheap mabinogi, I think our website is your choice. Many friends told me that in here can buy mabinogi gold, and you will also practice your online games skills. So i hope more and more players come here to buy the mabinogi online gold.

Do want to know the magic of online games, and here you can get more maple mesos. Do you want to have a try? Come on and mesos can make you happy.You can change a lot cheap mesos for play games. Playing online games can make much maplestory mesos. If you want your game level to up highly, you can come here. And you can use the maple story mesos do what you want to do in the online game.

Anonymous said...

buy wow goldAsesor ProfessionalUruguayProfessionalbuy wow goldOfficeLinksNotice

Anonymous said...

Do you know eve isk? I like it.
My brother often goes to the internet bar to buy eve online isk and play it.
After school, He likes playing games using these buy isk with his friend.
I do not like to play it. Because I think that it not only costs much money but also spend much time. One day, he give me many cheap eve isk and play the game with me.
I came to the bar following him and found buy eve online isk was so cheap. After that, I also go to play game with him.

Do you know fiesta Gold? I like it.
My brother often go to the internet bar to buy fiesta money and play it.
After school, He likes playing games using these fiesta online gold with his friend.
I do not like to play it. Because I think that it not only costs much money but also spend much time. One day, he give me many buy fiesta Gold and play the game with me.
I came to the bar following him and found fiesta online money was so cheap. After that, I also go to play game with him.

Anonymous said...

Have you heared about a game which you need use kal geons to play, and you can also borrow kal gold from other players? But you can buy kal online geons, or you will lose the choice if you do not have kal online gold. If you get kalonline Geons, you can continue this game.
Have you heared about a game which you need use shadow of legend Gold to play, and you can also borrow sol gold from other players? But you can buy shadow of legend Gold, or you will lose the choice if you do not have cheap shadow of legend Gold. If you get shadow of legend Gold money, you can continue this game.

Anonymous said...

What do you know angels gold. And do you want to know? You can get angels online gold here. And welcome to our website, here you can play games, and you will buy angels gold to play game. And it is very interesting. Do you want a try, come and view our website, and you will learn much about cheap angels online gold. Come and join with us. We are waiting for your coming.
What do you know Rose zuly. And do you want to know? You can get rose zulie here. And welcome to our website, here you can play games, and you will get rose online zuly to play game. I know rose online zulie, and it is very interesting.Do you want a try, come and view our website, and you will learn how to Arua ROSE zuly. Come and join with us. We are waiting for your coming.

Anonymous said...

they are like me and tell me anything about them wakfu kamas, I know wakfu gold. one of my friend likes to go to play buy wakfu kamas, I can not stand praising the land and the nature wakfu money , It makes us to be wakfu kama.
Do you know seal cegel? I like it.
My brother often go to the internet bar to buy sealonline cegel and play it.
After school, He likes playing games using these seal online cegel with his friends.
I do not like to play it. Because I think that it not only costs much money but also spend much time. One day, he give me many cheap seal cegeland play the game with me.
I came to the bar following him and found buy seal online cegelwas so cheap. After that, I also go to play game with him.

Anonymous said...

劉家肉粽韓國總統盧武鉉海賊王漫畫黃海寧部落格暮光之城結局無名正妹牆跑跑卡丁車官方98基測錄取pr值skype 中文版下載kmplayer繁體中文版下載PPS網絡電視下載Photoshop免費下載照片的眼睫毛製作方法98基測錄取pr值skype 中文版下載kmplayer繁體中文版下載PPS網絡電視下載Photoshop免費下載吳亭欣 blog挪亞方舟歌詞tvb 劇集show girl 張維庭王尹平真空 v薇琪性感照sweety 劉品言曾之喬陳亭妃 wiki呂韻季blog女駭客陳師迪林奇葳 wretch天使的跪座疣柄魔芋glamorous 平子理沙全慧珍圖片涂醒哲 sars關淑怡 mv吉娃娃達人林順輝吳亭欣 33c

Anonymous said...

戈偉如的部落格|劉玉璞部落格|星座運勢|雙子座男人|超級偶像張芸京陳雅倫影片危情台南月老廟五月天演唱會博物館驚魂夜2
bt
最新電影下載|博物館驚魂夜2bt|小女神花鈴漫畫|航海王One Piece|數碼暴龍圖鑑|最新動漫遊戲下載薇琪性感照|
show girl 張維庭|sweety 劉品言曾之喬|“鄭尚宮”呂韻季|陳亭妃 wik|全慧珍結婚|陳師迪部落格|天使的跪座|王尹平真空 v|平子理沙寫真|疣柄魔芋|關淑怡 mv|林順輝blog|涂醒哲 sars|孫樂欣 and 馮媛甄|黃海寧部落格|天母 sogo百|五股基隆冰雹

Anonymous said...

free poker bankroll no deposit bonuses Get your FREE POKER MONEY. Poker room's that offers gratis money for fun.
poker no deposit needed cash bonus or bonuses is like heaven for many poker players who play gaiming texas holdem rules.
free $50 $150 bankroll $30 starting capital +$120 bonus, refresh that obligatory tables.
sites construction fast - bonus growing level high - storage or boring.
bonuses without deposit, global worm poker finder and frerolls for your career to ending many options, poker portals free money.
Some online poker sites that have freeroll ant free sponsorship wtop tours where you don't need to make any deposit to enter
no quiz no deposit bonus, bonuses without deposit Chips brings you all the very latest no deposit poker offers. ... Promotion, $10 with no deposit requred at all sharks.
free poker cash and bonus titker rooms, so youound poker ...
free $50 no deposit online poker made for you a selection of the best poker deposit. create account is very simple.
free poker bankroll no deposit. for you to cash this bonusses: You only have to download the software and install on your computer and play internet gambling.
bonus no deposit required free
bonuses without deposit bankrolls eligible to your country.

Anonymous said...

. . . . . . . . . . . . . . . . . . . . . . . . . . good,very good!

Anonymous said...

賃貸

seoツール

育毛剤

leather

SEO对策

受託開発

seoツール

炊飯器 比較

掃除機比較

価格 マウス

プリンタ 価格

パソコン 価格

格安 カーナビ

市川市 不動産

スピーカー 比較

コラーゲン 美肌

食べ放題 六本木

アルカリイオン水

保土ヶ谷 不動産

江戸川区 不動産

川崎市幸区 不動産

ノート パソコン 価

自動車教習所 東京

ウォーター サーバー

日本ITブログポータルサイト

心情部落格 said...

星座星座星座
星座運勢星座運勢星座運勢
12星座12星座12星座
星座星座星座
星座配對星座配對星座配對
星座運勢星座運勢星座運勢
星座排名星座排名星座排名
愛情運勢愛情運勢愛情運勢
愛情配對愛情配對愛情配對
減肥餐減肥餐減肥餐
異性緣異性緣異性緣
黃金價格黃金價格黃金價格
金價金價金價
食譜食譜食譜
美食美食美食
心理測驗心理測驗心理測驗
2010虎年2010虎年2010虎年
2010生肖運勢2010生肖運勢2010生肖運勢
虎年財運虎年財運虎年財運
生肖財運生肖財運生肖財運