Schema for a TesLA Alliance standard command definition file (*.TCD) The default binding is defined at the DCA level. Attributes in bindings above a command and closer than the default override those defined in the default. Defines invocation syntax for for a specific binding and method as described in document at location referenced in bindingSpec. procedureCall element within a command element takes precedence over those at higher level. vendor-defined grouping for commands. Also see keyword element(s). additional locations for commands added after initial installation by DCA provider XML Schema segment describing structure of vendor-defined response. PRE-DEFINED ELEMENTS: vcCode (mandatory), tcCode (optional), vendorExtension (optional). See spec for structure. XML schema segment describing parameter (which may have multiple elements). Use of include statements encouraged. unsupported vendor-specific use, not parsed by DCA Consumer - passed in as-is as part of XML parameter Unless the default binding can be used, there should be one of these elements per binding for each command. other names for this command. Used by Consumers to determine equivalence with other similar commands. name of this command - must be unique in namespace defined in this command definition file. if absent, use name Commands may be included that are in various stages of development - and may never be fully supported. This could be alpha, beta, custom, customer-specific, internal, deprecated or GA (for example). Consumers should ONLY use GA commands unless otherwise arranged with Publisher and/or customer. The use of bindings is governed by the specification referenced at bindingSpec for each binding. Vendor-created URI in their domain link to specification describing use of this binding. The DCA standard only includes binding usage by reference. description of each possible vendor return code and message lookup. a vcCode is MANDATORY within the responseXSD. TesLA-defined return code with optional message. As this will be written into spec, inclusion here is optional and for convenience only. a tcCode is OPTIONAL within the response XSD. XML Schema segment describing structure of vendor-defined response. PRE-DEFINED ELEMENTS: vcCode (mandatory), tcCode (optional), vendorExtension (optional). See spec for structure. commandGroup may contain any number of commands and sub-groups