Artikel zum neuen Office Dateiformat:

“Directions on Microsoft” Report on Open XML formats http://www.directionsonmicrosoft.com/sample/DOMIS/update/2007/01jan/0107nffio2.htm

..Office 2007 won't support some old features

A list of potential Office compatibility problems is at technet2.microsoft.com/Office/en-us/library/9a753419-726c-422b-9863-7dfaf2f522c21033.mspx.

The file formats used in Office 2003 and previous versions are still available in the 2007 Office release...

Overview of the file formats in the 2007 Office system

Compatibility Mode capabilities and limitations are summarized at technet2.microsoft.com/Office/en-us/library/2f7456c2-67e6-4948-9e76-81fce661210e1033.mspx.

Open XML Converters for Mac Office

http://www.futurezone.at/

Should your goverment use ISO/OASIS ODF or ISO/Ecma OOX or XHTML?

Err…, yes. All of them, where they are appropriate. For converting archives of Word .DOC and .RTF documents into an XML format that retains fidelity, clearly OOX is the winner. For maximal interchange between applications and preventing application-specific formatting conventions leaking through, ODF is probabably the winner. For text which needs to have the maximum reach in different media, XHTML is the winner.

For documents which have embedded data that non-COTS applications use and which will be re-targeted to different kinds of publications (not just the same publication in different media/styles) then making your own home-made schema (subsetting public vocabularies whereever possible) is the appropriate.

Final Drafts of Ecma Office Open XML available , Monday October 9, 2006 8:13PM, by Rick Jelliffe in Articles

XML in Office Community

neues Dateiformat für Office:

• Microsoft Office Open XML Formats Frequently Asked Questions
• 2007 Office System: XML Schema Reference
• Introducing the Office (2007) Open XML File Formats
• Walkthrough: Word 2007 XML Format
• 2007 Office System Sample: Open XML File Format Code Snippets for Visual Studio 2005

InfoPath2007

• First Look at InfoPath 2007 (video)
• InfoPath 2007 Managed Object Model Poster
• Hosting the InfoPath 2007 Form Editing Environment in a Custom Web Form
• Hosting the InfoPath Form Editing Environment in a Custom Windows Form Application
• Using IOLECommands with the InfoPath Form Control
• Visual Studio 2005 Tools for Office Update: InfoPath 2007 Beta Support

oh dare: One of These is Not Like the Others

http://openxmldeveloper.org/default.aspx

Ein neues Portal mit zum Themenkreis
Office 2007 und XML - Dateiformate

Office Open XML Document Interchange Specification 
zip von PDF -  2000 Seiten

Office12 Dateiformate

erste Antworten in Newsgroup geben die Richtung ...

We won't provide lists and schema documentation until the fall.
In response to your specific questions though:

Embedded charts - XML
Chart sheets - XML
XLM Macro sheets - XML
Excel 5/95 dialog sheets - XML
Pictures / other drawing objects on sheets - Binary for pictures. Drawings
will be XML.
'Old' Excel controls on sheets - XML for the properties; Binary for the data
External links/values - XML
Pivot tables - XML
Pivot caches - XML
Query Table data - XML
ActiveX controls on sheets - XML for the properties; Binary for the data
VSTO controls on sheets - implemented via existing controls
Embedded Office applications (e.g. Word) - Native representation (ie ZIP
file with XML)
Embedded 3rd part apps (OLE Objects) - Binary

--
Brian Jones - Microsoft
http://blogs.msdn.com/brian_jones

This posting is provided "AS IS" with no warranties, and confers no rights.

news:microsoft.public.office.xml  
7. Juli 2005 - Re: Office 12 formats: Binary/XML list

kommendes neues Dateiformat für Dokumente:

The primary benefit of using ZIP is its container feature. The fact that packages are based on ZIP doesn’t necessarily imply that they are compressed; packages can be uncompressed or they can also be compressed in a multitude of ways (maximal, normal, or fast).

It appears that the new XML + ZIP page file format is going to be used Microsoft-wide, not just for Metro and Office, but elsewhere like in Avalon document containers, for example.

