Re: XForms 1.1 spec - section 11.1 - targetref - minor clarifications needed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: XForms 1.1 spec - section 11.1 - targetref - minor clarifications needed

John Boyer

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: [hidden email]  

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: [hidden email], [hidden email]
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