Resumo de Pad File

PAD Extensions
For situations, where the company and

product information in a PAD file is not sufficient,
the

PAD concept introduces a process to extend the default

dataset by custom fields.
PAD Extensions support is

part of the PAD Specification . A PAD Extension is a
set of

additional data fields that will be added to PAD files

within a separate XML node. A PAD Extension is defined

within a single HTML file including a form
representation

of the extension. Anyone may define a PAD Extension,
but

registration with the ASP is required to avoid naming

conflicts. If you plan to create a PAD Extension, see
below

for the Specification for PAD Extension Creation.

PAD

generation tools need to support PAD Extensions by

implementing plug-in capabilities to display an input
form

for each extension, validate the input, and add the
data to

the resulting PAD file. If you plan to implement PAD

Extension support within your PAD generation tool, see

below for the Specification for PAD Extension
Integration

into PAD Generation Tools.
The following
specification

is very generic, see below for some Examples.
For a

list of PAD Extensions see the PAD Extensions
Directory .

Specification for PAD Extension Creation
A PAD

Extension is defined within the HTML document format
(Note:

Although HTML is used, PAD Extensions are not subject
to be

displayed in web browsers). The following rules have to
be

respected when creating a PAD Extension:
A PAD

Extension needs to have an exclusive name, the
extension

identifier. The extension identifier has to be one
word,

only containing the characters A-Z, a-z, the numbers 0-
9

and the _ underscore, no blanks. To ensure that an

extension identifier is really unique, reservation with
the

ASP is required. Contact PAD Support to reserve your

identifier. This will ensure that your identifier is
not

yet used by someone else, and will not be issued twice.

The extension needs to be stored in a file named

[extension identifier].htm
The extension file must
be a

valid HTML 3.2 file, using the , and tags correctly.

The tag within the needs to contain the exact

extension identifier.
The needs to contain a .
The

tag does not need to have any attributes (like ACTION).
It

must not contain a submit button.
Within the form,

there needs to be a tag with the attribute NAME set

to "[extension identifier]_FORM" and the VALUE set
to "Y".

Within the form, there needs to be a tag with the

attribute NAME set to "[extension identifier]
_DESCRIPTION"

and the VALUE set to a brief, one-line description of
the

extension's purpose. The description will show up on
the

PAD Extensions Directory .
Within the form, there
needs

to be a tag with the attribute NAME set to "[extension

identifier]_VERSION" and the VALUE set to the version
of

the extension. The version should be incremented on
changes

to the extension.
Within the form, there needs to
be a

tag with the attribute NAME set to "[extension
identifier]

specific or "Program" if it is program information

specific. If the scope is both company and program

specific, "Program" should be set. PAD generation tools

that support saving company information to a central
place,

so it does not . The second one has

Resumos Relacionados