W3C home > Mailing lists > Public > public-forms@w3.org > October 2008

LC comment on access module usage with XForms

From: John Boyer <boyerj@ca.ibm.com>
Date: Mon, 6 Oct 2008 22:49:15 -0700
To: www-html-editor@w3.org
Cc: www-html@w3.org, public-forms@w3.org
Message-ID: <OF3BE96294.02094D3B-ON882574DB.001EF40D-882574DB.001FFA12@ca.ibm.com>
The Forms WG discussed the issue below at its last face to face meeting, 
and I see now that the action item to send this note to XHTML2 "fell off 
the side of my desk" so to speak.

The issue is how to handle the access element in the context of documents 
with a run-time execution model that includes some sort of dynamic content 
generation.

The main example that came to mind was the XForms repeat, which iterates 
its content once for each node of data associated with the repeat by the 
run-time execution model.

The template content may contain elements with IDs.  Such languages define 
(or should define) rules for how to handle IDREFs to repeated elements 
with IDs.  At a minimum, a note about the existence of such markup 
languages seems warranted, along with advice to suggest that IDREF 
resolution is done according to that language.

To ensure you fully consider whether you want to go with this suggestion 
please note that the IDREF resolution method in XForms has two properties 
to consider:

1) Suppose you have an access element in a document, suppose you have a 
repeat element as its following sibling, and suppose the targetid of the 
access element indicates an element within the repeat.  Since the access 
element is outside of the repeat, the XForms IDREF method would provide 
the run-time element that matched both the requested ID and the current 
index of the repeat.

2) Suppose you have an access element *inside* of a repeat whose targetid 
indicates an element within the same repeat.  The repeat will iterate the 
access element in each "repeat item".  The XForms IDREF method in this 
case would resolve to the same repeat item whether or not the repeat item 
is the one currently indexed.  Is it appropriate for the access element to 
be scoped to operating within the containing repeat item?

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
Received on Tuesday, 7 October 2008 05:49:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:49 UTC