[Linux-aus] [Noooxml] ebxml transactional oasis specification

Glen Turner gdt at gdt.id.au
Mon Aug 13 07:02:54 UTC 2007


On Sun, 2007-08-12 at 15:35 +0200, Alberto Barrionuevo wrote:
> El Domingo, 12 de Agosto de 2007 15:14, Janet Hawtin escribió:
> > In the Australian meeting the Microsoft team referred to paragraph two
> > about transactions and said this was what made their proposal
> > different.
> > He gave an example of having a paper form which interfaced with bank
> > transactions.

You've got to understand where Microsoft is coming from here. 

They need to show that OOXML doesn't cover the same field of
endeavour as ODF. This is a massive comment against OOXML,
since it is unlikely that a ISO Ballot Resolution Meeting
would achieve consensus on resolutions to this comment and
OOXML would stall, perhaps forever.

The ECMA Charter for OOXML mentions words to the effect of
"line of business systems" -- the ODF charter does not.

So it's a simple and cheap point to say that the difference
in Charters implies that OOXML is designed for easy interfacing
to business systems and, by implication, ODF isn't.
The point being that ISO should resolve the comment by
allowing OOXML to proceed because it covers a wider field
of application than ODF.

Of course, ODF is actually the more easily integrated with
e-business systems than OOXML. But explaining that takes
a great deal of technical detail.

But it's a political argument and probably needs a political
response for the audience to get the point.   Here it is:

ODF was designed by OASIS. OASIS are the industry standards
body responsible for e-business interworking. They designed
the whole family of e-business protocols --- ebXML, SOA, SAML.
It would be remarkable if OASIS designed ODF not to interwork
with its e-business protocols.  And natually, ODF was designed
to do so. This requirement was unusual for ECMA, so it was
highlighted in the Charter. This requirement was part of
very air OASIS breathed and so did not need to be highlighted
in a Charter but is listed in the "use case and requirements"
documents.





More information about the linux-aus mailing list