This does not define how a picture is named. Is it by a URI By a local file system path Either The example given has a DOS file path, a construct which is not portable.
Define how pictures are named.
- Part 4, Section 2.16.5.33
Te
Proposed Disposition of DIS 29500 Comment VE-0021 (Modified: 2008-01-11) Agreed, the mechanism is not properly specified; to address this, the following text will be changed: To Part 4, §2.16.5.33, page 1537, 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 1820: [Example: INCLUDEPICTURE " G:\\Photos\\Ellen in Oslo.jpg file:///g:/photos/Ellen in Oslo.jpg " end example] To Part 4, §2.16.5.34, page 1538, lines 1-7: Description: Inserts all or part of the text and graphics contained in the document named by field-argument-1. Field-argument-1 specifies the location of the document using an IRI (Duerst and Suignard 2005). If the document is a WordprocessingML document, the portion marked by the optional bookmark field-argument-2 is inserted. If no such bookmark is specified here, the whole document is inserted. If the document is an XML file, the fragment referred to by an XPath expression in the \x switch is inserted. If no such switch is specified, the whole XML file is inserted. If field-argument-1 contains white space, it shall be enclosed in double quotes. If field-argument-1 contains any backslash characters, each one shall be preceded directly by another backslash character. To Part 4, §2.16.5.34, page 1538, lines 11-18: [Example: The following field inserts the portion of the WordprocessingML document referred to by the bookmark Summary: INCLUDETEXT " file:/// C :\\ :/ Winword \\ / Port Development RFP" Summary The following field inserts the Name element of the XML document Resume.xml and applies the XSLT Display.xsl to it: INCLUDETEXT " file:/// C :\\ :/ Resume.xml" \n xmlns:a=\"resume-schema\" \t " file:/// C: \\ / display.xsl" \x a:Resume/a:Name 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 text which implies the use of DOS file paths will be removed from its 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. Similar Comments: CA-0023 , CL-0118 , CL-0121 , CO-0117 , CO-0119 , CZ-0026 , CZ-0052 , DE-0104 , DE-0108 , FR-0249 , FR-0254 , GB-0258 , GB-0260 , GR-0045 , GR-0046 , IR-0030 , IR-0031 , JP-0054 , JP-0055 , KE-0026 , KE-0027 , MY-0022 , PT-0059 , US-0102 , US-0104 , VE-0023
