When a presentation specifies an external location to which an optional copy might be pushed in the HTML format, this relationship shall be used to target the location where the HTML copy of the presentation is published. A package shall contain one HTML Publish Location relationship for each slide linked with an HTML publish location, and that relationships shall be an explicit relationship from the corresponding Presentation Properties (§13.3.7) part. [Example: A Presentation Properties part, stores an HTML Publish Location of http://www.openxmlformats.org/test.htm will contain the following relationship in that part's relationship part: <Relationships xmlns="…"> <Relationship Id="rId1" Type="http://…/htmlPubSaveAs" Target="http://www.openxmlformats.org/test.htm" type=”External”/> </Relationships> end example] An HTML publish location shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External). Slide Synchronization Server Location Source http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideUpdateUrl Relationship: When a slide is being synchronized with a copy stored on a remote server, this relationship shall be used to target the location where the server copy of the slide is stored. A package shall contain one Slide Synchronization Server Location relationship for each slide linked with server data, and that relationships shall be an implicit relationship from the corresponding Slide Synchronization Data (§13.3.11) part. [Example: A Slide Synchronization Data part that stores information about a slide that is synchronized with a server located at http://www.openxmlformats.org/slides/ will contain the following relationship in that part's relationship part item: <Relationships xmlns="…"> <Relationship Id="rId1" Type="http://…/slideupdateUrl" Target="http://www.openxmlformats.org/slides/" type=”External”/> </Relationships>
When a presentation specifies an external location to which an optional copy might be pushed in the HTML format, this relationship shall be used to target the location where the HTML copy of the presentation is published. A package shall contain one HTML Publish Location relationship for each slide linked with an HTML publish location, and that relationships shall be an explicit relationship from the corresponding Presentation Properties (§13.3.7) part. [Example: A Presentation Properties part, stores an HTML Publish Location of http://www.openxmlformats.org/test.htm will contain the following relationship in that part's relationship part: <Relationships xmlns="…"> <Relationship Id="rId1" Type="http://…/htmlPubSaveAs" Target="http://www.openxmlformats.org/test.htm" type=”External”/> </Relationships> end example] An HTML publish location shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External). Slide Synchronization Server Location Source Relationship: http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideUpdateUrl When a slide is being synchronized with a copy stored on a remote server, this relationship shall be used to target the location where the server copy of the slide is stored. A package shall contain one Slide Synchronization Server Location relationship for each slide linked with server data, and that relationships shall be an implicit relationship from the corresponding Slide Synchronization Data (§13.3.11) part. [Example: A Slide Synchronization Data part that stores information about a slide that is synchronized with a server located at http://www.openxmlformats.org/slides/ will contain the following relationship in that part's relationship part item: <Relationships xmlns="…"> <Relationship Id="rId1" Type="http://…/slideupdateUrl" Target="http://www.openxmlformats.org/slides/" type=”External”/> </Relationships>
Office%20Open%20XML%20Part%201%20-%20Fundamentals_final.docx