This
document was approved by the Steering Committee on
Introduction:
Once the parties have signed, the Forum Secretary will notify the general Membership via e-mail and post the Proposed DCP to the Document Archive of the member only section of the UPnP™ Forum Web site, officially starting the clock on the 60-Day Comment & Disclosure Period.
From Section 2.1(c) ii of the UPnP Forum Membership Agreement:
Prior to voting on a given Proposed DCP, the Steering Committee will make the Proposed DCP, Reference Implementation test logs, and test configuration files available to all Members for their comments and review. Simultaneously, the Secretary shall send electronically to UPnP Forum Members a notice, announcing the Comment and Disclosure Period, which shall state the name of the Proposed DCP, a copy of the Proposed DCP, Reference Implementation test logs, and test configuration files (or alternatively, the link(s) to a website in which the Proposed DCP, Reference Implementation test logs, and test configuration files are available for review), the names of the Members who contributed to the Proposed DCP, the start date of the Comment and Disclosure Period and the end date of the Comment and Disclosure Period. The Comment and Disclosure Period shall be at least sixty (60) calendar days and may be extended for an additional set period of time upon approval of three-fourths (3/4) of the entire then current Steering Committee; any Steering Committee representative abstaining from voting will be deemed to have voted against extending the Comment and Disclosure Period. The Secretary shall send electronically, contemporaneously a disclosure form with the notice announcing the Comment and Disclosure Period, for the purposes of Section 3.8 (a).
Upon the close of such Comment and Disclosure Period, the Secretary shall post all received comments and the Steering Committee will have ten (10) business days in which to adopt or reject the Proposed DCP as a Standardized DCP.
Terms:
“DCP” means device control protocol, including those portions of any Approved DCP Framework that are utilized by the device control protocol, which protocol enables interaction between a device associated with one Device Class and devices associated with the same or different Device Classes in a networked environment.
“Reference Implementation” means an implementation of a Proposed DCP and developed as part of the Working Committee process as set forth in Section 2.2 of the Membership Agreement.
“Proposed DCPs” means the specification defining the set of DCPs for a particular Device Class created by a Working Committee for submission to the Steering Committee for adoption as Standardized DCPs.
“Standardized DCPs” means the Proposed DCPs that have been approved by the Steering Committee as set forth in Section 2.1(c)(ii) of the Membership Agreement
“Sample Test Complete (STC)” means the Sample Reference Implementation is fully functional, demonstrates proof of concept per the UPnP test template and is submitted to the UPnP Forum for Proposed DCP approval. Fully functional does not imply semantic compliance, which is left to the individual Working Committee’s discretion.
“Template Design Complete (TDC)” means UPnP design template has been evaluated against the TDC checklist and is frozen by the Working Committee at Rev .9x (version number to be documented) for Sample Reference Implementation and Test.
Version and Date:
For the purpose of this form:
Summary tables of the devices and services in the DCP and the corresponding number of Reference Implementations and table of required XML Configuration Files are below. Auxiliary material(s) may be submitted to help in the interpretation and correct implementation of the specification.
To be completed by WC Chair:
|
R (required) |
O (optional) |
Number of Reference Implementations |
Device |
|
|
|
Service |
|
|
|
Service |
|
|
|
Device |
|
|
|
Service |
|
|
|
Service |
|
|
List of XML Configuration Files Required to Pass the Certification Test Tool for this DCP |
|
|
|
|
|
|
|
List of auxiliary material(s) submitted with this Proposed DCP (i.e. use case scenario, whitepaper, etc.) |
|
|
|
|
|
* The UPnP Certification Test Tool is provided for pre-certification purposes by Microsoft Corporation. In order to certify devices, vendors are required to follow the certification process as outlined by the UPnP Implementers Corporation (UIC).
The following parties hereby attest that:
Signature: _________________________________________ |
Date: ___________________ |
Signature: _________________________________________ |
Date: ___________________ |
Signature: _________________________________________ |
Date: ___________________ |
Signature: _________________________________________ |
Date: ___________________ |
I include a list of all devices and services in my implementation:
Device |
|
Service |
|
Service |
Signature: _________________________________________ |
Date: ___________________ |
I include a list of all devices and services in my implementation:
Device |
|
Service |
|
Service |
Signature: _________________________________________ |
Date: ___________________ |
I include a list of all devices and services in my implementation:
Device |
|
Service |
|
Service |
Signature: _________________________________________ |
Date: ___________________ |
I include a list of all devices and services in my implementation:
Device |
|
Service |
|
Service |
Signature: _________________________________________ |
Date: ___________________ |
I include a list of all devices and services in my implementation:
Device |
|
Service |
|
Service |
Signature: _________________________________________ |
Date: ___________________ |
I include a list of all devices and services in my implementation:
Device |
|
Service |
|
Service |
Signature: _________________________________________ |
Date: ___________________ |
Signature: _________________________________________ |
Date: ___________________ |
Signature: _________________________________________ |
Date: ___________________ |