General Comments from Sony Sony Corporation Toshiaki Kojima Mizuki Kanada.

General Commentsfrom SonySony CorporationToshiaki KojimaMizuki Kanada

Comment G1page10: Figure2

[E1] Service Capability, Capability Description, and Service Configuration in this specification should be changed to Service Description.- editorial[Part1] page 10: Figure2

Comment G2page16: Figure4

The thick circles in Figure 4 indicate the mandatory states that shall be implemented.[S1] Is Queued mandatory? - agreed NOT mandatory

[Part1] page 16: Figure 4

Comment G3page17: 6.2.1 Lifecycle of a jobAn external command may force the early termination of a job execution. To terminate a job means to force its completion. This is not an error situation and the result of the job processing until that moment is considered to be the result of the job execution.[S2] Terminate command can be used instead of CaptureStop Request command.[S3] As CaptureStopRequest is bound to the same port as request, if a service does not support queue, the service could not get this message forever.

[Part1] page 17: 6.2.1 Lifecycle of a job

Comment G4page20: 7.2.1 Schema of Service DescriptionThe file ServiceDiscoveryResponse.xsd represents an XML schema which shall be used to validate any response. The following sections describe the elements within this schema.[E1] Should be changed to Service Description - agreed, editorial[Part2_Base] page 90: S0.2 Service Description

Comment G5page20: 7.2.2.2 Service EndpointThe service shall indicate the URL to find and communicate with the service. - discuss[S4] Several URLs are defined for a service, Job Request, Manage Request, Notification. Is this URL for WSDL?[Part2_Base] page 90: S0.2.1.2 Service Endpoint

Comment G6page21: 7.2.2.7 Service Timing ModelsA service shall declare the FIMS timing models that are supported as a list. List entries shall be unique, and shall be the class name of any concrete Start and Stop types defined in section 9.2.4 and inheriting from any of StartJobAbstractType, StartProcessAbstractType and StopProcessAbstractType.[E2] No description of finishBefore. - agreed, editorial[Part2_Base] page 91: S0.2.1.7 Service Timing Models

Comment G7page21: 7.2.3 Transfer CapabilityAny service that uses Transfer Atoms within the description of a request (presently, all 3 do) may report the transfer capabilities that the system will work with.[S5] Description of Atom should be in the Base Description.- already done[Part2_Transfer] page 7: S1.2 Transfer Description

Comment G8page22: 7.2.3.2 Transfer Options

[S6] Is there anonymous SFTP? - agreed, delete 'Anonymous'[S7] Is any kind of URI allowed? - add note: uri syntax means a uri syntax has a form file:- Peter to supply text

[Part2_Transfer] page 7: S1.2.2 Transfer Options

Transfer ClassDescriptionProtocol OptionsFTPStandard FTP transfer protocol, as described by RFC959Anonymous, PassiveSFTPSSH File Transfer Protocol (also Secure File Transfer Protocol, Secure FTP, or SFTP). Currently a draft IETF standard available here: http://tools.ietf.org/html/draft-ietf-secsh-filexfer-13AnonymousHTTPStandard HTTP 1.1 transfer protocol, as described by RFC2616HTTP/TLSExtension of HTTP 1.1 to enable secure transfer, as described by RFC2818FILEFile-based access, with a required syntax option specifying unix, url , unc or dos formatting.Anonymous, Syntax

Comment G9page22: 7.2.3.2.2 DirectionEach option may define directionality to the transfer. This directionality determines if the service will collect the referenced input (input pull), must have content delivered (input push), will emit to a referenced location (output push) or will detail an output collection location (output pull). If this attribute is not defined, the transfer option is assumed to support both push and pull operations.For example, if a service does not deliver the output of a job, but returns a reference to access the results via FTP, this service supports FTP output pull[S8] Does not understand the intention of Push/Pull- delete, fix schema.[Part2_Transfer] page 7: S1.2.2.2 Direction

Comment G10page23: 7.2.4 Transform CapabilitiesAny service that uses Transform Atoms within the description of a request may report the transform capabilities and constraints that the system will work with.[S5] Description of Atom should be in the Base Description. - already done[Part2_Transform] page 8: S2.2 Transform Description

