Comments (6)
we've fixed #43 and will publish this with the next release. Nevertheless we need to fix the xrechnung configuration as well, which should use the acceptMatch
option
@renzok would you please fix this?
from validator.
I upgraded to validator 1.2.1 but I see no fix of the configuration. The Standard 1.2.2 should be provided on 01.07.2020. That is tomorrow. The actual 01.15a-INVOICE_ubl.xml in master-branch of the testsuite ist still the same than mine, but always the same result "rejected". Has the document format change or is that an issue of the validation? The same with 02_01a-Invoice_ubl-xml.
from validator.
A fast solution for me could be to use the 1.3.3 validation-tool with the actual configuration 1.2.2 2019-12-30. This would work, till the issue is fixed. Would it be o.k. to combine this versions?
from validator.
Hi @thomaspz
there is no version 1.3.3. of the validation tool.
Which exact target file do you use? If you used a recent version of 01.15a-INVOICE_ubl.xml (this one) and the xrechnung validator configuration 1.2.2 then you got a reject due to the fact, that the file is xrechnung version 2.0 and the configuration is looking for 1.2. E.g.
<match>/invoice:Invoice[ starts-with(cbc:CustomizationID,
'urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_1.2') ]</match>
does not match the file starting with
<?xml version="1.0" encoding="UTF-8"?>
<ubl:Invoice xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 http://docs.oasis-open.org/ubl/os-UBL-2.1/xsd/maindoc/UBL-Invoice-2.1.xsd">
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.0</cbc:CustomizationID>
You got a reject, since no scenario matches your input!
If you used another file please provide a running sample.
from validator.
I retried with validationtool Version 1.3.1 and Configuration Version validator-configuration-xrechnung_1.2.2_2019-12-30 and teststuite xrechnung-1.2.2-testsuite-2019-12-30.
Example Project : https://github.com/thomaspz/kosit-issue-example
Testclass : ValidationtoolEineXrechnungTest
Testdocument : 01.15a-INVOICE_ubl.xml
Kosit-Validation-Result :
AcceptRecommendation = Reject,
but Result Report contains :
Bewertung: Es wird empfohlen das Dokument anzunehmen und weiter zu verarbeiten.
Where can I determine, if I should procceed the XRechnung document,? The Validation Result has some warnings, but says "proceed the document"; So how could I determine this state in the code or why is the result "rejected" if the report contains "proceed".
from validator.
xrechnung-1.2.2-testsuite-2019-12-30 does not have an acceptMatch
-configuration as explained in #43.
The tool only evaluates technical validation results like schema an schematron. The configuration report contains business validation logic. Determination whether to accept the file should be based on business validation. But you should update to the recent xrechnung configuration which contains the acceptMatch
-configuration
from validator.
Related Issues (20)
- Role is null in FailedAssert HOT 9
- Loading of XSLT throws exception HOT 3
- Absolute path required
- Jakarta support HOT 2
- Deamon Mode Exception at startup HOT 4
- IllegalArgumetException wenn Repository Parameter nicht angegeben HOT 2
- BR-17 BT-59 Same name fΓΌr Payee and Seller is an error since xrechnung-2.3 HOT 3
- Multi language support for reports
- Assertion results output
- Saxon throws exception with new 1.5.0 validator (Java) HOT 4
- Documentation for version 1.5.0 not updated
- ValidationTool 1.5.0 Fails with "java.lang.IllegalArgumentException: No repository location for scenario definition 'default_1'" HOT 2
- Broken matching in multiple scenario files
- maven pom doesn't specify transitive dependencies HOT 2
- Document valid on https://kositvalidator.service-bw.de/ (1.4.2) not valid locally (neither 1.4.2 nor 1.5.0) HOT 5
- Custom Level ignored in Result via Java Api HOT 1
- Update README: "Third party validation configurations"
- Command line output says "reject", validation result document says "accept" HOT 1
- Outdated API Documentation for 1.5.0
- Check result to stdout causes an exception
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from validator.