Previous Next

                                       1020
APPENDIX E                                                       PDF Name Registry



  class names. Plug-in extensions that are publicly available should often use
  first-class names for their private data. First-class names and data formats must
  be registered with Adobe and are made available for all developers to use. To
  submit a private name and format for consideration as first-class, see the link
  on registering a private PDF extension, at the following Web page:
     < http://adobe.com/go/acrobat_developer >
• Second class. Names that are applicable to a specific developer. (Adobe does not
  register second-class data formats.) Adobe distributes second-class names by
  registering developer-specific prefixes, which must be used as the first char-
  acters in the names of all private data added by the developer. Adobe will not
  register the same prefix to two different developers, thereby ensuring that dif-
  ferent developers’ second-class names do not conflict. It is the responsibility of
  the developer not to use the same name in conflicting ways. To register a devel-
  oper-specific prefix, use the Acrobat SDK feedback form accessible through the
  following Web page:
     < http://adobe.com/go/acrobat_developer >
• Third class. Names that can be used only in files that other third parties will
  never see because they may conflict with third-class names defined by others.
  Third-class names all begin with a specific prefix reserved by Adobe for private
  plug-in extensions. This prefix, which is XX, must be used as the first characters
  in the names of all private data added by the developer. It is not necessary to
  contact Adobe to register third-class names.

Note: New keys for the document information dictionary (see Section 10.2.1, “Doc-
ument Information Dictionary”) or a thread information dictionary (in the I entry
of a thread dictionary; see Section 8.3.2, “Articles”) need not be registered.

Previous Next