[wfs-dev] GML 2.1.2 and XMLSpy
Bart van den Eijnden (OSGIS)
bartvde at osgis.nl
Wed Oct 25 09:15:59 EDT 2006
Hi Jørgen,
could you post your changes to the list, or offer the changed schemas as a
download? Thanks in advance.
I agree with Simon though that we should find a way to make this into a
change request, so that not everybody needs to patch their own set of
schemas.
Best regards,
Bart
--
Bart van den Eijnden
OSGIS, Open Source GIS
http://www.osgis.nl
--------- Oorspronkelijk bericht --------
Van: Münster-Swendsen, Jørgen <jrm at kms.dk>
Naar: wfs-dev at opengeospatial.org <wfs-dev at opengeospatial.org>
Onderwerp: Re: [wfs-dev] GML 2.1.2 and XMLSpy
Datum: 25/10/06 10:08
> I fully agree with Bart van den Eijnden, OSGIS, Open Source GIS.
>
> I have been forced to make modifications to geometry.xsd (or rather modify
other schemas including geometry.xsd) in order to be able to validate XML
documents.
>
> Regards
>
> Jørgen Münster-Swendsen
> Miljøministeriet / Ministry of the environment
> Kort & Matrikelstyrelsen / National Survey and Cadastre - Denmark
>
> -----Oprindelig meddelelse-----
> Fra: wfs-dev-bounces+jrm=kms.dk at opengeospatial.org
[mailto:wfs-dev-bounces+jrm=kms.dk at opengeospatial.org] På vegne af Bart van
den Eijnden (OSGIS)
> Sendt: 25. oktober 2006 11:18
> Til: Simon.Cox at csiro.au; bartvde at osgis.nl; wfs-dev at opengeospatial.org
> Emne: Re: [wfs-dev] GML 2.1.2 and XMLSpy
>
> It's really strange IMHO that there are no plans to bugfix GML 2.
>
> It is still widely used (WFS 1.0 should be the most out there currently),
> and is also used in specs like Web Map Context.
>
> How can you work with these standards if the XML cannot be validated ....
?
> One cannot expect everybody (and all the specs linking to GML) to move to
> GML 3 ....
>
> Best regards,
> Bart
>
> --
> Bart van den Eijnden
> OSGIS, Open Source GIS
> http://www.osgis.nl
>
>
> --------- Oorspronkelijk bericht --------
> Van: Simon.Cox at csiro.au
> Naar: bartvde at osgis.nl <bartvde at osgis.nl>,
wfs-dev at opengeospatial.org
> <wfs-dev at opengeospatial.org>
> Onderwerp: RE: [wfs-dev] GML 2.1.2 and XMLSpy
> Datum: 25/10/06 06:50
>
> > There are various schema validation issues with all versions of GML
> > prior to 3.1.1.
> > This was consistent with industry norms for schemas of this level of
> > complexity,
> > since XML processing technology was immature at the time of
development.
> >
> > Only in the last couple of years have they all started to agree - in
the
> > case of Xerces C++ only in the past couple of months!
> >
> > GML3 was adopted by OGC in January 2003 and there are no plans to
bugfix
> > GML2.
> >
> > Simon Cox
> >
> > -----Original Message-----
> > From: wfs-dev-bounces+simon.cox=csiro.au at opengeospatial.org
> > [mailto:wfs-dev-bounces+simon.cox=csiro.au at opengeospatial.org] On
Behalf
> > Of Bart van den Eijnden (OSGIS)
> > Sent: Saturday, 21 October 2006 3:30 AM
> > To: wfs-dev at opengeospatial.org
> > Subject: [wfs-dev] GML 2.1.2 and XMLSpy
> >
> > Hi list,
> >
> > when trying to validate WMC 1.0 documents with Altova XMLSpy I always
> > run into the following error in geometry.xsd from GML 2.1.2:
> >
> > File
> > D:svnmapbuildermapbuildermapbuilderdemodatacontextatlasWorld.xml
> >
> > could not be validated because of an error in XML Schema/DTD (see
below)
> > File http://schemas.opengis.net/gml/2.1.2/geometry.xsd is not
valid.
> > Type 'gml:MultiPolygonType' is not a valid restriction of
type
> > 'gml:GeometryCollectionType'.
> > Error location: schema / complexType / complexContent /
> > restriction / @base
> > Details
> > rcase-NameAndTypeOK.1: Element &lt;element
> > ref='gml:polygonMember'&gt; did not match name and target
namespace of the
>
> > respective base particle's term. (see below)
> > Name mismatch: restriction &lt;element
> > ref='gml:polygonMember'&gt;, base particle (minOccurs=1,
maxOccurs=1) with
>
> > term gml:geometryMember.
> > Name mismatch: restriction &lt;element
> > ref='gml:polygonMember'&gt;, base particle (minOccurs=1,
maxOccurs=1) with
>
> > term gml:pointMember.
> > range-ok.2.2: The restriction's 'maxOccurs' value
> > 'unbounded' must be less than or equal to '1'.
> > rcase-NameAndTypeOK.2: &lt;element
> ref='gml:polygonMember'&gt;
> >
> > occurrence range is not a valid restriction of particle (minOccurs=1,
> > maxOccurs=1) with term gml:polygonMember occurrence range.
> > rcase-NameAndTypeOK.1: The declarations' {name}s and
> > {target namespace}s are not the same: restriction element is
&lt;element
> > ref='gml:polygonMember'&gt; and base element is particle
(minOccurs=1,
> > maxOccurs=1) with term gml:lineStringMember.
> > rcase-RecurseLax.2: There is no complete
> > order-preserving functional mapping from the particles of particle
> > (minOccurs=1, maxOccurs=1) with term &lt;choice&gt; to the
particles of
> > particle (minOccurs=1, maxOccurs=unbounded) with term
&lt;choice&gt;.
> > rcase-RecurseAsIfGroup: &lt;element
> > ref='gml:polygonMember'&gt; is not a valid restriction of model
group
> > particle particle (minOccurs=1, maxOccurs=unbounded) with term
> &lt;choice&gt;.
> > cos-particle-restrict.2.1: Substitution group of
element
> >
> > &lt;element ref='gml:geometryMember'&gt; was expanded to a
choice model
> group.
> >
> > (see below)
> > 'gml:geometryMember'
> > 'gml:pointMember'
> > 'gml:polygonMember'
> > 'gml:lineStringMember'
> > rcase-NameAndTypeOK.1: Element &lt;element
> > ref='gml:Polygon'&gt; did not match name and target namespace of
the
> > respective base particle's term. (see below)
> > Name mismatch: restriction &lt;element
> > ref='gml:Polygon'&gt;, base particle (minOccurs=1, maxOccurs=1)
with term
> > gml:MultiPolygon.
> > Name mismatch: restriction &lt;element
> > ref='gml:Polygon'&gt;, base particle (minOccurs=1, maxOccurs=1)
with term
> > gml:LinearRing.
> > Name mismatch: restriction &lt;element
> > ref='gml:Polygon'&gt;, base particle (minOccurs=1, maxOccurs=1)
with term
> > gml:MultiPoint.
> > Name mismatch: restriction &lt;element
> > ref='gml:Polygon'&gt;, base particle (minOccurs=1, maxOccurs=1)
with term
> > gml:MultiGeometry.
> > Name mismatch: restriction &lt;element
> > ref='gml:Polygon'&gt;, base particle (minOccurs=1, maxOccurs=1)
with term
> > gml:MultiLineString.
> > Name mismatch: restriction &lt;element
> > ref='gml:Polygon'&gt;, base particle (minOccurs=1, maxOccurs=1)
with term
> > gml:LineString.
> > Name mismatch: restriction &lt;element
> > ref='gml:Polygon'&gt;, base particle (minOccurs=1, maxOccurs=1)
with term
> > gml:Point.
> > rcase-Recurse.2.2: Mandatory particle (minOccurs=1,
> > maxOccurs=unbounded) with term &lt;choice&gt; is missing in
the
> &lt;sequence&gt;.
> > derivation-ok-restriction.5.4: The content type
> > &lt;sequence&gt; is not a valid restriction of content type
> &lt;sequence&gt;.
> >
> > Is there a solution to this?
> >
> > Thanks in advance.
> >
> > Best regards,
> > Bart
> >
> > --
> > Bart van den Eijnden
> > OSGIS, Open Source GIS
> > bartvde at osgis.nl
> > http://www.osgis.nl
> >
> > _______________________________________________
> > wfs-dev mailing list
> > wfs-dev at opengeospatial.org
> > https://mail.opengeospatial.org/mailman/listinfo/wfs-dev
> >
> >
> >
>
>
>
> _______________________________________________
> wfs-dev mailing list
> wfs-dev at opengeospatial.org
> https://mail.opengeospatial.org/mailman/listinfo/wfs-dev
>
>
>
>
> _______________________________________________
> wfs-dev mailing list
> wfs-dev at opengeospatial.org
> https://mail.opengeospatial.org/mailman/listinfo/wfs-dev
>
>
More information about the wfs-dev
mailing list