Upgrading your download site to support PAD4

If you are a download site operator (listed and supported on the ASP www.padsites.org) and you were using PAD version 3 on your site in the past, these instructions will help you upgrade to the version 4.0.

Kindly note that this upgrade is mandatory. Support for PAD v3.1 and prior versions are officially discontinued. The Association of Software Professionals, the PAD(R) certification mark owner, requests that all PAD sites stop accepting PAD v3 from publishers on your site and require the latest version 4.0 Specification. PAD® v4.0 is fully backward compatible with the existing PAD v3. No changes in your PAD processing scripts, catalog or database structure are required. We do encourage all sites to immediately utilize the new fields introduced in the PAD version 4 (like Windows 8 support, video, social links and many more…). These fields are optional. It is up to you, the site operator, whether to use them or not.

PAD 4 is fully backward compatible with PAD v3. No changes in your PAD processing scripts or database structure are required. You are welcome to use the new fields introduced in the PAD version 4 (like Windows 8 support, social links and more…). The new fields are optional for sites to deploy. It is up to you, the site operator, whether to use them or not.

There is one CRITICAL change that you need to make in order to upgrade your site to PAD version 4. All the PAD v4 files are securely hosted in the “Official PAD Repository”. In addition, all publisher application PAD files are automatically validated and verified by a staff of live professionals. All you need to do verify a submitted PAD file validity to your site, all you have to do is the PAD file host URL. If a PAD file comes from http://repository.appvisor.com, it is a valid secured authenticated PAD file for the application and by the publisher.

If a PAD file comes from an unauthorized source (does not contain the appvisor.com domain in its hosted URL, you are advised reject it with an appropriate error message. You can find technical details on implementing the v4.0 validation with sample code to validate PAD URLs at http://appvisor.com/on-line-pad-validator/

We also encourage all PAD-supported sites to send out a notification e-mail to their publisher community. Since as many as 50% of publishers may be using an automated submission tools, they may not notice that their PADs are getting rejected on your site.  An e-mail notification will help them not find out the problem and upgrade to PAD version 4.

Finally, the Official PAD Repository offers all PAD Sites an API that allows you to receive new and updated PAD files directly from the PAD v4 Repository. Please don’t hesitate to contact our support. Our developers will help you to integrate the PAD Repository API.

Please register as a download site on our http://operators.appvisor.com and please do contact the ASP’s PAD Chair, Joel Diamond at Joeld@appvisor.com for additional details on how the PAD v4.0 platform can immediately improve your site, lead to new revenue opportunities and lays the foundation for many exciting things to come with the release of the PAD v4.1 Specification.