Jelte

FYI, the rule is in here in order to reduce the differences between NLCIUS and Peppol BIS, by matching rule BR-NL-12 from NLCIUS. Why it's limited there I do not...

But this was discussed in the WG last week, and the plan is to take a two-step approach; first limit it to NL->NL, then discuss full removal.

Update: the change appears to be (tentatively) accepted by openpeppol, but the deadline for the May release had apparently passed already, so they intend to include it in the November...

9994 is forbidden in PartyLegalEntity by both the European Norm (EN16931-3-2 page 19, business term BT-47), which limits it to official ISO6523 schemes, and NLCIUS (Gebruikersinstructie voor de basisfactuur 1.0.3,...

The people from TNO made it clear to me that NLCIUS makes the element essentially mandatory (was already implemented, but restated in https://github.com/peppolautoriteit-nl/validation/issues/27), as well as restrict it to only...

Sorry, I did not mean to imply that, i was trying to say that *if* you want to derive addressing information from the content of the message, the EndpointID field...

Since it's been added as a CR for NLCIUS, I'll close the issue here.

Just want to leave another note here, that came up as well today; if we ever want to expand into B2C we'll need to be able to create invoices where...

The suggested fix in and of itself isn't good, as the rules would then match any element that has a currencyID, and not the currencyID attribute node itself (thereby potentially...

Luckily we have a few months until the next release cycle... there's other attributes that are used as selectors as well But does this mean the Schematron (2016) specification is...