FIMS Media SOA Framework - AMWA

FIMS Media SOA Framework Phase1 (Preliminary)outputFileName [0..1]descriptiveMetadata [0..1]serviceMetadata [0..1]notifyAtOptional - if provided it should be used to name the new file, otherwise nameshould be generated form source file name.Optional - contains user-defined metadata (description, comment etc.) forwrapperOptional - Used to provide a extension mechanism for service providerimplementations, e.g. File Division on Time code Break / Capture Speed /Acquisition of Metadata.Optional - contains replyTo and faultTo endpoint addresses. If provided, theservice must respond to the supplied URIs when job completion or failed statusoccurs.Table 1 Input Parameters of Capture ServiceTransform Service – Output Parameters (Ack)ParameteroperationInfoserviceProviderInfoDescriptionIncludes: operationName, jobID, jobGUID, statusIncludes sp name, endpointTable 2 Output Parameters (Ack) of Capture ServiceTransform Service – Output Parameters (Notification)ParameteroperationInfoserviceProviderInfobmoautoQCStatusDescriptionIncludes: operationName, jobID, jobGUID, statusIncludes sp name, endpointContains the reference to the output media.Includes: Captured File Information (AssetID, start & stop code, duration)Contains the result of Auto QC.Table 3 Output Parameters (Notification) of Capture Service9.1.2.1 Examples of transformProfile configurationIn the transformProfile, the selection of the AV processes (LUT, Resize, Burn-in, etc) and their configurations,the kinds of codec and file wrapper to be used in Transform service is described according to thetransformProfile schema defined elsewhere.Figures 9 and 10 show two indicative transformProfile configurations for ‘simple’ and ‘complex’ capturerespectively.Private committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 77 of 89