simple-xspec-wrapper 0.1.0-java

data/vendor/xspec-1.0.0/tutorial/escape-for-regex.xslt

@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    xmlns:functx="http://www.functx.com" xmlns:xs="http://www.w3.org/2001/XMLSchema"
+    exclude-result-prefixes="xs" version="2.0">
+
+    <!-- The functx:escape-for-regex function escapes a string that you wish to be taken 
+         literally rather than treated like a regular expression. This is useful when, 
+         for example, you are calling the built-in fn:replace function and you want any 
+         periods or parentheses to be treated like literal characters rather than regex 
+         special characters. 
+         From: http://www.xsltfunctions.com/xsl/functx_escape-for-regex.html
+    -->
+    <xsl:function name="functx:escape-for-regex" as="xs:string">
+        <xsl:param name="arg" as="xs:string?"/>
+
+        <xsl:sequence
+            select=" 
+            replace($arg,
+            '(\.|\[|\]|\\|\||\-|\^|\$|\?|\*|\+|\{|\}|\(|\))','\\$1')
+            "
+        />
+    </xsl:function>
+
+
+    <!-- Escape regexes in a list of phrases -->
+
+    <xsl:template match="phrases">
+        <phrases>
+            <xsl:apply-templates select="phrase"/>
+        </phrases>
+    </xsl:template>
+
+    <xsl:template match="phrase">
+        <xsl:variable name="escaped-text" select="functx:escape-for-regex(.)"/>
+        <phrase status="{if (. = $escaped-text) then 'changed' else 'same'}">
+            <xsl:value-of select="functx:escape-for-regex(.)"/>
+        </phrase>
+    </xsl:template>
+
+</xsl:stylesheet>

data/vendor/xspec-1.0.0/tutorial/escape-for-regex.xspec

@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" xmlns:functx="http://www.functx.com" stylesheet="escape-for-regex.xslt">
+  <!--
+       This is a sample test suite written in the XSpec language.  It
+       tests the stylesheet escape-for-regex.xslt.  It contains three
+       main scenarios (the second of which in turn contains two sub-
+       scenarios).
+       
+       See https://github.com/xspec/xspec/wiki/Getting-Started for the
+       full tutorial it is part of.
+   -->
+  <!--
+       This is a very simple scenario, checking the return value of a
+       function call (the param does not contain any character to be
+       escaped).
+   -->
+  <x:scenario label="No escaping">
+    <!-- call the function with the string 'Hello' -->
+    <x:call function="functx:escape-for-regex">
+      <x:param select="'Hello'"/>
+    </x:call>
+    <!-- check the result -->
+    <x:expect label="Must not be escaped at all" select="'Hello'"/>
+  </x:scenario>
+  <!--
+       This scenario demonstrates:
+       (1) how to test a function (named templates can be simliarly tested)
+       (2) that scenarios can be nested
+       (3) a test can have multiple expectations.
+   -->
+  <x:scenario label="Test simple patterns">
+    <!-- first sub-scenario -->
+    <x:scenario label="When encountering parentheses">
+      <!-- call the function -->
+      <x:call function="functx:escape-for-regex">
+        <x:param name="arg" select="'(Hello)'"/>
+      </x:call>
+      <!-- check the result -->
+      <x:expect label="escape them." select="'\(Hello\)'"/>
+    </x:scenario>
+    <!-- second sub-scenario -->
+    <x:scenario label="When encountering a whitespace character class">
+      <!-- call the function with another parameter -->
+      <x:call function="functx:escape-for-regex">
+        <x:param name="arg" select="'\sHello'"/>
+      </x:call>
+      <!-- check the result -->
+      <x:expect label="escape the backslash" select="'\\sHello'"/>
+      <!-- we can have several checks on the same result -->
+      <x:expect label="result should have one more character than source" test="string-length(.) = 8"/>
+    </x:scenario>
+  </x:scenario>
+  <!--
+       This scenario demonstrates how to test a matching template.
+   -->
+  <x:scenario label="When processing a list of phrases">
+    <!-- apply template rules to this element -->
+    <x:context>
+      <phrases>
+        <phrase>Hello!</phrase>
+        <phrase>Goodbye!</phrase>
+        <phrase>(So long!)</phrase>
+      </phrases>
+    </x:context>
+    <!-- check the result -->
+    <x:expect label="All phrase elements should remain" test="count(phrases/phrase) = 3"/>
+    <x:expect label="Strings should be escaped and status attributes should be added">
+      <phrases>
+        <phrase status="same">Hello!</phrase>
+        <phrase status="same">Goodbye!</phrase>
+        <phrase status="changed">\(So long!\)</phrase>
+      </phrases>
+    </x:expect>
+  </x:scenario>
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-01.sch

