Login       -       Change Password       -       Recent Changes       -       Search:

InterStream Overview

InterStream FAQ

Working Groups

Governance

Technology and Standards

WiKi Help

edit SideBar

Meta-Data

Meta Data Integration and Philosophy

ISTP objects, or Handles, represent rich media objects on a multi-media grid. This grid is fully distributed across the Internet. As such, the objects themselves in addition to the mechanisms for accessing those objects must provide a rich interface so that information about those objects may be easily obtained, referenced (or linked), and the corresponding information about the object may be used in flexible manner.

Handles describe where and how objects on the media grid may be referenced. An overt goal of the ISTP system has been to support Tri-TouchTM (scroll ball) remote controls as those found with a television set in addition to a keyboard and mouse. Linking objects together via mouse clicks, or directly referencing them via a specified Handle using a keyboard may be accomodated using a tradtional HTML browser. Television set and browser integration with the same media objects have been a more problematic design constraint . Since media objects can be referenced on screen easily using a mouse for hyperlinked content, a scroll ball remote requires similar and seamless integration. Selection of a media object from the grid can be accommodated via keyboard search of meta-data in ordinary HTML fields, selection via a mouse, or use of a scroll ball remote and sophisticated on screen search and selection mechanisms.

End users are typically aware of "channels", TV programs and in the case of fully on-demand content, individually specified pieces of streaming content. These content segments may be linked together to form a contiuous streaming experience for an end-user. In addition, these objects must be capably displayed and selectable by a mouse or 5-button remote control. By standardizing the object container for ISTP Handles, individual rich media objects may have different behaviours associated with them for different user interface paradigms. The idea of channels, or a continuous stream of programs hyperlinked together is easily accomodated using this approach. In addition, an individual TV program with its own meta data and sub-programs may also be flexibly accomodated. Individual segments of hyperlinked rich media stream provide the basis for the system using a sequence of hyperlinked objects each with their own containers that interact with the an end-user differently depending upon user interface paradigm.

For example, a television interface may specify that object containers should display meta data about the object if it is selected on the screen. In addition, a thumbnail picture of the content along with playback attributes may be specified for the object visually if it is referenced within the system. The object, or handle, may also have playback attributes set as part of a playlist. Similarly, in the event the same object was referenced in a browsers, these same attributes may be displayed appropriately under a different playback and browsing paradigm.

InterStream intends to define the following for metadata use:

  1. Identifier (dc) [required]: The Media Grid Object Name (Handle) of the object. (self-reference)
  2. Title (dc) [required]: The title of the object.
  3. Creator (dc) [optional, required if adult content]: The creator of the object. ASACP identifier required if adult content.
  4. Date (dc) [optional]: Date that the movie was uploaded (made available via a URL).
    This value is automatically added when the metadata is initially entered into the service.
    DCMI Recommended Best Practice is to use the ISO 8601 profile for date format: YYYY-MM-DD.
  5. Subject (dc) [optional]: A list of keywords describing the content of the movie. (This is where subject words of a formal classification scheme would be used.)
  6. format (dc) [optional]: Format of the video file: Quicktime, Windows Media, etc. DCMI Recommended Best Practice is to use MIME type information.
  7. rights (dc) [required]: A reference to a text-based description of the movie's licensing terms. (referenced via URL or other grid object)
  8. Description [optional] - used as a container for "abstract"
  9. Comment [optional]
  10. Latitude [optional]
  11. Longitude [optional]
  12. Contributor (dc) [optional]: A person or organization who has contributed to the content of the resource.
  13. Rightsholder (dc) [optional]: A person or organization owning or managing rights over the resource. Recommended best practice is to use the URI or name of the Rights Holder to indicate the entity.
  14. Objectsize [optional]: positive integer in octets
  15. Objectname [optional]: Text
  16. Duration [optional]:
  17. Clip / time control [optional]: A portion of the playback, only. From SMIL 2.1: begin, dur, end, min, max, marker, clock-value, par, etc see W3 ORG
  18. Codec (Sorensen, etc.) - Can be used to gauge codec playback performance
  19. 2257 Compliance Information [required if adult content]: Adult Content which requires custodian of record information must fill out this field. If this field is filled, ISTP will presume that this designated content will be segregated in the system per the InterStream Terms of Service Agreement and adult content requirements.
  20. ASACP Certification [required if 2257 content]: Association of Sites Advocating Child Protection certificate. Associated with content creator identifier (above). Required if 2257 Compliance information is associated with content.
  21. Hash: A SHA-1 Hash value for the object.

Other optional elements could include

  • Person -
  • Image (for that person) -
  • Director -
  • Producer -
  • Aspect ratio -
  • Framerate -
  • Number of audio channels -
  • Sample rate
Edit - History - Print - Recent Changes - Search
Page last modified on March 08, 2008, at 05:06 PM PST