Official Schematron validation artefacts for CEN/TC 434. This repository does not contain validation rules for any CIUS.
Latest release
- UBL & CII: v1.1.0 (2018-06-26) - https://github.com/CenPC434/validation/releases/tag/validation-1.1.0
- EDIFACT: v1.0.0 (2018-02-08) - https://github.com/CenPC434/validation/releases/tag/validation-1.0.0
For each syntax a separate folder exists where all related artefacts are to be published.
ubl
- UBL 2.1 (ISO/IEC 19845:2015) - EN mandatory syntax- UBL Website: https://www.oasis-open.org/committees/ubl/
- Used XML Schemas: http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip
- Contact points
- Oriol Bausà (Rules)
- Siw Midtgard Meckelborg (Testing and QA)
cii
- Cross Industry Invoice (D16B) - EN mandatory syntax- XML Schemas overview: http://www.unece.org/cefact/xml_schemas/index.html
- Used XML Schemas: http://www.unece.org/fileadmin/DAM/cefact/xml_schemas/D16B_SCRDM__Subset__CII.zip
- Contact points
- Andreas Pelekies
- Tayfun Mermer (Testing and QA)
edifact
- UN/EDIFACT (and ISO 26025 based XML version) - EN optional syntax- Contact points
- Andreas Pelekies
- Jörg Walther (XML Schema)
- Martin Krusch (Testing and QA)
- Philip Helger (Java applications)
- Contact points
The action of performing validation of business documents is not directly supported by the artefacts in this repository. Standalone validation of EN-16931 rules can be performed on the following pages (in arbitrary order - please contact the operators directly):
- https://peppol.helger.com/public/menuitem-validation-bis2 - manual upload
- https://peppol.helger.com/public/menuitem-validation-ws2 - web service details page
- http://validex.net/en-service/ - registration needed
- https://open.validex.net/en/login - manual upload
- https://www.itb.ec.europa.eu/invoice/upload - CEF e-Invoicing support - manual upload
- https://www.itb.ec.europa.eu/invoice/api/validation?wsdl - CEF e-Invoicing support - web service
- https://www.itb.ec.europa.eu/cenws8/upload - similar service for CEN/TC 434 editors - manual upload
- https://www.itb.ec.europa.eu/cenws8/api/validation?wsdl - similar service for CEN/TC 434 editors - web service
- https://invoice.fans/fr/validation-des-messages/ - in French, registration is necessary
- https://invoice.fans/en/message-validation/ - in English, registration is necessary
- https://invoice.fans/de/validierung-von-nachrichten/ - in German, registration is necessary
If you also provide an open service that can validate EN-16931 artefacts and you want to be listed here send us an email to philip[at]helger.com
A simple demo implementation maintained by the project team can be found at https://github.com/CenPC434/java-tools/ - we do not recommend this for production usage.
-
v1.1.0 - 2018-06-26 (UBL and CII only)
- Note: this release does NOT contain the EDIFACT validation rules - its development is currently paused/stalled
- New participant identifier schemes are supported
- Rules targeting attributes were altered (issue #50)
- Fixed typo in
BR-CL-24
UBL (issue #52) - Some code list assertions had no
id
attributes (issue #53) - Rule
CII-SR-029
was removed and the context ofCII-SR-030
was adopted (issue #54) - Using
xs:decimal
instead ofxs:double
(issue #55) - The value of the VAT
@schemeID
attribute isVAT
(instead ofVA
) (issue #57) - Error in rule
BR-Z-10
UBL was fixed (issue #59) - Fixed error message of
BR-AF-05
CII (issue #60) - The value
532
was not supported inBR-CL-01
(issue #63)
-
v1.0.0 - 2018-02-08 (UBL, CII and EDIFACT)
- Initial release
For the Java projects contained in this repository, please consider the following prerequisites
- Java JDK 1.8.x latest (was tested only with a JDK and not with a JRE)
- Eclipse 4.6.x latest (m2e - Maven for Eclipse - must be contained)
- For building on the commandline use Apache Maven 3.x (latest)
Invoke mvn -f pom-xslt.xml process-resources
after changes - it will regenerate the XSLTs from the source SCHs.
Don't forget to update the license headers afterwards (see below).
Invoke mvn -f pom-validate.xml validate
after re-creating the XSLTs (see above).
The template for the license header resides in the file templates/license-template.txt
.
To add the license header to all relevant files invoke the following command:
mvn -f pom-license.xml license:format