@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2">
+    
+    <sch:pattern>
+        <sch:rule context="article">
+            <sch:assert test="title" id="a001">
+                article should have a title
+            </sch:assert>
+        </sch:rule>
+        <sch:rule context="section">
+            <sch:assert test="title" id="a002">
+                section should have a title
+            </sch:assert>
+        </sch:rule>
+    </sch:pattern>
+    
+</sch:schema>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-01.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<article>
+  <title>Example</title>
+  <section>
+    <title>Introduction</title>
+    <p>This is an example.</p>
+  </section>
+  <section>
+    <p>This is an example.</p>
+  </section>
+</article>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-01.xspec

@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-model href="../../src/schemas/xspec.rnc" type="application/relax-ng-compact-syntax"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" schematron="demo-01.sch">
+    <x:scenario label="demo-01">
+        <x:context href="demo-01.xml"/>
+        <x:scenario label="article should have a title">
+            <x:expect-not-assert id="a001"/>
+        </x:scenario>
+        <x:scenario label="section should have a title">
+            <x:expect-not-assert id="a002" location="/article[1]/section[1]"/>
+            <x:expect-assert id="a002" location="/article[1]/section[2]"/>
+        </x:scenario>
+    </x:scenario>
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-02-PhaseA.xspec

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-model href="../../src/schemas/xspec.rnc" type="application/relax-ng-compact-syntax"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" schematron="demo-02.sch">
+    <x:param name="phase">PhaseA</x:param>
+    <x:scenario label="Pattern 1">
+        <x:context href="demo-02.xml"/>
+        <x:expect-assert id="t1-1" role="warn"/>
+        <x:expect-not-assert id="t2-1"/>
+    </x:scenario>
+    <x:import href="demo-02-import1.xspec"/>
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-02-PhaseB.xspec

@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-model href="../../src/schemas/xspec.rnc" type="application/relax-ng-compact-syntax"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" schematron="demo-02.sch">
+    <x:param name="phase">PhaseB</x:param>
+    <x:scenario label="Pattern 2">
+        <x:context href="demo-02.xml"/>
+        <x:expect-assert id="t2-1" role="error"/>
+        <x:expect-not-assert id="t1-1"/>
+    </x:scenario>
+    <x:import href="demo-02-import1.xspec"/>
+    <x:import href="demo-02-import3.xspec"/>
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-02-import1.xspec

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-model href="../../src/schemas/xspec.rnc" type="application/relax-ng-compact-syntax"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" schematron="demo-02.sch">
+    <x:scenario label="Pattern 3 - Shared">
+        <x:context href="demo-02.xml"/>
+        <x:expect-assert id="t3-1"/>
+    </x:scenario>
+    <x:import href="demo-02-import2.xspec"/>
+</x:description>
+    

data/vendor/xspec-1.0.0/tutorial/schematron/demo-02-import2.xspec

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-model href="../../src/schemas/xspec.rnc" type="application/relax-ng-compact-syntax"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" schematron="demo-02.sch">
+    <x:scenario label="Pattern 4 - example of a second level of imported scenarios">
+        <x:context href="demo-02.xml"/>
+        <x:expect-report id="t4-1" role="warn"/>
+    </x:scenario>
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-02-import3.xspec

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" xmlns:local="local"> 
+    <x:scenario label="XSpec function scenario imported">
+        <x:call function="local:add">
+            <x:param name="a" select="5" as="xs:integer"/>
+            <x:param name="b" select="2" as="xs:integer"/>
+        </x:call>
+        <x:expect label="add 5 + 2" select="xs:integer(7)"/>
+    </x:scenario>
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-02.sch

