xforms:bind/@type date always required

Dave,

A neat trick in theory, but I think that once your remove the type binding to the value, your control will display the date as a string instead of using the date picker. Did you try it?

-Erik

David McIntyre wrote:

Wouldn't it be possible to use <xforms:bind nodeset="/blah[. != '']" type="xs:date"/> ?
Then, if the node is empty then the bind won't match so it won't enforce the datatype
constraint.
 
Cheers,
 
Dave
 
 

**
       
*Dave McIntyre   *MA, DPhil, GradDipSci
*Software Developer*
[hidden email] [hidden email]
P: +64 9 638 0600
F: +64 9 638 0699
M: +64 21 212 8087
S: dave.mcintyre
www.orionhealth.com <http://www.orionhealth.com/>


 >>> Erik Bruchez [hidden email] 5/06/2007 10:15 a.m. >>>
Ryan,

Do you see it as required-but-empty, or as invalid? The latter produces
an exclamation mark (!). I suspect that's what you get?

This said: if you bind an xs:date to instance data, then that data
cannot be blank per the type definition. So a blank date will always be
invalid.

You would think that saying required="false()" would fix this, but it
won't, because required="false()" is already the default, and
required-ness doesn't override the fact that the data is invalid.

To fix this, XForms 1.1 introduces new types which include the blank
space, so you can use xforms:integer instead of xs:integer:

   http://www.w3.org/TR/xforms11/#empty-content-types

But we have yet to implement them in Orbeon Forms for example (we hope
to do so real soon).

I think that you are seeing the issue because we did quite a bit of
improvements to validation last week, and quite likely we fixed that
feature along the way ;-) In particular, we now support using simple
types declared in a schema in xforms:bind (previously we only supported
built-in simple types). We also improved schema validation quite a bit,
including supporting lax and strict validation per instances.

So the answer is that we now follows the spec better. Do you have a
workaround (pending support for the xforms:date type)?

-Erik

Ryan Puddephatt wrote:
 > Hi,
 >     I'm trying to define an optional xforms:input for xs:date,
 > previously I had
 >
 > <xforms:bind nodeset="/blah" type="xs:date"/>
 >
 > and it displayed fine, but in the latest build of OF it is always
 > required. Is this the spec or a bug? I've tried explicitly setting
 > required to false() and constraint to true(), but this didn't work
 > either, so I'm assuming its a bug because of that.
 >
 > This can be seen in the Date example for the xforms-sandbox if you blank
 > the field and change the input.
 > --
 >
 > Ryan Puddephatt
 > Software Engineer
 >  > Teleflex Group - IT UK
 > 1 Michaelson Square
 > Livingston
 > West Lothian
 > Scotland
 > EH54 7DP
 >  > e> [hidden email] [hidden email]
 > t> +44(0)1506 407 110
 > f> +44(0)1506 407 108
 > w> www.teleflex.com <http://www.teleflex.com <http://www.teleflex.com/>>
 >
 > "Measuring programming progress by lines of code is like measuring
 > aircraft building progress by weight." - /Bill Gates/
 > "If you lie to the compiler, it will get its revenge." - /Henry Spencer/
 > "It's hard enough to find an error in your code when you're looking for
 > it; it's even harder when you've assumed your code is error-free." -
 > /Steve McConnell/
 > "If builders built buildings the way programmers wrote programs, then
 > the first woodpecker that came along would destroy civilization." -
 > /Gerald Weinberg/
 >


-- 
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

On 6/5/07, Ryan Puddephatt [hidden email] wrote:

     I had already tried that. I don't have a workaround for this, do I take
it there is currently no way to have an optional date input?

What about:

<xforms:bind constraint="'. = '' or . castable as xs:date"/>

Would this work?

Alex

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Ryan,

> Why are optional xs:dates not possible any more?

The fact that Orbeon Forms let them through before was a bug. The
XForms spec does not allow that behavior. This bug got fixed last week
as a consequence of doing other schema work.

> How long till xforms:date is introduced? Wouldn't it be better to
> wait until these are implemented before making xs:date type
> constrained.

All right, all right: I just implemented support for the built-in
XForms types :-)

http://forge.objectweb.org/tracker/index.php?func=detail&aid=307162&group_id=168&atid=350207

-Erik

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Erik,
    I see it was a bug fix, not a feature. I understand now. I'll get the latest OF and test it out.

Thanks for the speedy response, now I can release my app :-)

Ryan

Ryan Puddephatt
Software Engineer
 
Teleflex Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotland
EH54 7DP
 
e> [hidden email]
t> +44(0)1506 407 110
f> +44(0)1506 407 108
w> www.teleflex.com

"Measuring programming progress by lines of code is like measuring aircraft building progress by weight." - Bill Gates
"If you lie to the compiler, it will get its revenge." - Henry Spencer
"It's hard enough to find an error in your code when you're looking for it; it's even harder when you've assumed your code is error-free." - Steve McConnell
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." - Gerald Weinberg

Erik Bruchez wrote:

Ryan,

> Why are optional xs:dates not possible any more?

The fact that Orbeon Forms let them through before was a bug. The
XForms spec does not allow that behavior. This bug got fixed last week
as a consequence of doing other schema work.

> How long till xforms:date is introduced? Wouldn't it be better to
> wait until these are implemented before making xs:date type
> constrained.

All right, all right: I just implemented support for the built-in
XForms types :-)

http://forge.objectweb.org/tracker/index.php?func=detail&aid=307162&group_id=168&atid=350207

-Erik

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Ryan,

On 6/5/07, Ryan Puddephatt [hidden email] wrote:

     This would work, but it doesn't provide the date selector, adding
type="xs:date" brings back to problem. Why are optional xs:dates not
possible any more? How long till xforms:date is introduced? Wouldn't it be
better to wait until these are implemented before making xs:date type
constrained.

You are right. My "workaround" wasn't really one. But apparently your
wished have been heard and now we have an xforms:date!

Alex

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws