Re: [whatwg] Form Control Group Labels (was: Re: How not to fix HTML)

Matthew Raymond wrote: Example: | | Gender: | | | | Male | | | | | Female | | I just realised a problem with this proposal. What if we want to associate a label with several controls, with different names? Here's a few use cases: 1. Seperate fields for

Re: [whatwg] caption (was: How not to fix HTML)

Le 1 nov. 2006 à 22:01, Jonathan Worent a écrit : I think this is a good idea. Caption could be used with just about any embedded content. Taking cues form the label element for forms you could either make the association explicit by wrapping the caption around the element its captioning

Re: [whatwg] [HTML5] 3.10.9. The |abbr| element

Le 1 nov. 2006 à 21:44, Jonathan Worent a écrit : I disagree. There is never a guarantee that people will know what an abbreviation stands for, I know what AIDS is but not what it stands for. Also accessing the title information is optional. If the user knows what the abbreviation stands fo

Re: [whatwg] caption (was: How not to fix HTML)

--- Lachlan Hunt <[EMAIL PROTECTED]> wrote: > Lachlan Hunt wrote: > > Ian Hickson wrote: > >> Joe Clark wrote: > >>> http://blog.fawny.org/2006/10/28/tbl-html/ > > > > FYI, my response to that his here. > > http://lachy.id.au/log/2006/10/fixing-html > > Joe Clark has responed. > http://lachy.

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

--- James Graham <[EMAIL PROTECTED]> wrote: > Anne van Kesteren wrote: > > On Wed, 01 Nov 2006 19:24:17 +0100, Christoph Päper > > <[EMAIL PROTECTED]> wrote: > >> And HTML5 isn't that semantically pure anyway. > > > > Where can it be improved? > > To take a slight detour into the (hopefully n

Re: [whatwg] [HTML5] 3.10.9. The |abbr| element

--- Christoph Päper <[EMAIL PROTECTED]> wrote: > First off I think the requirement for a |title| is too strict, > because there are time and space saving abbreviations everyone knows > -- i.e. either their expansion or their meaning -- that do not need > an expansion, e.g. "e.g." or "AIDS"

Re: [whatwg] XMLHttpRequest connection limit

On 1-Nov-06, at 4:42 PM, Charles Iliya Krempeaux wrote: Hello, I think we're starting to see some of the limits of HTTP being hit. We're actually quite far from using the full capabilities of HTTP. We're definitely bumping into limits exposed by HTTP implementations, though (in the case of

Re: [whatwg] XMLHttpRequest connection limit

Hello,I think we're starting to see some of the limits of HTTP being hit.Personally, I'd like to a protocol which allows communication in both ways.HTTP 1.2?  XMPP/Jabber?  Something else? See yaOn 11/1/06, Ted Goddard <[EMAIL PROTECTED]> wrote: Ajax applications often make use of multiple concurre

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

Hello James,On 11/1/06, James Graham <[EMAIL PROTECTED]> wrote: Charles Iliya Krempeaux wrote:>> To take a slight detour into the (hopefully not too) abstract, what do>> people think the fundamental point of semantics in HTML is? I'd say Machine readability. >Sorry to be pedantic but wh

[whatwg] XHTML5 DOM building and IDness

The spec says: The rules for parsing XML documents (and thus XHTML documents) into DOM trees are covered by the XML and Namespaces in XML specifications, and are out of scope of this specification. However, the spec says the following about the id attribute: If the value is not the empty str

Re: [whatwg] Semantics in HTML

Anne van Kesteren wrote: [...] I also don't know which view best fits my position because I don't really understand what people are trying to achieve with (the markup in) HTML -- I think there are things I would change in the current draft, but there seems little point talking about which marku

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

Also sprach James Graham: > To take a slight detour into the (hopefully not too) abstract, what do > people think the fundamental point of semantics in HTML is? To keep HTML high enough on the ladder of abstraction [1] to remain a media-independent markup language. [1] http://people.opera.com

