055812.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
 <HEAD>
   <TITLE> [whatwg] html5 + ogg
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20html5%20%2B%20ogg&In-Reply-To=%3CE0229C49-1658-4BF4-B2B6-D087FAF6DD49%40mac.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <style type="text/css">
       pre {
           white-space: pre-wrap;       /* css-2.1, curent FF, Opera, Safari */
           }
   </style>
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="055811.html">
   <LINK REL="Next"  HREF="055813.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[whatwg] html5 + ogg</H1>
<!--htdig_noindex-->
    <B>Henry Mason</B> 
    <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20html5%20%2B%20ogg&In-Reply-To=%3CE0229C49-1658-4BF4-B2B6-D087FAF6DD49%40mac.com%3E"
       TITLE="[whatwg] html5 + ogg">hmason at mac.com
       </A><BR>
    <I>Sat Dec 29 11:19:40 PST 2007</I>
    <P><UL>
        <LI>Previous message: <A HREF="055811.html">[whatwg] html5 + ogg
</A></li>
        <LI>Next message: <A HREF="055813.html">[whatwg] html5 + ogg
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#55812">[ date ]</a>
              <a href="thread.html#55812">[ thread ]</a>
              <a href="subject.html#55812">[ subject ]</a>
              <a href="author.html#55812">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--/htdig_noindex-->
<!--beginarticle-->
<PRE>
On Dec 29, 2007, at 12:01 PM, Philip Parker wrote:

&gt; The removal of ogg as a baseline for audio/video implementation
&gt; strikes me as ridiculous. Theres nothing stopping other formats from
&gt; being used after all

If the specification included the Ogg baseline and few web browsers 
actually supported it, what use would the specification be? Simply 
specifying it won't actually make it widely implemented.

There's also nothing stopping you from using Ogg in the things you  
develop right now, so how does the removal change what you choose to do?

&gt; As things stand with how easily large corporations can
&gt; obstruct/corrupt the process for their own goals, I might as well just
&gt; stick to xhtml1 and avoid rich media elements where possible in any
&gt; site I may end up developing until - and indeed if sense prevails.

I guess by &quot;rich media elements&quot; you also mean JPEG, GIF, PNG, SVG, 
and Flash? None of those are included as baselines in the XHTML1 
specification either.

-Henry

</PRE>

<!--endarticle-->
<!--htdig_noindex-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="055811.html">[whatwg] html5 + ogg
</A></li>
	<LI>Next message: <A HREF="055813.html">[whatwg] html5 + ogg
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#55812">[ date ]</a>
              <a href="thread.html#55812">[ thread ]</a>
              <a href="subject.html#55812">[ subject ]</a>
              <a href="author.html#55812">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
mailing list</a><br>
<!--/htdig_noindex-->
</body></html>

/lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/055812.html