FIMS Media SOA Framework - AMWA

More documents

Recommendations

Info

FIMS Media SOA Framework Phase1 (Preliminary)8.2.2.1.1.2.2 ResourceInfoTypeconstraints on the schema adopted for metadata.This type provides resource information such as the type of storage and the geographical location.8.2.2.1.1.2.2.1 ParametersParameter Type DescriptionstorageType StorageEnumType The storage type, enumerated in StorageEnumType(e.g. "online").locationInfo xsd:string Location information for the media content (e.g. NewYork).8.2.2.1.1.2.3 FormatRefTypeThis type provides the reference to the content format ID. The description of the content format is treated as apartially opaque object by the FIMS framework, to provide maximum flexibility and transparency to theintroduction of new formats and codecs. The framework shall support a mechanism to registry and referencemedia formats and identify them by their unique id.8.2.2.1.1.2.3.1 ParametersParameter Type DescriptionId UID The unique reference to the format ID.Description xsd:description An optional description for the media format.8.2.2.1.1.2.4 DurationTypeThis type is used to specify the duration of audiovisual content. It provides a choice between two elements, oneexpressing the duration as time, and one expressing the duration as number of frames.8.2.2.1.1.2.4.1 ParametersParameter Type DescriptiontimeDuration xsd:time This choice element expresses duration as time.framesDuration xsd:long This choice element expresses duration as number offrames.8.2.2.1.1.2.5 DescriptiveMetadataTypeThis type allows the flexible insertion of metadata. Since it is based on the XSD "any" type, it can transparentlyhost any type of metadata schema. This metadata is treated by the FIMS framework as an opaque object, sothere are no constraints on the schema adopted for metadata. When using a type based on a standard or userdefinedschema, the xsi:type and xsi:schemaLocation attributes shall be used, as specified in XML Schema Part1: Structures Second Edition - W3C Recommendation 28 October 2004.8.2.2.1.1.2.5.1 ParametersParameter Type DescriptionId UID An optional attribute used to indicate thePrivate committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 52 of 89
FIMS Media SOA Framework Phase1 (Preliminary)ID of the metadata. This attribute can beused to reference by ID metadata thatcan be embedded in a content essencecontainer, such as MXF.Any xsd:any A choice element for wrapping theembedded metadata. This field cannot beset if the “ref” element is used.Ref xsd:anyURI A choice element with a URL reference tometadata, defined according to RFC1738 -Uniform Resource Locators (URL). Themetadata shall be accessible through thespecified URL. This field cannot be set ifthe “any” element is used.8.2.2.1.1.3 Extended Content TypesThe BMBaseContentType is extended by the following content types, each providing additional type-specificproperties:8.2.2.1.1.3.1 BMVideoContentTypeThis type extends BMBaseContentType and provides a reference to video content. It inherits all the elementsfrom BMBaseContentType, and provides an additional optional element (of type DurationType) to express theduration of the video as xsd:time or number of frames.8.2.2.1.1.3.2 BMAudioContentTypeThis type extends BMBaseContentType and provides a reference to audio content. It inherits all the elementsfrom BMBaseContentType, and provides an additional optional element (of type DurationType) to express theduration of the audio as xsd:time or number of frames.8.2.2.1.1.3.3 BMImageContentTypeThis type extends BMBaseContentType and provides a reference to image content. It inherits all the elementsfrom BMBaseContentType.8.2.2.1.1.3.4 BMDocumentContentTypeThis type extends BMBaseContentType and provides a reference to document content. It inherits all theelements from BMBaseContentType.8.2.2.1.1.3.5 BMWrappedContentTypeThis type extends BMBaseContentType and provides a reference to wrapped content. A wrapped contentcontains multiple elementary audio, video and data streams. Examples of wrapped content are: MXF files,MPEG-2 TS, Quicktime, Windows Media files. It inherits all the elements from BMBaseContentType, andprovides an additional optional element (of type DurationType) to express the duration of the content asxsd:time or number of frames. Furthermore, it provides a mechanism to describe structural information (whichstreams are inside the wrapper) specifying the tracks components.The following is a simple BMO example for a MXF file.MXF DV25 filefile://server1/home/virtuser/outbox/op1a-pal-dv25-dms1.mxfPrivate committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 53 of 89
Page 1 and 2: FIMS Media SOA FrameworkAMWA Specif
Page 3 and 4: FIMS Media SOA Framework Phase1 (Pr
Page 51: FIMS Media SOA Framework Phase1 (Pr
Page 89: FIMS Media SOA Framework Phase1 (Pr

FIMS Media SOA Framework - AMWA

Create successful ePaper yourself

Delete template?

Save as template?