Based on information from TechEd and the title of a new session in PDC, Microsoft will be encouraging ISVs to adopt the same format for their own applications. Widespread use of this format would make more tools available, and it would also make it easier for businesses to create, modify and consume non-Microsoft file formats. API support for this package format is found in the new System.IO.Packaging namespace defined in WindowsBase.dll in WinFX.

gefunden bei http://wesnerm.blogs.com/net_undocumented/

da treffen sich die wichtigen autoren

Gefunden via Blog:
http://blogs.msdn.com/brian_jones/archive/2005/06/01/424085.aspx

Der Hinweis auf:

beschreibt die neue Dokumentstruktur ..

"Yes this is proprietary and not defined by a standards body, but it can be used by and interoperable with others. They don't need Microsoft software to read and write. It is not an open standard but an open format," Paoli explained.

• http://www.betanews.com/article/Microsoft_Opens_Office_File_Formats/1117692086
• Microsoft Office and XML: Why not the OASIS OpenOffice.org XML format?
• OASIS: Microsoft Announces Adoption of XML for Default File Formats in 'Office 12'.

Die aktuelle Diskussion über Dateiformate von Dokumenten

• Sun & Microsoft on Open Document Formats & XML Strategy
• http://www.gilbane.com/conferences/San_Francisco_05_program.html

Keynote Debate: Microsoft & Sun: What is the Right XML Strategy for Information Interchange?

Until recently it was difficult and costly to preserve your content in an "open" industry standard format so that it wasn't, in effect, held hostage by being in a software vendor's proprietary format and their own product and business goals. Integration of office documents into enterprise applications was a risky proposition for the same reason. With the widespread adoption of XML, and in particular Microsoft's support for XML in their Office suite, it seems like enterpises should finally be able to own their own information, share it with whom they want, and integrate office documents into critical enterprise applications. But is it really that simple?

At one level this can be framed as a debate between Microsoft and Sun/OpenOffice.org - and that is a choice organizations will have to make, but it is more complicated than that. In spite of the fact that OpenOffice and Microsoft Office both provide comprehensive XML support, there are still subtle differences that need careful consideration. Is one more "open" than the other? What are the practical implications of each approach? What are the relevant technical, legal, policy, and resource considerations? This is a significant issue: governments in Europe and in the U.S. (e.g., Massachusetts) are making policy/purchasing decisions about "open" document formats as well as about open source code. This panel, who are each intimately involved in the debate, will look at all sides of the debate, peel away the political and marketing hype, and provide you with a clear understanding of the real issues so you can make your own well-informed decisions.
...For some background see Jon Udell's posts here and here, and the Cover Pages here.

Ein Dokument ist eine Sammlung von Daten und Formaten,..
für den Prozess werden nur die Daten gebraucht ..

XML liefert Antworten darauf, aber welche Formulierung ist nun die Richtige?

• W3C Publishes First Requirements Working Draft for Compound Document Formats.

... When combining user interface markups, specific problems have to be resolved that are not addressed by the individual markups specifications, such as the propagation of events across markups, the combination of rendering or the user interaction model with a combined document. The Compound Document Formats working group will address this type of problems. This work is divided in phases and two technical solutions: combining by reference and by inclusion ..

John R. Durant zu Office2003

• BlogPost Office 2003 .NET Samples
• GDN The Office 2003 PIA Sample Launcher (OPSL)
• MSDN Introduction to the Office 2003 Primary Interop Assemblies Sample Launcher

Unter http://www.devx.com/officeprodev ein neues Portal zu Office und XML...

neue Updates im Q1 2005 auf http://msdn.microsoft.com/office/downloads/sdks/default.aspx

SDKs

• InfoPath SDK
• Research Services SDK
• SmartDoc SDK
• Smart Tag SDK
• SPPT SDK
• Office Reference Schemas
• Visio SDK
• WordML Viewer
• Word XML Toolbox
• Web Part Templates
• Web Part Packager
• Managed SmartDoc Wrapper
• InfoPath 2003 Toolkit for Visual Studio.NET
• Research Services Development Extras
• Smart Tag Developer Tools
• WordML XSLT Inference Tool
• Word XML SDK