Profile

Attached is the list of issues, in Excel format. The fields of this small database was a merger between a W3 issues list (I think it was XForms) and an OASIS issues list (I think it was BTP). We should decide in the F2F how to update this list, and more importantly, how to resolve all the issues! Yours, ...

Tim, Yup. Same thing. The differences are minor (except for the fact that you did not ignore the "scope" issue). To your questions on the differences: 1-2. On the question of placeholders/defaults. I tried to be true to the XForms "philosophy" where an instance is always there, and where "bind" is optional. ...

A small addendum to my proposal of yesterday. Re-reading the XForms spec, it seems that the <instance> can have multiple elements inside it, so that we can remove the redundant <values> tag everywhere. Thus, the example will look a lot cleaner : 1. Description of an entity with two properties ...

Objectives: 1. Separate Property definition (meta-data) from property values from property querying. 2. Do it simply . General model (as defined by XForms 1.0 in http://www.w3.org/TR/xforms/ ) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ value1 value2 ... below ...

Note also that this field is in _InteractionResponse_, which means that a simple "link" which only changes navigationalState cannot do this. I understand the rationale - interaction is blocking while navigation change is not, which means that two Producers can simultaneously request a redirectURL which ...