Home » Archived » XML Schema Definition (XSD) » NIST's XSD Test Suite
|
| Re: NIST's XSD Test Suite [message #3576 is a reply to message #3543] |
Tue, 22 October 2002 14:13   |
Eclipse User |
|
|
|
Not yet, but I'll see what I can do. 8-)
Note that the XSD Schema Infoset Model library is not a parser; i.e. if you want to parse instance documents and ensure that
they're schema-valid, you need something like Xerces. If, on the other hand, you want to manipulate the schema itself (either
it's file.xsd representation, or the abstract 'schema-ness' of it), then the library is what you want.
- Shane
On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas) wrote:
> Has anyone run the parser against all the xsd's from NIST's Test Suite?
> (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
>
> Thanks,
> dims
>
|
|
| |
| Re: NIST's XSD Test Suite [message #3674 is a reply to message #3576] |
Thu, 24 October 2002 09:22 |
| Eclipse User |
|
|
|
Originally posted by: dims.yahoo.com
Shane,
I understand...We want to be able to suck in an xsd using the library,
manipulate the contents using your API and then spit out the modified xsd.
Thanks,
dims
Shane Curcuru wrote:
> Not yet, but I\'ll see what I can do. 8-)
> Note that the XSD Schema Infoset Model library is not a parser; i.e. if you
want to parse instance documents and ensure that
> they\'re schema-valid, you need something like Xerces. If, on the other
hand, you want to manipulate the schema itself (either
> it\'s file.xsd representation, or the abstract \'schema-ness\' of it), then
the library is what you want.
> - Shane
> On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas)
wrote:
> > Has anyone run the parser against all the xsd\'s from NIST\'s Test Suite?
> > (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
> >
> > Thanks,
> > dims
> >
|
|
| |
| Re: NIST's XSD Test Suite [message #3735 is a reply to message #3576] |
Thu, 24 October 2002 09:29 |
| Eclipse User |
|
|
|
Originally posted by: dims.yahoo.com
Shane,
Here's the scenario:
#1: For each xsd in NIST's Test Suite do the following
#2: Load the Say Foo-In.XSD
#3: Generate the Foo-Out.XSD from the in-memory representation
#4: Use XMLUnit (http://sourceforge.net/projects/xmlunit) to check if
there are differences between Foo-In.XSD anf Foo-Out.XSD
This will make sure that "XSD Schema Infoset Model library" can
#1: supports the "XML Schema Part 2: Datatypes" spec.
#2: There's no loss of information in the load/save process.
This will be the best test harness possible for your library.
Thanks,
dims
Shane Curcuru wrote:
> Not yet, but I'll see what I can do. 8-)
> Note that the XSD Schema Infoset Model library is not a parser; i.e. if you
want to parse instance documents and ensure that
> they're schema-valid, you need something like Xerces. If, on the other
hand, you want to manipulate the schema itself (either
> it's file.xsd representation, or the abstract 'schema-ness' of it), then the
library is what you want.
> - Shane
> On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas)
wrote:
> > Has anyone run the parser against all the xsd's from NIST's Test Suite?
> > (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
> >
> > Thanks,
> > dims
> >
|
|
|
| Re: NIST's XSD Test Suite [message #4292 is a reply to message #3735] |
Thu, 24 October 2002 11:29 |
| Eclipse User |
|
|
|
Actually I have a modified copy of the org.apache.qetest harness (from xml-xalan) that already does this. I've been testing my
own set of schemas with a round-tripper already and the library handles a very wide variety quite nicely. I'm still booked on
other tasks so I haven't been able to run it on the NIST suite yet, but I'm betting that I've already covered the majority of
cases in there.
- Shane
On Thu, 24 Oct 2002 13:29:31 +0000 (UTC), dims@yahoo.com (Davanum Srinivas) wrote:
> Shane,
>
> Here's the scenario:
> #1: For each xsd in NIST's Test Suite do the following
> #2: Load the Say Foo-In.XSD
> #3: Generate the Foo-Out.XSD from the in-memory representation
> #4: Use XMLUnit (http://sourceforge.net/projects/xmlunit) to check if
> there are differences between Foo-In.XSD anf Foo-Out.XSD
>
> This will make sure that "XSD Schema Infoset Model library" can
> #1: supports the "XML Schema Part 2: Datatypes" spec.
> #2: There's no loss of information in the load/save process.
>
> This will be the best test harness possible for your library.
>
> Thanks,
> dims
>
> Shane Curcuru wrote:
>
> > Not yet, but I'll see what I can do. 8-)
>
> > Note that the XSD Schema Infoset Model library is not a parser; i.e. if you
> want to parse instance documents and ensure that
> > they're schema-valid, you need something like Xerces. If, on the other
> hand, you want to manipulate the schema itself (either
> > it's file.xsd representation, or the abstract 'schema-ness' of it), then the
> library is what you want.
>
> > - Shane
>
> > On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas)
> wrote:
> > > Has anyone run the parser against all the xsd's from NIST's Test Suite?
> > > (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
> > >
> > > Thanks,
> > > dims
> > >
>
>
>
>
>
>
|
|
|
| Re: NIST's XSD Test Suite [message #563200 is a reply to message #3543] |
Tue, 22 October 2002 14:13 |
| Eclipse User |
|
|
|
Not yet, but I'll see what I can do. 8-)
Note that the XSD Schema Infoset Model library is not a parser; i.e. if you want to parse instance documents and ensure that
they're schema-valid, you need something like Xerces. If, on the other hand, you want to manipulate the schema itself (either
it's file.xsd representation, or the abstract 'schema-ness' of it), then the library is what you want.
- Shane
On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas) wrote:
> Has anyone run the parser against all the xsd's from NIST's Test Suite?
> (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
>
> Thanks,
> dims
>
|
|
| |
| Re: NIST's XSD Test Suite [message #563276 is a reply to message #3576] |
Thu, 24 October 2002 09:22 |
| Eclipse User |
|
|
|
Shane,
I understand...We want to be able to suck in an xsd using the library,
manipulate the contents using your API and then spit out the modified xsd.
Thanks,
dims
Shane Curcuru wrote:
> Not yet, but I\'ll see what I can do. 8-)
> Note that the XSD Schema Infoset Model library is not a parser; i.e. if you
want to parse instance documents and ensure that
> they\'re schema-valid, you need something like Xerces. If, on the other
hand, you want to manipulate the schema itself (either
> it\'s file.xsd representation, or the abstract \'schema-ness\' of it), then
the library is what you want.
> - Shane
> On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas)
wrote:
> > Has anyone run the parser against all the xsd\'s from NIST\'s Test Suite?
> > (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
> >
> > Thanks,
> > dims
> >
|
|
| |
| Re: NIST's XSD Test Suite [message #563335 is a reply to message #3576] |
Thu, 24 October 2002 09:29 |
| Eclipse User |
|
|
|
Shane,
Here's the scenario:
#1: For each xsd in NIST's Test Suite do the following
#2: Load the Say Foo-In.XSD
#3: Generate the Foo-Out.XSD from the in-memory representation
#4: Use XMLUnit (http://sourceforge.net/projects/xmlunit) to check if
there are differences between Foo-In.XSD anf Foo-Out.XSD
This will make sure that "XSD Schema Infoset Model library" can
#1: supports the "XML Schema Part 2: Datatypes" spec.
#2: There's no loss of information in the load/save process.
This will be the best test harness possible for your library.
Thanks,
dims
Shane Curcuru wrote:
> Not yet, but I'll see what I can do. 8-)
> Note that the XSD Schema Infoset Model library is not a parser; i.e. if you
want to parse instance documents and ensure that
> they're schema-valid, you need something like Xerces. If, on the other
hand, you want to manipulate the schema itself (either
> it's file.xsd representation, or the abstract 'schema-ness' of it), then the
library is what you want.
> - Shane
> On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas)
wrote:
> > Has anyone run the parser against all the xsd's from NIST's Test Suite?
> > (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
> >
> > Thanks,
> > dims
> >
|
|
|
| Re: NIST's XSD Test Suite [message #563428 is a reply to message #3735] |
Thu, 24 October 2002 11:29 |
| Eclipse User |
|
|
|
Actually I have a modified copy of the org.apache.qetest harness (from xml-xalan) that already does this. I've been testing my
own set of schemas with a round-tripper already and the library handles a very wide variety quite nicely. I'm still booked on
other tasks so I haven't been able to run it on the NIST suite yet, but I'm betting that I've already covered the majority of
cases in there.
- Shane
On Thu, 24 Oct 2002 13:29:31 +0000 (UTC), dims@yahoo.com (Davanum Srinivas) wrote:
> Shane,
>
> Here's the scenario:
> #1: For each xsd in NIST's Test Suite do the following
> #2: Load the Say Foo-In.XSD
> #3: Generate the Foo-Out.XSD from the in-memory representation
> #4: Use XMLUnit (http://sourceforge.net/projects/xmlunit) to check if
> there are differences between Foo-In.XSD anf Foo-Out.XSD
>
> This will make sure that "XSD Schema Infoset Model library" can
> #1: supports the "XML Schema Part 2: Datatypes" spec.
> #2: There's no loss of information in the load/save process.
>
> This will be the best test harness possible for your library.
>
> Thanks,
> dims
>
> Shane Curcuru wrote:
>
> > Not yet, but I'll see what I can do. 8-)
>
> > Note that the XSD Schema Infoset Model library is not a parser; i.e. if you
> want to parse instance documents and ensure that
> > they're schema-valid, you need something like Xerces. If, on the other
> hand, you want to manipulate the schema itself (either
> > it's file.xsd representation, or the abstract 'schema-ness' of it), then the
> library is what you want.
>
> > - Shane
>
> > On Tue, 22 Oct 2002 16:20:24 +0000 (UTC), dims@yahoo.com (Davanum Srinivas)
> wrote:
> > > Has anyone run the parser against all the xsd's from NIST's Test Suite?
> > > (http://xw2k.sdct.itl.nist.gov/xml/page4.html)
> > >
> > > Thanks,
> > > dims
> > >
>
>
>
>
>
>
|
|
|
Goto Forum:
Current Time: Tue May 13 15:50:59 EDT 2025
Powered by FUDForum. Page generated in 0.04504 seconds |
Home