https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0026
Steven: We didn't resolve officially to do this.
Erik: I'm OK with that.
Philip: Me too
RESOLUTION: remove linking from <help/>
[Whether to allow mixed content in <output/>]
https://lists.w3.org/Archives/Public/public-xformsusers/2018Mar/0038
Steven: My proposal is to allow
text as a child of <output/> (as with the other
elements)
... but not the UI elements such as, indeed, <output/>
itself.
Erik: <label/> allows
host-language markup
... how about that?
<ebruchez> <label>Some <i>stuff</i> with <output value="42"/>.</label>
Erik: The spec allows that currently
<ebruchez> <output>Some <i>stuff</i>.</output>
Erik: Would that be
allowed?
... I don't know...
... one of the rationals was that output would be like
<span/>. In that case it would make sense.
Steven: Shall we give it a try?
Erik: I'm leaning towards
consistency
... but not 100% sure
Steven: More time to think about it?
Erik: Sure
Philip: I'd like more time.
Steven: I'll post a message summarising the issue
https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0031
Steven: Is there any case where a binding error would be dispatched according to this rule?
Erik: Logically that is what is implied.
<ebruchez> <input ref=".name">
Erik: If you made a mistake
Steven: That is not a name indeed
Erik: So that would be silently ignored.
Steven: As it would if there *were* an instance.
Erik: That seems fine.
<scribe> ACTION: Steven to modify the lazy authoring rule.
<trackbot> Created ACTION-2171 - Modify the lazy authoring rule. [on Steven Pemberton - due 2018-04-25].
https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0032
Steven: My last mail on the
subject:
https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0038.html
... my proposal was @contenttype or @content-type
Erik: Not really clear enough; we
need something more descriptive
... eg response-content-type
Steven: Works for me.
Philip: OK with me.
<scribe> ACTION: Steven to add @response-content-type to spec
<trackbot> Created ACTION-2172 - Add @response-content-type to spec [on Steven Pemberton - due 2018-04-25].
https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0030
Steven: Do we want to add a sort
function, or just use external defintions as Orbeon does for
instance?
... The problem is that XPath 3 already has sort(), and so
anything we add will only be a stopgap.
Erik: Right. And without functions as parameters, we would have to pass the sort expression as a string.
Steven: So leave as-is, ans see it as something we get for free later?
Erik: Yes.
Philip: Yes.
https://homepages.cwi.nl/~steven/forms/TestSuite/index.xhtml
Steven: New one posted, with lots
of new Event tests
... now starting on actions.
Steven: I will be presenting on XForms to a day for Dutch science journalists in June organised by NWO, the Dutch NSF.
[ADJOURN]
<scribe> ACTION: Steven summarise issues wrt <output/> mixed content.
<trackbot> Created ACTION-2173 - Summarise issues wrt <output/> mixed content. [on Steven Pemberton - due 2018-04-25].
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/rep/resp/ Succeeded: s/g// Succeeded: s/orb/Orb/ Present: Erik Philip Steven Regrets: Alain No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0036 Found Date: 18 Apr 2018 People with action items: 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]