- From: Charles F Wiecha <wiecha@us.ibm.com>
- Date: Mon, 27 Jul 2009 12:56:19 -0400
- To: public-xg-app-backplane <public-xg-app-backplane@w3.org>
Received on Monday, 27 July 2009 16:57:07 UTC
Here's the plan for the ODF text (ODT) subset to be used in implementing the expense report in our scenario...for discussion in our next call: 1. A reminder of the expense report appearance (as created in a full ODF editor): (See attached file: expenses-demo.pdf) 2. The ODT markup generated by the editor, edited only to remove content not needed by the POC implementation (e.g. style declarations might be added back later, template declarations for the TOC entries). Otherwise, XML is as generated by the editor: (See attached file: ubiquity-expense-odt.xml) 3. A list of the elements and their behavior necessary to implementing the demo: (See attached file: ubiquity-odf-elements.html) Charles Wiecha Multichannel Web Interaction IBM T.J. Watson Research Center P.O. Box 704 Yorktown Heights, N.Y. 10598 Phone: (914) 784-6180, T/L 863-6180, Cell: (914) 320-2614 wiecha@us.ibm.com
Received on Monday, 27 July 2009 16:57:07 UTC