Re: zogi - birthDate attribute of Contact

On Mon, 2008-06-09 at 01:30 +0200, Helge Hess wrote:
> On 08.06.2008, at 16:01, Adam Tauno Williams wrote:
> > I may just have to adopt the same solution - making 1001-01-01  
> > indicate no-value-defined.
> This sounds really ugly,

It is.  

> I almost like the empty <string> solution better.

With .NET 2.0 there is a nullable DateTime type - you use "DateTime?
dateTime" as the declaration in place of "DateTime dateTime".  I'm
willing to use this for the .NET binding; the result of which is
dropping .NET 1.1 support. I'm OK with that since I'm pretty sure I've
broken .NET 1.1 support in other ways already.

I'm pretty sure Python supports </nil>.  At least some Java binding
support it as well.  But using nil would probably freeze out user's of
'oddball' languages or bindings.

I'm also pretty sure SOPE doesn't support null/nil in coding; a nil
isn't a string/date/etc.. in Obj-C, it is just null. (?)  And correctly
coding null/nil still requires a type.

Empty string is slightly cleaner IMO,  but using 1001-01-01 puts the
value or null coding burden on the server side (where it will at least
be consisten);  there is no potential to crash a client side binding.
The downside is the possibility of a weird value appearing in a UI that
doesn't catch the special value.

-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc