RE: [legalxml-courtfiling] ECF-3.0-CoreFilingMessage-Example.xml is not valid

["Graham, Gary" <GGraham@courts.az.gov>]

Thanks you Jim for your response. I also got responses from Rex McElrath and George Kneckt; thanks also to George and Rex..

 

George said:

 

 We were having similar issues, and abandoned actually validating because of it. We report this to the ECF committee at the NY meeting and were asked to provide specific examples. To date, we hadn't sent over specific examples.

 

Perhaps your example will get the issue on the table again.

 

And Rex made the following suggestions:

 

  I think it is the XML engine in use.  I tried the schema with OxygenXML and it validated.  Shane Durham had similar issues when using the Microsoft XML engine.  I couldn’t find the page for how to change them, but there is a download for the Altova XML/XSLT/XQuery engine that should become the default when installed at http://www.altova..com/download_components.html ..   An upgrade to version 3 also may set the parser to the Altova one by default as I believe they moved toward using it exclusively in the version 3 edition. 

 

I did some more experimenting and found this out:

 

            If you open XMLspy, then open the ECF-3.0-CoreFilingMessage-Example.xml file exported from the LegalXML ECF[3[1].01_Core_spec.zip, then XMLspy will tell you the file is not valid (it is well formed though).

 

However, if you then open the jxdm.xsd file from the …\xsd\constraint\jxdm\3.0.3\ folder, and revalidate using XMLspy, now the Example CoreFiling xml file is valid. I can’t explain why this works just yet, or why the xml is not valid when the jxdm.xsd is not open, but I thought I would let everyone know that there is a solution/work around.

 

Thanks again for the responses

 

Gary Graham

 

 

-----Original Message-----
From: Cabral, James E. [mailto:JCabral@mtgmc.com]
Sent: Wednesday, June 06, 2007 5:54 PM
To: Graham, Gary; legalxml-courtfiling@lists.oasis-open.org
Subject: RE: [legalxml-courtfiling] ECF-3.0-CoreFilingMessage-Example.xml is not valid

 

Gary,

 

It validates on my system.  I suggest:

 

1.       It is possible that one of the files on your system was changed and there several interdependencies to check. I would re-download the specification from http://www.oasis-open.org/apps/org/workgroup/legalxml-courtfiling/download.php/21069/ECF_v_3.01_Core_Spec.zip and try to validate again.

2.       There may be an issue with that particular version of XMLSpy.  I am using XMLSpy 2007 sp3 without a problem.

 

jim

 

From: Graham, Gary [mailto:GGraham@courts.az.gov]
Sent: Wednesday, June 06, 2007 2:39 PM
To: legalxml-courtfiling@lists.oasis-open.org
Subject: [legalxml-courtfiling] ECF-3.0-CoreFilingMessage-Example.xml is not valid

 

I am using XMLspy (version 2006 sp2) to look at the ECF-3.0-CourtFilingMessage-Example.xml included in the ECF_3[1].01_Core_Spec.zip

 

XMLspy says “This file is not valid: The base type “j:TextType” of complex type ‘common:PolicyDefinedCodeTextType’ (simpleContent, extension) must be a simple type.

 

Can anyone telling why I am getting this error and what must be done to correct it?

 

 

Gary Graham

Arizona Supreme Court