I just read on Wikipedia that HTML 5 is planning to have new video and audio api's. Is this really nessesary? Not all machines support things like that, and besides, isn't that what flash is for?
I just read on Wikipedia that HTML 5 is planning to have new video and audio api's. Is this really nessesary? Not all machines support things like that, and besides, isn't that what flash is for?
And the Firefox 3.1 Betas actually support it (partially).
Yes.Is this really nessesary?
An UA need not actually support video and audio output and can still claim compliance with HTML5, as long as it has the correct fallback behavior.Not all machines support things like that,
1) More machines support video than support Flash.and besides, isn't that what flash is for?
2) Flash is a proprietary format, subject to the whims of Adobe.
3) Flash requires installation of a plugin.
4) Flash only supports .flv videos, which use proprietary codecs.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
Note that an API is an application programming interface, which allows you to program something for the web, using a language. As an example, I think Yahoo has an API so that you can integrate Yahoo search into whatever bigger web project you have. Clearly not what you are thinking of.
The relevant section of the article is
I used to make web pages frequently, and take it from my experience that these are welcome changes. A standard interface for music and video is a godsend since, currently, you have to use the object containers with unintelligible jibberish like clsid= attributes and parameter tags.HTML 5 provides a number of new elements and attributes that reflect typical usage on modern Web sites. Some of them are technically similar to <div> and <span> tags, but have a meaning, for example <nav> (website navigation block) and <footer>. Such tags would facilitate indexing by search engines and handling by small-screen devices or voice readers for the visually impaired.[citation needed] Other elements provide new functionality through a standardized interface, such as the <audio> and <video> elements.[3]
Flash is a tool but it shouldn't be the only option. Flash video and sound quality, frankly, sucks. People can watch their favorite shows online now as TV stations try to connect with more internet addicted, computer affluent audience. It's not too hard to imagine that they would like a simple interface to bring high quality streaming to their audience.
I have confidence that if broadband internet speeds, video cards, and processors aren't ready for this now, then they will catch up in short order; there is also no reason to assume that every web site is interested in providing this kind of content. It is very much a wait and see situation in terms of what happens in practice.
Alright you guys got me. I never even thought of this:
An UA need not actually support video and audio output and can still claim compliance with HTML5, as long as it has the correct fallback behavior.
Do you think XHTML 2 will also include these api's? I hope they do.
At this point, I very much doubt XHTML 2 will ever come into existence. You may be thinking of the XML serialization of HTML 5 (informally called XHTML 5), which is just another way of writing HTML5.Do you think XHTML 2 will also include these api's?
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
Perhaps. XHTML2 has some nice ideas. But the incredible sluggishness of the working group led, I believe, to its dissolution.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
Oh well. I'll just keep using XHTML 1.1.
"The Internet treats censorship as damage and routes around it." - John Gilmore