W3C

- DRAFT -

XForms Users Community Group Teleconference

13 Sep 2017

Agenda

See also: IRC log

Attendees

Present
Alain, Erik, Philip, Steven
Regrets
Chair
Steven
Scribe
Steven

Contents


<alain> No

<pfennell> No

<ebruchez> we can hear you

<pfennell> Erik and I can hear each other so the problem is still with you Steven.

ACTION-2134: Add the two email types to the spec

https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0002

Steven: This is done

ACTION-2131: Adopt new validation rule in text

https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0011

Steven: Also done

context information for action-error on actions with IDREF

https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0012

Steven: What should the value of error-type be?

Erik: I think we treat it as a binding error in other places.
... see if I can find an example
... maybe I'm wrong
... A separate value would be preferable.

Steven: ID-error?

Erik: yes, or idref

Steven: OK

<scribe> ACTION: Steven to make errortype for bad IDs idref-error [recorded in http://www.w3.org/2017/09/13-forms-minutes.html#action01]

<trackbot> Created ACTION-2137 - Make errortype for bad ids idref-error [on Steven Pemberton - due 2017-09-20].

setvalue context information for action-error

https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0013

Steven: Two different values?

Erik: We don't need to be that sepcific I think
... let me see if there is a precedent
... let's make something up

Steven: setvalue-error?

Erik: There is a similar case with submission
... replace="text"
... target-non-element in that case.
... so it is different, since setelement can set attributes as well
... maybe reuse "target-xxx"
... target-children
... a bit specific.
... just make it up

<scribe> ACTION: Steven to assign anj error name to the settarget errors [recorded in http://www.w3.org/2017/09/13-forms-minutes.html#action02]

<trackbot> Created ACTION-2138 - Assign anj error name to the settarget errors [on Steven Pemberton - due 2017-09-20].

Email type

https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0018

Erik: I fully agree that the user doesn't have to do work
... If the user types leading and trailing spaces, it should not give an error
... whitespace MIP deals with this
... for most fields if not all, you want spacing to be normalised
... and then you don't need spaces in the type.

Steven: if incremental="true" then a trailing space would give a validation error, which will go if you tab away.
... rather odd.

Erik: Yes there is a tension in this case.
... it's a general problem.
... We would solve it for email, and not for the other cases.
... It is seldom that you use incremental.

Steven: So in fact, you would paste the email, and tab away, whitespace MIP would come into effect, and so wouldn't show up as a validation error.

Erik: Yes

Steven: You have convinced me.

Erik: the other data types that we import don't include spaces, so this shouldn't either.

Telephone number type

https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0016

https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0028

Steven: Do we think it's worth adding?

Erik: Clearly useful.
... we don't have such a type.
... We are investigating.
... we want to do more than syntax checking but also semantic properties

Steven: Comparable to how we do credit cards, one part that does the syntax, and a constraint function that checks the semantics.

Erik: So the question is whether a syntax check is enough.

Steven: The type does a basic level of consistency checking
... even with emails, you don't know if it is a real email address until you have sent an email and got a reply.

Erik: With dates, we have an internal form and a localised external form. This might also be the case for phone numbers.
... I'm not sure if you want brackets and dashes in the data.

Steven: If you are all OK with adding it.

Alain: I'm OK with it. There is an issue with formatting.
... it's not that easy.

Philip: I'm OK too.

<scribe> ACTION: Steven to add telephone datatype. [recorded in http://www.w3.org/2017/09/13-forms-minutes.html#action03]

<trackbot> Created ACTION-2139 - Add telephone datatype. [on Steven Pemberton - due 2017-09-20].

Dynamic dependencies

https://lists.w3.org/Archives/Public/public-xformsusers/2017Mar/0012

[Awaiting an example]

Steven: Just a reminder

AOB

Steven: I'm giving a lecture at the Royal College of Art in two weeks time, so there will be a call next week, but not the week after.

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Steven to add telephone datatype. [recorded in http://www.w3.org/2017/09/13-forms-minutes.html#action03]
[NEW] ACTION: Steven to assign anj error name to the settarget errors [recorded in http://www.w3.org/2017/09/13-forms-minutes.html#action02]
[NEW] ACTION: Steven to make errortype for bad IDs idref-error [recorded in http://www.w3.org/2017/09/13-forms-minutes.html#action01]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/09/13 13:56:30 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/TH/Th/
Succeeded: s/nd/d/
Succeeded: s/abit/a bit/
Succeeded: s/agre/agree/
Present: Alain Erik Philip Steven
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0029
Found Date: 13 Sep 2017
Guessing minutes URL: http://www.w3.org/2017/09/13-forms-minutes.html
People with action items: steven

[End of scribe.perl diagnostic output]