W3C

- DRAFT -

Forms Working Group Teleconference

07 May 2014

Agenda

See also: IRC log

Attendees

Present
pfennell, Steven_, [IPcaller], ebruchez, Alain
Regrets
Chair
Steven
Scribe
Steven

Contents


<trackbot> Date: 07 May 2014

Announcements

Steven: I am presenting something on XForms at XML London
... Philip will be there as well.

ACTION-1970 - Propose list of page access functions

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

Erik: We discussed this last time.

Steven: It would be useful.

Erik: One function to get the URI, it is called Location in browsers
... I have to admit I don't understand the subtleties of URIs, but the other functions extract parts of a URI
... I have used the names used in the Java class for this

Steven: Why might the 'raw' part be useful?

Erik: I'm not fully convinced.
... it might be so that you can split parts properly, for instance if there is an "=" in the query string
... I'm only 60% convinced

Steven: Though the 'param-values' should solve that anyway.

Erik: Should we use the 'anyURI' type at all?
... it seems to allow any string at all nowadays.
... it does make it clear in the function signature, but it doesn't give you any gains.
... so 'parameter-values' could just take a string

Steven: So that any string would work, as long as it contained parameters in URI form?

Erik: Yes

Steven: So you could apply 'parameter-values' to a string that had been extracted from a URI with uri-query

<ebruchez> ?abc=def&ghi=klm

<ebruchez> ?abc=d%26ef&g%26hi=klm

Erik: The question is when to process the % escapes

<ebruchez> abc -> d&ef

<ebruchez> xf:uri-query(‘http://abc.org/foo?abc=d%26ef&g%26hi=klm’)

Steven: That then explains why you need the 'raw' parameter

<ebruchez> processed -> ‘abc=d&ef&g&hi=klm’)’

<ebruchez> raw -> ‘d%26ef&g%26hi=klm’)’

Erik: It in any case allows you access to everything

Steven: So the two questions are: Do we want to use the anyURI data type, and 2) Do we want to include the 'raw' versions

<ebruchez> http://www.w3.org/TR/2014/REC-xpath-functions-30-20140408/

Erik: In that link, they mention that every character is allowed in an anyURI

Philip: There are very few functions that take an anyURI, the vast majority are taken as strings

Erik: Maybe we should follow XPath that return values are anyURI, but parameters are strings.
... I don't know if that is accepted practice though

<ebruchez> http://www.w3.org/TR/xpath-30/#promotion

<ebruchez> “URI type promotion: A value of type xs:anyURI (or any type derived by restriction from xs:anyURI) can be promoted to the type xs:string. The result of this promotion is created by casting the original value to the type xs:string.”

" and it allows any character string to appear as the value of an xs:anyURI item. '

Erik: Validation of anyURI gives you nothing

Steven: If XSD 1.1 says that anyURI==string, then you neither gain nor lose.

<ebruchez> http://expath.org/modules/http-client/

Erik: EXPath has modules for http

<ebruchez> http://expath.org/spec/http-client

<ebruchez> “ It is an xs:anyURI, but is declared as a string to be able to pass literal strings (without requiring to explicitly cast it to an xs:anyURI)”

Erik: "It is an xs:anyURI, but is declared as a string to be able to pass literal strings (without requiring to explicitly cast it to an xs:anyURI)."

<ebruchez> foo(‘’http:///example.org)

<ebruchez> foo(xs:anyURI(‘http://example.org’))

Steven: OK, let's follow that example then
... String it is then

Erik: I will ask someone who knows about it, to see if there's anything we need to consider

Steven: And do we go with 'raw'?

Erik: Yes
... One last question.
... EXPath is not a large organisation
... it could be an interesting place to propose these functions there.

Steven: Go for it!

Erik: But still a part of XForms?

Steven: That would be faster I guess, but it would be good to share

<scribe> ACTION: Erik to contact EXPath about URI functions [recorded in http://www.w3.org/2014/05/07-forms-minutes.html#action01]

<trackbot> Created ACTION-1973 - Contact expath about uri functions [on Erik Bruchez - due 2014-05-14].

Steven: If we adopt this, we need spec text.

action; erik to spec URI functions

<scribe> ACTION: Erik to spec URI functions [recorded in http://www.w3.org/2014/05/07-forms-minutes.html#action02]

<trackbot> Created ACTION-1974 - Spec uri functions [on Erik Bruchez - due 2014-05-14].

AOB?

Erik: Someone sent me directly an email about multipart in submission

<ebruchez> http://www.w3.org/2013/05/22-forms-minutes.html

Erik: I replied that it hadn't been done, and is a bit late for XForms 2.0
... But we should revive that.

Steven: Let's look at it again. I'll put it on the agenda.

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Erik to contact EXPath about URI functions [recorded in http://www.w3.org/2014/05/07-forms-minutes.html#action01]
[NEW] ACTION: Erik to spec URI functions [recorded in http://www.w3.org/2014/05/07-forms-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2014/05/07 15:40:58 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/wow/wo/
Succeeded: s/TH/Th/
Succeeded: s/“RI/“URI/
Succeeded: s/\//
Succeeded: s/,/./
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Default Present: pfennell, Steven_, [IPcaller], ebruchez
Present: pfennell Steven_ [IPcaller] ebruchez Alain
Agenda: http://lists.w3.org/Archives/Public/public-forms/2014May/0001
Found Date: 07 May 2014
Guessing minutes URL: http://www.w3.org/2014/05/07-forms-minutes.html
People with action items: erik

[End of scribe.perl diagnostic output]