This subclause defines an INCLUDEPICTURE field which "Retrieves the picture contained in the document named". This does not define how a picture is named.

Use the Open Packaging Convention (Part 2 of this specification) nomenclature to define the relationships.

Part 4,
Section 2.16.5.33

te

Proposed Disposition of DIS 29500 Comment BR-0010 (Modified: 2008-01-13) Agreed, the current text does not specify how an image is referenced. The proposal to use OPC relationships for the INCLUDEPICTURE field is unfortunately not an option as the location of the picture stored within rich content inserted by the user that can contain rich formatting. Because of this, the location must be stored with the rest of the field text. In order to make it clear how the location is used though, the following text will be added to Part 4, §2.16.5.33, page 1,537, lines 12­14: To Part 4, §2.16.5.33, page 1,537, lines 12­14: Description: Retrieves the picture contained in the document named by field-argument. Field-argument specifies the location of the picture using an IRI (Duerst and Suignard 2005). If field-argument contains white space, it shall be enclosed in double quotes. If field-argument contains any backslash characters, each one shall be preceded directly by another backslash character. To Part 4, §2.16.5.33, page 1,537, lines 18­20: [Example: INCLUDEPICTURE " G:\\Photos\\Ellen in Oslo.jpg file:///g:/photos/Ellen in Oslo.jpg " end example] To the normative references: Duerst, M, and M Suignard. "Internationalized Resource Identifiers (IRIs)." IETF. January 2005. http://tools.ietf.org/html/rfc3987. Existing references which imply use of DOS file paths will be removed from their current location in the specification (Part 4, §2.16.5.33, page 1537, lines 12-14; Part 4, §2.16.5.34, page 1538, lines 1-7), and placed into a new annex for deprecated features. Following the precedent set by other ISO standards (such as SQL’s ISO 9075:2003 Part 1 and C++’s ISO/IEC 14882:1998), we will make use of a new Annex that contains normative descriptions of all deprecated features. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features to preserve their fidelity, while noting that new documents should not use them. Accordingly, the Conformance clause will also be changed to state that newly created documents (those not created by migrating existing binary documents) should not use deprecated features. All deprecated features will be removed from their current locations in the standard, but will be fully defined in this new Annex.