OASIS Universal Business Language (UBL) TC

Dear Svante,

 

Thank you for your input and assistance. I've put your email on the agenda for our UBL TC meeting today and will get back to you afterwards.

 

Best regards,

 

Kenneth

 

 

From: Svante Schubert <svante.schubert@gmail.com>
Date: Thursday, February 20, 2025 at 5:18 PM
To: OASIS-ubl@connectedcommunity.org <OASIS-ubl@connectedcommunity.org>
Cc: Kenneth Bengtsson <kbengtsson@efact.pe>
Subject: Adding codes for the lexical representation of ISO 8601 (xsd:date & xsd:time)

Dear UBL TC,

 

in my attempt to have all codes and code lists of the European e-Invoice standard (EN16931) formally added to the spreadsheet (and genericode files) at the registry of the e-Invoice Technical Advisory Group (eTAG), I would like to suggest registering the lexical representations of ISO 8601 used by UBL in code list 2379 of Trade Data Interchange Directory (UNTDID) - https://service.unece.org/trade/untdid/d24a/tred/tred2379.htm

 

UBL is reusing the lexical representation of W3C XSD datatypes, from my understanding, the formatting is:

• xsd:date - CCYY-MM-DD - see https://www.w3.org/TR/xmlschema11-2/#date-lexical-mapping 
• xsd:time - hh:mm:ss - see https://www.w3.org/TR/xmlschema11-2/#time-lexical-mapping

The datatype xsd:date is already being used by multiple business terms in EN16931, while xsd:time will be used in the upcoming revision of EN16931 by a new business term "Invoice issue time".

 

If you like, I can be of assistance, as I will be attending the next UN/CEFACT Forum in Geneva this year and I am also (partly) responsible for the upcoming revision of the syntax-binding of EN16931.

In addition, it would be helpful if you could please verify if the new requirements of EN16931-1 are already covered by the UBL syntax. 

As multiple TC members are also CEN TC 434 WG 1 members you should already be informed.

While there is no strict timeline yet, the syntax binding is likely to be delivered for review mid of this year!

 

Kind regards,

Svante

Este correo electrónico y cualquier archivo transmitido con él son propiedad de Efact S.A.C., contiene información confidencial, y están destinados exclusivamente al uso de la persona o entidad a la que van dirigidas. Si usted no es el destinatario señalado, no puede difundir y distribuir o copiar este e-mail. Por favor notifique inmediatamente al remitente por correo electrónico si usted ha recibido este correo electrónico por error, y eliminar este correo electrónico de su sistema. Si usted no es el destinatario, se le notifica que revelar, copiar, distribuir o tomar cualquier acción basada en el contenido de esta información está estrictamente prohibida.

This email and any files transmitted with it are the properties of Efact S.A.C., contains confidential information, and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you may not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake, and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.