- From: John Boyer <boyerj@ca.ibm.com>
- Date: Wed, 3 Jun 2009 17:23:38 -0700
- To: Vlad Trakhtenberg <vladt@ca.ibm.com>
- Cc: www-forms@w3.org, www-forms-editor@w3.org
- Message-ID: <OFCF1E1F7E.72CF9FAE-ON882575CB.0001F212-882575CB.00022B40@ca.ibm.com>
Hi Vlad, The behaviors for the cases you mention are covered clearly in Section 11.10 on Replacing Data with the Submission Response ( http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-all.html#submit-data-replacement ). I believe the mixup is that you are reading the attribute summary only. Best regards, 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 From: Vlad Trakhtenberg/CanWest/IBM To: www-forms@w3.org, www-forms-editor@w3.org Cc: John Boyer/CanWest/IBM@IBMCA Date: 06/03/2009 10:58 AM Subject: XForms 1.1 spec - section 11.1 - targetref - minor clarifications needed Dear Editor/WG, I think some clarifications are needed in description of the targetref attribute in section 11. 1. What should happen if the targetref resolves to an empty nodeset? (And specifically, with respect to instance attribute presence :). 2. What should happen if targetref points to a 'wrong' instance (given by the instance attribute)? Ignoring instance attribute if targetref if present (and resolves to an non-empty nodeset?) or even its deprecation seems like a reasonable outcome. Thanks, Vlad Trakhtenberg, IBM, Victoria Software Lab
Received on Thursday, 4 June 2009 00:24:18 UTC