Signature Definitions Schema (§A.1) This annex includes the W3C XSD schema for the Signature Definitions part. OpenXPS Document Schema (§A.2) This includes the W3C XSD schema for the FixedDocument, FixedDocumentSequence, and FixedPage parts. Resource Dictionary Key Schema (§A.3) This annex provides the W3C XSD schema for the resource dictionary Key attribute, used by several elements in the OpenXPS Document schema. Document Structure Schema (§A.4) This provides the W3C XSD schema for the DocumentStructure and StoryFragments parts. Discard Control Schema (§A.5) This includes the W3C XSD schema for the DiscardControl part for interleaving. 3D-Graphic Content Schema (§A.6) This annex includes the optional W3C XSD schema for 3D-Graphics support. Abbreviated Geometry Syntax Algorithm (§C) This annex provides a sample algorithm for interpreting the abbreviated geometry syntax provided to succinctly describe geometric regions in a single attribute. Standard Namespaces and Content Types (§D) This annex defines all of the XML namespace names, content types, and relationship types used by all OpenXPS Document parts and relationships.
It is RECOMMENDED that there be exactly one Required Resource relationship from the FixedPage part for each resource referenced from markup [S2.1]. Multiple Required Resource relationships from a FixedPage part to a resource are not considered an error, but they reduce efficiency. It is not considered an error if a FixedPage part that does not use a specific resource in its markup references the resource via a Required Resource relationship; however, doing so might reduce efficiency for consumers. Relationship types are defined in §D.3. Table 9–2. Fixed payload relationships Name Description Required/Optional Core Properties Relationship from the package to the Core Properties part. OPTIONAL [O2.8] Digital Signature Origin Relationship from the package to the Digital Signature Origin part. OPTIONAL [O2.9] Digital Signature Relationship from the Digital Signature Origin part to a Digital Signature XML Signature part. OPTIONAL [O2.10] Digital Signature Certificate Relationship from a Digital Signature XML Signature part to a Digital Signature Certificate part. OPTIONAL [O2.11] Digital Signature Definitions Relationship from the FixedDocument part to a Digital Signature Definitions part. OPTIONAL [O2.12] DiscardControl Relationship from the package to a DiscardControl part. OPTIONAL [O2.13] DocumentStructure Relationship from the FixedDocument part to a DocumentStructure part. OPTIONAL [O2.14] PrintTicket Relationship from a FixedDocumentSequence part, a FixedDocument part, or a FixedPage part to a PrintTicket part. OPTIONAL [O2.15] Required Resource Relationship from a FixedPage part to a required resource, including Font, Image, ColorProfile, and Remote Resource Dictionary parts. Required resources can be shared between pages. REQUIRED for each resource referenced from a FixedPage [M2.10] Restricted Font Relationship from a FixedDocument part to a Font part. Specifies the referenced font as restricted, disallowing any modification or editing of any <Glyphs> element text the referenced font. REQUIRED for each preview and print font used [M2.12]
annotation The <VisualBrush> element is used to fill a region with a drawing. The drawing can be specified as either a <VisualBrush.Visual> property element or as a resource reference. Drawing content can include exactly one <Canvas>, <Path>, or <Glyphs> element and that element’s child and descendant elements. Visual brushes share a number of tile-related properties with image brushes. For details, see §13.4. <VisualBrush.Visual> Element element VisualBrush.Visual diagram
Common Properties Several OpenXPS Document elements share property attributes and elements as summarized in Table 14–1 and Table 14–2 and detailed in the following sections. Other than the Name, FixedPage.NavigateUri, and xml:lang attributes, these properties compose their results from parent to child, as described in §18.5. Table 14–1. Common property attributes Name Applies to Description Clip <Canvas> <Glyphs> <Path> Restricts the region to which a brush can be applied. Opacity <Canvas> <Glyphs> <ImageBrush> <LinearGradientBrush> <Path> <RadialGradientBrush> <SolidColorBrush> <VisualBrush> Defines the uniform transparency of the element. OpacityMask <Canvas> <Glyphs> <Path> Specifies a mask of values that is applied in the same fashion as the Opacity attribute, but allows different alpha values on a pixel-by-pixel basis. RenderTransform <Canvas> <Glyphs> <Path> Establishes a new coordinate space through the use of an affine matrix transformation. For more information, see §14.4. Transform <ImageBrush> <LinearGradientBrush> <PathGeometry> <RadialGradientBrush> <VisualBrush> Establishes a new coordinate space through the use of an affine matrix transformation. Name <Canvas> <FixedPage> <Glyphs> <Path> Defines a hyperlink target or identifies an element uniquely for document structure markup to reference. For more information, see §16.2. FixedPage.NavigateUri <Canvas> <Glyphs> <Path> Defines a hyperlink source. For more information, see §16.2.
In the absence of such information, in a typical case, with ICC profiles conforming to the ICC Profile specification, ICC.1:2001-04 [M8.12], a consumer SHOULD apply the defaults shown in Table 15–4 [S8.20]. Table 15–4. Recommended ICC rendering intent usage Color type Object type ICC Source Rendering Intent ICC Destination Rendering Intent sRGB Raster image Perceptual Perceptual sRGB Vector Relative Colorimetric Relative Colorimetric* scRGB Raster Perceptual Perceptual scRGB Vector Relative Colorimetric Relative Colorimetric* RGB color space Raster Perceptual Perceptual RGB color space Vector Relative Colorimetric Relative Colorimetric* CMYK, Gray color space Raster image Relative Colorimetric Perceptual CMYK, Gray space Vector Relative Colorimetric Relative Colorimetric* color, N-Channel Any Relative Colorimetric Relative Colorimetric *In the optional case, with ICC profiles conforming to the requirements of ISO 15076-1, based on ICC.1:2004-10 [O8.9], the Saturation Rendering Intent components of the profiles should be optimized for business graphics and may provide preferred results. (See §15.1.8 for the appropriate use of ISO 15076-1 profiles.)