Re: [whatwg] RDFa

On Fri, 22 Aug 2008, Ben Adida wrote: > > > Why would it scale any less than URIs? That's basically all URIs are. > > Why would you reinvent URIs in a way that they can't be de-referenced? > Is that really a good design, in your opinion? It seems to work well for the Java community. I'd ask th

Re: [whatwg] Scripted query proposal

Robert O'Callahan wrote: > On Fri, Aug 22, 2008 at 1:56 PM, Tim Starling <[EMAIL PROTECTED] > > wrote: > > interface HTMLMediaElement { >... >boolean supportsType(in DOMString type); >... > } > > The supportsType() method must return fal

Re: [whatwg] Scripted query proposal

On Sat, Aug 23, 2008 at 11:21 AM, Eric Carlson <[EMAIL PROTECTED]>wrote: > > A three state return is an interesting idea, but wouldn't you then be > required to return "maybe" for MIME types that can describe multiple > formats? For example, "video/mpeg" can be used to describe a video > element

Re: [whatwg] RDFa

Silvia Pfeiffer wrote: > I would like to understand exactly what changes to the existing HTML5 > spec would be required to support RDFa. Ben - can you clarify? Maybe > the extension mechanism that Ian refers to already covers all the > needs, but it has not been clarified. Thanks for the straight-

Re: [whatwg] RDFa

Ian Hickson wrote: > Just to emphasise: I don't know if you trimmed the quote above just to > make your e-mail shorter or for some other reason, but the rest of the > paragraph was actually the most important part. To be explicit, the most > important details in any proposal like this are: > >

Re: [whatwg] Scripted query proposal

On Aug 22, 2008, at 2:36 PM, Robert O'Callahan wrote: On Sat, Aug 23, 2008 at 1:46 AM, Eric Carlson <[EMAIL PROTECTED]> wrote: On Aug 21, 2008, at 8:56 PM, Robert O'Callahan wrote: Does that actually enumerate all supported codecs? Looking at the Webkit code and the Quicktime docs, it loo

Re: [whatwg] Scripted query proposal

On Sat, Aug 23, 2008 at 1:46 AM, Eric Carlson <[EMAIL PROTECTED]>wrote: > > On Aug 21, 2008, at 8:56 PM, Robert O'Callahan wrote: > > Does that actually enumerate all supported codecs? Looking at the Webkit > code and the Quicktime docs, it looks like it's just enumerating > file/container types.

Re: [whatwg] RDFa

On Fri, 22 Aug 2008, Ben Adida wrote: > > > > It would be helpful if you could send a separate message that is > > specifically asking for the changes you desire > > Perfectly reasonable: we'll put together a precise proposal regarding: > (1) what would need to validate, (2) what would browsers

Re: [whatwg] RDFa

[Response to Ian and Henri in one email... but then I saw the other responses and am breaking out the remainder responses in separate emails.] Ian Hickson wrote: > I've whitelisted your e-mail address so that you can post to the WHATWG > list without subscribing. Thanks Ian, I think I unsubscri

Re: [whatwg] Creative Commons Rights Expression Language

12. DOCTYPE declarations have to use prefixes where the corresponding namespaces are yet undeclared. The same problem affects external CSS. This effectively fixes the prefixes, making the redirection to the URL redundant. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PR

Re: [whatwg] 2.7.4. Content-Type sniffing

GNU libmagic used by the command line utility "file" can be used for content-type sniffing as well. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Pilgrim Sent: Friday, August 22, 2008 4:51 AM To: whatwg@lists.whatwg.org Subject: [whatwg] 2.7.4

Re: [whatwg] Scripted query proposal

On Aug 21, 2008, at 8:56 PM, Robert O'Callahan wrote: On Fri, Aug 22, 2008 at 2:57 PM, Eric Carlson <[EMAIL PROTECTED]> wrote: It is possible to build a list of all types supported by QuickTime dynamically. WebKit does this, so Safari knows about both the built in types and those added by

Re: [whatwg] Ressurecting a11y thread [was Re: Video, Closed Captions, and Audio Description Tracks]

At 12:59 +0200 22/08/08, Aaron Leventhal wrote: Has anyone put any further thought on what to do about captions for Ogg? We've started to throw some thoughts together here: https://wiki.mozilla.org/Accessibility/Captioning_Work_Plan We could use some help from individuals who understand the ar

[whatwg] Ressurecting a11y thread [was Re: Video, Closed Captions, and Audio Description Tracks]

Has anyone put any further thought on what to do about captions for Ogg? We've started to throw some thoughts together here: https://wiki.mozilla.org/Accessibility/Captioning_Work_Plan We could use some help from individuals who understand the area of video and captions. The problem of deciding

Re: [whatwg] Creative Commons Rights Expression Language

Le 22 août 2008 à 16:50, Henri Sivonen a écrit : At least in the case of New York, the settlers had the good sense to choose a short disambiguating prefix instead of thinking they were off in a different default namespace like Texas and free to reuse local names causing problems with global

Re: [whatwg] Creative Commons Rights Expression Language

Bonner, Matt wrote: On Wed, Aug 20, 2008 at 5:22 PM, Bonner, Matt wrote: Hola, I see that the Creative Commons has proposed additions to HTML to support licenses (ccREL): http://www.w3.org/Submission/2008/SUBM-ccREL-20080501/ ... Tab Atkins Jr. replied: The whole thing would

Re: [whatwg] Creative Commons Rights Expression Language

On Aug 21, 2008, at 21:53, Ben Adida wrote: Not to mention that our design approach was specifically tailored to be HTML5-friendly. It really isn't HTML5-friendly, since it depends on the namespace mapping context at a node. Henri Sivonen writes: and those additions use a Namespace-depe

Re: [whatwg] members

On Mon, 6 Aug 2007, Anne van Kesteren wrote: > On Sat, 04 Aug 2007 08:40:08 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote: > > I don't know. Currently, the only elements that use defaultFoo are > > with defaultSelected, with defaultValue and > > defaultChecked, and and with defaultValue. Given

Re: [whatwg] details == footnote ?

On Wed, 8 Aug 2007, Elliotte Harold wrote: > > Here's what I would ask: irrespective of presentation issues like when > and where the notes appear on the page, what is the meaning of a details > element and what is the meaning of a hypothetical footnote element? Are > they significantly differe