See also: IRC log
<trackbot> Date: 16 April 2014
Coming calls (Steven away for two weeks)
Steven: Let us have a break for two weeks. So next call will be May 7.
http://lists.w3.org/Archives/Public/public-forms/2014Apr/0013.html
http://lists.w3.org/Archives/Public/public-forms/2014Apr/0020.html
http://lists.w3.org/Archives/Public/public-forms/2014Apr/0022.html
Steven: Are we OK with the error
codes not being backwards compatible?
... the other option is to keep error-type the same, and have a
new sub-type that differentiates them
Erik: I don't think that it's a big deal; I just wanted to be sure we did it with full awareness
Alain: I'm OK with it too.
http://lists.w3.org/Archives/Public/public-forms/2014Apr/0021.html
[Erik explains email]
Steven: My use case is just
"parameter-value" (not sure if there should be an s on the
end)
... I like driving the design with use cases
Erik: I am frustrated by the paucity of functions in XPath
Steven: I agree, but we need use
cases
... such as for location-protocol
Alain: I have use cases for those things
Steven: Fine. I don't want top get in the way, just make sure we include things that will actually be used.
Erik: We don't have to do this
right now.
... there is clearly a use case for parameter names; not clear
about port, but then why allow some and exclude others?
Steven: Well, if you have the whole URL, you can string process.
Erik: True
... we could provide a function for the location url, and then
functions for *any* url
Steven: Good idea!
Erik: I can follow up on that.
Steven: Great!
http://lists.w3.org/Archives/Public/public-forms/2014Apr/0023.html
Steven: So why is the default
action for a submission error "do nothing"?
... and if you don't like the new default, well you can always
switch it off.
... (it's a single line)
Erik: You can make a similar case
for other errors
... see section 10.5
<ebruchez> https://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#Error_Handling
Erik: I see no harm in it.
Steven: The default action doesn't have to be a dialog; just some indication of what has gone wrong.
Erik: OK
Alain: OK, as long as it doesn't have to be language specific
http://lists.w3.org/Archives/Public/public-forms/2014Apr/0028.html
Steven: I think this is an error
<ebruchez> <xsd:group ref="xforms:UI.Common" minOccurs="0" maxOccurs="unbounded"/>
<ebruchez> <xsd:group name="UI.Common">
<ebruchez> <xsd:sequence>
<ebruchez> <xsd:choice minOccurs="0" maxOccurs="unbounded">
<ebruchez> <xsd:element ref="xforms:help"/>
Erik: The schema I have here has unbounded repeat wherever it is used
<ebruchez> <xsd:element ref="xforms:hint"/>
<ebruchez> <xsd:element ref="xforms:alert"/>
<ebruchez> <xsd:group ref="xforms:Action"/>
<ebruchez> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<ebruchez> </xsd:choice>
<ebruchez> </xsd:sequence>
<ebruchez> </xsd:group>
Steven: I intend to fix this, by changing the definition of UI Common
http://lists.w3.org/Archives/Public/public-forms/2014Apr/0029.html
Erik: The schema I have here says that <output> uses @UI Common
<ebruchez> <xsd:element name="trigger">
<ebruchez> <xsd:complexType>
<ebruchez> <xsd:sequence>
<ebruchez> <xsd:element ref="xforms:label"/>
<ebruchez> <xsd:group ref="xforms:UI.Common" minOccurs="0" maxOccurs="unbounded"/>
<ebruchez> </xsd:sequence>
<ebruchez> <xsd:attributeGroup ref="xforms:Common.Attributes"/>
<ebruchez> <xsd:attributeGroup ref="xforms:Single.Node.Binding.Attributes"/>
<ebruchez> <xsd:attributeGroup ref="xforms:UI.Common.Attrs"/>
<ebruchez> </xsd:complexType>
<ebruchez> </xsd:element>
<ebruchez> <xsd:element name="output">
<ebruchez> <xsd:complexType>
<ebruchez> <xsd:sequence minOccurs="0">
<ebruchez> <xsd:element ref="xforms:label"/>
<ebruchez> <xsd:element ref="xforms:mediatype" minOccurs="0"/>
<ebruchez> <xsd:element ref="xforms:filename" minOccurs="0"/>
<ebruchez> <xsd:group ref="xforms:UI.Common" minOccurs="0" maxOccurs="unbounded"/>
<ebruchez> </xsd:sequence>
<ebruchez> <xsd:attributeGroup ref="xforms:Common.Attributes"/>
<ebruchez> <xsd:attributeGroup ref="xforms:Single.Node.Binding.Attributes"/>
<ebruchez> <xsd:attributeGroup ref="xforms:UI.Common.Attrs"/>
<ebruchez> <xsd:attribute name="value" type="xforms:XPathExpression" use="optional"/>
<ebruchez> <xsd:attribute name="mediatype" type="xsd:string" use="optional"/>
<ebruchez> </xsd:complexType>
<ebruchez> </xsd:element>
<ebruchez> http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
Erik: The online schema may not have it
Steven: You are right; it has
@appearance, and not @UI Common
... OK I'll fix.
[none]
Steven: Next call in three weeks
[ADJOURN]
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/roor/rror/ Succeeded: s/:p/"p/ Succeeded: s/erros/errors/ No ScribeNick specified. Guessing ScribeNick: Steven_ Inferring Scribes: Steven_ Default Present: Steven_, [IPcaller], ebruchez Present: Steven_ [IPcaller] ebruchez Alain Regrets: Nick Uli Philip Agenda: http://lists.w3.org/Archives/Public/public-forms/2014Apr/0026 Found Date: 16 Apr 2014 Guessing minutes URL: http://www.w3.org/2014/04/16-forms-minutes.html People with action items:[End of scribe.perl diagnostic output]