OpenSkills offers a number of services publicly. Some of these may be used by organisations separate from OpenSkills to promote their own goals, and these goals may be commercial in nature.
The default position is: OpenSkills offers no service level warranty for publicly available services (e.g. the SkillsBase).
OpenSkills has been aproached regarding the possibility of branded access to the SkillsBase. Such requests should be considered by the committee on a case-by-case baisis, but the following guildelines should be bourne in mind:
- OpenSkills should not warrant service availability. If an organisation would like to see specific service levels, they can work towards this by donating services which improve availability (e.g. paying for hosting on better hardware). Such agreements should give OpenSkills plenty of notice (i.e. >6 months) if they are to terminate.
- OpenSkills should not provide various levels of service. Interfaces in the OpenSkills run systems should be equally available to all. This need not prevent external organisations from building value-added solution. For example, if external organisation X wished to fund a developmet effort to add web-service interfaces to the SkillsBase and at the same time build systems that make imaginative use of these interfaces. The additional web services would be available to all. The particular system would be the property of X to do with as they wished.
- OpenSkills should not allow its systems to be swamped. This means that if a single entity, e.g. a company, is consuming an excessive amount of resources (e.g. bandwidth), OpenSkills should throttle back connections from them, or suggest that they fund a larger pipe for everyone.