FW: Web Page Proposal from F2F

At the Face to Face we discussed using Web Page and "states" of a page to
address the Web Page/Unit issue. 

 

We got close but did not work out a final wording.  Here is my best take on
where we got to.     

 

Comments solicited.   I will try to incorporate them and we can take this up
next week since it looks like we have a full agenda this week. 

 

 

 

 

 

*	Conformance would be by Web Page(s) at a URI or a defined set of
URIs

 

*	A web page is   (from Web Characterization Terminology & Definitions
Sheet  --  W3C Working Draft 24-May-1999)

*	A collection of information, consisting of one or more Web
resources, intended to be rendered simultaneously, and identified by a
single URI. More specifically, a Web page consists of a Web resource with
zero, one, or more embedded Web resources intended to be rendered as a
single unit, and referred to by the URI of the one Web resource which is not
embedded.

*         Examples: An image file, an applet, and an HTML file identified
and accessed through a single URI, and rendered simultaneously by a Web
client.

*         Note: The components of a Web page can reside at different network
locations. The location of the Web page, however, is determined by the URI
identifying the page.

*         Note: The scope of a Web page is limited to the collection of Web
resources which are displayed simultaneously by requesting the Web page's
URI. The components of a Web page actually rendered in a page view is
client-dependent.  [Suggest we delete this last note and replace it with:
NOTE: The scope of a Web Page is limited to the collection of Web resources
that are displayed simultaneously with the primary resource (the resource
that is downloaded first from the URI) at some time.   Resources that are
part of the page may be displayed at different times and may differ
depending on the client software (user agent) used. 

*         New Note:  Dynamic Web pages may have multiple states.   Immersive
or animated content may change its state many times a second. 

 

*	With dynamic content such as Ajax, a user could request a URI and
encounter a page that had multiple states. These states may appear to the
user as variations of the same page or as completely different pages. In
either case, any conformance claim made would apply to each state of the
page and each state of the page would need to be accessible in order for the
claim to be valid. 

*	An example of multiple page states at a single URI could be an
entire web application or an entire email application that was at one URI.
With this single URI application you move from the inbox to an address book
without leaving the URI or .    

 

*	Even immersive environments could be covered because they would just
constitute a sequence of continually changing states in the web page.
*	It is possible to implement the same application as multiple pages
or as multiple states of a single page.  They could be so identical in
appearance that the only way that a user could tell that they have not gone
to a new page was by looking up at the URI to see if it changed.   Since all
states of all pages need to be accessible - this difference doest not matter
since they would both need to be accessible.  

 

Sites that implement whole sections or a whole site at one URI reduce their
ability to focus the scope of any claim.   

 


Gregg
 -- ------------------------------ 
Gregg C Vanderheiden Ph.D.