I have a need to validate my XML file prior to trying to create an instance of it. So, I took the latest schema files provided by w3c and make some tweaks so that it would accept syntax supported by Commons SCXML.
It currently passes validation for XML supported by Commons SCXML, but it may not be strict enough and may still pass validation for unsupported elements & syntax. I would be happy to post it to this mailing list if there are folks who could review and perhaps refine it. -Mike -----Original Message----- From: Rahul Akolkar [mailto:[email protected]] Sent: Thursday, February 04, 2010 3:30 PM To: Commons Users List Subject: Re: Which XSD file can I use to validate my SCXML before I try to use it? On Thu, Feb 4, 2010 at 6:15 PM, Michael McCarthy <[email protected]> wrote: > Hello, > > I am looking for a way to validate my SCXML document before I try to > instantiate a state machine from it using Commons SCXML. > > I have tried to use various versions of the XSD provided in the W3C > SCXML spec (including the latest version at: > http://www.w3.org/TR/scxml/) > > but I am finding discrepancies in that schema as compared to what > Commons SCXML supports. > > Could someone please point me to the definitive SCXML XSD profile that I > should be using to validate Commons SCXML documents? > <snip/> We don't have such an XSD ATM. It'd be good to have one ofcourse -- an interesting exercise if someone wants to come up with the XSD for the subset we support then I imagine it'd be easy to maintain going forward. -Rahul > > > Thank you for any help you can provide. > > Sincerely, > > > > Michael McCarthy, Director of Software Development > TouchCommerce > 30501 Agoura Road * Ste203 * Agoura Hills, CA 91301 > D 818.575.2141 * M 818.355.0996 * F 818.575.2105 > E [email protected] > www.touchcommerce.com <http://www.touchcommerce.com/> > > > > This communication, along with any attachments, may include confidential > TouchCommerce Inc. information. Any distribution or copying of this > material is strictly prohibited. If you are not the intended recipient > of this transmission, please contact the sender immediately. > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
