Re: [bcm] Office 2003 XML and OpenOffice XML

[David RR Webber <david@drrw.info>]

Duane,

Forms is a different topic.

In BCM we're looking at business templates.

Granted forms can be a part of that - but you should
not be thinking solely about a form style interface.

Documents and spreadsheets are critical here too - as
is the ability to develop outlines and classification
schemes.

Thanks, DW.

Quoting Duane Nickull <duane@yellowdragonsoft.com>:

> 
> 
> 
>   
>   
> 
> 
> David:
> 
> 
> 
> I would also urge the BCM group to look at Acrobat 6. The eForms component
> can save the form data as XML instance and also import it back in.  I want
> to introduce you to Melonie (she is in the DC area with you).
> 
> 
> 
> Matt and I have been playing around with it and belive it will play an
> important
> part of future ebXMl demos going forward.
> 
> 
> 
> Duane
> 
> 
> 
> David RR Webber wrote:
> 
>   
>   
>  
>   
>  
>     
>   Team,
>  
>    
>  
>   These products are now supporting the
> functionality  that allows the business
>  
>   user to create documents that can direct
> downstream  systems.
>  
>    
>  
>   I'm sure we'll get more into this as our
> template  models mature.
>  
>    
>  
>   Thanks, DW
>  
>    
>  
>   ----------------------------------------------------------------------
> 
>   
> 
> XML  in Microsoft Office Word 2003
> 
> Aaron Skonnard, MSDN Magazine
> 
>   
> 
> Microsoft  Office Word 2003 introduces the 'Save as XML' command that
> 
> produces WordML  documents. Later, when you double-click on an XML
> 
> document produced by Word,  the Windows loader automatically associates
> 
> the file with Word. WordML is  powerful and flexible enough to capture
> 
> all of the rich editing and  formatting of a Word document with full
> 
> round-tripping. The introduction of  WordML is probably the most
> 
> significant change in Microsoft Office Word 2003,  but it's definitely
> 
> not the only one. Developers can also attach custom XML  Schema
> 
> definitions and XSLT transformations to Word documents.  Developers
> 
> can mark up content with elements from the attached schemas,  making
> 
> it possible to inject meaningful business-specific markup  that
> 
> simplifies processing down the road. When you save a document in  Word,
> 
> it can validate the document against the attached schema and apply  a
> 
> custom XSLT transformation during the process.
> 
>   
> 
>   http://msdn.microsoft.com/msdnmag/issues/03/11/XMLFiles/default.aspx
> 
>   
> 
> ----------------------------------------------------------------------
> 
>   
> 
> OpenOffice.org  XML Essentials: Using OpenOffice.org's XML Data Format
> 
> J. David Eisenberg,  O'Reilly & Associates
> 
>   
> 
> The author provides draft content submitted to  an open review process,
> 
> published under a Creative Commons License.  OpenOffice.org has as its
> 
> mission "to create, as a community, the leading  international office
> 
> suite that will run on all major platforms and provide  access to all
> 
> functionality and data through open-component based APIs and  an
> 
> XML-based file format."  The OpenOffice.org file format is not  simply
> 
> an XML wrapper for a binary format, nor a one-to-one  correspondence
> 
> between the XML tags and the internal data structures.  Instead, it is
> 
> an idealized representation of the structure. This allows  future
> 
> versions of OpenOffice.org to implement new features or  completely
> 
> alter internal data structures without requiring major changes to  the
> 
> file format.  Although the XML file format is human-readable, it  is
> 
> fairly verbose. To save space, OpenOffice.org files are stored in  JAR
> 
> (Java Archive) format. A JAR file is a compressed ZIP file that has
> 
> an  additional manifest file that lists the contents of the archive.
> 
> If you, as a  human, want to read the XML directly, you can unpack an
> 
> OpenOffice.org file  with any ZIP tool.
> 
>   
> 
>   http://books.evc-cit.info/
> 
> See also the  Creative Commons Project:
> http://xml.coverpages.org/creativeCommons.html
> 
>   
> 
>   
> 
> 
> 
> -- 
> ***************************************************
> Yellow Dragon Software - http://www.yellowdragonsoft.com
> Web Services & ebXML Messaging / Registry Downloads
> UN/CEFACT eBusiness Architecture/ ebXMl Technical Architecture 
> Phone:   +1 (604) 738-1051 - Canada: Pacific Standard Time
> Direct:  +1 (604) 726-3329 
> 
> 
> 
> 
> 
> 
> 
> 
> To unsubscribe from this mailing list (and be removed from the roster of the
> OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/bcm/members/leave_workgroup.php.
> 
> 


http://drrw.net