<trackbot> Date: 02 April 2014

ACTION-1969 - Send list of possible useful functions to do with

page (was Access to arguments)

http://lists.w3.org/Archives/Public/public-forms/2014Apr/0000.html

Steven: Thanks for doing this. The last sentence is the important one. "What should XForms standardise?".
... If several implementations are doing this, then it is all the more important to standardise

Erik: I think we should take the client mindset, rather than the server one

Steven: Which of these do we have a use case for? I definitely have a use case for the parameters

Erik: I think they could all be useful
... You could navigate to another page by accessing the URL that it comes from

Steven: So in other words we need to think about this a bit longer: the naming, and which we need?
... Shall I leave it at that, and talk about it next week, with a proposal?

<scribe> ACTION: Erik to propose list of page access functions [recorded in http://www.w3.org/2014/04/02-forms-minutes.html#action01]

<trackbot> Created ACTION-1970 - Propose list of page access functions [on Erik Bruchez - due 2014-04-09].

resource-error on xforms-submit-error

http://lists.w3.org/Archives/Public/public-forms/2014Apr/0002.html

Steven: Summary of decisions to be made:

- fix or not

- use new values of error-type, or use error-message

- agree on names

- agree on extra information that is proposed between []

- be more explicit with xforms-action-error?

- should error-information really be error-message?

Steven: Do we fix?

Erik: error-information seems like a mistake. Deprecate, and standardise on error-message.

Steven: I think with xforms-action-error I can do a bit of digging to find out when the other values are meant to arise
... Then for the submission cases, do we agree to split them out, and if so, which method?

Erik: Another way to go with it is to use error-codes, so that we don't have to name the new cases

Steven: We could do that, it would be backwards compatible. On the other hands with names, the errors are self-explanatory, and therefore you don't need to look them up.

Philip: I agree that human-readable is more acceptable

Steven: Would you object Erik to splitting them out and giving them new names?

Erik: The non-backward compatible way?

Steven: Yes

[Erik checks his collection of XForms code to see if he uses resource-error]

Philip: I have to leave now, and regrets for next week.

Steven: What would your preference be, Erik, in this case?

Erik: error-message is for human-readable text, so I would prefer the extra information not to go there.

Steven: Well, we could repurpose "error-information"
... for information like what the media type we got was when in error

Erik: error-message would be fine for that

@label, @help, @hint, @alert

http://lists.w3.org/Archives/Public/public-forms/2014Mar/0008.html

Steven: I sent the summary of what I am going to do, to make sure we agreee, before I actually do all the work.

http://lists.w3.org/Archives/Public/public-forms/2014Apr/0005.html

Steven: I would just like the group to read and agree to the actions

[ADJOURN]

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/TH/Th/
Succeeded: s/{/[/
No ScribeNick specified.  Guessing ScribeNick: Steven_
Inferring Scribes: Steven_
Default Present: pfennell, ebruchez, Steven_
Present: pfennell ebruchez Steven_
Regrets: Uli Alain
Agenda: http://lists.w3.org/Archives/Public/public-forms/2014Apr/0004
Found Date: 02 Apr 2014
Guessing minutes URL: http://www.w3.org/2014/04/02-forms-minutes.html
People with action items: erik