Comment G11page24 7.2.5 Capture CapabilitiesAny service that uses Capture Atoms within the description of a request may report the Capture capabilities and constraints that the system will work with.[S9] There is NO Capture Atoms.- agreed, delete[Part2_Capture] page 16: S3.2 Capture Description

Comment G12page25: 8.1.1.2 Asynchronous Request/Response with Notification[S10] As commented in Comment [P2], it should be described whether both Notification and Polling mandatory or one of them? - discuss[Part1] page 20: 8.1.1.2 Asynchronous Request/Response with Notification

Comment G13page26: 8.1.1.3 Asynchronous Request/Response with PollingThis is another interaction pattern for long running processes, where the preferred interaction pattern is not possible (e.g. a firewall preventing a service to call back a client). It is similar to the Asynchronous Request/Response with Polling interaction mode with the exception that a notification is not sent by the service when the service completes the operation. The notifyAt parameter shall not be provided for the service to operate in this mode. [E3] Should be Notification. - agreed, editorial[Part1] page 21: 8.1.1.3 Asynchronous Request/Response with Polling

Comment G14page30: 8.1.5 Job QueueThe service shall implement the manageQueue operation to process queue commands. In case the service does not implement a queue it shall respond with Feature Not Supported error code.A job queue may have a maximum size and when it is reached no more jobs will be accepted. A fault indicating the queue is full shall be thrown by the service when a client issues a new job request (ErrorCode APP0107).[E4] Should be consistent with below (including ErrorCode number)- agreed, editorial[Part1] page 25: 8.1.5 Job Queue

Comment G15page32: 8.1.9 JobsAn essential aspect for the management of long-running media operations is the ability to check the status and interact with requested jobs. For example, the following tasks might be performed for transcoding operations:Check the status of a job or list of jobsCancel an active job Pause an active job Stop an active jobChange priority of a job Clear a queue Lock/unlock a queue[E5] No definition of stop. Is this terminate?- agreed, editorial[Part1] page 27: 8.1.9 Jobs

Comment G16page34: 8.2.1.1 Concept4.finishBeforefinishBefore is one of the elements of the BaseRequestType, and is applicable to any service. It specifies the time by which the job shall have been completed. [S11] Need to discuss exact meaning of finishBefore. See Comment [P5]- discuss.[Part1] page 29: 8.2.1.1 Concept

Comment G17page38: Profiles

[E6] atoms is NOT included in BaseProfileType.- agreed, update picture (editorial)

[Part1] page 32: 8.2.2 Profiles

Comment G18page38: ProfilesA profile instance (a set of operational parameters) is captured by an id, which is relevant to the business process, and by an optional name and description. Specific Profile types for define FIMS service interfaces are created by extending the BaseProfileType. If a custom profile is required for extension beyond the specification, the custom profile should inherit from an appropriate specified profile. Where possible, implementations should use the specified profiles and not a custom profile.[S12] Definition of Profile should be re-discussed. BaseProfileType still needed?- discuss[Part1] page 32: 8.2.2 Profiles

Comment G19page40: 8.2.3.1 Transfer ServiceThe Transfer Service copies or, optionally, moves one or more files to another place (or to several places). The FIMS version 1 specification permits 5 different transfer protocols. These are HTTP, HTTPS, FTP, SFTP and FILE. A Transfer Service may implement one or more of these protocols, but a Transfer Service shall implement at least one protocol for an input and an output (although these do not need to match).[S13] How to use move function?- agreed, delete "or, optionally moves"[Part2_Transfer] page 2: S1.1 Transfer Service Interface

Comment G20page40: 8.2.3.3 Capture ServiceThe Capture Service interface builds on the Transform Service interface, but is constrained to support isochronous stream-based input, for example an HD-SDI or RTP stream. [S14] How to handle this in the current specification?- agreed, add the necessary parameters (Richard to propose) - consider additional Service Description[Part2_Capture] page 2: S3.1 Capture Service Interface

Comment G21page44: 9.2.1.1 BaseRequestType

