ACTION-2142: Research if anything else has such an attribute and to

suggest a name [for overriding incoming mediatype]

https://lists.w3.org/Archives/Public/public-xformsusers/2017Nov/0003

Steven: Now closed, and done

Lazy authoring

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0043

Steven: Also done

ACTION-2172: Add @response-content-type to spec

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0057

Steven: Also done, with a change of the attribute name
... plus media-type to mediatype

Serialization and submission

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0050

Steven: Are we all OK with all 3 cases being not important for submission="none"?

All: Yes

<scribe> ACTION: Steven to make the change for submission="none"

<trackbot> Created ACTION-2174 - Make the change for submission="none" [on Steven Pemberton - due 2018-05-02].

ACTION-2166: Unify output/label/help/hint/alert

[Whether to allow mixed content in <output/>]

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0048

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0066.html

Steven: A new summary of the use of @value
... <header/> looks like a case
... instead of

<header name="Accept"

value="'application/sparql-results+xml'"

combine="replace"/>

scribe: we should be able to write

<header name="Accept"

combine="replace">application/sparql-results+xml</header>

Steven: TO summarise my proposals:
... deprecate submission/header/name submission/header/value
... allow submission/header to have PCDATA content
... also function/result and function/var
... and that leaves <output/> to discuss
... Comments?
... and then <output/> https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0048

Erik: I think we're OK with text in <output/>, and we haven't decided on nested <output/>
... I think text is fine. And nested host markup.

Alain: It should be limited to output. Really it sounds like curly brackets.
... When you want to generate HTML with XQuery, you use curly brackets.

Steven: So what is you opinion of allowing <output>text</output>

?

Alain: I'm OK with it. Why not? But just output of course.

Philip: Makes sense.

<scribe> ACTION: Steven to add PCDATA to output content model.

<trackbot> Created ACTION-2175 - Add pcdata to output content model. [on Steven Pemberton - due 2018-05-02].

Content models

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0067.html

Steven: I'll give myself an action item to make those consistent.

<scribe> ACTION: Steven to add content models to element descriptions where missing

<trackbot> Created ACTION-2176 - Add content models to element descriptions where missing [on Steven Pemberton - due 2018-05-02].

Default for dispatch/@targetid

[This is an agenda item that somehow got lost in the past]

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0009

Steven: I propose we discuss this next week.

Test Suite 2.0

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0051

Steven: I'll continue with actions this week.

AOB

[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/wnat/want/
Succeeded: s/Stevfen/Steven/
Present: Alain Erik Philip Steven
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0060
Found Date: 25 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.)