On Thu, Jan 14, 2010 at 11:10 AM, Paul Dietrich <[email protected]> wrote: > Just a quick note. This has the largest impact on LTK Perl since it uses > LTK-XML DOM as its native objects, but would also affect LTKJava and LTKNET > >
Applications have canned LTK-XML messages that do not call out the new fields. They would need to be fixed for compatibility with the new schema. Which would make sense... I don't think you want applications that are using LTK-Perl loaded against the new schema to be able to pretend that they are not broken. The values of all valid fields need to be specified. Hmm... it has been a while since I've used it. If there isn't such a feature already, we could make demand for a given field in XML messages optional in the case that a default value is given for it is in the schema. It might cause some parse-ability issue though. But if it could be made to work, all bits previously reserved could be given a default value of zero. This would mean you could make it so old apps wouldn't break. That's from the point of view of Encode/Decode functions. W3C XML Schema validations would of course still fail to validate against mismatched schema versions. -- John. ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
