Blogs

gkholman

Open specifications open marketplaces!

An essay regarding the Canadian and US approaches towards building government electronic invoicing, in comparison to the European approach:

On Google+

http://plus.google.com/+GKenHolman-Crane/posts/2AT1WNfi7Cz

On LinkedIn

Read more

Factura Electrónica con UBL

Factura Electrónica en Europa

La comunidad europea ha establecido que el estándar UBL sea el utilizado en las transacciones electrónicas en las dependencias de gobierno, lo que permite el intercambio electrónico de información como son:

 

  • Pedidos
  • Facturas

 

Read more

Factura Electrónica con UBL

Factura E - España y la Factura Electrónica

El gobierno español ha decretado que la nueva versión de la Factura Telemática en España se utilice el formato UBL en la versión 2.1., lo que permite estandarizar el envío de las facturas electrónicas a la dependencias de Gobierno, y que a su vez les permite lograr la homogeneidad de la información que anteriormente no estaba estructurada por un formato electrónico universal. 

Read more

Factura Electrónica con UBL

UBL se empieza a integrar en América

UBL 2.0 es utilizado en América por primera vez para integrar la Factura Electrónica en Perú. 

De acuerdo a la publicación de la SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria) la Factura Electrónica en Perú es de manera obligatoria para todos los contribuyentes y las especificaciones técnicas de los documentos tributarios electrónicos como:

Read more

go2UBL

Purchase Orde location

 

In The NEtherlands UBL is growing. A lot of bookkeepingprograms are able to import UBL files. 

 

Now there is some disagreement about the location in the UBL file tag for the Purchase Ordernumber.

 

Who can give me right location (tag) for a purchase order in a UBL file? 

tim.mcgrath

What makes UBL a good standard for e-documents?

I was asked this question recently and my response is available at: 

http://blog.tradeshift.com/the-strongest-case-ever-made-for-an-international-e-document-standard/  

asuman

Semantic Representations of the UN/CEFACT CCTS-based Electronic Business Document Artifacts

The purpose of this SET TC deliverable is to provide standard semantic representations of electronic document artifacts based on UN/CEFACT Core Component Technical Specification (CCTS)  and hence to facilitate the development of tools to support semantic interoperability. The basic idea is to explicate the semantic information that is already given both in the CCTS and the CCTS based document standards in a standard way to make this information available for automated document interoperability tool support.

Read more

asuman

Electronic Document Interoperability in eBusiness and eGovernment Applications

This special issue contains articles addressing document interoperability from several different perspectives. The first three articles demonstrate the use of UN/CEFACT CCTS and OASIS UBL specifications.

Please click for downloading the full deliverable 

asuman

A Survey and Analysis of Electronic Business Document Standards

No document standard is sufficient for all purposes because the
requirements significantly differ among businesses, industries, and
geopolitical regions. On the other hand, the ultimate aim of business
document interoperability is to exchange business data among partners
without any prior agreements related to the document syntax and
semantics. Therefore, an important characteristic of a document standard
is its ability to adapt to different contexts, its extensibility, and
its customization. The UN/CEFACT Core Component Technical Specification

Read more

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I