- From: John Boyer <xforms-issues@mn.aptest.com>
- Date: Fri, 6 Jul 2007 12:51:10 -0500
- To: Steven.Pemberton@cwi.nl
- CC: www-forms-editor@w3.org
Hi Steven, Actually, this is not how the resource attribute works and was not part of the discussion about adding the resource attribute. The resource attribute is not even resolved unless there is no inline content. The intent was to allow something *similar* to what you have described, though. When a form is first served out to the user, their may be no prepopulation data for the instance, in which case it is left blank and thus the resource attribute is resolved and the empty template instance data is used. The user may then interact with the instance data and "save" the instance data. This may occur by submitting the data to a server-side database or, in a document-centric XForms system, it may occur by placing the serialization of the instance data into the xforms:instance before serializing the document containing the XForm to disk. Either way, when the form is next provided to the user, the saved instance data either is or can be placed into the xforms:instance element as prepopulation data that overrides the resource attribute. In conclusion, the resolution of the resource attribute only after checking for inline content is by design, so I hope that this response satisfies your concern about the behavior of the resource attribute. Thanks, John Boyer
Received on Friday, 6 July 2007 17:55:27 UTC