W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2007

RE: bug in Web Page definition

From: Sean Hayes <Sean.Hayes@microsoft.com>
Date: Mon, 5 Nov 2007 16:05:37 +0000
To: Carlos A Velasco <carlos.velasco@fit.fraunhofer.de>, Gregg Vanderheiden <gv@trace.wisc.edu>
CC: 'Jason White' <jason@jasonjgw.net>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <180FE13BBE2B8A4997536D3B81D8A47AB6792FD8@EA-EXMSG-C324.europe.corp.microsoft.com>
Only the top most resource needs an HTTP(S) URI under the proposed definition, the other resources can come from anywhere - thus 1 & 3 below would not necessarily be excluded. If we allowed 2 as you propose, then the definition of web page would cease to have any meaning at all, as it would effectively encompass all information.

HTTP transfer pretty much defines the World Wide Web (as opposed to the internet as a whole which does use a wider set of protocols), and WCAG is Web content authoring guidelines, and not internet authoring guidelines, or indeed general principles for software design.

One might choose to apply the WCAG guidelines to arbitrary software, which might work in many cases, as they do embody general principles, but given the scope of the working group the restriction seems reasonable


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Carlos A Velasco
Sent: 05 November 2007 15:45
To: Gregg Vanderheiden
Cc: 'Jason White'; w3c-wai-gl@w3.org
Subject: Re: bug in Web Page definition


Dear Gregg,

Gregg Vanderheiden wrote:
> That is correct Jason.
>
>
> An HTML page that is not on the Web is not a Web Page.

I do not understand the issue here, and I disagree that «Web pages» can
only be served only via HTTP. Here are some scenarios:

- I can put -for some obscure given reason- all my CSS files in an FTP
server. Does it mean that for WCAG these CSS files do not exist?

- An Intranet Web site, based on the file protocol, where all files are
mounted locally via NFS, SMB, ... like Jason proposed.

- An AJAX application where the Web Services interaction happens via Web
Services using directly TCP, SMTP or any other protocol. I have not
tested whether this is supported by user-agents yet, but there are
already Web Services' implementations where you can built such scenarios
(server- and client-side).

Are we excluding all of these?

> ...

regards,
carlos
--
Dr Carlos A Velasco
  Fraunhofer Institute for Applied Information Technology (FIT)
  Web Compliance Center: http://webcc.fit.fraunhofer.de/

  imergo®: http://imergo.com/ · http://imergo.de/

  Schloss Birlinghoven, D53757 Sankt Augustin (Germany)
  Tel: +49-2241-142609 · Fax: +49-2241-1442609

Received on Monday, 5 November 2007 16:06:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:51 GMT