9.1.1 Guidance to complete the form of
declaration
(1) Every declaration should be identified
for easy reference. Contact the Registrar to
have a unique number assigned before
submission of the declaration (e.g.,
99-I-001). Declarations of Interoperability
must refer to a previously submitted
Declaration of Compatibility for the same
product -- this declaration must be
referenced.
(2) The issuing supplier should be
unequivocally specified. For larger
companies, it may be necessary to specify
operation groups or departments.
Suppliers whose products that were tested
with the issuing suppliers should also be
unequivocally specified with their products.
(3) The "product" should be
unequivocally described so that the
declaration may be related to the product in
question.
("Product": it is sufficient to
give the name, type, model, version number,
etc.).
(4) Each of the products tested with the
issuing supplier’s product should be
listed including the supplier, product name,
date of testing and this vendor’s
Declaration number.
(5) The sub-heading text should appear
only if additional information is given. Such
information is typically required for
approval of the Declaration of
Interoperability, for example:
- the name and address of the test
laboratory or certification body (if
involved in the testing),
- description of test environment used
during testing (e.g., via firewall,
dial-up ISP),
- description of user agents used besides
the traditional telephone user interface,
- reference to attached or forthcoming
interoperability test reports (one
required for each of the bilateral tests)
, and
- any other information deemed important
for the conformance declaration.
(6) The number of signatures included will be
the minimum determined by the legal form of
the supplier’s organization.
(7) Contact information must be included
for at least one of the
"signatures". Typically, the most
important contact to list is the person
responsible for interoperability testing of
the product. The contact information must
include a phone number and email address.
The features of VPIM v2 are summarized in
"Appendix A - VPIM v2 Conformance", of
the specification, they are also included in this
document (see 8.1) in a format appropriate for
the Declaration of Compatibility.
o A 'MUST' feature must have a 'Y' or 'X'
(or 'C#' or '#') to indicate that it is
supported.
o A 'MUST NOT' feature must have a 'Y' or 'X'
(or 'C#' or '#') to indicate that feature is
not implemented.
o A 'SHOULD' feature would have a 'Y' or 'X'
(or 'C#' or '#') to indicate it is supported.
(i.e. that feature is in the product)
o A 'SHOULD NOT' feature would have a 'Y' or
'X' (or 'C#' or '#') indicating that the
feature is not implemented. (i.e. that
feature is not in the product)
o A 'MAY' feature would have a 'Y' or 'X' (or
'C#' or '#') to indicate it is supported.
(i.e. that feature is in the product)
However, if the product does not implement or
support a particular feature exactly as
explained in the VPIM specification, then the
feature is not supported. A feature that is
only partially supported must not be listed
as supported (i.e., ‘Y’ or
‘X’), instead the condition must be
described in an associated note (and noted in
the table as ‘C#’ or
‘#’).
