One of the steps involved in getting your platform Sedona Framework certified
is that it must pass all tests
when run against the sedonacert test suite. The sedonacert program
verifies that 1) your platform is compliant with the Sox protocol and 2) your
platform can be provisioned in a standard way. In order for your platform to
pass the tests for provisioning, it must implement the following requirements:
Requirements
App and Scode naming requirements
- a Sox get file request for a file with URI
app.sabmust return the currently running app.sab file. - a Sox get file request for a file with URI
kits.scodemust return the currently running kits.scode file.
Standard provisioning process requirements
A Sox client must be able to provision a new app.sab and
kits.scode on your device by executing these steps:
- Write the new app.sab with URI
app.sab.writingusing a Sox put file request. - Write the new kits.scode with URI
kits.scode.writingusing a Sox put file request. - Rename URI
app.sab.writingto URIapp.sab.stageusing a Sox file rename request. - Rename URI
kits.scode.writingto URIkits.scode.stageusing a Sox file rename request. - Invoke the
restart()action on the device's platform service to restart the SVM. When the SVM restarts, it must use the newly staged app and scode files to run the application. See the section on bootstrapping for more details.