@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron"
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    queryBinding="xslt2">
+    
+    <sch:ns uri="local" prefix="local"/>
+    
+    <xsl:function name="local:add" as="xs:integer"> 
+        <xsl:param name="a" as="xs:integer"/>
+        <xsl:param name="b" as="xs:integer"/>
+        <xsl:value-of select="$a + $b"/>
+    </xsl:function>
+    
+    <sch:phase id="PhaseA">
+        <sch:active pattern="Pattern1"/>
+        <sch:active pattern="Pattern3"/>
+        <sch:active pattern="Pattern4"/>
+    </sch:phase>
+    
+    <sch:phase id="PhaseB">
+        <sch:active pattern="Pattern2"/>
+        <sch:active pattern="Pattern3"/>
+        <sch:active pattern="Pattern4"/>
+    </sch:phase>
+    
+    <sch:pattern id="Pattern1">
+        <sch:rule context="sec">
+            <sch:assert test="@sec-type" id="t1-1" role="warn">
+                sec element should have a sec-type attribute.
+            </sch:assert>
+        </sch:rule>
+    </sch:pattern>
+    
+    <sch:pattern id="Pattern2">
+        <sch:rule context="sec">
+            <sch:assert test="@sec-type" id="t2-1" role="error">
+                sec element should have a sec-type attribute.
+            </sch:assert>
+        </sch:rule>
+    </sch:pattern>
+    
+    <sch:pattern id="Pattern3">
+        <sch:rule context="sec">
+            <sch:assert test="title" id="t3-1">
+                section should have a title
+            </sch:assert>
+        </sch:rule>
+    </sch:pattern>
+    
+    <sch:pattern id="Pattern4">
+        <sch:rule context="sec">
+            <sch:report test="count(p) = 1" id="t4-1" role="warn">
+                Short section has only one paragraph.
+            </sch:report>
+        </sch:rule>
+    </sch:pattern>
+    
+</sch:schema>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-02.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<article>
+    <article-title>Demo 2</article-title>
+    <body>
+        <sec sec-type="introduction">
+            <title>Welcome!</title>
+            <p>Schematron is a wonderful tool for testing XML to find out if the XML follows an expected structure.</p>
+            <p>In addition to validating XML, Schematron can also raise alerts for things you might want to know through warnings and informational messages. It can pass/fail validation and much more!</p>
+        </sec>
+        <sec>
+            <p>Schematron uses XPath to test the contents of XML.</p>
+        </sec>
+        <sec sec-type="testing">
+            <title>Testing Schematron</title>
+            <p>While Schematron is useful for testing XML files, it is also useful to have a tool for testing Schematron itself.</p>
+            <p>Schematron is simple to use. However sometimes tests can sometimes become very complex. A good set of test cases can help you to avoid problems and makes your work go faster.</p>
+        </sec>
+    </body>
+</article>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-03-doc1.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+    <section>
+        <title>Introduction</title>
+    </section>
+</document>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-03-doc2.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+    <section>
+        <title>INTRODUCTION</title>
+        <p>Some text</p>
+    </section>
+</document>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-03.sch

@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2">
+    
+    <sch:pattern>
+        
+        <sch:rule context="title">
+            <sch:assert test="following-sibling::p" id="a0001">
+                title should be followed by a paragraph
+            </sch:assert>
+            <sch:assert test="string() ne upper-case(string())" role="warn" id="a0002">
+                title should not be all upper case
+            </sch:assert>
+        </sch:rule>
+        
+        <sch:rule context="p">
+            <sch:report test="string-length() lt 10" id="a0003" role="warn">
+                paragraph is less than 10 characters long
+            </sch:report>
+        </sch:rule>
+        
+        <sch:rule context="document" role="info" id="a0004">
+            <sch:report test="section" role="info">
+                the document has at least one section
+            </sch:report>
+        </sch:rule>
+        
+    </sch:pattern>
+    
+</sch:schema>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-03.xspec

