Two proposals received from Doordarshan for consideration by the meeting of sg-6 are attached for comments



Download 127.38 Kb.
Page2/3
Date28.05.2018
Size127.38 Kb.
#51641
1   2   3

REPUBLIC OF INDIA



User requirements for Metadata related to digital production,

post-production, recording and archiving of sound

and television Programmes in broadcasting

Introduction

With every multimedia content, there is lot of associated information. In days of analog, this information about the content was kept in the form of a paper datasheet. Sometimes database entries were made in the computers, with a unique media identifier number marked on the media envelope. In case of loss of datasheet or unique identifier, the whole information about the content was lost.

With the advent of Digital technologies, similar process used to be in place. Content and information about the content used to be kept separately in servers and databases. Many a times, content is removed from server, but database entry remains there; and synchronization of database & Audio files is a tedious process. Every time file is copied, its associated information has to be manually entered into the database. Sending content for exchange within the organization still requires need of sending the information in the form of a paper or separate Computer file in this case.
The advancement in digital technologies in the field of broadcasting has made it possible to include the information about the content file itself. This associated information is called Metadata. This has many benefits. The Database can read the metadata directly from the file. There is no need to send the information about the content separately while sending the content for exchange. However, it is desirable to have standard terminologies, formats etc. for the metadata structure and its scheme of embedding so that there are less chances of its misinterpretation and loss.
ITU-R Question 46-1/6 pertains to various aspects related to Metadata for production and post-production in broadcasting. The present document addresses these aspects and tries to find out suitable answers to queries raised in ITU-R Question 46-1/6.

2 Various functions of metadata
The following functions are expected of metadata:


  1. It should help in selecting proper playback application/module/software depending upon the format of the content.

  2. It should support all the standard Broadcast formats.

  3. It should not hinder/disrupt playback of the content.

  4. Metadata should also not degrade the playback quality of the multimedia.

  5. It should be able to indicate the ownership and distribution rights of an organization/company over the content.

  6. It should be able to help in searching/Browsing/viewing the content on Content’s General & intellectual Information

  7. A few fields in the Metadata should be editable only by the owner.

  8. The metadata information should be directly accessible through the databases for search etc.


3 What information should be provided in the form of Metadata accompanying digital recordings of sound and television programmes?
Information in the form of eighteen elements can be accompanied with digital recording of sound and television programme. Details of exact information to be provided in each of these eighteen elements are given below. Efforts have been made to use the terms which are frequently used in production and post production of broadcast content in India.


Element 1: Media No. / Code No. /Identifier


Name: Resource Identifier

Definition: An unambiguous reference to the resource within a given context.

Comment: Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI)
Element 2: Title

Name: Title

Definition: An easy and familiar name given to the resource.

Comment: Typically, album/title will be a name by which the resource is formally known. The Title is tied to the production/post-production/archived item: The Title may some time be elaborated by adding additional information e.g. ‘Evening News 2006.06.21’.


Element 3: Theme/Subject

Name: Theme

Definition: The topic of the content of the resource.

Comment: Typically, a Theme will be expressed as keywords, key phrases or classification codes that describe a topic of the resource.


Element 4: Description

Name: Description

Definition: A summary of the content of the resource.

Comment: Describing briefly about the content. This will provide listeners an opportunity to know about the content without actually listening it.


Element 5: Publisher/ Production Company

Name: Company

Definition: An entity responsible for creating/making the resource

available

Comment: It is the entity that has made the resource available in its present form.

Examples of a Producer include a person, an organization, or a service. Typically, the name of a producing Organization should be used to indicate the entity as “All India Radio’.


Element 6: Type/ Category

Name: Resource Type

Definition: The nature or genre of the content of the resource.

Comment: Type includes terms describing general categories, functions, genres, or aggregation levels for content. To describe the physical or digital manifestation of the resource, use the FORMAT element.



Element 7: Producer/Creator


