update

test/assets/eInvoicing-EN16931/templates/original/Template_Schematron.sch

@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<!--
+
+    Licensed under European Union Public Licence (EUPL) version 1.2.
+
+-->
+<!--Using xslt2 for transformation-->
+
+<schema xmlns="http://purl.oclc.org/dsdl/schematron"
+    xmlns:ns2="http://www.schematron-quickfix.com/validator/process" schemaVersion="iso"
+    queryBinding="xslt2">
+
+    <!--
+        
+        Title should reflect name of the norm, what kind of rules (codelists in separate file?), and to what syntax it is valid for.
+        Example for syntax specific rules:  "EN16931 Syntax rules CII Validation"
+        Example for codelists:              "EN16931 Code list rules ISO Validation"
+    
+    -->
+
+    <title>EN16931 Business rules UBL Validation</title>
+    <ns uri="urn:oasis:names:specification:ubl:schema:xsd:Tender-2" prefix="ubl"/>
+    <ns uri="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" prefix="cbc"/>
+    <ns uri="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" prefix="cac"/>
+    <pattern>
+
+        <!--Example from eSens/EHF PreAward-->
+        
+        <rule context="/ubl:Tender">
+            <assert test="not(count(//*[not(node()[not(self::comment())])]) &gt; 0)" flag="fatal"
+                id="ESENS-T45-R001">A tender receipt notification MUST not contain empty
+                elements.</assert>
+            <assert test="(cbc:UBLVersionID)" flag="fatal" id="ESENS-T45-R003">A tender receipt
+                notification MUST have a syntax identifier.</assert>
+        </rule>
+
+
+        <rule context="/ubl:Invoice">
+            <!--
+                
+                Using assert, not report to check validity. 
+                
+                @flag can have value either "fatal" or "warning" (if any) 
+                
+                @id to be set equal to corresponding business rule in norm draft
+                    - for syntax specific rules, suggest following legend for rule ids:
+                        Syntax-'SR'-sequence
+                        (SR=Syntax rule)
+                        
+                        Example:    UBL-SR-14
+                                    EDIFACT-SR-12
+                                    CII-SR-02
+                                    ISO-SR-07
+                Error text also identical to norm description of business rules, if new rules (/sytax specific) use wording "shall" and "shall not" to express rules.
+                -->
+            
+            <assert test="(cbc:ID)" flag="fatal" id="BR-2">An Invoice shall have an Invoice
+                number</assert>
+        </rule>
+
+    </pattern>
+</schema>