1 - 3 - 7 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W
semantic
Click on the red underlined text to get to the source
... RFC2568]
Internet Printing Protocol/1.0: Model and Semantics (this document)
Internet Printing Protocol/1.0: Encoding ...
... clients, applications, printer drivers, etc.) cooperate and interact
with print service providers. This model and semantics document
describes a simple, abstract model for IPP even though the underlying
...
... server-side protocol. The rest of the Printer object implements (or
gateways into) the application semantics of the print service itself.
The Printer objects may be embedded in an output device ...
... output
device and print service provider, a Printer object could be used to
represent any real or virtual device with semantics consistent with
the Printer object, such as a fax device, an imager, or even a CD ...
... the operation request.
This section describes the semantics of the IPP operations, both
requests and responses, in terms of the parameters, attributes, and
...
... Common Semantics ...
... IPP operations require some common parameters and operation
attributes. These common elements and their semantic characteristics
are defined and described in more detail in the following sections.
...
... See the 'charset' attribute syntax description in Section 4.1.7
for the syntax and semantic interpretation of the values of this
attribute and for example values.
...
...
See the 'naturalLanguage' attribute syntax description in
section 4.1.8 for the syntax and semantic interpretation of the
values of this attribute and for example values.
...
... so in some implementation specific manner.
The "status-code" value is a numeric value that has semantic meaning.
The "status-code" syntax is similar to a "type2 enum" (see section
4.1 on "Attribute Syntaxes") except that values can range ...
... IPP SHOULD convert status code values into
any localized message that has semantic meaning to the end user.
If the Printer object supports the "status-message" operation
attribute ...
... version number MUST change
when introducing a new version of the Model and Semantics document
[RFC2566] or a new version ...
... version number. Items that might affect the changing of the major
version number include any changes to the Model and Semantics
document [RFC2566] or the Encoding ...
... version to
the next are deprecated so that they can never be reused with new
semantics.
Implementations that support a certain major version ...
... operation attribute identifies the total
size of the document(s) in K octets being submitted (see section
4.3.17 for the complete semantics). If the client supplies the
...
... operation attribute identifies
the total size in number of impressions of the document(s) being
submitted (see section 4.3.18 for the complete semantics).
See note under "job-k-octets".
...
... operation attribute identifies the
total number of media sheets to be produced for this job (see
section 4.3.19 for the complete semantics).
See note under "job-k-octets".
...
... 4 includes the name of attribute syntax(es) in the heading (in
parentheses). A conforming implementation of an attribute MUST
include the semantics of the attribute syntax(es) so identified.
Section 6.3 describes how the protocol can be extended with new
attribute syntaxes.
...
... See Section 4.1.7 for the specification of the 'charset'
attribute syntax, including restricted semantics and examples of
charsets.
...
... letter. Furthermore, keywords MUST be in U.S. English.
This syntax type is used for enumerating semantic identifiers of
entities in the abstract protocol, i.e., entities identified in this
...
... be unique just within the scope of that attribute. That is, the same
keyword MUST NOT be used for two different values within the same
attribute to mean two different semantic ideas. However, the same
keyword MAY be used across two or more attributes, representing
different semantic ...
... semantic ideas. However, the same
keyword MAY be used across two or more attributes, representing
different semantic ideas for each attribute. Section 6.1 describes
how the protocol can be extended with new keyword values. Examples
of attribute name ...
... Charsets are used for labeling certain document contents and 'text'
and 'name' attribute values. The syntax and semantics of this
attribute syntax are specified in RFC 2046draft [RFC2046 ...
... resolution (positive integer value), and a units value. The
semantics of these three components are taken from the Printer MIB
[RFC1759 ...
... Note: The effect of this attribute on jobs with multiple documents
MAY be affected by the "multiple-document-handling" job attribute
(section 4.2.4), depending on the job sheet semantics.
...
...
Keywords are used within this document as identifiers of semantic
entities within the abstract model (see section 4.1.2.3). Attribute
names, some attribute values, attribute syntaxes, and attribute group ...
... for supporting a value is undefined and left up to the
implementation. However, if a Printer object supports a value, some
manual human action may be needed to realize the semantic action
associated with the value, but no end user action is required.
...
... This section defines status code enum keywords and values that are
used to provide semantic information on the results of an operation
request. Each operation response MUST include a status code. The
...
... IPP attributes to
take precedence over embedded job production instructions, a Printer
might not be able to support the semantics that IPP attributes
override the embedded instructions.
...
... IPP attribute values to the document data interpreter.
4) Anything else that allows for the semantics that IPP attributes
override embedded document data instructions.
...
... the document data also has the same PDL instruction, it will
override what the Printer object pre-pended. In other words,
this implementation is using the same implementation semantics
for the client-supplied IPP ...
... 2) Parse the document data and replace the conflicting embedded
instruction with a new embedded instruction that approximates,
but does not match, the semantic intent of the IPP attribute
value.
...
... when the document data contains embedded instructions depends on the
ability of the Printer to override the instructions embedded in the
document data with the semantics of the IPP attributes. If the
document data attributes can be overridden ("pdl-override-supported"
...