Metadata definitions are very limited to work in proprietary implementations. There is no clear definition for customized metadata needed in data search and recovery operations, such as search engines or multivendor DBMS serving over the Internet.

Include a more specific definition for metadata components. Also a procedure for customized metadata creation and retrieval.

Entire sub clause Part 3. 7.2

te

Proposed Disposition of DIS 29500 Comment MX-0007 (Modified: 2008-01-04) We absolutely agree that a location where customized metadata can be stored is an essential piece of the specification, as many domain-specific mechanisms exist to serve specific uses. Accordingly, Part 3, §7.3 “Custom XML Data” describes just such a mechanism ­ within an Office Open XML document, any number of Custom XML Data parts can be stored within the package, as described in Part 3, §7.3, page 440: “Within an Office Open XML document, it is sometimes desirable or necessary to store custom XML data (that is, data in a format not defined by this Office Open XML specification) within the contents of the package. To accommodate this need, Office Open XML allows the storage of any arbitrary XML within a package as the target of the http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml relationship (valid source parts are listed within Part 1 of the Standard). The following examples illustrate potential uses of this mechanism: A document which collects and displays information from a backend data source might want to store the original form of that backend data, so it can be manipulated and uploaded to the original data source at a later date. A document author may wish to store additional metadata in an XML format not defined by this Office Open XML specification’s existing metadata schemas. A document management system may wish to store data tracking the workflow status, retention policies, and so on for this document along with the document.”