Name: Producer

Definition: An entity primarily responsible for making the content of the resource.

Comment: Examples of a producer include a person, an organization, or a service. Typically, the name of a producer should in order: surname, first name; however they can also be written according to local practice to indicate the entity.

Element 8: Writer/Lyrics /Contributor

Name: Writer

Definition: An entity responsible for making contributions to scripting of the content of the resource.

Comment: Examples of a Writer include normally a person, an organization, or a service. Typically, the name of a Writer should be used to indicate the entity. It is recommended that names are written inverted; surname, first name, but they can also be written according to local practice.


Element 9: Composer

Name: Composer

Definition: Person/cooperation responsible for composing the music used in the Programme.

Comment: Examples of a Composer include a person or group of persons by a single name. Typically, the name of a Composer or group name such as Raman-Sethi etc should be used to indicate the entity. It is recommended that names are written inverted; surname, first name, but they can also be written according to local practice.

Element 10: Artist/Singer


Name: Artist

Definition: A person who uses his or her voice with or without instrumental accompaniment to produce music. The Artist's performance may or may not include his actual words the extent or scope of the content of the resource.


Comment: Examples of an Artist include a person by a single name. Typically, the name of an Artist should be used to indicate the entity. It is recommended that names are written inverted; surname, first name, but they can also be written according to local practice.
Element 11: Actor

Name: Actor

Definition: Actor is an entity on whom the programme has been

presented

Comment: Typically the Actor is different than Artist as Singer is always on the Front while singer is behind the scene. Actor/Singer may not necessarily be one rather they may be more than one. Such cases most prominent actor name should be considered to indicate the entry.
Element 12: Date

Name: Date

Definition: A date associated with an event in the life cycle of the

resource.

Comment: Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 and follows the YYYY-MM-DD format.

Comment: Date of formal issuance (e.g. publication) of the

resource. It is recommended to use the element both

for recordings that are “born-digital” and recordings

that are digitized. The date for digitizing may also be

placed in Date entry.


Element 13: Format

Name: Format

Definition: The physical or digital manifestation of the resource.

Comment: Typically, Format may include the media-type or dimensions of the Resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Compression technique, sampling rate, sample resolution & number of channel etc. in brief.


Element 14: Country/Source

Name: Source

Definition: Name of the country where origin of resource lies. A Reference to a resource from which the present resource is derived.

Comment: The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system. The Recommended best practice is to use a unique identifier to identify the physical source that has been used to create the digital resource. In the case of a digitized analogue recording, it is the recording used for digitization which is the source. For commercial recordings the label and number is normally given.




Element 15: Language

Name: Language

Definition: A language of the intellectual content of the resource.

Comment: Recommended best practice for the values of the Language element is defined by RFC 1766 [26], which includes a two-letter Language Code (taken from the ISO Standard 639 [27]), followed optionally, by a two-letter Country Code (taken from the ISO Standard 3166 [28]). For example, ‘hnd’ for Hindi 'eng' for English, 'frn' for French, or 'en-uk' for English used in the United Kingdom.


Element 16: Rights

Name: Rights Management

Definition: Information about rights held in and over the

resource.

Comment: Typically, a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource.

By “Rights” we here mean the rights to the programme (sound file etc.) as a whole. For rights covering parts of the file (music, poetry etc included in the file) keep these in the institutions locally. Here register for instance NRK, BBC or the production company responsible for the programme or the record company that owns the rights to a phonogram. Here one can use an URL to point to places with more information on rights.

RIGHT Type Type of access rights permitted e.g. Pay -Per-View, Repeats-Payable, Copy, Publish, Broadcast, On-sell, Unrestricted. A descriptive classification, often part of a controlled vocabulary, which designates the group to which something belongs.



Download 127.38 Kb.

Share with your friends:
1   2   3




The database is protected by copyright ©ininet.org 2024
send message

    Main page