The element name "Types" is very confusing.
Use "ContentTypes". If this change is not possible, there should be some notes about this inappropriate name at the very least.
Part 2 Clause 9.1.2.2.4 and Part 1 Clause 11.2
ed
Proposed Disposition of DIS 29500 Comment JP-0043 (Modified: 2008-01-04) Agree; taken out of context the element name alone may not be clear enough. In the examples referenced, the namespace is not shown, which leads to the confusion. In order to make this clear, we will update one example to specify the namespace, as well as update the other example to make it clear that the Types element is not for generic types but instead is specifically for content types. Part 1, §11.2, page 25, lines 1122: [Example: The following package represents the minimal conformant WordprocessingML package as defined by this Standard: First, the content type for relationship parts and the Main Document part (the only required part) must be defined (physically located at /[Content_Types].xml in the package): <Types xmlns=" … http://schemas.openxmlformats.org/package/2006/content- types "> <Default Extension="rels" ContentType="application/vnd.openxmlformats- package.relationships+xml"/> <Override PartName="/document.xml" ContentType="application/vnd.openxmlformats- officedocument.wordprocessingml.document.main+xml"/> </Types> Part 2, §9.1.2.2.4, page 26, lines 110: 9.1.2.2.4 Content Types Stream Markup Example [Example: Example 97. Content Types stream markup <Types xmlns="http://schemas.openxmlformats.org/package/2006/content-types"> <Default Extension="txt" ContentType="text/plain" /> <Default Extension="jpeg" ContentType="image/jpeg" /> <Default Extension="picture" ContentType="image/gif" /> <Override PartName="/a/b/sample4.picture" ContentType="image/jpeg" /> </Types> [Note: The Types element is not a container for generic types, but specifically for content types to be used within the package. end note]