[whatwg] Semantics in HTML (was: Re: Joe Clark's Criticisms of the WHATWG and HTML 5)

On Wed, 01 Nov 2006 20:55:58 +0100, James Graham <[EMAIL PROTECTED]> wrote: And HTML5 isn't that semantically pure anyway. Where can it be improved? To take a slight detour into the (hopefully not too) abstract, what do people think the fundamental point of semantics in HTML is? I've no

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

Charles Iliya Krempeaux wrote: To take a slight detour into the (hopefully not too) abstract, what do people think the fundamental point of semantics in HTML is? I'd say Machine readability. Sorry to be pedantic but what do you mean "machine readable"? All (conforming) HTML documen

[whatwg] [HTML5] Editorial: 3.10.18. The |sup| and |sub| elements

The second to last example should probably better read: E = m · c2 or maybe, as the speed of light is a constant, E = m · c2.

Re: [whatwg] Video (Was: How not to fix HTML)

Hello,On 11/1/06, Christoph Päper <[EMAIL PROTECTED]> wrote: *Ian Hickson*, 2006-10-30:>> Sure. FWIW, there's a lot of interest in browser vendors about> introducing> a element or some such (or maybe making browsers natively> support > video in , or both).I think it would be helpful to /explicitly

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

*Anne van Kesteren*, 2006-11-01: On Wed, 01 Nov 2006 19:24:17 +0100, Christoph Päper <[EMAIL PROTECTED]> And HTML5 isn't that semantically pure anyway. Oh, I thought I had removed this slightly offending sentence before sending, anyways ... Where can it be improved? I just think that

Re: [whatwg] How not to fix HTML

Hi, From: Lachlan Hunt <[EMAIL PROTECTED]> I believe the issue is with the way screen readers handle existing forms. The problem is that each radio button or checkbox has it's own label, but the whole group is often associated with a single question and there is no way mark that up. e.g. G

Re: [whatwg] How not to fix HTML

Lachlan Hunt wrote: Ian Hickson wrote: Joe Clark wrote: http://blog.fawny.org/2006/10/28/tbl-html/ FYI, my response to that his here. http://lachy.id.au/log/2006/10/fixing-html Joe Clark has responed. http://lachy.id.au/log/2006/10/fixing-html#comment-713 His comment is copied here for di

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

Hello,On 11/1/06, James Graham <[EMAIL PROTECTED]> wrote: Anne van Kesteren wrote:> On Wed, 01 Nov 2006 19:24:17 +0100, Christoph Päper> <[EMAIL PROTECTED]> wrote:>> And HTML5 isn't that semantically pure anyway. >> Where can it be improved?To take a slight detour into the (hopefully not too) abstr

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

Anne van Kesteren wrote: On Wed, 01 Nov 2006 19:24:17 +0100, Christoph Päper <[EMAIL PROTECTED]> wrote: And HTML5 isn't that semantically pure anyway. Where can it be improved? To take a slight detour into the (hopefully not too) abstract, what do people think the fundamental point of seman

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

Hello Christoph,On 11/1/06, Christoph Päper <[EMAIL PROTECTED]> wrote: *Henri Sivonen*, 2006-10-29:>> http://blog.fawny.org/2006/10/28/tbl-html/>>> * HTML has samp, var, and kbd. I use all of them and I am >> pretty much the only one who does.>> FWIW, I think and don't deserve to be in HTML a

[whatwg] [HTML5] 3.10.9. The |abbr| element

First off I think the requirement for a |title| is too strict, because there are time and space saving abbreviations everyone knows -- i.e. either their expansion or their meaning -- that do not need an expansion, e.g. "e.g." or "AIDS". Therefore the second sentence should use 'may', not 's

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

On Wed, 01 Nov 2006 19:24:17 +0100, Christoph Päper <[EMAIL PROTECTED]> wrote: And HTML5 isn't that semantically pure anyway. Where can it be improved? -- Anne van Kesteren

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

*Henri Sivonen*, 2006-10-29: http://blog.fawny.org/2006/10/28/tbl-html/ * HTML has samp, var, and kbd. I use all of them and I am pretty much the only one who does. FWIW, I think and don't deserve to be in HTML and I am not convinced that the use cases for could not be satisfied

Re: [whatwg] Video (Was: How not to fix HTML)

*Ian Hickson*, 2006-10-30: Sure. FWIW, there's a lot of interest in browser vendors about introducing a element or some such (or maybe making browsers natively support video in , or both). I think it would be helpful to /explicitly/ allow content types (alias media types) in |type| of

[whatwg] XMLHttpRequest connection limit

Ajax applications often make use of multiple concurrent HTTP requests; in particular Ajax Push (Comet/Reverse Ajax) makes use of two HTTP connections: one to block waiting for messages from the server, the other to send messages to the server. The problem is that the connection limit for many br

Re: [whatwg] Dialogue and inline quotations

Le 31 oct. 2006 à 16:26, Henri Sivonen a écrit : I know it has already been discussed, but I'd suggest this: What benefits do consumers of HTML get from knowing that something is a dialog? What tangible benefits can authors see from marking up dialogs as dialogs? That is, what is t

Re: [whatwg] The Module Tag

> > The sender is suspended until the receiver returns. > And what happens to the receiver? Is the script currently > running in the receiver context interrupted? The send function checks the type of its argument. It then checks for the existence of the receive function. If it exists, it calls

Re: [whatwg] How not to fix HTML

Matthew Raymond wrote: The element gives the label for the group. That's similar to the idea I posted. True, but it eliminates the need for an |info| attribute on every element. Oops. Those info attributes were a copy and paste error. They should have been removed from #1 and #2,

Re: [whatwg] How not to fix HTML

Lachlan Hunt wrote: > Matthew Raymond wrote: >>Here's a thought: >> >> | >> | Gender: >> |Male >> |Female >> | >> >>The element gives the label for the group. > > That's similar to the idea I posted. True, but it eliminates the need for an |info| attribute on every elemen

Re: [whatwg] Element name expressiveness

On Wed, 01 Nov 2006 08:56:05 +0100, Michael(tm) Smith <[EMAIL PROTECTED]> wrote: If the design criteria were to try to keep names of new elements reasonably short while still having unobscure meanings, then and would seem to meet that criteria, and would better be . But I'm not sure what the

Re: [whatwg] Browser Signature Standards Proposal

On Wed, 01 Nov 2006 14:22:15 +0600, Channy Yun <[EMAIL PROTECTED]> wrote: >> What benefit does this provide over simply using HTTPS with a client-side >> certificate? > Using HTTPS with a client-side certificate doesn't support digital > signature.The digital signature is same with the signing or

Re: [whatwg] Browser Signature Standards Proposal

Dear Alexey, Using HTTPS with a client-side certificate doesn't support digital signature.The digital signature is same with the signing or stamp of contract in real world. Many governments encourage to add digital signature to transactional data (form data). It legally assures data and transacti