Warning:
This wiki has been archived and is now read-only.

User:Jfoliot/UseCases

From HTML WG Wiki
Jump to: navigation, search

Ref: ACTION-250 - Review use-cases 8-12 for accessibility considerations https://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases

"Use Case Eight – Download and Go"

Description: Using a web browser, a user downloads a series of videos onto a tablet, intending to use them to entertain the kids on a road trip.

Alternative: Using a web browser, a user downloads a series of videos onto a TV with storages and then plays some of them on TV until midnight. After that, the user copies the stored video from TV to the smart phone via home network, intending to watch the rest of them in airplane on business trip. Need/justification: Accessing live video streams may not be possible (e.g. no network, or per content provider policy) or desirable (e.g. due to data usage or low QoE) when mobile or away from home. Nonetheless with video-capable devices, there will be a desire to be able to watch videos even in those circumstances.

Status: WIP

Accessibility Requirements:

  • Whenever a media asset is downloaded for local storage and playback, all related out-of-band accessibility assets (closed captions, picture-in-picture sign language, transcripts, etc.) MUST also be available for download and storage as well (preserve dependencies), the user-agent MAY offer the option to select specific assets prior to download (for example, the user chooses to download the Caption file, but omit the Transcript).
  • The Download and Storage of the supplemental assets SHOULD preserve a local hierarchy tree, to maintain authored dependencies (precedent: when a “web page” is downloaded and saved locally, the file directory structure is preserved in the download – for example a new local directory is created for “images”). Alternatively, as part of the download, the user-agent dynamically re-writes the dependency tree (to facilitate storage needs – for example places all files inside of a .zip or .cab file), and re-interprets those dependencies maintaining the programmatic link between the multiple assets.

"Use Case Nine – Watch and Record"

Description: Using a web browser, a user watches a video and records it for later playback at the same time.

Need/justification: Ability to record a video for later playback while simultaneously watching the same video is a basic thing that many users will expect.

Status: WIP

Accessibility Requirements:

  • Whenever a media asset is recorded to local storage for subsequent playback, all related out-of-band accessibility assets (closed captions, picture-in-picture sign language, transcripts, etc.) MUST also be available for recording and storage as well. The user-agent MAY offer the option to select specific assets to be recorded (for example, the user chooses to record the Caption file, but omit the Transcript).
  • The Storage of the supplemental assets SHOULD preserve a local hierarchy tree, to maintain authored dependencies .Alternatively, as part of the recording process, the user-agent dynamically re-writes the dependency tree (to facilitate storage needs – for example places all files inside of a .zip, or.cab file, or common directory), and re-interprets those dependencies maintaining the programmatic link between the multiple assets.


10. "Use Case Ten – Sync Among Browser- and non-Browser Devices"

  • Contributor: Sheau Ng (NBCU)

Prerequisite:

  • User has content services on non-browser based devices (e.g., Smart TV, STB, etc.) and browser-based devices (e.g., PC)
  • TV service provider offers services on multiple platforms, including browser and non-browser platforms.
  • All devices have ability to recognize the content/program that is displaying on TV.
  • All devices have been previously joined to the user's home network and identified as belonging to the different members of the family.
  • Different members of the family use a different companion device
  • TV program has multiple content elements that are uniquely suited for different platforms.

Use Case:

  • User is watching a Game Show on TV with family members
  • A competition among several contestants is showing on TV
  • A prompt appears on TV asking user to opt in to interactive mode
  • User confirms to opt in.
  • Companion devices (App on tablet) and browser on laptop receive notifications of incoming content
  • All devices are automatically synchronized to the program on TV
  • Each device displaying different pieces of content synchronous to the TV show
  • Family members independently interact with the TV show
  • Game Show prompts everyone on their companion device to rank the contestants
  • TV Show displays in real-time the family's vote on the contestants
  • TV Show also displays in real-time the family's vote along with the general viewers' vote

Accessibility Requirements:

The majority of the Accessibility Requirements for this Use Case are addressed at Media Accessibility User Requirements/System Requirements

11. "Use Case Eleven – Parental Control in Content Access"

  • Contributor: Sheau Ng (NBCU)

Prerequisite:

  • User has content services from multiple content service providers CP1, CP2, and CP3.
  • User uses third-party parental control service from XYZ.
  • User sets up different levels of parental control for different members of the household.
  • Member Junior is one of the household members.
  • Junior is currently watching a children's program on TV
  • TV has been previously set to Junior-level Content Access.

Use Case:

  • Junior presses Program Listing button on a controller device.
  • TV screen shows a listing of content that is suitable for Junior-level Content Access according to the XYZ setting.
  • Content listing spans the content available to User from CP1, CP2, and CP3
  • Programs/Content from CP1, CP2, and CP3, which do not pass the Junior-level Content Access filter are hidden from the listing that Junior sees.
  • Junior selects a program that interests him/her from the listing, and watches the new program.

Accessibility Requirements:

The majority of the Accessibility Requirements for this Use Case are addressed at Media Accessibility User Requirements/System Requirements

12. "Use Case Twelve – Multiscreen Advertisement"

  • Contributor: Louay Bassbouss (Fraunhofer FOKUS)

Prerequisite:

  • Subscriber has a set-top box or Smart TV connected to home network
  • Subscriber has subscribed to a TV broadcasting service
  • Subscriber has a companion screen device (Smartphone, Tablet, etc.) also connected to the home network
  • Companion screen device runs a multiscreen service, which can be discovered from the set-top box or TV

Use Case:

  • Subscriber watches a movie on the TV.
  • During commercial breaks, the Broadcasting service shows Ads for some products.
  • Broadcasting service displays a text on the TV offering the subscriber the option to buy products (currently displayed in the Ad) and save 10% of the price.
  • The subscriber clicks the Ok button on his remote.
  • Set-top box discovers the multiscreen service running on the companion device and sends a request to launch a companion screen (CS) App.
  • multiscreen service running on the companion device receives the launch request and shows a notification (like push notification).
  • Subscriber clicks on the notification and the CS App will be launched and connected to the set-top-box immedialtey.
  • CS App shows additional information to the products currently displyed on the TV (CS App and TV App are in Sync).
  • Subscriber clicks on the "Add to Basket" button for products he deceided to buy.
  • Subscriber complete payment on companion device.
  • Alternative:
  • If there is more than one companion screen device running a multiscreen service available in the home network, the App running on the set-top box or TV may offer an option to select the target device.

Accessibility Requirements:

The majority of the Accessibility Requirements for this Use Case are addressed at Media Accessibility User Requirements/System Requirements

Retrieved from "https://www.w3.org/html/wg/wiki/index.php?title=User:Jfoliot/UseCases&oldid=14193"