The mechanism for extending the set of art borders is not defined.
An interface or extension mechanism should be provided for authors and application developers to specify their own art borders.
Part 4, Section 2.18.45
te
Proposed Disposition of DIS 29500 Comment IR-0033 (Modified: 2007-12-08) Agreed; we should provide a mechanism to allow users to specify their own custom defined border. The following changes will be made: In Part 4, §2.18.4, page 1,646, add a new enumeration value to ST_Border: Enumeration Value Description custom (Custom Defined Art Border) Specifies a custom art border using the parent element’s attributes to reference one or more custom art border images. In Part 4, §2.6.2, page 597, after line 17, modify the bottom element definition in the following manner: When a document has a bottom border that is relative to the text (using the offsetFrom attribute on pgBorders), it shall span only the necessary width to satisfy the requirement of spanning the width of the text. When a document has custom border art specified by the bottomLeft, bottomRight, and/or id attributes, it shall use the corresponding relationship part item as an image for the bottom left corner, bottom right corner, and/or bottom border, respectively. If the corresponding relationship part item cannot be located, the consumer shall use the border specified by the value of the val attribute. If the corresponding value of the val attribute cannot be resolved no bottom left corner, bottom right corner, or bottom border is present when the page is displayed. When a document has a custom border art specified by the id attribute without specifying the bottomRight and/or bottomLeft attributes, the bottom border as resolved by the corresponding relationship part item of the id attribute shall span to the corners not specified by bottomRight and/or bottomLeft attributes. In Part 4, §2.6.2, page 598, add the following attributes to element bottom: Attributes Description id (Custom Defined Border Specifies the relationship ID for the relationship which contains the custom border image for the parent element. This custom border image is contained in a separate Attributes Description Relationship Reference) Namespace: …/officeDocument/2006/relationships part within the WordprocessingML package. The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom bottom border in a document: <w:bottom w:val="custom" r:id="rIdCustomBottomBorder" …/> The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomBottomBorder shall contain the custom bottom border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). bottomLeft (Custom Defined Bottom Left Border Relationship Reference) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID for the relationship which contains the custom bottom left border image for the parent element. This custom border image is contained in a separate part within the WordprocessingML package. The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom bottom left border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom bottom left border in a document: <w:bottom w:val="custom" r:bottomLeft="rIdCustomBottomLeftBorder" …/> The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomBottomLeftBorder shall contain the custom bottom left border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). bottomRight (Custom Defined Bottom Right Specifies the relationship ID for the relationship which contains the custom bottom right border image for the parent element. This custom border image is contained in a separate part within the WordprocessingML package. Attributes Description Border Relationship Reference) Namespace: …/officeDocument/2006/relationships The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom bottom left border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom bottom right border in a document: <w:bottom w:val="custom" r:bottomRight="rIdCustomBottomRightBorder" …/> The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomBottomRightBorder shall contain the custom bottom right border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). In Part 4, §2.6.2, page 603, line 2, element bottom is modified to use complex type CT_BottomPageBorder The following XML Schema fragment defines the contents of this element: <complexType name="CT_BottomPageBorder"> <complexContent> <extension base="CT_PageBorder"> <attribute ref="r:bottomLeft" use="optional"/> <attribute ref="r:bottomRight" use="optional"/> </extension> </complexContent> </complexType> In Part 4, §2.6.7, page 612, after line 20, modify the left element definition in the following manner: When a document has a left border that is relative to the text (using the offsetFrom attribute value of text on pgBorders), it shall span only the necessary width to satisfy the requirement of spanning the width of the text. When a document has custom border art specified by the id attribute, it shall use the corresponding relationship part item as an image for the left border. If the corresponding relationship part item cannot be located, the consumer shall use the border specified by the value of the val attribute. If the corresponding value of the val attribute cannot be resolved, no left border is present when the page is displayed. In Part 4, §2.6.7, page 613, add the following attribute to element left: Attributes Description id (Custom Defined Border Relationship Reference) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID for the relationship which contains the custom border image for the parent element. This custom border image is contained in a separate part within the WordprocessingML package. The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom bottom border in a document: <w:bottom w:val="custom" r:id="rIdCustomBottomBorder" …/> The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomBottomBorder shall contain the custom bottom border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). In Part 4, §2.6.7, page 618, line 2, element left is modified to use complex type CT_PageBorder: The following XML Schema fragment defines the contents of this element: <complexType name="CT_PageBorder"> <complexContent> <extension base="CT_Border"> <attribute ref="r:id" use="optional"/> </extension> </complexContent> </complexType> In Part 4, §2.6.15, page 634, line 4, modify the right element definition in the following manner: When a document has a right border that is relative to the text (using the offsetFrom attribute value of text on pgBorders), it shall only span the necessary width to satisfy the requirement of spanning the width of the text. When a document has custom border art specified by the id attribute, it shall use the corresponding relationship part item as an image for the right border. If the corresponding relationship part item cannot be located, the consumer shall use the border specified by the value of the val attribute. If the corresponding value of the val attribute cannot be resolved, no right border is present when the page is displayed. In Part 4, §2.6.15, page 635, add the following attribute to element right: Attributes Description id (Custom Defined Border Relationship Reference) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID for the relationship which contains the custom border image for the parent element. This custom border image is contained in a separate part within the WordprocessingML package. The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom bottom border in a document: <w:bottom w:val="custom" r:id="rIdCustomBottomBorder" …/> The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomBottomBorder shall contain the custom bottom border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). In Part 4, §2.6.15, page 640, line 2, element right is modified to use CT_PageBorder: The following XML Schema fragment defines the contents of this element: <complexType name="CT_PageBorder"> <complexContent> <extension base="CT_Border"> <attribute ref="r:id" use="optional"/> </extension> </complexContent> </complexType> In Part 4, §2.6.21, page 652, after line 6, modify the top element definition in the following manner: When a document has a top border that is relative to the text (using the offsetFrom attribute value of text on pgBorders), it shall only span the necessary width to satisfy the requirement of spanning the width of the text. When a document has custom border art specified by attributes topLeft, topRight, and/or id, it shall use the corresponding relationship part item as an image for the top left corner, top right corner, and/or top border, respectively. If the corresponding relationship part item cannot be resolved the consumer shall use the border specified by the value of the val attribute. If the corresponding value of the val attribute cannot be resolved no top left corner, top right corner, or top border is present when the page is displayed. When a document has a custom border art specified by attribute id without specifying either attributes topRight and/or topLeft, the top border as resolved by the corresponding relationship part item of attribute id shall span to the corners not specified by topRight and/or topLeft attributes. In Part 4, §2.6.21, page 653, add the following attributes to element top: Attributes Description id (Custom Defined Border Relationship Reference) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID for the relationship which contains the custom border image for the parent element. This custom border image is contained in a separate part within the WordprocessingML package. The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom bottom border in a document: <w:bottom w:val="custom" r:id="rIdCustomBottomBorder" …/> Attributes Description The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomBottomBorder shall contain the custom bottom border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). topLeft (Custom Defined Top Left Border Relationship Reference) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID for the relationship which contains the custom top left border image for the parent element. This custom border image is contained in a separate part within the WordprocessingML package. The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom top left border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom top left border in a document: <w:top w:val="custom" r:topLeft="rIdCustomTopLeftBorder" …/> The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomTopLeftBorder shall contain the custom top left border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). topRight (Custom Defined Top Right Border Relationship Reference) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID for the relationship which contains the custom top right border image for the parent element. This custom border image is contained in a separate part within the WordprocessingML package. The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/image or the document shall be considered non-conformant. If this attribute is omitted, then no custom top left border shall be used when the parent element is instantiated. [Example: Consider the following WordprocessingML markup for a custom top right border in a document: <w:top w:val="custom" r:topRight="rIdCustomTopRightBorder" …/> Attributes Description The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rIdCustomTopRightBorder shall contain the custom top right border image for the document. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). In Part 4, §2.6.21, page 657, line 2, element top is modified to use complex type CT_TopPageBorder: The following XML Schema fragment defines the contents of this element: <complexType name="CT_TopPageBorder"> <complexContent> <extension base="CT_PageBorder"> <attribute ref="r:topLeft" use="optional"/> <attribute ref="r:topRight" use="optional"/> </extension> </complexContent> </complexType> Updates to wml.xsd: Add a new complex type CT_PageBorder: <complexType name="CT_PageBorder"> <complexContent> <extension base="CT_Border"> <attribute ref="r:id" use="optional"/> </extension> </complexContent> </complexType> We will add a new complex type CT_TopPageBorder: <complexType name="CT_TopPageBorder"> <complexContent> <extension base="CT_PageBorder"> <attribute ref="r:topLeft" use="optional"/> <attribute ref="r:topRight" use="optional"/> </extension> </complexContent> </complexType> We will add a new complex type CT_BottomPageBorder: <complexType name="CT_BottomPageBorder"> <complexContent> <extension base="CT_PageBorder"> <attribute ref="r:bottomLeft" use="optional"/> <attribute ref="r:bottomRight" use="optional"/> </extension> </complexContent> </complexType> Updates to orel.xsd, the following top-level attributes are added: <xsd:attribute name="topLeft" type="ST_RelationshipId" /> <xsd:attribute name="topRight" type="ST_RelationshipId" /> <xsd:attribute name="bottomLeft" type="ST_RelationshipId" /> <xsd:attribute name="bottomRight" type="ST_RelationshipId" /> Similar Comments: AU-0021 , CA-0028 , CL-0127 , CZ-0030 , DE-0095 , FI-0006 , FR-0320 , GB-0272 , GR-0052 , IN-0041 , IR-0034 , KE-0034 , US-0109 , VE-0032
It is basically about generalizing. The border shall be an svg image. The images for backwards compatibility with the old binary format can be published in a non-normative fashion as public domain. It is just a conversion issue that does not belong in a hardcoded fashion into the new standard.