Services

Services are groupings of associated operations that are made available by World Engines and User Communities to allow dynamic manipulation of virtual world properties. All service specifications published on this site use the Web Services Description Language (WSDL 2.0), and are licensed under the GNU Lesser General Public License. They may therefore be used to create both open source and proprietary software products.

A service name is mapped to the name attribute of the interface element within the WSDL document that defines the service. An operation name is mapped to the name attribute of the operation element within the interface element. Zelestra Standards services and operations are defined by WSDL documents that include the types, interface, and binding elements only. The WSDL service element is not included in these specifications because service endpoints are implementation specific. The WSDL documents specified here may be directly included into the actual service defining WSDL documents referenced by the Services element of documents of type DefinitionElementType. Where it is necessary, previous authentication of the requestor is assumed. All HTTP bindings that require authentication have whttp:cookies set to true and return an Unauthorized fault as needed.

Service operations MAY be implemented as REST based web services. Request parameters may be supplied as URL Encoded parameters, or as XML or JSON formatted content. URL Encoded parameter names are in lowerCamelCase. XML tag names are in UpperCamelCase. JSON attribute names are in lowerCamelCase. The HTTP ContentType header of the request should be set to the appropriate MIME type for the request. A JSONP formatted response may be requested by including callback=method as a parameter in the request. The response format is determined by the HTTP Accept header. If a specified response format can not be determined by the request's Accept header, then the request's ContentType header may be used to help determine the appropriate response format, otherwise a default response format is supplied which is usually XML. A specific response format may be forced using a URL Encoded parameter of format=format. Where format can be json or xml. If the callback parameter is specified, then the response is returned as JSONP.

Core Framework

The core framework provides the fundamental services required for distributed virtual world development.

Clips Framework

The clips framework extends the core framework by adding service definitions for managing multimedia clips.