Comment on reliable embedding of scripting in DIS 29500 Michiel Leenaars, Wouter van Vugt *** Comment Common non-textual objects such as macro's, scripting and embedded software do not have an easily recognisable position within the DIS 29500 zip container format. It is undesirable from the view of both consumers and interoperability that every producer should find its own location for part(s) containing script in the document structure. *** Proposed change: Just like digital signatures, an 'embedded-code origin part' should be added with a known relationship-type refered to from within the package. This part will be empty and uses relationship types which are not part of the Open Xml standard to refer to parts where the code is located. This makes sure that every consumer and producer can recognise that indeed there is scripting or macro code, and optionally can interpret this using the second relationship type. The tree structure of a package would resemble(with fictional relationship types) Root (zip) - code origin part (http://schemas.openxmlformats.com/embeddedcode ) - VBA (http://schemas.microsoft.com/VBA ) - PHP (http://php.com/PHP ) - Java - main part (http://schemas.openxmlformats.com/2006/document/main ) - regular childparts