This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8334 - the stadandard shall explicity cite an example of a url based on RTSP to promote this standard. Today LIVE sreaming is too often achieved with improper "tricks" like HTTP streaming...
Summary: the stadandard shall explicity cite an example of a url based on RTSP to prom...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
: 8335 8627 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-11-19 12:55 UTC by contributor
Modified: 2010-10-04 14:45 UTC (History)
4 users (show)

See Also:


Attachments

Description contributor 2009-11-19 12:55:05 UTC
Section: http://www.whatwg.org/specs/web-apps/current-work/#mime-types

Comment:
the stadandard shall explicity cite an example of a url based on RTSP to promote this standard. Today LIVE sreaming is too often achieved with improper "tricks"  like HTTP streaming...

Posted from: 82.190.122.204
Comment 1 Ms2ger 2009-11-19 18:01:00 UTC
*** Bug 8335 has been marked as a duplicate of this bug. ***
Comment 2 Henri Sivonen 2010-01-04 13:42:42 UTC
*** Bug 8627 has been marked as a duplicate of this bug. ***
Comment 3 Ian 'Hixie' Hickson 2010-01-11 11:45:12 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: I would be very happy to do this, but I know nothing about RTSP. Could someone provide some example markup showing what this would look like in practice? (ideally with an actual working example so I can test it and see if there's anything in particular I need to bring to the attention of the reader)