W3C home > Mailing lists > Public > www-forms@w3.org > November 2004

RE: WD 15 November 2004 replace="instance"

From: John Boyer <JBoyer@PureEdge.com>
Date: Wed, 17 Nov 2004 13:45:54 -0800
Message-ID: <7874BFCCD289A645B5CE3935769F0B52C72A1D@tigger.pureedge.com>
To: "Klotz, Leigh" <Leigh.Klotz@pahv.xerox.com>, <www-forms@w3c.org>

Hi Leigh,

Good to hear from you again!

The idea was that replace=instance means that an instance will be replaced, not a portion.

So, anyone wanting to replace a portion of an instance could write an xforms-submit-done handler that used the duplicate action to copy the replaced instance into the portion of some other instance they wanted to replace.  

It's a little more markup to achieve the same functionality, but it side-stepped a number of problems.  The simplest was replace instance not saying what it meant, but there were deeper issues like having two single-node bindings on the same submission, e.g. what if you wanted to use the bind attribute for both?

Best regards,
John Boyer

-----Original Message-----
From: Klotz, Leigh [mailto:Leigh.Klotz@pahv.xerox.com]
Sent: Wednesday, November 17, 2004 11:08 AM
To: 'www-forms@w3c.org'
Subject: WD 15 November 2004 replace="instance"

In XForms 1.1 WD 15 November 2004 at
the replace="instance" functionality is augmented with attribute instance
which contains an IDREF.

1. Was the IDREF chosen over an XPath expression in order to resolve
ambiguities present in replacing entire instances (including root nodes), or
was there some other reason?
It seems like the functionality would be useful.

2. Why was the attribute value for replace not changed to reflect this new
If backward compatibility is needed, authors could use replace="instance"
without specifying an instance attribute, and replace the submitted
instance; other behaviors are not obtainable with XForms 1.0.

Received on Wednesday, 17 November 2004 21:46:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:14 UTC