- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Thu, 9 Feb 2006 11:12:52 -0600
- To: "'Bailey, Bruce'" <Bruce.Bailey@ed.gov>, <w3c-wai-gl@w3.org>
I agree - we should see if there is any way to avoid creating a new term if we can. We just have to be careful not to redefine a defined term. Hmmmm Web Document.... That works well technically but would an interactive movie be viewed by many as a document? I'm afraid 'document' would is too heavily loaded with paper document concept. RE your definition of content. You substituted Web Unit for perceivable unit. Can't do that - they aren't equivalent. Putting perceivable unit back in you get Content: Information in the web unit that is used by the user agent to generate perceivable units. This includes the code and markup that define the structure, presentation, and interaction, as well as text, images, and sounds that convey information to the end-user. RE your question This begs the question, Why not use "resource" (or web resource) everywhere that delivery unit now appears? Resources has the same problem as delivery units. All Web units are resources but not all resources are Web units AND most resources can't meet the guidelines. Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison -----Original Message----- From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Bailey, Bruce Sent: Thursday, February 09, 2006 7:38 AM To: w3c-wai-gl@w3.org Subject: RE: BIG ISSUE -- re Delivery Units > The term Web Page (which I would dearly love to use) isn't sufficient > because of example 2 in the definition. >> Example 2: An interactive movie like shopping environment where the >> user navigates about and activates products to have them >> demonstrated, and moves them to cart to buy them. Browser Page (or User Agent Page) as well as "web document" (or a compound phrase like "web document or web application") covers example 2 without having to invent whole new terms, nor having try to explain what is meant by "unit". I have read all the excellent subsequent comments. I think I prefer the idea of using pages always in quotes over trying to define a whole new term. > The goal is to replace "delivery unit" throughout with "Web Unit". Understood. Is the plan to strike all three (delivery/perceivable/authored unit) completely, or might they still appear in the glossary? > So the D U term in content would be replaced as well. Right, but assuming we are get rid of three, a straight substitution reads: Content: Information in the web unit that is used by the user agent to generate web units. This includes the code and markup that define the structure, presentation, and interaction, as well as text, images, and sounds that convey information to the end-user. So again, I suggest it might be instructive to define content without referencing Web Units. The most recent definition of Web Unit is nice in that it doesn't reference content. It does, however, introduce the new undefined term "resource". This begs the question, Why not use "resource" (or web resource) everywhere that delivery unit now appears?
Received on Thursday, 9 February 2006 17:12:48 UTC