[S15] Need to discuss exact meaning of finishBefore. See Comment [P5.]- discuss when we discuss P5 [Part2_Base] page 4: S0.1.1.2.1.1 BaseRequestType

Comment G22page46: 9.2.1.2 BaseResponseType, etc.

[E7] Need consistency Note?(page6: 2 Conformance Languate)All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as "Informative" or individual paragraphs that start with "Note: - agreed: editorial, use "Note:". [Part2_Base] page 6: S0.1.1.2.1.2 BaseResponseType

Comment G23page46: 9.2.1.2 BaseResponseType

[S16] See Comment [P5].Should re-consider the necessity. - Need to make consistent rule throughout the specification like: 1. One type has one "extension" with same type 2. Remove "extension" until it is needed.- discuss when we discuss P5

[Part2_Base] page 6: S0.1.1.2.1.2 BaseResponseType

Comment G24page47: 9.2.1.4 MediaResponseTypepage48: 9.2.1.6 ComplexMediaResponse

[E8] Old diagram. (not BMContentType but BMContentFormatType).- agreed, delete - DONE (see slide 26)[Part2_Base] page 8: S0.1.1.2.1.4 MediaResponseTypepage10: S0.1.1.2.1.6 ComplexMediaTResponseype

Comment G25page47: 9.2.1.5 ComplexMediaRequestTypepage47: 9.2.1.6 ComplexMedaiResponseTypepage60: 9.2.3.3 BMComplexObjectTypepage61: 9.2.3.4 BMFolderType[S17] Not in use in V1.00. Remove?- agreed, delete[Part2_Base] page 8: S0.1.1.2.1.5 ComplexMediaRequestTypepage10: S0.1.1.2.1.6 ComplexMediaTResponseypepage64: S0.1.2.6.3 BMComplexObjectTypepage65: S0.1.2.6.1 BMFolderType

Comment G26page48: 9.2.1.6 ComplexMedaiResponseType

[S18] Not consistent with MediaResponseType- DONE (deleted).(MediaResponseType)[Part2_Base] page10: S0.1.1.2.1.6 ComplexMediaResponseype

bmResultMapThis element provides the relationship between the content components in input to a job and the content component on output from the job. The framework may exploit this information to track media content as it moves along a business process. This element shall be provided when a job produces media content in output for some input media content. If the content is not produced from the input media content, then this element should not be set (e.g. a retrieve content operation or capture content from tape should not use this element).BMResultMapTypeNoNo

bmResultMapProvides the relationship between the content components in input to a job and the content component in output from the job. The framework may exploit this information to track media content as it moves along a business process. This element shall be provided when a job produces media content in output for some input media content. If the content is not produced from input media content, then this element shall not be set (e.g. a retrieve content operation or capture content from tape shall not use this element).BMResultMapTypeNoNo

Comment G27page50: 9.2.1.8.1 PriorityTypeEnumerates the list of possible values for priority: "low", "medium", "high", "urgent" and "immediate". The priority handling by the services is discussed in 6.2.6.[E9] 8.1.6?- check that link is correct[Part2_Base] page11: S0.1.1.2.2.1 PriorityType

Comment G28page57: 9.2.2.3.1ServiceCapabilitySelectionTypeThis is an enumeration of the list of the service capability type: -ref: obtain the capability XML file URI.-value: obtain the capability XML.[S19] Do we need value type?- agreed, delete "value" type[Part2_Base] page30: S0.1.1.4.2.1 ServiceCapabilitySelectionType

Comment G29page62: BMContentFormatType

[S20] Does a service or an orchestration system need to distinguish whether URL or ID?Amend to: "A reference to the location of the essence that shall be a URI, see RFC2396.",delete following sentence. [S21] Are NFS, CIFS included in the supported protocols for the Transfer Service? - yesS20S21[Part2_Base] page66: S0.1.2.6.5 BMContentFormatType

