Digital signatures is as you say just a variation of authentication. The things
that the DS people wants to add are:
- A process that differs from authentication from the user's point of view
- A persistent trace of the authenticated operation. This is what the signature
adds to the picture.
On Nov 2, 2006, at 3:44 PM, Jonathan Worent wrote:
--- 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
Alexey Feldgendler [EMAIL PROTECTED], 2006-11-02 15:23 +0600:
On Thu, 02 Nov 2006 14:27:33 +0600, Anders Rundgren [EMAIL PROTECTED] wrote:
- A process that differs from authentication from the user's point of view
This is a problem of browser UI design, not of web standards.
What do you
Lachlan Hunt wrote:
Abbreviation expansions should only be supplied when they help the
reader to understand the content, not just because the word happens to
be an abbreviation.
I agree, unless using abbr with no title is useful to get the correct
rendering of abbreviations in non-visual
James Graham wrote:
Lachlan Hunt wrote:
Abbreviation expansions should only be supplied when they help the
reader to understand the content, not just because the word happens to
be an abbreviation.
I agree, unless using abbr with no title is useful to get the correct
rendering of
Lachlan Hunt wrote:
Matthew Raymond wrote:
Example:
| p
| label group=genderGender:/label
|
| label for=m
| input type=radio id=m name=gender value=m
| Male
| /label
|
| label for=f
| input type=radio id=f name=gender value=f
| Female
| /label
| /p
I
On 2-Nov-06, at 4:48 AM, Anne van Kesteren wrote:
FYI: The list for raising issues on XMLHttpRequest is public-
[EMAIL PROTECTED]
Thanks, I'll bring up the topic there as well. Changing
the policy on browser connection limits is lightweight
enough, though, that whatwg could be very
On 2-Nov-06, at 5:05 AM, Dave Raggett wrote:
well how about an XMLBEEPRequest specification then?
Beep is kind of like a bidirectional version of HTTP and includes
multiplexing capabilities with stream prioritization, see:
http://beepcore.org/index.html
Beep isn't in widespread use
I can see what everyones reasoning for not requiring the title (I change my
vote :)
--- Lachlan Hunt [EMAIL PROTECTED] wrote:
James Graham wrote:
Lachlan Hunt wrote:
Abbreviation expansions should only be supplied when they help the
reader to understand the content, not just because
Although the XMLHttpRequest has the capability of making a DOM
available from the resulting text, the client and server don't have to
make use of it. One could take the responseText and pass it to eval()
if the other end sent JSON. A BEEP API should support any valid use of
BEEP, just as
On Thu, 02 Nov 2006 20:06:31 +0600, Kornel Lesinski [EMAIL PROTECTED] wrote:
I'm thinking that footnotes would be flowed independently of normal
content. Browser would flow normal content from the top of the page, and
flow footnotes from the bottom of the page at the same time. Break when
On Thu, 02 Nov 2006 15:55:54 +0600, Michael(tm) Smith [EMAIL PROTECTED] wrote:
This is a problem of browser UI design, not of web standards.
What do you expect might happen when N different browser vendors
each go off on their own and, working in isolation from one
another, independently
12 matches
Mail list logo
