Re: [whatwg] Give guidance about RFC 4281 codecs parameter

2007-04-10 Thread Silvia Pfeiffer
Hi Charles, Dave, On 4/10/07, Charles Iliya Krempeaux [EMAIL PROTECTED] wrote: Hello, On 4/9/07, Dave Singer [EMAIL PROTECTED] wrote: * Theora video and Vorbis audio in Ogg container. (application/ogg; .ogg) * Dirac video and Vorbis audio in Ogg container. (application/ogg; .ogg) *

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Simon Pieters
On Mon, 09 Apr 2007 21:37:31 +0200, Jon Barnett [EMAIL PROTECTED] wrote: I can think of two possibilities. One would be to allow the param element as a child of any element (or any block level element?) http://www.whatwg.org/specs/web-apps/current-work/#param And then make an attribute of

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Sam Ruby
On 4/10/07, Simon Pieters [EMAIL PROTECTED] wrote: Or allow any attribute that starts with x_ or something (to prevent clashing with future revisions of HTML), as private attributes. Instead of starts with x_, how about contains a colon? A conformance checker could ensure that there is a

Re: [whatwg] Give guidance about RFC 4281 codecs parameter

2007-04-10 Thread Dave Singer
At 18:33 +1000 10/04/07, Silvia Pfeiffer wrote: Recent discussion at Xiph around http://www.ietf.org/rfc/rfc4281 suggests the use of the following parameters: # application/ogg; codecs=theora, vorbis for Ogg Theora/Vorbis files # application/ogg; codecs=theora, speex for Ogg Theora/Speex

Re: [whatwg] Give guidance about RFC 4281 codecs parameter

2007-04-10 Thread Ralph Giles
On Tue, Apr 10, 2007 at 11:21:10AM -0700, Dave Singer wrote: # application/ogg; disposition=moving-image; codecs=theora, vorbis # application/ogg; disposition=sound; codecs=speex what is the 'disposition' parameter? The idea of a 'disposition-type' is to mark content with presentational

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Anne van Kesteren
On Tue, 10 Apr 2007 20:21:27 +0200, Sam Ruby [EMAIL PROTECTED] wrote: Or allow any attribute that starts with x_ or something (to prevent clashing with future revisions of HTML), as private attributes. Instead of starts with x_, how about contains a colon? A conformance checker could ensure

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Jon Barnett
On 4/10/07, Sam Ruby [EMAIL PROTECTED] wrote: Instead of starts with x_, how about contains a colon? A conformance checker could ensure that there is a corresponding xmlns declaration that applies here, and possibly even do additional verification if it recognizes the namespace. An HTML5

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Sam Ruby
On 4/10/07, Anne van Kesteren [EMAIL PROTECTED] wrote: On Tue, 10 Apr 2007 20:21:27 +0200, Sam Ruby [EMAIL PROTECTED] wrote: Or allow any attribute that starts with x_ or something (to prevent clashing with future revisions of HTML), as private attributes. Instead of starts with x_, how

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Anne van Kesteren
On Tue, 10 Apr 2007 22:41:12 +0200, Sam Ruby [EMAIL PROTECTED] wrote: How so? I missed the part where you wanted to change existing HTML parsers. I thought Hixie pointed out earlier (by means of examples) why we can't have namespace parsing in HTML. I suppose we can discuss it again...

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Sam Ruby
Anne van Kesteren wrote: On Tue, 10 Apr 2007 22:41:12 +0200, Sam Ruby [EMAIL PROTECTED] wrote: How so? I missed the part where you wanted to change existing HTML parsers. I thought Hixie pointed out earlier (by means of examples) why we can't have namespace parsing in HTML. I suppose we can

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Anne van Kesteren
On Tue, 10 Apr 2007 23:14:16 +0200, Sam Ruby [EMAIL PROTECTED] wrote: I missed the part where you wanted to change existing HTML parsers. I thought Hixie pointed out earlier (by means of examples) why we can't have namespace parsing in HTML. I suppose we can discuss it again... It is a

Re: [whatwg] Sequential List Proposal

2007-04-10 Thread Kevin Marks
On 4/8/07, Elliotte Harold [EMAIL PROTECTED] wrote: Michel Fortin wrote: So I propose a sl element (sequential list) which can be used to replace dialog as well as other things. The proposal can be found here: Sounds a little redundant with ol (ordered list). Also sounds needlessly

Re: [whatwg] List captions

2007-04-10 Thread Kevin Marks
On 4/6/07, Elliotte Harold [EMAIL PROTECTED] wrote: Andy Mabbett wrote: How often do we see something like: pAnimals:/p ul liCat/li liDog/li liHorse/li liCow/li /ul This would be more meaningful as: ul

Re: [whatwg] base versus xml:base

2007-04-10 Thread Jonas Sicking
In mozilla we currently don't allow relative URIs in the href at all. If the uri is relative it is ignored. This is per HTML4, and I think it would be ok for HTML5 to say the same. Alternatively it could say that it should be relative to the URI used to retrieve the base element. In most

Re: [whatwg] Give guidance about RFC 4281 codecs parameter

2007-04-10 Thread Maciej Stachowiak
On Apr 10, 2007, at 11:58 AM, Ralph Giles wrote: On Tue, Apr 10, 2007 at 11:21:10AM -0700, Dave Singer wrote: # application/ogg; disposition=moving-image; codecs=theora, vorbis # application/ogg; disposition=sound; codecs=speex what is the 'disposition' parameter? The idea of a

Re: [whatwg] Give guidance about RFC 4281 codecs parameter

2007-04-10 Thread Silvia Pfeiffer
On 4/11/07, Maciej Stachowiak [EMAIL PROTECTED] wrote: On Apr 10, 2007, at 11:58 AM, Ralph Giles wrote: On Tue, Apr 10, 2007 at 11:21:10AM -0700, Dave Singer wrote: # application/ogg; disposition=moving-image; codecs=theora, vorbis # application/ogg; disposition=sound; codecs=speex what

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Maciej Stachowiak
On Apr 10, 2007, at 2:14 PM, Sam Ruby wrote: Anne van Kesteren wrote: On Tue, 10 Apr 2007 22:41:12 +0200, Sam Ruby [EMAIL PROTECTED] wrote: How so? I missed the part where you wanted to change existing HTML parsers. I thought Hixie pointed out earlier (by means of examples) why we can't

Re: [whatwg] Attribute for holding private data for scripting

2007-04-10 Thread Sam Ruby
Maciej Stachowiak wrote: On Apr 10, 2007, at 2:14 PM, Sam Ruby wrote: Anne van Kesteren wrote: On Tue, 10 Apr 2007 22:41:12 +0200, Sam Ruby [EMAIL PROTECTED] wrote: How so? I missed the part where you wanted to change existing HTML parsers. I thought Hixie pointed out earlier (by means of

Re: [whatwg] Sequential List Proposal

2007-04-10 Thread Benjamin Hawkes-Lewis
Kevin Marks wrote: I think the dialog example is a retrograde step. The olliciteq|blockquote pattern seems much better than redefining dt and dd, which will confuse XOXO parsers that try to be Postelian. Did I miss some reasoning here? Fictional dialogs don't involve the excerpt and citation