Mark Nottingham wrote: > > On 04/07/2005, at 6:18 PM, Thomas Broyer wrote: > >> Really good work! > > > Thanks! > > > >> Why not using an xs:boolean for fh:stateful? hence allowing values 0, >> 1, true and false. > > > I did it this way because I'm not a huge XML Schema fan :) > > At this point, stateful is effectively xs:boolean with a constraint on > the lexical space. I'm not against changing it to '"1" or "true" / "0" > or "false", except that this makes the spec more verbose (but that's a > pretty minor concern, properly managed). What do others think (in either > direction)?
1. I don't want to have to link to an XSD library in my XML toolchain just to process true/false in an attribute. 2. I don't want to hack some code together to recognize a single XSD primitive just because I don't want to link to an XSD library. cheers Bill
