Re: Ask for advice:cloud office interoperability
Hi,Zhengfan and Ian Lynch, All format office documents' interoperability is important. 1. ODF and OOXML, is more concerned about data storage. Microsoft, and OpenOffice is the supporter。But we need ODF and OOXML to be merged to a new one format. And some wroking are doing 。Otherwise， we should face the question,just like Ian Lynch's problem. 2. HTML, is more concerned about data revealing。 Google Docs，IBM Docs，Microsoft Office 365,Zoho,Think Free,Adobe Acobat, Cisco WebEx ,all these cloud office documents select the same format. Maybe it is a new way for office documents interoperability. As Rob Weir ,OASIS OpenDocument TC chairman,says" I find the topic of web editor interoperability very interesting. It is, in many ways, the continuation of the "office interop" battles we have fought for the last decade. But the new technology brings new challenges and new opportunities, and perhaps even an opportunity to avoid repeating the mistakes of the past! " ODF? OOXML?PDF?HTML?...I think it is better to choose one format for documents interoperability,than choose two or three! It is important ,just like ASCII which is the basic for Information Interchange. Do you agree? ZhunGuo 2012/10/1 Ian Lynch > On 1 October 2012 05:41, zheng.easyfan wrote: > > > > > HI, Zhun Guo: > > > > In general, I agree with your second point in the mail that, we should > > make better interoperability of office productions. And my opinion here > is > > that, in the category of interoperability, we even should not trying to > > separate the office applications as on line or off line ones. For > whatever > > the type of an office application it is, the exactly necessary function > it > > should supplied is to represent a document with specified file format > > correctly. And to any document from any user of any office application, > > there should be only one CORRECT representation result anyway. > > And I guess, the interoperability topics are the most important ones for > > each member of this community. For such kind of issues, as the most > visible > > ones, are always directly driven by users :( > > So, what is your suggestion or idea for it? > > > > My recent experience with docx to odt has been that for any document with > tables it is not good enough. I get a lot of routine docs in docX format > from UK government departments and very few can be used without a lot of > work. I also don't know how well docs I send to them as exports will appear > to them. Since Word processing documents are the most common and docX is > now in much wider use I think the priority needs to be to get the docX odt > filter to as good a standard as possible particularly with tables, headers, > footers and page structures. Without this it is going to be very difficult > for anyone that has to work with government departments to adopt AOO as an > alternative to MSO. Google Docs does it better and so it means Google Docs > is then a bigger competitor for AOO too. I also think that whichever of AOO > or LibO implements these filters the best is likely to get adoption over > the other. > > Zhengfan > > > > > > > > 已从三星手机发送zhun guo 写道：Dear All: > > It is necessary for all cloud office interoperability with each > > other. Do you think so ? > > What I want to do,is not to design a product for my own company. I > > just want to , between all cloud office websites, it can send documents > > quickly. Such as ,Google Docs can send documents to Microsoft Office 365 > > quickly, and directly . But now , Google Docs can only send documents > > using email (SMTP) to Hotmail.So i think HTTP(SPDY) is better than > SMTP > > for transfer online office documents ? So we should suggest ,IBM Docs > > and Office 365 ,Acobat.com use the same protocol. > >The second thing I want to do ,all online office interoperability . > > your know , for native office, an Microsoft Office 2010 document should > > be open and reedit by an Openoffice.org user , it means native office > > interoperability.Then for the cloud office, it also need > > interoperability. > >So let us do this thing together!As I know ,you all are great man and > > warmhearted! ?Thanks ! > > Please see more details in my email attachments! or via a web site: > > http://online-office-interoperability.blogspot.com/ > >Best Regards! > > > > Zhun Guo > > Shanghai Biaoma IT Co. > > www.mabaoo.com > > mike5guo(at)gmail.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > Ian > > Ofqual Accredited IT Qualifications (The Schools ITQ) > > www.theINGOTs.org +44 (0)1827 305940 > > The Learning Machine Limited, Reg Office, 36 Ashby Road, Tamworth, > Staffordshire, B79 8AQ. Reg No: 05560797, Registered in England and > Wales. >
Re: Ask for advice:cloud office interoperability
Hi,all,Joost not knew our means. We means ,how to solve the problem,the difficult of ODF interoperate with OOXML ,which Ian Lynch had met. this is for native office software. *The second , cloud office documents company also face the same question, *Google Docs，Microsoft Office 365，Zoho，苹果icloud，Adobe Acrobat.com<https://www.acrobat.com/> ，ThinkFree <http://thinkfree.com/>，Cisco WebEx WebOffice<http://www.weboffice.com/> ，IBM Docs ,etc, use ODF,OOXML,PDF,HTML . Then how to interoperate with each other? Zhun Guo 2012/10/2 Joost Andrae > Hi, > > Am 02.10.2012 13:03, schrieb zhun guo: > > Hi,Zhengfan and Ian Lynch, > > All format office documents' interoperability is important. > > 1. ODF and OOXML, is more concerned about data storage. Microsoft, and > > OpenOffice is the supporter。But we need ODF and OOXML to be merged to a > > new one format. And some wroking are doing 。Otherwise， we should face the > > question,just like Ian Lynch's problem. > > 2. HTML, is more concerned about data revealing。 Google Docs，IBM > > Docs，Microsoft Office 365,Zoho,Think Free,Adobe Acobat, Cisco WebEx ,all > > these cloud office documents select the same format. Maybe it is a new > way > > for office documents interoperability. As Rob Weir ,OASIS OpenDocument TC > > chairman,says" > > I find the topic of web editor interoperability very interesting. It > > is, in many ways, the continuation of the "office interop" battles we > > have fought for the last decade. But the new technology brings new > > challenges and new opportunities, and perhaps even an opportunity to > > avoid repeating the mistakes of the past! > >" > > ODF? OOXML?PDF?HTML?...I think it is better to choose one format for > > documents interoperability,than choose two or three! It is important > ,just > > like ASCII which is the basic for Information Interchange. > > Do you agree? > > ACSII compared to the characters within a GB18030 font ? This is just > one example why ASCII doesn't work here. UNICODE characters within a XML > based document format is much better for information exchange especially > if you use an application that has been globalized and localized to a > valuable number of languages. And as long as ODF and it's counterparts > are comparable to other document formats then why should there be a new > document format? ODF is ISO and OASIS approved, has been designed for > this purpose and it can be used by everyone. And parts of your ideas > have already been implemented as UOF in China. > Using ODFDOM (http://incubator.apache.org/odftoolkit/) as a basis for > such an application could serve very well as a container to proof > interoperability between applications by using ODF as it's container. > > Kind regards, Joost > > >
Re: Ask for advice:cloud office interoperability
to Juergen, Microsoft will never support ODF. But Microsoft's market share is 95%. We must cooperate with Microsoft. Which all company support is HTML . So it is the only format ,with it all the company can interoperate? Zhun Guo 2012/10/4 Jürgen Schmidt > On 10/4/12 4:06 PM, zhun guo wrote: > > Hi,all,Joost not knew our means. We means ,how to solve the problem,the > > difficult of ODF interoperate with OOXML ,which Ian Lynch had met. this > is > > for native office software. > > *The second , cloud office documents company also face the same > > question, *Google Docs，Microsoft Office 365，Zoho，苹果icloud，Adobe > > Acrobat.com<https://www.acrobat.com/> > > ，ThinkFree <http://thinkfree.com/>，Cisco WebEx > > WebOffice<http://www.weboffice.com/> > > ，IBM Docs ,etc, use ODF,OOXML,PDF,HTML . Then how to interoperate with > > each other? > > by supporting one really open standard like ODF ;-) And work together on > improvements or enhancements where necessary. Online editors are tools > that work on docs in an cloud storage and desktop clients like AOO can > access these docs as well. The question is more how collaborative > editing on ODF can be managed in a way that online editors as well as > desktop clients can use it. It probably don't have to be a completely > new format. > > Juergen > > > > > > Zhun Guo > > > > > > 2012/10/2 Joost Andrae > > > >> Hi, > >> > >> Am 02.10.2012 13:03, schrieb zhun guo: > >>> Hi,Zhengfan and Ian Lynch, > >>> All format office documents' interoperability is important. > >>> 1. ODF and OOXML, is more concerned about data storage. Microsoft, and > >>> OpenOffice is the supporter。But we need ODF and OOXML to be merged to > a > >>> new one format. And some wroking are doing 。Otherwise， we should face > the > >>> question,just like Ian Lynch's problem. > >>> 2. HTML, is more concerned about data revealing。 Google Docs，IBM > >>> Docs，Microsoft Office 365,Zoho,Think Free,Adobe Acobat, Cisco WebEx > ,all > >>> these cloud office documents select the same format. Maybe it is a new > >> way > >>> for office documents interoperability. As Rob Weir ,OASIS OpenDocument > TC > >>> chairman,says" > >>> I find the topic of web editor interoperability very interesting. It > >>> is, in many ways, the continuation of the "office interop" battles we > >>> have fought for the last decade. But the new technology brings new > >>> challenges and new opportunities, and perhaps even an opportunity to > >>> avoid repeating the mistakes of the past! > >>>" > >>> ODF? OOXML?PDF?HTML?...I think it is better to choose one format > for > >>> documents interoperability,than choose two or three! It is important > >> ,just > >>> like ASCII which is the basic for Information Interchange. > >>> Do you agree? > >> > >> ACSII compared to the characters within a GB18030 font ? This is just > >> one example why ASCII doesn't work here. UNICODE characters within a XML > >> based document format is much better for information exchange especially > >> if you use an application that has been globalized and localized to a > >> valuable number of languages. And as long as ODF and it's counterparts > >> are comparable to other document formats then why should there be a new > >> document format? ODF is ISO and OASIS approved, has been designed for > >> this purpose and it can be used by everyone. And parts of your ideas > >> have already been implemented as UOF in China. > >> Using ODFDOM (http://incubator.apache.org/odftoolkit/) as a basis for > >> such an application could serve very well as a container to proof > >> interoperability between applications by using ODF as it's container. > >> > >> Kind regards, Joost > >> > >> > >> > > > >
Re: Ask for advice:cloud office interoperability
To Dennis, why not consider about HTML ? Zhun Guo
Re: Ask for advice:cloud office interoperability
To Yong Lin Ma,my proposal is to get all office software to be convenient for common user, include native office software or cloud office software. I like ODF,OOXML,PDF or HTML . And you? Zhun Guo
Re: Ask for advice:cloud office interoperability
to all ,I suggest AOO to develop its own online office software quickly, just as Libre-office-on-line(LOOL) ! It is the Trend!
Re: Ask for advice:cloud office interoperability
Dear all , Who know some person,which work in Google Docs, IBM Docs,Cisco WebEX,Zoho,ThinkFree, these people maybe are more helpful for the topic, native and cloud office documents interoperability! We can invite them. Zhun Guo
Re: Ask for advice:cloud office interoperability
> > > In October 2006, Sir Tim Berners-Lee wrote a blog post in which he admitted that the attempt to move the web from HTML to XML just wasn’t working
Re: Ask for advice:cloud office interoperability
> > > To Alexandro Colorado: This article is so good for understanding of > history of HTML or XML. Thanks! >
Re: Ask for advice:cloud office interoperability
> > What means ? >
Re: Ask for advice:cloud office interoperability
To avoid this deadly risk, the first design goal of XML should have been that existing valid HTML documents were well formed XML documents. The result might have been a more complex format and specification, but this risk to create a gap between XML and HTML communities would have been minimized. Another reason to explain this failure is that XML is about extensibility. This is both its main strength and weakness: extensibility comes at a price and XML is more complex than domain specific languages. Remove the need for extensibility and XML will always loose against DSLs, we’ve seen a number of examples in the past: - RELAX NG compact syntax - JSON - HTML - N3 - CSS - … Is it a time to refactor XML? Converge or convert?
Re: Ask for advice:cloud office interoperability
cloud office productivity documents website: how to make both user experience consistent , for users between different websites, with the experience for users within the same site ? interoperability of cloud office productivity documents ? This is my question. Thanks!
