Skip to content

Latest commit

 

History

History
53 lines (29 loc) · 2.94 KB

print-schema.md

File metadata and controls

53 lines (29 loc) · 2.94 KB
description ms.assetid title ms.topic ms.date
This overview describes the Print Schema and links to Print Schema reference topics. The Print Schema includes the Print Schema Keywords and the Framework.
d746bdd1-96c2-41f5-ad99-0b51c8ee8731
Legacy Print Schema Reference
article
05/31/2018

Legacy Print Schema Reference

This topic is not current. For the most current information, see the Print Schema Specification.

The Print Schema and related technologies are available in the Microsoft .NET Framework 3.0, Microsoft Windows Vista, and later releases.

The Print Schema provides an XML-based format for expressing and organizing a large set of properties that describe either a job format or PrintCapabilities in a hierarchically structured manner.

The Print Schema is an umbrella term that includes two components, the Print Schema Keywords and the Print Schema Framework. The Print Schema Keywords document is a public schema that defines a set of element instances that can be used to describe device attributes and print job formatting. The Print Schema Framework is a public schema that defines a hierarchically structured collection of XML element types, and specifies how the element types can be used together.

The Print Schema Keywords and the Print Schema Framework form the foundation for two Print Schema-related technologies, the PrintCapabilities Schema, and the PrintTicket Schema.

It is important to keep in mind that one of the goals of the Print Schema is to support schema extensions by providers. That is, providers are not restricted to using only those Property, Feature, Option, or ParameterInit instances defined in the Print Schema Keywords in the technologies built on the Print Schema Framework. Provider-specific element instances may be freely interspersed within element instances defined in the Print Schema Keywords. The only requirement is that provider-specific (that is, private) Property instances must belong to a namespace that is clearly associated with the provider.

Related topics

Print Schema Specification