Jaxer is the world's first true Ajax server.
HTML, JavaScript, and CSS are native to Jaxer, as are XMLHttpRequests, JSON,
DOM scripting, etc.
And as a server it offers access to databases, files, and networking, as well as logging,
process management, scalability, security, integration APIs, and extensibility.
Harmonizing ODF and OOXML: The DIN - ISO "Harmonization" Project - 0 views
-
Contact: Gerd Schürmann Fraunhofer Institute FOKUS Tel +49 (0)30 3463 7213 gerd.schuermann@fokus.fraunhofer.de Berlin
-
At a recent meeting in Berlin, The DIN Fraunhoffer Institute pushed forward with the EU project to harmonize ODF and OOXML. Microsoft and Novell attended the harmonization effort. Sun and IBM did not. This in spite of invitations and pleas to cooperate coming into Sun and IBM from government officials across the European continent. We've long insisted that inside the OASIS ODF Technical Committee walls there have been years of discussions concerning ODF compatibility with the billions of MS binary documents, and ODF interoperability with MSOffice. Sun in particular has been very clear that they will not compromise OpenOffice application innovations to improve interoperability with MSOffice and MSOffice documents. The infamous List Enhancement Proposal donnybrook that dominated OASIS ODF discussions from November 20th, 2006, to the final vote in April of 2007, actually begins with a statement from Sun arguing that application innovation is far more important than market demands for interoperability. The discussions starts here: Suggested ODF1.2 items The first of many responses declaring Sun's position that innovation trumps interop, and that if anyone needs to change their application it should be Microsoft: see here DIN will submit a "harmonization" report with recommendations to ISO JTC1. I wonder if IBM and Sun will continue to insist on government mandated "rip out and replace" solutions based on their ODF applications when ISO and the EU have set a course for "harmonization"?
Aptana Jaxer | Aptana - 0 views
Q&A: Nicholas Carr on the big switch to utility computing - 0 views
-
I think we’re at the early stages of a fundamental shift in the nature of computing, which is going from something that people and businesses had to supply locally, through their own machines and their own installed software, to much more of a utility model where a lot of the computer functions we depend on are supplied from big, central stations, big central utilities over the Internet.
Issue 51726: OpenOffice ODF Graphics Nightmare - 0 views
-
Currently, the above given specification is a draft and has to be adjusted. Beside the change of the context menu and the navigator it's is needed to adjust the import of the XML file formats (OpenDocument and OpenOffice.org) and the export to the OpenOffice.org file format. The import needs adjustment, because the existence of name is used to distinguish Writer graphics/text boxes and Draw graphics/text boxes. The new criterium is now, that Draw graphics/text boxes of Writer documents doesn't have a parent style. The export to the OpenOffice.org file format needs adjustment, because a Writer document in the OpenOffice.org file format doesn't contain names for shapes.
-
The EU DIN effort to harmonize or merge ODF and OOXML has uncovered some incredible inconsistencies in OpenOffice ODF tht will break interop every time, guaranteed. This particular issue has to do with problems naming graphics, and the hack solution now in use. It's hacks like this that make it impossible to convert MSOffice binaries to ODF.
-
» Government turns to SaaS to salvage IT failures | IT Project Failures | ZDN... - 0 views
-
As Administrator of E-Government and Information Technology, for the Office of Management and Budget, Evans oversees the government’s CIO Council, comprised of Chief Information Officers from various agencies. In September, 2007, she testified before the Senate, about high-risk IT projects:
[office] The infamous list-override list enhancement proposal - 0 views
-
Well, I think the problem we face is that there are different interpretations of the 1.1 specification regarding the numbering of numbered paragraphs that have different list styles assigned. We therefore cannot say that the one or the other proposal is backward-compatible to the ODF 1.1 specification regarding the number or the style. We can only say whether it is backward-compatible to a certain _interpretation_ of the ODF 1.1 specification regarding the number or the style.
A Closer Look At Those "Single Standard" Policy Mandates : Oliver Bell's weblog - 0 views
-
2. Achieving interoperability is rarely as straight forward as selecting a single technical standard, and many of the policy positions around the world recognize this. Applications need to be designed to work together, groups need a solid framework for collaboration and the standards need to be ready to support these two objectives.
» Getting enveloped by the potential of Cloud computing | Web 2.0 Explorer | ... - 0 views
-
By taking a fundamentally Web-based approach to the development of applications, we shift from bolting Web capabilities onto the silo toward a mode in which data and functionality are native to the Web: a mode in which the design decisions are more about modelling business requirements for limiting the ways in which data flows from one point to another rather than trying to anticipate the places in which it might be needed in order to design those pathways into software from the outset.
-
How do we change the mindset of today’s application developers, in order that they stop building ‘old’ applications in the new world?
IBM to take Lotus Symphony apps 'Beyond Office' | Tech news blog - CNET News.com - 0 views
-
Under a strategy called "Beyond Office," IBM is developing several technologies to make Symphony an extensible development platform for business applications and Web-based document editors. Rather than compete head-to-head with Microsoft Office, IBM's strategy is to make documents act like "containers" for information within workflow and collaboration applications, according to IBM executives. The plan also calls for IBM to make documents based on the Open Document standard available through Web browsers using Adobe Flash or HTML. On Wednesday, IBM opened a Web site called Bluehouse where small business people can access hosted Web applications for sharing documents.
IBM's Stance Against OpenXML Is Increasingly Confusing : Oliver Bell's weblog - 0 views
-
Events have played out in the media and in the blogosphere over the last couple of weeks that represent a breakdown of some of those anti-OpenXML arguments that have been played back so frequently over the last year. Arguments that there is a lack of demand for Open XML, the specification is too complex to implement, the specification can’t be deployed cross platform and the long running but baseless claim that the Ecma-376 specification might be encumbered by IPR and patent threats all appear to have been cast aside as big blue steps up to meet the demands of their own customers and the market in general. Here is a blow by blow review of the relevant activity over the last two weeks…
IBM's Director of Strategy comes clean on OpenXML - IBM *WILL* support OpenXML in its L... - 0 views
-
Well, if that's IBM's plan they're going to need more than ODF, that's for sure - and that brings us to the announcement I've been wondering about: IBM favors ODF as a file format because it is "truly open" and technically elegant, Heintzman said. But IBM will support Open XML, which is the current document format in Office 2007, in its Lotus collaboration and portal products. IBM already supports older versions of Office. I feel a Pamela Jones moment coming on .... there it is, as plain as day for the world to see, Doug Heintzman breaks through all IBM's doublespeak and hypocrisy and admits it. I don't know about "Beyond Office" as a plan, I think the real game here is "Beyond ODF"
A pox on both your houses! | Independent study advises IT planners to go OOXML - 0 views
-
What you've posted are examples of MSOffice ”compatibility settings” used to establish backwards compatibility with older documents, and, for the conversion of alien file formats (such as various versions of WordPerfect .wpd). These compatibility settings are unspecified in that we know the syntax but have no idea of the semantics. And without the semantic description there is no way other developers can understand implementation. This of course guarantees an unacceptable breakdown of interoperability. But i would be hesitant to make my stand of rejecting OOXML based on this issue. It turns out that there are upwards of 150 unspecified compatibility settings used by OpenOffice/StarOffice. These settings are not specified in ODF, but will nevertheless show up in OpenOffice ODF documents – similarly defying interoperability efforts! Since the compatibility settings are not specified or even mentioned in the ODF 1.0 – ISO 26300 specification, we have to go to the OOo source code to discover where this stuff comes from. Check out lines 169-211. Here you will find interesting settings such as, “UseFormerLineSpacing, UseFormerObjectPositioning, and UseFormerTextWrapping”.
Can IBM save OpenOffice.org from itself? - 0 views
-
In e-mailed comments, Heintzman said his criticisms about the situation have been made openly. "We think that Open Office has quite a bit of potential and would love to see it move to the independent foundation that was promised in the press release back when Sun originally announced OpenOffice," he said. "We think that there are plenty of existing models of communities, [such as] Apache and Eclipse, that we can look to as models of open governance, copyright aggregation and licensing regimes that would make the code much more relevant to a much larger set of potential contributors and implementers of the technology.... "Obviously, by joining we do believe that the organization is important and has potential," he wrote. "I think that new voices at the table, including IBM's, will help the organization become more efficient and relevant to a greater audience.... Our primary reason for joining was to contribute to the community and leverage the work that the community produces.... I think it is true there are many areas worthy of improvement and I sincerely hope we can work on those.... I hope the story coming out of Barcelona isn't a dysfunctional community story, but rather a [story about a] potentially significant and meaningful community with considerable potential that has lots of room for improvement...."
-
Heintzman must be referring to the Rob Weir -OASIS ODF Adoption (cough marketing-lobbying) TC event called the "ODF Interoperability Workshop". This was a day long event demonstrating for all the world to see that there is no such thing as ODF interoperability. The exchange of documents between OpenOffice 2.0, KOffice and Lotus Symphony is pathetic. The results of the day long event were so discouraging that Rob Weir took to threatening developers who attended in his efforts to keep a lid on it. I think this is called damage control :). From what i hear, it was a very long day for Rob. but that's no excuse for his threatening anyone who might publicly talk about these horrific interop problems. The public expects these problems to be fixed. But how can they be fixed if the issues can't be discussed publicly?
-
Lotus Symphony is based on the OpenOffice 1.1.4 code base that IBM ripped off back when OpenOffice was under dual license - SSSL and LGPL.
office by thread - 0 views
-
[Fwd: clarification: OpenDocument and SVG] From Lars Oppermann <Lars.Oppermann@Sun.COM> on 2 Feb 2005 10:31:44 -0000 Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer <Michael.Brauer@Sun.COM> on 2 Feb 2005 12:16:44 -0000 Message not available. Message not available. Message not available. Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 10:14:18 -0000 Message not available. Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 14:01:24 -0000 Propsal regarding the use of the SVG namespace in OpenDocument From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 13:49:10 -0000 Use of SVG namespace From Patrick Durusau <Patrick.Durusau@sbl-site.org> on 7 Feb 2005 13:34:56 -0000
-
Hello Jesper .... this is what you are looking for. The very contentious exchange of messages between the W3C SVG Workgroup, and the OASIS ODF TC. The issue at stake is the W3C namespace highjacking by the OASIS ODF TC.
-
Re: [office-comment] Public Comment - 0 views
-
Regarding section 1.5 itself: The Open Office TC decided to use the term MAY rather than MUST (or will) at the mentioned location, because it wanted to ensure that the OpenDocument specification can be used by as many implementations as possible. This means that the format should also be usable by applications that only support a very small subset of the specification, as long as the information that these applications store can be represented using the OpenDocument format. A requirement that all foreign elements and attributes must be preserved actually would mean that some applications may not use the format, although the format itself would be suitable. Therefor, we leave it up to the implementations, which elements and attributes of the specification they support, and whether they preserve foreign element and attributes. Some more information about this can be found in appendix D of the specification.
-
This OASIS ODF discussion is about the Compliance - conformance clause of the ODF specification: Section 1.5. A developer has complained that use of MAY instead of MUST in the wording of the clause would enable conforming applications to destroy foreign elements and alien attribute markup at will. This of course would result in ZERO Interoeprability!!!!! The foreign elments and alien attributes were included for the purposes of improved ODF compatibility with the billions of MSOffice binary documents that would need to be converted to ODF. Sadly, the section 1.5 loop hole falls short of the compatibility goal, but that only begins to scratch the surface of the ODF problems. OpenOffice only supports foreign elements and alien attributes for text spans, and paragraphs!!!!!! All other such markup is unrecognized and therefore "destroyed" by OpenOffice. ZERO interop. No roundtripping with MSOffice desktops. Lossy conversion with jagged fidelity. Guaranteed.
-
Independent study advises IT planners to go OOXML - 0 views
-
From: Bill Gates Sent: Saturday, December 5 1998 To: Bob Muglia, Jon DeVann, Steven Sinofsky Subject : Office rendering "One thing we have got to change in our strategy - allowing Office documents to be rendered very well by other peoples browsers is one of the most destructive things we could do to the company. We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities. Anything else is suicide for our platform. This is a case where Office has to avoid doing something to destroy Windows. I would be glad to explain at a greater length. Likewise this love of DAV in Office/Exchange is a huge problem. I would also like to make sure people understand this as well." Tuesday, August 28, 2007
-
3.2.2.2. A pox on both your houses! gary.edwards - 01/22/08 Hi Robert, What you've posted are examples of MSOffice ”compatibility settings” used to establish backwards compatibility with older documents, and, for the conversion of alien file formats (such as various versions of WordPerfect .wpd). These compatibility settings are unspecified in that we know the syntax but have no idea of the semantics. And without the semantic description there is no way other developers can understand implementation. This of course guarantees an unacceptable breakdown of interoperability. But i would be hesitant to make my stand of rejecting OOXML based on this issue. It turns out that there are upwards of 150 unspecified compatibility settings used by OpenOffice/StarOffice. These settings are not specified in ODF, but will nevertheless show up in OpenOffice ODF documents – similarly defying interoperability efforts! Since the compatibility settings are not specified or even mentioned in the ODF 1.0 – ISO 26300 specification, we have to go to the OOo source code to discover where this stuff comes from. Check out lines 169-211. Here you will find interesting settings such as, “UseFormerLineSpacing, UseFormerObjectPositioning, and UseFormerTextWrapping”. So what's going on here?
-
..... response to Robert Crocker concerning Mary Jo's article, "Independent study advises IT planners to go OOXML". 3.2.2. So this is well documented? Robert Crocker - 01/14/08 : Mind explaining these functions to us then? - Section 2.15.3.6 page 2161, autoSpaceLikeWord95. - Section 2.15.3.26 page 2199, footnoteLayoutLikeWW8. - Section 2.15.3.31 page 2209, lineWrapLikeWord6. - Section 2.15.3.32 page 2210, mwSmallCaps. - Section 2.15.3.41 page 2225, shapeLayoutLikeWW8. - Section 2.15.3.51 page 2245, suppressTopSpacingWP
-
A gadfly's take on IBM's 'support' for Open XML | Computerworld Blogs - 0 views
-
On the revelation that some of IBM's products would support a document format that it officially, adamantly opposes, Hiser is not surprised one bit. IBM and Sun have both had "the magic blueprints" to Microsoft's document formats, including Open XML, for the past several years, Hiser said. With that key technical interoperability information, "how could you not expect IBM to start coding around OOXML?" he asked.
-
Right on Sam!
-
Podcast: ODF, OOXML and CDF .... The OpenDocument Foundation Responds | Between the Lin... - 0 views
-
David continues his deep dive into the curious case of the OpenDocument Format and the OpenDocument Foundation.
-
Dragged through the mud
« First
‹ Previous
201 - 220 of 523
Next ›
Last »
Showing 20▼ items per page