NameDescriptionTypeRequiredArraylocatorA reference to the location of the essence. The URI shall be either a URL or a unique id. A unique id can be used for frameworks where media references are stored in a media repository. In this case the media repository shall provide a mechanism to access a reference to the physical essence. If a URL, the URL field shall follow the standard structure for a URL as defined in RFC1738 - Uniform Resource Locators (URL). In case of a file protocol scheme, the host field shall explicitly be included in the URL. The URL covers different protocol schemes, such as NFS mounts RFC2224, which defines nfs://[host]:[port]/[directory].../[filename], and the internet draft for the smb: scheme for CIFS.xs:anyURIYesNo

Comment G30page65: ResourceInfoType

[S22] Whats the relationship between this and locator in BMContentFormatType?- Praveen to supply text to clarify[S23] Is there any intention that BMO is used for other than file in the future?- yes, but for the future.S22S23[Part2_Base] page 69: S0.1.2.6.7.1 ResourceInfoType

NameDescriptionTypeRequiredArraystorageTypeThe storage type, enumerated in StorageEnumType (e.g. "online").StorageEnumTypeYesNolocationInfoAn element for providing user information on the geographical location of the content (e.g. 'New York')xs:stringYesNolocatorAn "address for a resource". For an organization or producer acting as caretaker for a media resource, this field may contain information about a specific e.g. tape name, shelf location for an asset, including an organizations name, departmental name, shelf id. and contact information. The locator for a data file or web page may include a complete URI with a domain, path, filename or html URL. See http://tools.ietf.org/html/rfc3986. Example: Archives Building A, Row J, Shelf 2". See also 'locator' on EBU Tech 3293.xs:stringNoNo

Comment G31page67: 9.2.3.7.5 DescriptiveMetadataByValueType

[E10] Invalid XML.- No xsi:type= in tag.- tag is not closed.- yes, editorial

[Part2_Base] page 50: S0.1.2.5.1.1 DescriptiveMetadataByValueType

Program title John

Comment G32page68: 9.2.3.7.7.1 VideoFormatType

[E11] This diagram is NOT made by IBM tool- editorial, IBM to supply diagram.[Part2_Base] page 53: S0.1.2.5.2.1 VideoFormatType

Comment G33page77: 9.2.4.8 StartProcessByTimeMarkTypepage78: 9.2.4.13 StopProcessByTimeMarkTypepage79: 9.2.4.16 TimeType

[S24] Are normalPlayTime and editUnitNumber needed? See comment [P15].TimeType is used only by StartProcessByTimeMarkType, StopProcessByTimeMarkType, SourceInPointByTimeMarkType, and SourceOutPointByTimeMarkType. These types do NOT use normalPlayTime and editUnitNumber.[S25] TimeType should be TimeMarkType?- add note to say TimeType aligns with EBUCore - J-P- durationType - check: J-P [Part2_Base]

page 73: S0.1.2.7.2.3 StartProcessByTimeMarkTypepage 77: S0.1.2.7.4.1 TimeType

Comment G34page82: 9.2.5.3 ManageQueueResponseTypeThis type provides a mechanism to manage a queue, for example checking the status of the queue, stopping and starting the queue and locking the queue. The queue management request uses the queueCommand to set the intent of the command (requesting status or acting on the queue state).[E12] Description of ErrorCode when a service does not support queue need to be added.- add field to ManageQueueResponseType in 9.2.5.4[Part2_Base] page 18: S0.1.1.3.1.3 ManageQueueRequestType

Comment G35page84: 9.2.5.8 QueryJobResponseType

[E13] Old diagram (two jobInfos are existing).- check schema, update diagram (IBM)[Part2_Base] page 23: S0.1.1.3.1.6 QueryJobResponseType

Comment G36page89: JobInfoSelectionType

[S26] See Comment [P11].Because "extendedJobInfo" has option parameters, it would be better to make all parameters in "extendedJobInfo" optional and combine to "compactJobInfo"- Praveen to considerIn this case, jobInfoSelection can be changed to "includedJobInfo" like "includedJobResult". - consider laterAlso the name "compactJobInfo" should change to "jobInfo" for consistency.[E14] Indent error. - check pdf[Part2_Base] page 43: S0.1.2.4.1 JobInfoSelectionType

Comment G37page90: 9.2.5.10.14 QueryJobInfoType

