FIMS Media SOA Framework - AMWA

FIMS Media SOA Framework Phase1 (Preliminary)8.2.1.2.1.2.2 MetadataTagTyperequired format and make intelligentdecision on the choice of a suitableprovider for a media-processing job. Itshould be noted that the profile mightcarry (in the “any” container) serviceproviderspecific information to map eachspecified format ID to the service providerspecific format definitions.A metadata tag type provides a simple tag/value pair for simple metadata tagging.8.2.1.2.2 Transcode Request AcknowledgementWhen a job is submitted to the transform media service, the service shall reply with an acknowledgement. Theacknowledgement message uses the BaseResponseType described in the base schema.8.2.1.2.3 TransformFaultTypeThis type provides the fault information for the transform media service. It extends the base FaultType, andadds an extended code which allows to set adapter-specific error codes if needed. If an exception is generatedwhen the transform request message is submitted to the adapter, the adapter shall respond with a messagebased on the TransformFaultType.Specific error codes for the transform media service are enumerated in TransformErrorCodeType such as:- DATA0101: Invalid target media format8.2.1.2.4 TranscodeNotificationTypeIf the notifyAt element is set in the job transcode request, then the service shall respond with a notification tothe specified endpoint when the job completes. The transcode notification message uses theTranscodeNotificationType, which extends the MediaResponseType described in the base schema.The optional autoQCStatus element provides status information for a transform media service that supportautomatic QC of the transformed content. The status values enumerated in AutoQCStatusCodeType are thefollowing:- passed: the QC was completed with successPrivate committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 45 of 89