@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-model href="../../src/schemas/xspec.rnc" type="application/relax-ng-compact-syntax"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" schematron="demo-03.sch">
+
+    <x:scenario label="demo 3">
+
+        <x:scenario label="inline context">
+            <x:scenario label="valid">
+                <x:context>
+                    <document>
+                        <title>Introduction</title>
+                        <p>some paragraph text</p>
+                    </document>
+                </x:context>
+                <x:expect-not-assert id="a0001"/>
+                <x:expect-valid/>
+            </x:scenario>
+            <x:scenario label="not valid">
+                <x:context>
+                    <document>
+                        <title>Introduction</title>
+                    </document>
+                </x:context>
+                <x:expect-assert id="a0001"/>
+            </x:scenario>
+            <x:scenario label="valid with warning">
+                <x:context>
+                    <document>
+                        <title>Introduction</title>
+                        <p>Hello!</p>
+                    </document>
+                </x:context>
+                <x:expect-valid/>
+                <x:expect-report id="a0003"/>
+            </x:scenario>
+        </x:scenario>
+
+        <x:scenario label="file as context">
+            <x:scenario label="valid file with warning">
+                <x:context href="demo-03-doc2.xml"/>
+                <x:expect-valid/>
+                <x:expect-assert id="a0002" role="warn"/>
+                <x:expect-report id="a0003" role="warn"/>
+            </x:scenario>
+            <x:scenario label="not valid file">
+                <x:context href="demo-03-doc1.xml"/>
+                <x:expect-assert id="a0001"/>
+            </x:scenario>
+        </x:scenario>
+
+        <x:scenario label="example" pending="tests marked as pending are not executed">
+            <x:context href="demo-03-doc1.xml"/>
+            <x:expect-valid/>
+        </x:scenario>
+        
+        <x:scenario label="id or role can be placed on on the rule">
+            <x:context href="demo-03-doc1.xml"/>
+            <x:expect-report id="a0004" role="info"/>
+        </x:scenario>
+
+    </x:scenario>
+
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-04.sch

@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2">
+    
+    <sch:ns uri="http://example.com/ns1" prefix="ex1"/>
+    <sch:ns uri="http://example.com/ns2" prefix="ex2"/>
+    <sch:ns uri="http://example.com/ns3" prefix="ex3"/>
+    
+    <sch:pattern>
+        <sch:rule context="ex1:article">
+            <sch:assert test="ex2:title">article should have a title</sch:assert>
+        </sch:rule>
+        <sch:rule context="ex3:sec">
+            <sch:assert test="ex2:para">sec should have at least one para</sch:assert>
+        </sch:rule>
+        <sch:rule context="figure">
+            <sch:assert test="caption">figure should have a caption</sch:assert>
+        </sch:rule>
+    </sch:pattern>
+    
+</sch:schema>

data/vendor/xspec-1.0.0/tutorial/schematron/demo-04.xspec

