Proposed Service Discovery Capability/Configuration Description EBU-AMWA FIMS

Capture related Capability Description Following three files seem to be required so that an Orchestration System can issue request message properly: –WSDL Describe interfaces. –Capability Description Describe functions (parameters) which the service support. –Configuration Description Describe source configurations (source ID, source type etc.) which are connected to the service. These file locations are now implicit understanding basis. –We would like to propose the inquiry message for at least obtaining URIs of the Capability/Configuration file locations. –It would be the system policy if the message is used.

Service Capability & Configuration Inquiry Message QueryCapabilityRequestType capabilitySerlection[1…1]ServiceCapabilitySelectionType queryCapabilityRequest [QueryCapabilityRequestType] queryCapabilityResponse [QueryCapabilityResponseType] QueryCapabilityResponseType capability[1…1]ServiceCapabilityAbstractType - ServiceCapabilityByReferenceType ref[1…1]xs:anyURI ServiceCapabilityByReferenceType value[1…1]ServiceCapabilityType Capability XML file URI Capability Schema (TBD) ENUM which specifies type of capability to obtain. - ref : Obtain "Capability XML file URI" - value : Obtain "Capability XML" ENUM which specifies type of capability to obtain. - ref : Obtain "Capability XML file URI" - value : Obtain "Capability XML" Above example is the case where Capability and Configuration are described in the same XML file. In the case where Capability and Configuration are described in the different XML files, parameters for configuration need to be added.

Capture related Capability Description CategoryParameterDescription Basic Capability StartJob Describe if following types are supported. Time, Latest It corresponds to whether PQ1 is implemented. FinishBefore Describe if supported? It corresponds to if the service can manage QoS and controls the job completion time. Note that even if a service does not itself support the function to control the job completion time, a requester should specify FinishBefore as a deadline when either External Trigger or TimeMark is specified in the startProcess or the stopProcess. Capture Capability StartProcess Describe if following types are supported?.Time, TimeMark(timecode, elapsed time, elapsed unit, time), SourceDefinedTime StopProcess Describe if following types are supported. Time, TimeMark(timecode, elapsed time, elapsed unit, time), SourceDefinedTime, duration (time, media unit) OutputFileNamePattern Describe whether this parameter is supported. It means the service can create file name according to the specified pattern. SplitOnTCBreakDescribe whether this parameter is supported. WrapperMetadata Describe the maximum number of wrapper metadata to be described. If this parameter is not supported, describe "0". ProcessesDescribe the maximum number of processes to be requested. ProfilesDescribe the maximum number of profiles to be requested.

Capture related Configuration Description Each Capture service is supposed to advertise their source configurations by "Configuration Description". ID number shall be unique within a service. ID Number Source Type Minimum time between StartJob and StartProcess Description 1VTR5 Minutes 2FEED5 Frames N--