Decided to ticket this issue in GeoServer land. Please move as appropriate:
https://osgeo-org.atlassian.net/browse/GEOS-6971 Thanks, Mike Mike Pumphrey User Advocate | Boundless [email protected] http://boundlessgeo.com @boundlessgeo On 4/1/2015 1:32 PM, Mike Pumphrey wrote: > 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 > [email protected] > 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 <[email protected]> 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 >> > ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