@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-model href="../../src/schemas/xspec.rnc" type="application/relax-ng-compact-syntax"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" schematron="demo-04.sch"
+    xmlns:ex1="http://example.com/ns1" xmlns:ex2="http://example.com/ns2" xmlns:ex3="http://example.com/ns3">
+    
+    <x:scenario label="demo 4">
+        <x:scenario label="XPath location with namespaces">
+            <x:context>
+                <ex1:article>
+                    <ex3:sec>
+                        <ex2:para>paragraph 1</ex2:para>
+                    </ex3:sec>
+                    <ex3:sec ex2:type="3">
+                        <figure><img src="example.png"/></figure>
+                    </ex3:sec>
+                </ex1:article>
+            </x:context>
+            <x:scenario label="using oXygen's Copy XPath">
+                <x:expect-assert location="/ex1:article[1]"/>
+                <x:expect-assert location="/ex1:article[1]/ex3:sec[2]"/>
+                <x:expect-assert location="/ex1:article[1]/ex3:sec[2]/figure[1]"/>
+            </x:scenario>
+            <x:scenario label="using XPath without [1] or leading /">
+                <x:expect-assert location="ex1:article"/>
+                <x:expect-assert location="ex1:article/ex3:sec[2]"/>
+                <x:expect-assert location="ex1:article/ex3:sec[2]/figure"/>
+            </x:scenario>
+            <x:scenario label="expecting no assert should fail">
+                <x:expect-not-assert location="ex1:article"/>
+            </x:scenario>
+        </x:scenario>
+    </x:scenario>
+</x:description>

data/vendor/xspec-1.0.0/tutorial/schematron/quickfix.sch

