On Mon, Jan 24, 2011 at 4:49 PM, Justin Deoliveira <jdeol...@opengeo.org> wrote:
> On Mon, Jan 24, 2011 at 8:42 AM, Andrea Aime <andrea.a...@geo-solutions.it>
> wrote:
>>
>> On Mon, Jan 24, 2011 at 1:11 PM, Jody Garnett <jody.garn...@gmail.com>
>> wrote:
>> > This look a very well thought out and detailed proposal; you have
>> > answered a
>> > couple of my questions/confusions on IRC.
>> > So a big +1 for the proposal.
>> > A couple questions around the edges; how well does this play with:
>> > - SLDParser / Encoder (you do note that work is required)
>>
>> Very well
>>
>> > - Justin's recent SE work?
>>
>> Ugh, forgot about that one, still haven't played with SE at all.
>> So the answer is, not at all.
>> In the SLDParser the change needed was very small and localized,
>> not sure how an equivalent change would look like in the SE
>> parser
>>
> Is there an updated schema somewhere describing what the Transformation
> element looks like. If it is just a container for some Expressions we can
> probably just get away with modifying the FeatureTypeStyleBinding. Worst
> case it would involve a custom binding for the Transformation element.
> Either way should  not be much work.

The altered SLD 1.0 schema looks like:

<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:sequence>
    </xsd:complexType>
  </xsd:element>
  <xsd:element name="SemanticTypeIdentifier" type="xsd:string"/>
  <xsd:element name="Transformation" type="sld:TransformationType"/>
  <xsd:complexType name="TransformationType">
    <xsd:sequence>
      <xsd:element ref="ogc:Function"/>
    </xsd:sequence>
  </xsd:complexType>

Does this help?

Cheers
Andrea

-- 
Ing. Andrea Aime
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584962313
fax:     +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to