[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Request for XSLT2.0 / XML Schema triples

---

---

I'll try and dig out a few examples for you. Most of my test cases have
either an input schema or an output schema but not both, and others are
proprietary to clients, so I don't actually have all that much material.

Do you assume there are no templates applied to temporary trees? One of the
difficulties in doing this kind of analysis is that a template rule with
match="E" is not necessarily matching an element that conforms to the
definition of E in the input schema. Similarly a template that constructs an
element E might be writing it to a temporary tree rather than to the final
output tree. Of course if you are only after an approximate verdict you can
afford the luxury of making guesses on such things. 

Michael Kay
http://www.saxonica.com/

> -----Original Message-----
> From: Soren Kuula [mailto:dongfang@xxxxxxxxxxx] 
> Sent: 28 November 2005 22:59
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] Request for XSLT2.0 / XML Schema triples
> 
> Hi,
> 
> I'm working on a static analysis program (thesis!) that will take a 
> _triple_ of
> 
> - an input schema (DTD og XML Schema)
> - an otuput schema (DTD og XML Schema)
> - an XSL stylesheet
> 
> -- and then return a conservatively approximate verdict whether
>    - given input documents that are valid by the input 
> schema, will the 
> transform always output docuements that are valid by the 
> output schema?
> 
> Previous experiments with DTD and XSLT1.0 only revealed that this 
> analysis is feasible with good accuracy.
> 
> Now, I'm feverishly looking for real-life triples of XSD 
> schema and XSLT 
> 1 or 2 transforms that I can test run my analyzer on.
> 
> Do any of you guys know some examples? That is, I need names of 
> publically available (of available upon request) schema and XSL 
> transforms, such that I have a schema specifying the input of the 
> transform, and a schema specifying the (expected) output of the 
> transform. Same schema input and output is OK, too. DTD on 
> one side is 
> OK, too. XSLT2.0 transforms that make use of XSD specific stuff are 
> particularly interesting.
> 
> If I can get it all finished in time (or if anyone is particularly 
> interested) I can make the analyzer available online.
> 
> Thanks for any suggestions.
> 
> Soren

---