@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2"
+    xmlns:sqf="http://www.schematron-quickfix.com/validator/process" defaultPhase="check-id">
+    
+    <sch:ns uri="http://purl.oclc.org/dsdl/schematron" prefix="sch"/>
+    
+    <sch:p>
+        This Schematron Quick Fix is intended to help with adding id and role attributes to assert and report elements in a Schematron.
+        
+        To use this quick fix create a validation scenario in oXygen that uses this Schematron. 
+        The validation scenario configuration might look something like this:
+        
+        <![CDATA[
+            file to validate    File type           Validation engine   Auto    Schema                 Phase
+            ${currentFileURL}   Schematron Document Default engine      Yes
+            ${currentFileURL}   XML Document        Default engine      Yes     /path/to/quickfix.sch  #ALL
+        ]]>
+        
+        Apply the validation scenario to validate any Schematron. 
+        
+        Using the check-id phase,
+        each assert or report element that is missing an id attribute will be flagged.
+        Click on each flagged element and use the quick fix to insert an id attribute. 
+        The generated ID will be based on a running number and will use the nearest ancestor ID if there is one.
+        
+        Using the check-role phase,
+        each assert or report element that is missing a role attribute will be flagged.
+        Click on each flagged element and use the quick fix to insert a role attribute to
+        make the result of the test be an 'error', 'warn', or 'info'.
+    </sch:p>
+    
+    <sch:phase id="check-id">
+        <sch:active pattern="sqf-add-id"/>
+    </sch:phase>
+    
+    <sch:phase id="check-role">
+        <sch:active pattern="sqf-add-role"/>
+    </sch:phase>
+
+    <sch:pattern id="sqf-add-id">
+        <sch:rule context="sch:assert | sch:report">
+            <sch:assert test="@id" sqf:fix="add-id" id="sch0001" role="warn"><sch:name/> should have an id attribute.</sch:assert>
+            <sch:let name="nearest-id" value="ancestor-or-self::*[@id][1]/@id"/>
+            <sch:let name="id-prefix" value="'sch'"/>
+            <sqf:fix id="add-id">
+                <sqf:description>
+                    <sqf:title>Add id attribute</sqf:title>
+                </sqf:description>
+                <sqf:add node-type="attribute" target="id" select="
+                    if (not($nearest-id)) then concat($id-prefix, format-number(count(//sch:assert[@id][not(ancestor::*[@id])] | //sch:report[@id][not(ancestor::*[@id])]) + 1, '0000'))
+                    else concat($nearest-id, '-', format-number(count(ancestor::*[@id = $nearest-id]//(sch:assert[@id] | sch:report[@id])) + 1, '00'))
+                    "/>
+            </sqf:fix>
+        </sch:rule>
+    </sch:pattern>
+    
+    <sch:pattern id="sqf-add-role">
+        <sch:rule context="sch:assert | sch:report">
+            <sch:assert test="@role" sqf:fix="sqf-add-role-error sqf-add-role-warn sqf-add-role-info" role="warn" id="sch0002"><sch:name/> should have a role attribute.</sch:assert>
+            <sqf:fix id="sqf-add-role-error">
+                <sqf:description>
+                    <sqf:title>Add role 'error'</sqf:title>
+                </sqf:description>
+                <sqf:add node-type="attribute" target="role" select="'error'"/>
+            </sqf:fix>
+            <sqf:fix id="sqf-add-role-warn">
+                <sqf:description>
+                    <sqf:title>Add role 'warn'</sqf:title>
+                </sqf:description>
+                <sqf:add node-type="attribute" target="role" select="'warn'"/>
+            </sqf:fix>
+            <sqf:fix id="sqf-add-role-info">
+                <sqf:description>
+                    <sqf:title>Add role 'info'</sqf:title>
+                </sqf:description>
+                <sqf:add node-type="attribute" target="role" select="'info'"/>
+            </sqf:fix>
+        </sch:rule>
+    </sch:pattern>
+    
+</sch:schema>

data/vendor/xspec-1.0.0/tutorial/xquery-tutorial.xq

@@ -0,0 +1,8 @@
+module namespace functx = "http://www.functx.com";
+
+declare function functx:capitalize-first
+($arg as xs:string?) as xs:string? {
+    
+    concat(upper-case(substring($arg, 1, 1)),
+    substring($arg, 2))
+};

data/vendor/xspec-1.0.0/tutorial/xquery-tutorial.xspec

@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" 
+               xmlns:functx="http://www.functx.com"
+               query="http://www.functx.com" 
+               query-at="xquery-tutorial.xq">
+
+  <x:scenario label="Calling function capitalize-first">
+    <x:call function="functx:capitalize-first">
+      <x:param select="'hello'"/>
+    </x:call>
+
+    <x:expect label="should capitalize the first character of the string" select="'Hello'"/>
+
+  </x:scenario>
+
+</x:description>

data/vendor/xspec-1.0.0/xproject/project.xml

@@ -0,0 +1,8 @@
+<project xmlns="http://expath.org/ns/project"
+         name="http://www.jenitennison.com/xslt/xspec"
+         abbrev="xspec"
+         version="0.4.0rc1">
+
+   <title>XSpec</title>
+
+</project>

data/vendor/xspec-1.0.0/xproject/release-project.xsl

@@ -0,0 +1,41 @@
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:proj="http://expath.org/ns/project"
+                xmlns:zip="http://expath.org/ns/zip"
+                exclude-result-prefixes="#all"
+                version="2.0">
+
+   <xsl:import href="http://expath.org/ns/project/release.xsl"/>
+
+   <!-- The overload point. -->
+   <xsl:template match="zip:file" mode="proj:modify-release">
+      <xsl:apply-templates select="." mode="add-readme"/>
+   </xsl:template>
+
+   <!-- Copy everything... -->
+   <xsl:template match="node()" mode="add-readme">
+      <xsl:copy>
+         <xsl:copy-of select="@*"/>
+         <xsl:apply-templates select="node()" mode="add-readme"/>
+      </xsl:copy>
+   </xsl:template>
+
+   <!-- ...and add the README file, and the Java, bin and tutorial dirs. -->
+   <xsl:template match="zip:file/zip:dir" mode="add-readme">
+      <xsl:copy>
+         <!-- copy the existing -->
+         <xsl:copy-of select="@*"/>
+         <!-- add the README file -->
+         <zip:entry src="{ resolve-uri('README', $proj:project) }"/>
+         <!-- copy the existing -->
+         <xsl:apply-templates select="node()" mode="add-readme"/>
+         <!-- additional dirs -->
+         <xsl:for-each select="'bin/', 'java/', 'tutorial/'">
+            <!-- resolve the dir, absolute, from the project's dir -->
+            <xsl:variable name="dir" select="resolve-uri(., $proj:project)"/>
+            <!-- recurse dir and create the appropriate zip:file elements -->
+            <xsl:sequence select="proj:zip-directory($dir)"/>
+         </xsl:for-each>
+      </xsl:copy>
+   </xsl:template>
+
+</xsl:stylesheet>