.. /*  
    * This file is part of the SavaPage project <https://www.savapage.org>.
    * Copyright (c) 2026 Datraverse B.V.
    * Author: Rijk Ravestein.
    *
    * SPDX-FileCopyrightText: (c) 2020 Datraverse B.V. <info@datraverse.com>
    * SPDX-License-Identifier: CC-BY-SA-4.0
    *
    * For more information, please contact Datraverse B.V. at this
    * address: info@datraverse.com
    */

.. _app-ipp-ext-external:

External IPP Extensions
-----------------------

External IPP Extension attributes as defined in implementation specific
configuration files. To distinguish them from IANA registrations, their
names have a ``org.savapage.ext-`` prefix.

.. important::

   External IPP attributes can be used as IPP Job Ticketing Extension
   only.

The syntax is as follows:

-  External *value* extensions with “type2 keyword” syntax must be
   ``ext.`` prefixed.

-  Value ``none`` is a reserved internal value, indicating that the
   attribute option is not selected.

-  External attribute values can be added to an
   :ref: `Internal IPP Job Ticket Extension <app-ipp-ext-internal-jobticket>`.

   -  For example: to charge cost for a finishing to wrap a printed copy
      into a folder, a ``ext.folder`` value could be added to
      :ref:`org.savapage-finishings-ext <app-ipp-org.savapage-finishings-ext>`.

External IPP Extensions open the way to full customization of Job
Ticketing options. Any option with any number of choices can be
configured in a PPDE file as ``*SPJobTicket/Copy`` finishing, and
thereupon be used in any cost rule. See 
:ref:`Using External IPP Extensions <app-ppd-ext-job-ticket-copy-options-ext>`
and :ref:`IPP Localization <app-ipp-ext-localization>`.