Steven: I'll be teaching at the xmlsummerschool in 2 weeks time, so we'll cancel that call.
submission [DONE]
https://lists.w3.org/Archives/Public/public-xformsusers/2018Aug/0014.html
Stven: Done
https://lists.w3.org/Archives/Public/public-xformsusers/2018Aug/0020.html
Steven: Done
identification
https://lists.w3.org/Archives/Public/public-xformsusers/2018Aug/0029.html
Philip: seems to be easy to
read.
... I'm OK with it.
Erik: I need time to absorb it.
Steven: Than I'll add it to next week's agenda
https://lists.w3.org/Archives/Public/public-xformsusers/2018Aug/0016.html
https://lists.w3.org/Archives/Public/public-xformsusers/2018Aug/0023.html
Steven: We may need more time to
absorb this too
... Andreas is proposing a library for XPath 3
Erik: There are three
possibilities: As is, XML doc, Maps.
... We could support a subset of XPath maps to support this
feature.
... in XPath 3 there are native syntax, which we can't
have
... but also functions in the map namespace
... which we could provide
... we do that in our implementation, at least some of the
functions
... in XPath 2.
... Just new functions, and a new item type (hashmap)
... The other argument is a philiosophy
... the drawback is that it is more error-prone, because it is
hard to check.
... I'm not sure, I'm not sold on a map or an XML doc.
Steven: Let it sink in? More discussion?
Erik: We can wait.
https://lists.w3.org/Archives/Public/public-xformsusers/2018Jun/0033
Steven: What happens in the example?
Erik: The text was designed for the nested bind case
Steven: Quite
Erik: I think I agree that the
text doesn't cover this.
... but what is intended?
Steven: Agree.
... I think of
<bind ref="date">
<bind ref="@value" type="date" id="DATE"/>
</bind>
scribe: as a shorthand for:
<bind ref="date/@value" type="date" id="DATE"/>
scribe: in which case the repeat
has a well-defined meaning
... so the question is, is that what is intended?
Erik: I would like to check what
we do in this case.
... I suspect we do what you suggest there.
<scribe> ACTION: Erik to check what happens in his implementation with the nested bind/repeat
<trackbot> Created ACTION-2194 - Check what happens in his implementation with the nested bind/repeat [on Erik Bruchez - due 2018-09-05].
https://lists.w3.org/Archives/Public/public-xformsusers/2018Jul/0001
Steven: I have this use-case often. It would be fairly easy to supply a better version
Erik: reasonable thing to
do
... in what cases would you fall back?
Steven: In the submission case, whenever you get an xforms-submit-error, rather than a submit-done
Erik: should there be an error
when the @src fails?
... We get a link-error currently
Steven: Should we get that as well?
Erik: It would be useful.
<scribe> ACTION: Steven to spec up instance fallback
<trackbot> Created ACTION-2195 - Spec up instance fallback [on Steven Pemberton - due 2018-09-05].
[None]
[ADJOURN]
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/misis/missi/ Succeeded: s/fails./fails?/ Succeeded: s/teachning/teaching/ Succeeded: s/AGree/Agree/ Succeeded: s/nexted/nested/ Succeeded: s/nexted/nested/G Present: Steven Erik Philip Jorge_Sanchez No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Aug/0030.html Found Date: 29 Aug 2018 People with action items: erik steven WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]