On 8/29/07, Christian Floerkemeier <[EMAIL PROTECTED]> wrote: > Are you leaving this kind of constraint checking to the "application level"?
Yes. If we wanted it in llrpdef.xml we would have to provide some support for integer ranges within the specified field type (u8, s8, u16...). It certainly can be modelled at the llrp.xsd level, but without that information modelled in llrpdef.xml, I can't autogenerate that. It would have to be done by hand. How to model it in llrpdef.xml? Probably an attribute with a list of permitted ranges, since you need to deal with gaps: "0,1,3..7,9-1000" I think that would be useful for automating regression "boundary value" checks. As an attribute it would be easy to ignore, and might help some implementers, so if someone contributed a comprehensive patch to llrpdef.xsd and llrpdef.xml I would welcome it. A whole other level is things like "if field A has value x then value y is disallowed in field B". I definitely don't think we want to go that far. -- John. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
