Public Comment

[comment-form@oasis-open.org]

Comment from: martin.forsberg@amnis.se

Name: Martin Forsberg 
Organization: On behalf of Nortern European Subset Group 
Regarding Specification: UBL2.0 

In the ongoing work within the Northern European Subset group on e-procurement an issue has come up that we need to find a solution for. We are developing and defining a subset for a couple of common business processes and business rules. The problem, in a nutshell, is that we can't, by just looking at a document instance, see what business process/context the instance belongs to. We need to identify the context by looking at the instance to decide what business rules (schematron), subset schema and optionally what work flow to apply. The Small Business Subset SC has developed a great method of defining context specific subsets, but the document instance (e.g. the invoice) doesn't reflect it. 

  
Suggested solutions: 

A new BIE called "Document Context Identifier" of type Identifier is added on document level (0..1). 

By adopting the UN/CEFACT context drivers or other suitable keys, an Identifier can be built. 

Example: 
For the Order to Invoice process defined in the northern european subset, the identifier could be: NES:OrderToInvoice (Geo political context + Business process context)

Without this BIE, the only solution (as we see it) is to define specific namespaces for every business process and that will give a very negative impact on interoperability.



Best Regards 
Martin Forsberg 
SFTI (Single Face To Industry, Sweden)