What a PrintCapabilities Document Is Not
This topic is not current. For the most current information, see the Print Schema Specification.
It is worthwhile to list some of the functionality and information the PrintCapabilities document is not intended to provide.
A PrintCapabilities document:
Does not represent multivalued (configuration-dependent) data.
Each PrintCapabilities document is constructed for a specific configuration. No Property or ScoredProperty in the document can have a Value that depends on the particular configuration. In the initial schema version, the PrintCapabilities provider must process the input PrintTicket and create a PrintCapabilities document that contains Property values appropriate for the configuration specified in the PrintTicket.
Does not contain constraint information.
The PrintCapabilities document does not indicate which configurations are allowed and which are not allowed. In the initial schema version, the PrintCapabilities provider must store any information needed to validate configurations, supply a method that validates the input PrintTicket, and return a corrected PrintTicket in the event that the specified PrintTicket violates one or more constraints.
Does not contain dynamic device information.
There is too much overhead involved in constructing the PrintCapabilities document for it to be used to hold rapidly changing status information, such as ink levels, paper remaining in each tray, or paper jam status.