See also: IRC log
<nvdbleek> ACTION-1984?
<trackbot> ACTION-1984 -- Nick Van Den Bleeken to Summarise duration types clashes -- due 2014-10-29 -- OPEN
<trackbot> https://www.w3.org/2005/06/tracker/xforms/actions/1984
<nvdbleek> http://www.w3.org/TR/xpath-functions/#duration-subtypes
<nvdbleek> https://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#dt-dayTimeDuration
Erik: I noticed that these two
types were defined a long time ago by XForms but since then
have been taken up by XPath 2 and Schema 1.1
... though they don't refer to each other
<nvdbleek> xforms:dayTimeDuration inherits from xsd:duration and not xs:dayTimeDuration
Erik: maybe for dependency
reasons
... so they are redundant in XForms
... our daytimeduration was not a union with empty
... and the same is true of xf:email
Steven: Well we need to fix that
Nick: the text says that it is
derived from xs:duration, but in fact it isn't
... we should check the schema
Steven: If schema has them, we should use them, and add empty
Erik: If we do that it will make an incompatibilty with XForms 1.1, since it will now accept empty
<nvdbleek> The schema https://dvcs.w3.org/hg/xformsusers/file/88aaa18ff8a3/2.0/core/schema/xsd/XForms-20-Schema.xsd#l1584 derives from xsd:duration
Steven: But if someone has pointed the lack of empty out in XF1.1, we would have accepted it as an error. It should be seen as an erratum
Nick: The schema says that they
accept empty, so we may be alright.
... the one in the spec definitely allows empty
... see section 5.2.4
...
https://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#dt-dayTimeDuration
Steven: xf:email allows empty too, so we're safe.
Erik: We had to change the definition of email
<ebruchez> info@orbeon.com/
Steven: Send an error report then!
Erik: Ending with a slash would
work
... but shouldn't
<ebruchez> info@orbeon is valid too
Steven: This is the most revcent
spec: http://tools.ietf.org/html/rfc5321
... and http://tools.ietf.org/html/rfc5322#section-3.4.1
Erik: It is a problem, all the same
Nick: There are new specs for international domains as well
Erik: The data type lets too many things through
Nick: The spec should allow an
implementation to do more checks on the type
... such as checking the existence of the domain
Steven: How about http://tools.ietf.org/html/rfc6530
Nick: Take offline?
Steven: OK
Nick: back to duration
<nvdbleek> https://dvcs.w3.org/hg/xformsusers/file/88aaa18ff8a3/2.0/core/schema/xsd/XForms-20-Schema.xsd#l1584
Nick: In our schema for
daytimeduration and yearmonthduration
... we don't allow empty
... because it is a restriction on xsd:duration, and should be
string
Erik: The spec text is compatible, but does allow empty
Nick: Let me just do an experiment with the current schema
Erik: There is a wording problem
in the spec, using "derives" in the wrong way
... but conceptually does the right thing
Steven: So we use the xsd version and union it with empty. Good
<nvdbleek> <xs:simpleType name="dayTimeDuration">
<nvdbleek> <xs:union memberTypes="xs:dayTimeDuration">
<nvdbleek> <xs:simpleType>
<nvdbleek> <xs:restriction base="xs:string">
<nvdbleek> <xs:length value="0"/>
<nvdbleek> </xs:restriction>
<nvdbleek> </xs:simpleType>
<nvdbleek> </xs:union>
<nvdbleek> </xs:simpleType>
Steven: I have made the
corresponding changes
... in the spec
<nvdbleek> Nick: hmm we can’t do it like this because the xs:dayTimeDuration is a Schema 1.1 and our schema is 1.0
Erik: Then we use XPath 2.0
... data model, that we reference
<ebruchez> http://www.w3.org/TR/xpath-datamodel/#types-predefined
<scribe> ACTION: Steven to clean up references to XPath Data Model (capitalisation and ref) [recorded in http://www.w3.org/2014/10/31-forms-minutes.html#action01]
<trackbot> Created ACTION-1985 - Clean up references to xpath data model (capitalisation and ref) [on Steven Pemberton - due 2014-11-07].
Steven: I have changed the wording of 5.2.1 to mention that the types come from XSD or XDM
Nick: I have updated the schema
<ebruchez> <item label="Cash" value="cash"/>
<ebruchez> <item label="Credit" value="cc"/>
<ebruchez> <instance id="headers">
<ebruchez> <my-headers>
<ebruchez> <my-header><name>Content-Type</name><value>application/xml</value></my-header>
<ebruchez> <my-header><name>Accept</name><value>application/xml,text/json</value></my-header>
<ebruchez> </my-headers>
<ebruchez> </instance>
<ebruchez> <header ref="instance('headers')/my-header" name="{name}" value="value"/>
<ebruchez> produces 2 headers:
<ebruchez> Content-Type: application/xml
<ebruchez> Accept: application/xml,text/json
[Lunch]
Steven: I have now finished adding @name and @ value to <header>
https://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#submit-header
I added @value to element value inthe overview
Nick: I have updated the schema for @label etc.
<nvdbleek> link to diff https://dvcs.w3.org/hg/xformsusers/diff/1180ef4957b0/2.0/core/schema/xsd/XForms-20-Schema.xsd
Steven: Does https://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#Typed_Values need to be updated with the new duration types?
<nvdbleek> http://www.w3.org/TR/xpath20/#id-typed-value
<ebruchez> http://www.w3.org/TR/xslt20/#built-in-types
Erik: This is where the list comes from
Steven: I have modified section 4.3 to refer to the types in 5.2.1
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/Presnet/Present/ Succeeded: s/O/o/ Succeeded: s/TH/Th/ Succeeded: s/types/type/ Succeeded: s/abut/about/ Succeeded: s/xs:duration/xs:dayTimeDuration/ Succeeded: s/ST/St/ Succeeded: i/Steven: I have now finished adding @name and @ value to <header>/Topic: Editing session No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Present: Steven Nick Erik Got date from IRC log name: 31 Oct 2014 Guessing minutes URL: http://www.w3.org/2014/10/31-forms-minutes.html People with action items: steven[End of scribe.perl diagnostic output]