From a924a4a5e5999e7a5897a46b265f4d8d4aed68c3 Mon Sep 17 00:00:00 2001
From: Menzo <menzo.windhouwer@meertens.knaw.nl>
Date: Mon, 11 Jul 2016 17:52:21 +0200
Subject: [PATCH] ValueScheme patterns were lost.

---
 src/main/resources/toolkit/xslt/comp2schema.xsl | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/main/resources/toolkit/xslt/comp2schema.xsl b/src/main/resources/toolkit/xslt/comp2schema.xsl
index 269b38c..a534e17 100755
--- a/src/main/resources/toolkit/xslt/comp2schema.xsl
+++ b/src/main/resources/toolkit/xslt/comp2schema.xsl
@@ -126,7 +126,7 @@
     <xsl:template match="text()" mode="types"/>
 
     <!-- first pass: create the complex types on top of the resulting XSD -->
-    <xsl:template match="Element/ValueScheme[exists(Vocabulary/enumeration)]" mode="types">
+    <xsl:template match="Element/ValueScheme[exists(Vocabulary/enumeration) or exists(pattern)]" mode="types">
         
         <!-- only handle the ValueScheme if this is the first occurence of the Component -->
         <xsl:variable name="Component" select="ancestor::Component[exists(@ComponentRef)]"/>
@@ -207,8 +207,8 @@
 
     <!-- Process all Elements, its attributes and children -->
 
-    <!-- Highest complexity: a ValueScheme and possibly attributes, link to the type we created during the preprocessing of the ValueScheme -->
-    <xsl:template match="Element[./ValueScheme[exists(Vocabulary/enumeration)]]" priority="3">
+    <!-- Highest complexity: a restrictive ValueScheme and possibly attributes, link to the type we created during the preprocessing of the ValueScheme -->
+    <xsl:template match="Element[./ValueScheme[exists(Vocabulary/enumeration) or exists(pattern)]]" priority="3">
         <xs:element name="{@name}">
 
             <xsl:apply-templates select="@ConceptLink"/>
@@ -226,7 +226,7 @@
         </xs:element>
     </xsl:template>
 
-    <!-- Medium complexity: attributes (or Multilingual field) but no ValueScheme, can be arranged inline -->
+    <!-- Medium complexity: attributes (or Multilingual field) but no restrictive ValueScheme, can be arranged inline -->
     <xsl:template match="Element[./AttributeList or ./@Multilingual='true']" priority="2">
         <xs:element name="{@name}">
 
@@ -259,7 +259,7 @@
         </xs:element>
     </xsl:template>
 
-    <!-- Simple case: no attributes and no ValueScheme, 1-to-1 transform to an xs:element, just rename element and attributes -->
+    <!-- Simple case: no attributes and no restrictive ValueScheme, 1-to-1 transform to an xs:element, just rename element and attributes -->
     <xsl:template match="Element" priority="1">
         <xs:element>