You are here: Developer Guides > SDK for .NET Programming Guide > Events for Building a Translation Connector
A translation management system (TMS) or machine translation (MT) service implements a Clay Tablet Translation Connector to:
- receive translation requests and download files for translation from the Clay Tablet Platform, using events. For details, see Events a Translation Connector Receives. For an example of using events to receive requests and files for translation, see Code Sample: Retrieving Messages, Deserializing Event Objects, and Handling Events.
- retrieve metadata about a translation job. For details, see Retrieving Job Metadata.
- use event to send translated content to the Clay Tablet Platform, where it can be retrieved by the CMS. For details, see Events a Translation Connector Can Send. For examples of using events to send status updates and translated content, see Code Sample: Sending Translation Status or Translated Files.
The Clay Tablet Platform uses Message Queues to provide asynchronous communications with external applications, such as a TMS or an MT service. For information about asynchronous communications, see http://en.wikipedia.org/wiki/Asynchronous_communication.
Note about the XML format of assets sent for translation: The format in which you send content for translation is important. There is an industry standard called XLIFF, which we recommend you review and adhere to if possible for content sent for translation. For information about this standard, see: http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html