See also: IRC log
<trackbot> Date: 13 March 2013
Steven: next week the call is one hour earlier
Steven: I've got a tutorial accepted on XForms
<Steven> http://lists.w3.org/Archives/Public/public-forms/2013Feb/0002.html
nvdbleek: Don't we already have it?
ebruchez: We only have it on xf:output
Steven: I'm ok with it
nvdbleek: Most implementations already support it I think
Steven: Would we include an xhtml media type to
nvdbleek: Don't we just need to
add the media type attribute
... If you have another host-language it might not make sense
to require html as a media type attribute
... e.g. ODT might want to use ODT but not html
Steven: We can do this by the wording should or may it shouldn't be a must
alain: I think it should be
specified at the data level, not on the control
... in my implementation you have to define a type in a
schema
Steven: Would you like to send your proposal to us, before we make a decision?
ebruchez: Not all control types
are specified by data types
... we could have both (in the model and on the control)
<alain> <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.agencexml.com/xsltforms/rte">
<alain> <simpleType name="standardHTML">
<alain> <restriction base="xsd:string" xsltforms:rte="TinyMCE"/>
<alain> <annotation>
<alain> <appinfo>
<alain> {
<alain> theme : "advanced",
<alain> skin : "o2k7",
<alain> plugins : "lists",
<alain> theme_advanced_buttons1 : ",bold,italic,underline,strikethrough,",
<alain> theme_advanced_buttons2 : "",
<alain> theme_advanced_buttons3 : "",
<alain> }
<alain> </appinfo>
<alain> </annotation>
<alain> </simpleType>
Steven: what is the type
<alain> </schema>
ebruchez: It is stored as text
nvdbleek: The spec doesn't allow controls to be bound to complex content, so you have to serialise it to a string
<Steven> http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_textarea_Element
Steven: if it a string then a type on the model doesn't looks the correct solution. Then it is more an input mode. xg:input already has this
ebruchez: Is anybody already using this to create a rich text control
Steven: There is no value for it yet
alain: You want to specify the features you want to allow
ebruchez: An implementation needs
to have a way to configure this. But I don't think we can
standardise this yet?
... an html capture control is something we can standardise
this
... in HTML5 they have e-mail, number,… to configure the type
of keyboard on mobile
... We generate those types based on the data type of the
instance
... for html we don't have a type so we can't do that yet
nvdbleek: we could create a tagging type to signal that we want to capture HTML
<Steven> (Erik to propose syntax)
<Steven> http://lists.w3.org/Archives/Public/public-forms/2013Jan/0028.html
Steven: Alain could you send in
examples of how you implement it?
... Erik you have an action item on this
ebruchez: I haven't done it yet
Steven: can we give you deadline, let say next week for this?
ebruchez: yes, I will do
... We discussed this a bit last week
... and we were thinking of making the syntax lighter
<Steven> http://www.w3.org/MarkUp/Forms/wiki/Xforms-action-error
nvdbleek: please read this and comment on it by next week
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/CH/Ch/ No ScribeNick specified. Guessing ScribeNick: nvdbleek Inferring Scribes: nvdbleek Default Present: Steven, [IPcaller], nvdbleek, ebruchez Present: Steven [IPcaller] nvdbleek ebruchez WARNING: Replacing previous Regrets list. (Old list: None) Use 'Regrets+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Regrets+ Uli Regrets: Uli Agenda: http://lists.w3.org/Archives/Public/public-forms/2013Mar/0006 Found Date: 13 Mar 2013 Guessing minutes URL: http://www.w3.org/2013/03/13-forms-minutes.html People with action items:[End of scribe.perl diagnostic output]