[E15] Old diagram (anyAttribute is NOT included in QueryJobInfoType).- check/correct schema/diagram (IBM)[Part2_Base] page 44: S0.1.2.4.2 QueryJobInfoType

Comment G38page91: 9.2.5.10.15 JobInfoType

[S27] See Comment P5.Should re-consider the necessity. - Need to make consistent rule throughout the specification like: 1. One type has one "extension" with same type 2. Remove "extension" until it is needed. consider later (Service description)

[Part2_Base] page 45: S0.1.2.4.3 JobInfoType

Comment G39page91: 9.2.5.10.15 JobInfoType

[E16] Should describe mandatory if queue is supported.- agreed. Add text to 9.2.5.10.15

[Part2_Base] page 45: S0.1.2.4.3 JobInfoType

currentQueuePositionThe position of the job in the queue.xs:nonNegativeIntegerNoNo

Comment G40page93: 9.2.5.10.16 JobExtendedInfoTypeThis type provides detailed information on a job, such as the status, the job ID, the current priority and several job statistics. It extends JobInfoType[E17] These are NOT items of JobExtendedInfoType BUT items of JobInfoType- Should be: "This type extends JobInforTye and provides detailed information on a job."Delete the rest[Part2_Base] page 46: S0.1.2.4.4 JobExtendedInfoType

Comment G41page97: 9.2.6.2 TransferAtomType[Informative] Some parameters might be added to the profile in future version to specify network resource utilization, a list of acceptable transfer mechanisms or additional security options including whether the received files should be checked against a fingerprint and whether they are encrypted.[E18] Atom?- agreed, replace "profile" with "Atom"[Part2_Base] page 80: S0.1.3.1 TransferAtomType

