Remote GoToR annotation XFDF interchange

The mapped annotation codec preserves remote GoToR actions through native headless, ordinary loaded-document, and existing Windows/Linux callback annotation import and export paths

Interchange serializes PDF action data only; it does not execute an action, resolve a path, read a remote document, or open a viewer

Structure

<xfdf xmlns="http://ns.adobe.com/xfdf/">
  <annots>
    <link page="0" rect="10,10,30,30">
      <OnActivation><Action>
        <GoToR NewWindow="yes">
          <File OriginalName="../manuals/remote.pdf"/>
          <Dest><Fit Page="42"/></Dest>
        </GoToR>
      </Action></OnActivation>
    </link>
  </annots>
</xfdf>

GoToR requires exactly one File and one Dest child, in either order, and File requires OriginalName

Remote explicit destinations use a zero-based integer page in the remote document, from 0 through 2147483647, independently of the current document's page count

The saved remote destination starts with that integer rather than an indirect reference to a local page

Named targets retain their Unicode name without resolving a local destination name tree

The eight explicit destination modes retain their existing coordinate, nullable value and exact decimal behavior

NewWindow preserves omission, false and true separately; the bounded compatibility profile accepts yes/no, true/false and 1/0

File specifications and Unicode

Import creates an external Filespec dictionary with F and UF values; UF is the authoritative Unicode target and is represented using PDFDocEncoding or UTF-16BE with a BOM

F uses PDFDocEncoding when representable and otherwise retains UTF-8 compatibility bytes; older readers that ignore UF can interpret those fallback bytes differently

Paths remain opaque spellings without operating-system conversion or filesystem access

Export accepts an external file-specification string or dictionary and prefers UF over F

Validation and transactions

The entire remote action subtree follows the existing Adobe namespace profile, including correctly bound prefixes; the ordinary codec retains its explicit legacy unnamespaced compatibility profile

Foreign namespaces, duplicate or missing required children, unexpected attributes, invalid target types and malformed numeric or window values are rejected before a native transaction is published

Native snapshot preparation retains its existing byte, object, depth, working-storage and cancellation limits

Existing JSON operation records, public callback layouts and symbols remain unchanged

Windows ordinary imports also enforce authenticated current-graph, encryption and signed-revision policies

Format references and boundaries

The File, GoToR, OriginalName and NewWindow mapping follows Adobe's XML Forms Data Format Specification 3.0, printed pages 59, 63 and 87-88

Remote PDF action and file-specification semantics follow ISO 32000-1:2008, sections 7.11.2, 7.11.3 and 12.6.4.3

This path-only profile does not transport embedded GoToE documents, platform-specific file alternatives, filesystem selectors, descriptions, arbitrary action chains, AP streams or FDF action interchange