...
Number | Description | Provisional Tools | Supported Tools |
---|---|---|---|
Support |
|
|
|
1.1 | Identified group of committers. |
|
|
|
| ||
1.3 | Two sites in production. Recommendations. | One | Two |
1.4 |
|
| |
1.5 |
|
| |
1.6.1 |
|
| |
1.6.2 |
|
| |
1.7 |
|
| |
Technical |
|
|
|
|
| ||
2.1.2 | Initialize databases appropriately. |
|
|
2.1.3 | All data access via APIs. |
|
|
2.2 | Configuration via Sakai properties. |
|
|
2.3.1 | Operate properly with Sakai authorization. |
|
|
2.3.2 | Operate properly with tool placement. |
|
|
2.3.3 | Use existing or publish security functions. |
|
|
2.4 | No patches to other tools or framework. |
|
|
2.5 | Must work in clustered server environment.1 |
|
|
2.6 | No new shared JARs. |
|
|
2.7 | Work with existing technology versions. |
|
|
2.8 | Clean licensing. |
|
|
2.9 | Compiled code must run in Tomcat.2 |
|
|
Interaction |
|
|
|
3.1.1 | Support the Sakai user experience.3,4 |
|
|
3.1.2 | Inherit skins from Sakai. |
|
|
3.1.3 | Follow Sakai Style Guide.3,4 |
|
|
3.2 | Use UI components where available.3,4 |
|
|
3.3 |
|
| |
3.4 | Provide basic help. |
|
|
Other |
|
|
|
4.1 | Internationalized from external strings. |
|
|
4.2 | Accessibility practices.4 |
|
|
4.3 | Separation of application services.6 |
|
|
4.4 | Web service API.6 |
|
|
4.5 | Participate in import and export.6 |
|
|
4.6 | Interoperate and integrate with other tools.6 |
|
|
4.7 | Generate event codes.6 |
|
|
4.8 | ORM Support.6 |
|
|
4.9 | Minimize functionality overlap. |
|
|
...