Thanks for confirming. Drat, wishing I had just tested validation of the existing SLD when I was copyediting.
Not being sure whether this is a GeoTools or GeoServer issue, where should I ticket this? Thanks, Mike Mike Pumphrey User Advocate | Boundless m...@boundlessgeo.com http://boundlessgeo.com @boundlessgeo On 4/1/2015 10:24 AM, Andrea Aime wrote: > On Wed, Apr 1, 2015 at 7:03 PM, Mike Pumphrey <m...@boundlessgeo.com> wrote: > >> Hi all. As part of the 2.7 release process I got to copyedit the new >> color-blending docs, but not actually go through the example. >> >> >> http://docs.geoserver.org/2.7.0/user/styling/sld-extensions/composite-blend/example.html >> >> I'm doing that now, and finding that the SLD as saved doesn't validate: >> >> http://docs.geoserver.org/2.7.0/user/_downloads/statesblend.sld >> >> Specifically, the errors seem to be regarding having >> FeatureTypeStyle-level VendorOptions. >> >> line 69: cvc-complex-type.2.4.a: Invalid content was found starting with >> element 'VendorOption'. One of '{"http://www.opengis.net/sld":Rule}' is >> expected. >> line 81: cvc-complex-type.2.4.a: Invalid content was found starting with >> element 'VendorOption'. One of '{"http://www.opengis.net/sld":Rule}' is >> expected. >> >> Is this user error, SLD error, or a bug? >> > > Sigh, every time we forget to add new elements to the SLD this comes up... > the file is valid, > but I evidently forgot to update the SLD schemas used to perform validation. > > And yet... just checked the schema, the VendorOption is there: > > <xsd:element name="FeatureTypeStyle"> > <xsd:annotation> > <xsd:documentation> > A FeatureTypeStyle contains styling information specific to one > feature type. This is the SLD level that separates the 'layer' > handling from the 'feature' handling. > </xsd:documentation> > </xsd:annotation> > <xsd:complexType> > <xsd:sequence> > <xsd:element ref="sld:Name" minOccurs="0"/> > <xsd:element ref="sld:Title" minOccurs="0"/> > <xsd:element ref="sld:Abstract" minOccurs="0"/> > <xsd:element ref="sld:FeatureTypeName" minOccurs="0"/> > <xsd:element ref="sld:SemanticTypeIdentifier" minOccurs="0" > maxOccurs="unbounded"/> > <xsd:element ref="sld:Transformation" minOccurs="0"/> > <xsd:element ref="sld:Rule" maxOccurs="unbounded"/> > <xsd:element ref="sld:VendorOption" minOccurs="0" > maxOccurs="unbounded" /> > </xsd:sequence> > </xsd:complexType> > </xsd:element> > > Not sure what's going on here, did we start using some other schema for > validation, > other than the ones in gt-xsd-sld?? > > Cheers > Andrea > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