Comment G42page100: 9.3.1 Transfer Service InterfaceA transfer media service allows copying, moving, or accessing media files over local and/or wide area IP networks. The same interface supports transfer, in accordance with the following requirement: The destination parameter shall be a URL providing the target agent URL.(For example: https://target.broadcaster.com/transfer-agent/)[E18] We forgot to delete the sentence when destination parameter was moved to Atom. Remove. - agreed[Part2_Transfer] page 2: S1.1 Transfer Service Interface

Comment G43page100: 9.3.1.1 TransferRequestType

[E19] This is an old Profile definition.- separate discussion on Profile[E20] This describes Atom. We forgot to delete the sentence. Remove. - agreedE19E20[Part2_Transfer] page 2: S1.1.1.1 TransferRequestType

NameDescriptionTypeRequiredArraytransferProfileThis element represents the profile used by the transfer media service to transfer files. The profile provides a mechanism to specify service-specific information for each service provide by BaseProfileType. Each profile can specifies one destination and in the case of specifying multiple destinations, multiple profiles are used.TransferProfileTypeYesYes

Comment G44page101: 9.3.1.3 TransferFaultTypeSpecific error codes for the transfer media service are enumerated in TransferErrorCodeType (based on xs:string), such as:- DATA0220: Invalid URI protocol specified for Transport operations. - DATA0221: Invalid Output Directory or Target URI path- DATA0222: Unsupported protocol[S28] Need to create a rule to count number in each service.- nice to do: Kojima-san to make proposal. namespace issue? urn?[Part2_Transfer] page 4: S1.1.1.3 TransferFaultType

Comment G45page103: 9.3.2.1 TransformRequestType

[E21] If there is no sample of regular expression, this should be removed. - example from Praveen[E22] No closing. - agreed, editorial[E23] There is no explanation of this type.- discuss laterE21E22E23[Part2_Transform] page 3: S2.1.1.1 TransformRequestType

NameDescriptionTypeRequiredArrayoutputFileNamePatternThis element allows specifying a pattern for the name(s) of the file(s) to be produced in output. The pattern should be specified using a simple expression to specify a pattern to build the output file name. The expression should allow to reference the following variables in the expression: Source name file DateProfile name used for the transformation Format name used for the transformation Frame reference AutoIncrementCounter which is incremented by 1 for each new file If not specified, the service should use the name of the input file(s) (provided in the bmo to produce the output file name(s). xs:stringNoNotransformProfileThis element represents the profile to specify the process how to transform essence files. Multiple profiles are used when specifying multiple transform processes.The profile provides a mechanism to specify service-specific information for each service provider by parameters of BaseRequest. TransformProfileTypeYesYeswrapperMetadataA set of elements for wrapper metadata. These elements may contain user metadata such as: program name, description, content, location, scene number, rating, etc.MetadataTagTypeNoYes

Comment G46page103: 9.3.2.1 TransformRequestType

[S28] Should re-consider the necessity. - later[Part2_Transform] page 3: S2.1.1.1 TransformRequestType

NameDescriptionTypeRequiredArrayoutputFileNamePatternThis element allows specifying a pattern for the name(s) of the file(s) to be produced in output. The pattern should be specified using a simple expression to specify a pattern to build the output file name. The expression should allow to reference the following variables in the expression: Source name file DateProfile name used for the transformation Format name used for the transformation Frame reference AutoIncrementCounter which is incremented by 1 for each new file If not specified, the service should use the name of the input file(s) (provided in the bmo to produce the output file name(s). xs:stringNoNotransformProfileThis element represents the profile to specify the process how to transform essence files. Multiple profiles are used when specifying multiple transform processes.The profile provides a mechanism to specify service-specific information for each service provider by parameters of BaseRequest. TransformProfileTypeYesYeswrapperMetadataA set of elements for wrapper metadata. These elements may contain user metadata such as: program name, description, content, location, scene number, rating, etc.MetadataTagTypeNoYes

Comment G47page108: 9.3.3.4 CaptureNotificationType

[S29] Currently, 1 request = 1 process = - or 1 source.This Notification could not be needed.- consider offline

[Part2_Capture] page 6: S3.1.1.4 CaptureNotificationType

NameDescriptionTypeRequiredArraysourceIDAn element providing the allocated device ID for the capture (VTR, Input port etc.).xs:stringNoNo

Comment G48page111: 9.3.3.8.1 CaptureProcessType

[E24] No clip concept any more. amend "each clip" to "capture process"[E25] This description is for Transform Service only. - agreed, deleteE24E25[Part2_Capture] page 11:S3.1.2.1 CaptureProcessType

outputFileNamePatternAn element to specify the a pattern for the name(s) of the file(s) produced by the capture for the clip. If the name is not provided, the service shall automatically generate the name for each clip. The pattern should be specified using a regular expression (IEEE POSIX Basic Regular Expressions (BRE) standard) to specify a pattern to build the output file name. The Regular expression should allow to reference the following variables in the expression: Source name fileProfile name used for the transformationFormat name used for the transformationFrame number An index or counter which is incremented by 1 for each new file If not specified, the service should use the name of the input file(s) (provided in the bmContent) to produce the output file name(s). (Need informative examples).xs:stringNoNo

Comment G49page112: 9.3.3.8.2 CaptureSourceType

[E26] Not be needed. - consider offline[Part2_Capture] page 12: S3.1.2.2 CaptureSourceType

NameDescriptionTypeRequiredArraysourceIDThe ID of the source. This parameter is optional, since it is possible to specify only the type of the source with the sourceType and have the service allocate the actual source ID, which is returned later on by the service. xs:anyURINoNo

Comment G50page113: 9.3.3.8.7 SourceInPointByBeginningTypeThis type indicates to start a clip capture at the beginning of specified source. The capture shall start at the beginning of the tape. This parameter, together with the "End" parameter in the "SourceOutType", realizes the "whole" capture of a tape or a file.[E27] Should be removed. - delete "or a file".[Part2_Capture] page 13: S3.1.2.4.3 SourceInPointByBeginningType

Comment G51page116: 9.4 Service Consumer InterfaceThe service consumer interface describes the mechanism used to provide the result and the status of long running operations. The support for long-running, asynchronous operations for FIMS services shall be implemented by two different interaction patterns:Request/response with asynchronous notification patternRequest/response with status polling patternThese interaction patterns are explained in more details in section 6.2.1.[S30] Is this feature required for V1.0.0?If yes, Description in the Service Description needed?IBM to clarify need for this

[Part2_Base] page 83: S0.1.4 Service Consumer Interface