W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2004

RE: Meaning and scope of "authored unit"

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Sun, 25 Jul 2004 11:36:12 -0500
To: "'Web Content Guidelines'" <w3c-wai-gl@w3.org>
Message-ID: <auto-000034515487@spamarrest.com>

Thanks Jason

This is a very good leap forward on these topics.  I think we should use
your # 1 definition to work from rather than the two parter. Also I am not
sure about the "may be retrieved' so I suggest  "[may be / are]" til we
figure it out.

RE content negotiation -- since not everything DOES content negotiation -
and it may not be clear which version to get with multiple disabilities - I
believe that there must be default version.  

 So that would give us:


<propose>

An "authored unit" includes a resource identified by a URI, together
with any other resources directly or indirectly associated with it,
that [may be/ are] retrieved in the course of rendering or otherwise
processing it.
</propose>
 

<propose>
Where a resource identified by a URI can be retrieved in multiple forms
depending on content negotiation or other aspects of the delivery context,
the resource conforms to WCAG at some level if the version that will be
retrieved in the absence of content negotiation conforms to WCAG at that
level. 

NOTE: Additional form may be provided that are more or less accessible to
different groups but a conformance claim must be made based on a single form
not on a union of different forms. 

</propose>


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 Jason White
Sent: Sunday, July 25, 2004 5:25 AM
To: Web Content Guidelines
Subject: Meaning and scope of "authored unit"


To start addressing some of the issues raised at last week's meeting:


Alternative proposal:

<propose>
An "authored unit" includes a resource identified by a URI, together
with any other resource contained within it.

A resource is contained in an authored unit if it is retreived as part
of it, or linked to it directly or indirectly by a standard linking
mechanism and may be retrieved in the course of rendering or otherwise
processing the authored unit.
</propose>

Remarks

1. The purpose here is to specify that subsidiary resources which may
   be retrieved by a user agent or other processing software, are part
   of (or contained in) the authored unit. This avoids such scenarios
   as where an XHTML document is an authored unit but its associated
  raster-based images, style sheets etc., are not, with the result
   that the conformance claim would only cover the XHTML document
   itself, considered separately from the images and style sheets
   etc., that would be retrieved in the process of rendering it.

2. According to RFC 2396, the fragment identifier is not part of a
   URI, but the query part is. This answers a question raised at last
   week's meeting. In general, I don't think it is a good idea to
   impose restrictions on URI's in order to try to prevent conformance
   claims from being made with respect to, for example, part of a
   document; any such restriction can easily be circumvented.

3. A resource, according to RFC 2396, can be anything with identity.
   This means that the content of a resource (ie., what is obtained
   via a retrieval operation) can change over time, can be constructed
   dynamically and can vary according to any content negotiation which
   is performed.

I propose that where a resource identified by a URI can be retrieved
in multiple forms depending on content negotiation or other aspects of
the delivery context, the resource conforms to WCAG if at least one
version of its content conforms. Where there is a default version that
will be retrieved in the absence of content negotiation, this default
version must conform to WCAG.
Received on Sunday, 25 July 2004 12:36:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:17:58 UTC