Diff for UBL FAQ

Thu, 2014-05-29 00:06 by tim.mcgrathThu, 2014-05-29 01:25 by tim.mcgrath
< previous diffnext diff >
Changes to Body
Line 1Line 1
 
<p style="margin-bottom: 0in">
 
<p style="margin-bottom: 0in">
-
1.    What is UBL?
+
<!--[if gte mso 9]><xml>
-
<br />
+
<o:DocumentProperties>
-
<br />
+
<o:Revision>0</o:Revision>
-
2.    Where did UBL come from? <br />
+
<o:TotalTime>0</o:TotalTime>
-
<br />
+
<o:Pages>1</o:Pages>
-
3.   
+
<o:Words>4247</o:Words>
-
Where does UBL stand at this point? <br />
+
<o:Characters>24210</o:Characters>
-
<br />
+
<o:Company>Document Engineering Services</o:Company>
-
4.    How
+
<o:Lines>201</o:Lines>
-
can I get the UBL 2.1 package, and what's in it? <br />
+
<o:Paragraphs>56</o:Paragraphs>
-
<br />
+
<o:CharactersWithSpaces>28401</o:CharactersWithSpaces>
-
5.   
+
<o:Version>14.0</o:Version>
-
Where can I discuss UBL with other users? <br />
+
</o:DocumentProperties>
-
<br />
+
<o:OfficeDocumentSettings>
-
6.   
+
<o:AllowPNG/>
-
Who owns UBL? <br />
+
</o:OfficeDocumentSettings>
-
<br />
+
</xml><![endif]-->
-
7.    How much will it cost to
+
<!--[if gte mso 9]><xml>
-
use UBL? <br />
+
<w:WordDocument>
-
<br />
+
<w:View>Normal</w:View>
-
8.    Can UBL be customized to meet
+
<w:Zoom>0</w:Zoom>
-
specific business requirements <br />
+
<w:TrackMoves/>
-
<br />
+
<w:TrackFormatting/>
-
9.    Has UBL
+
<w:PunctuationKerning/>
-
been successful in real-world implementations <br />
+
<w:ValidateAgainstSchemas/>
-
<br />
+
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
-
10.   
+
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
-
Can I use UBL in other contexts? <br />
+
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
-
<br />
+
<w:DoNotPromoteQF/>
-
11.    Is the
+
<w:LidThemeOther>EN-AU</w:LidThemeOther>
-
UBL effort still open to participation? <br />
+
<w:LidThemeAsian>JA</w:LidThemeAsian>
-
<br />
+
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
-
12.   
+
<w:Compatibility>
-
How does UBL facilitate international trade? <br />
+
<w:BreakWrappedTables/>
-
<br />
+
<w:SnapToGridInCell/>
-
13.   
+
<w:WrapTextWithPunct/>
-
Can I use UBL in a Single Window environment? <br />
+
<w:UseAsianBreakRules/>
-
<br />
+
<w:DontGrowAutofit/>
-
14.   
+
<w:SplitPgBreakAndParaMark/>
-
Is UBL a ‘real’ global standard for electronic business? <br />
+
<w:EnableOpenTypeKerning/>
-
<br />
+
<w:DontFlipMirrorIndents/>
-
15.   
+
<w:OverrideTableStyleHps/>
-
What is the relationship of UBL to ebXML? <br />
+
<w:UseFELayout/>
-
<br />
+
</w:Compatibility>
-
16.   
+
<m:mathPr>
-
What is the relationship of UBL to ebXML Core Components?
+
<m:mathFont m:val="Cambria Math"/>
  +
<m:brkBin m:val="before"/>
  +
<m:brkBinSub m:val="&#45;-"/>
  +
<m:smallFrac m:val="off"/>
  +
<m:dispDef/>
  +
<m:lMargin m:val="0"/>
  +
<m:rMargin m:val="0"/>
  +
<m:defJc m:val="centerGroup"/>
  +
<m:wrapIndent m:val="1440"/>
  +
<m:intLim m:val="subSup"/>
  +
<m:naryLim m:val="undOvr"/>
  +
</m:mathPr></w:WordDocument>
  +
</xml><![endif]--><!--[if gte mso 9]><xml>
  +
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  +
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  +
LatentStyleCount="276">
  +
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  +
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  +
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  +
<w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  +
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  +
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  +
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  +
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  +
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  +
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  +
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Table Grid"/>
  +
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  +
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  +
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Shading"/>
  +
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light List"/>
  +
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Grid"/>
  +
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 1"/>
  +
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 2"/>
  +
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 1"/>
  +
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 2"/>
  +
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 1"/>
  +
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 2"/>
  +
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 3"/>
  +
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Dark List"/>
  +
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Shading"/>
  +
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful List"/>
  +
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Grid"/>
  +
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  +
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light List Accent 1"/>
  +
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  +
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  +
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  +
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  +
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  +
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  +
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  +
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  +
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  +
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  +
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  +
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  +
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  +
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  +
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  +
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  +
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  +
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light List Accent 2"/>
  +
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  +
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  +
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  +
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  +
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  +
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  +
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  +
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  +
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  +
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  +
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  +
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  +
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  +
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light List Accent 3"/>
  +
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  +
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  +
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  +
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  +
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  +
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  +
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  +
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  +
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  +
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  +
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  +
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  +
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  +
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light List Accent 4"/>
  +
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  +
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  +
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  +
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  +
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  +
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  +
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  +
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  +
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  +
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  +
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  +
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  +
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  +
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light List Accent 5"/>
  +
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  +
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  +
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  +
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  +
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  +
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  +
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  +
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  +
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  +
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  +
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  +
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  +
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  +
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light List Accent 6"/>
  +
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  +
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  +
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  +
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  +
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  +
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  +
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  +
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  +
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  +
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  +
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  +
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
  +
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  +
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  +
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  +
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  +
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  +
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
  +
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  +
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  +
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
  +
</w:LatentStyles>
  +
</xml><![endif]-->
  +
<!--[if gte mso 10]>
  +
<style>
  +
/* Style Definitions */
  +
table.MsoNormalTable
  +
{mso-style-name:"Table Normal";
  +
mso-tstyle-rowband-size:0;
  +
mso-tstyle-colband-size:0;
  +
mso-style-noshow:yes;
  +
mso-style-priority:99;
  +
mso-style-parent:"";
  +
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
  +
mso-para-margin:0cm;
  +
mso-para-margin-bottom:.0001pt;
  +
mso-pagination:widow-orphan;
  +
font-size:12.0pt;
  +
font-family:Cambria;
  +
mso-ascii-font-family:Cambria;
  +
mso-ascii-theme-font:minor-latin;
  +
mso-hansi-font-family:Cambria;
  +
mso-hansi-theme-font:minor-latin;}
  +
</style>
  +
<![endif]-->
  +
<!--StartFragment-->
 
</p>
 
</p>
-
<p style="margin-bottom: 0in">
+
<p class="MsoToc1">
-
17.   
+
<!--[if supportFields]><span lang=EN-US><span
-
How does UBL support the European electronic invoicing Directive?
+
style='mso-element:field-begin'></span><span
-
<br />
+
style="mso-spacerun:yes"> </span>TOC \o &quot;1-3&quot; <span style='mso-element:
-
<br />
+
field-separator'></span></span><![endif]--><span><span>1.</span></span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>What is UBL?</span>
-
17.1.    Will UBL be the standard European
+
-
invoice format? <br />
+
-
<br />
+
-
17.2.    Isn<span style="font-family: 'Arial Unicode MS'">ﾒ</span>t
+
-
this yet another standard? <br />
+
-
<br />
+
-
17.3.    What will
+
-
a standard European electronic invoice look like? <br />
+
-
<br />
+
-
17.4.   
+
-
Should I delay my electronic invoicing programme until we see what
+
-
the European semantic standard is?
+
 
</p>
 
</p>
-
<p style="margin-bottom: 0in">
+
<p class="MsoToc1">
-
18.   Can I use digital signatures to electronically sign UBL documents?
+
<span>2.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>Where did UBL come from?</span>
 
</p>
 
</p>
-
<p style="margin-bottom: 0in">
+
<p class="MsoToc1">
-
&nbsp;
+
<span>3.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>Where does UBL stand at this point?</span>
 
</p>
 
</p>
-
<p style="margin-bottom: 0in">
+
<p class="MsoToc1">
-
<br />
+
<span>4.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>Is UBL a ‘real’ global standard for
  +
electronic business?</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136260" title="_Toc262136260"></a>1.    
+
<p class="MsoToc1">
-
What is UBL?</h2>
+
<span>5.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>How can I get the UBL 2.1 package, and
-
<p>
+
what's in it?</span>
-
UBL, the Universal Business Language, is the product of an
+
-
international effort to define a royalty-free library of standard
+
-
electronic XML business documents such as purchase orders and
+
-
invoices. Developed in an open and accountable OASIS Technical
+
-
Committee with participation from a variety of industry data
+
-
standards organizations, UBL is designed to plug directly into
+
-
existing business, legal, auditing, and records management practices,
+
-
eliminating the re-keying of data in existing fax- and paper-based
+
-
supply chains and providing an entry point into electronic business
+
-
for small and medium-sized businesses.
+
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136261" title="_Toc262136261"></a>2.    
+
<p class="MsoToc1">
-
Where did UBL come from?</h2>
+
<span>6.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>How much will it cost to use UBL?</span>
-
<p>
+
-
The UBL initiative originated in efforts beginning in mid-1999 to
+
-
create a set of standard XML &quot;office documents&quot; within
+
-
OASIS. The work of the OASIS OfficeDoc TC under the leadership of
+
-
Murray Altheim of Sun Microsystems was set aside when OASIS and
+
-
UN/CEFACT began collaboration on ebXML in December 1999. Interest in
+
-
the creation of a standard XML syntax for basic commercial documents
+
-
revived again in May 2000 with the decision in ebXML to omit a
+
-
standard XML &quot;payload&quot; syntax from the initial set of ebXML
+
-
deliverables. The working group that came to be known as UBL began in
+
-
April 2001 as a discussion group sponsored by CommerceNet and was
+
-
established as an OASIS Technical Committee in November 2001.
+
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136262" title="_Toc262136262"></a>3.    
+
<p class="MsoToc1">
-
Where does UBL stand at this point?</h2>
+
<span>7.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>Where can I discuss UBL with other users?</span>
-
<p>
+
-
UBL 1.0 was released as an OASIS Standard on 8 November 2004
+
-
following three years of open development and public review. UBL 2.0,
+
-
which expanded the scope of UBL to include the commercial
+
-
collaborations of international trade, was approved in November 2006.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
The current version, UBL 2.1 was approved as an OASIS Standard in November 2013 and extends the functionality of UBL 2.0
+
<span>8.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>Who owns UBL?</span>
-
to include support for collaborative planning, forecasting, and
+
-
replenishment; vendor managed inventory; utility billing; tendering;
+
-
and intermodal freight management.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
UBL 2.1 is fully backward compatible with UBL 2.0. It is the
+
<span>9.</span><span style="font-size: 12pt; font-weight: normal"><span>    </span></span><span>Is the UBL effort still open to
-
intention of the UBL Technical Committee to stabilize on the UBL 2
+
participation?</span>
-
for the foreseeable future so that subsequent releases of UBL will
+
-
not affect the validity of any UBL 2.0 (and later) documents. 
+
-
This means future releases will focus on further extensions to the
+
-
functionality and will not require changes to existing UBL
+
-
implementations.
+
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136263" title="_Toc262136263"></a>4.    
+
<p class="MsoToc1">
-
How can I get the UBL 2.1 package, and what's in it?</h2>
+
<span>10.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>Can UBL be customized to meet specific
-
<p>
+
business requirements?</span>
-
UBL 2.1 can be downloaded as a single zip archive from
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip">http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip</a>
+
<span>11.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>Has UBL been successful in real-world
  +
implementations?</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
The UBL 2.1 release package contains an overview of identified
+
<span>12.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>What is the UBL semantic data model?<span> </span></span>
-
Business Processes:
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>13.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>Can I use UBL in other contexts?</span>
-
</span>Tendering
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>14.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>How does UBL facilitate international
-
</span>Catalogue
+
trade?</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>15.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>Can I use UBL in a Single Window
-
</span>Quotation
+
environment?</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>16.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>What is the relationship of UBL to ebXML?</span>
-
</span>Ordering
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>17.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>What is the relationship of UBL to ebXML
-
</span>Fulfilment
+
Core Components?</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>18.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>How does UBL support the European
-
</span>Billing
+
electronic invoicing Directive?</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>Will UBL be the standard European invoice format?</span>
-
</span>Freight Billing
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>Is the Directive asking for yet another standard?</span>
-
</span>Utility Billing
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>What will a standard European electronic invoice look
-
</span>Payment Notification
+
like?</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc2">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>Should I delay my electronic invoicing programme until
-
</span>Report State of Accounts
+
we see what the European semantic standard is?</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoToc1">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>19.</span><span style="font-size: 12pt; font-weight: normal"><span> </span></span><span>Can I use digital signatures to electronically
-
</span>Collaborative Planning, Forecasting, and Replenishment
+
sign UBL documents?</span>
 
</p>
 
</p>
-
<p>
+
<h1><!--[if supportFields]><span lang=EN-US><span style='mso-element:field-end'></span></span><![endif]--><span> </span></h1>
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973724" title="_Toc262973724"></a><!--[if !supportLists]--><span><span>1.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>What is UBL?</span></h1>
-
</span>Vendor Managed Inventory
+
<p class="MsoNormal">
  +
<span>UBL, the Universal Business Language, is
  +
the product of an international effort to define a royalty-free library of
  +
standard electronic XML business documents such as purchase orders and invoices.
  +
Developed in an open and accountable OASIS Technical Committee with
  +
participation from a variety of industry data standards organizations, UBL is
  +
designed to plug directly into existing business, legal, auditing, and records
  +
management practices, eliminating the re-keying of data in existing fax- and
  +
paper-based supply chains and providing an entry point into electronic business
  +
for small and medium-sized businesses.</span>
 
</p>
 
</p>
-
<p>
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973725" title="_Toc262973725"></a><!--[if !supportLists]--><span><span>2.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>Where did UBL come from?</span></h1>
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<p class="MsoNormal">
-
</span>International Freight Management
+
<span>The UBL initiative originated in efforts
  +
beginning in mid-1999 to create a set of standard XML &quot;office
  +
documents&quot; within OASIS. The work of the OASIS OfficeDoc TC under the
  +
leadership of Murray Altheim of Sun Microsystems was set aside when OASIS and
  +
UN/CEFACT began collaboration on ebXML in December 1999. Interest in the
  +
creation of a standard XML syntax for basic commercial documents revived again
  +
in May 2000 with the decision in ebXML to omit a standard XML
  +
&quot;payload&quot; syntax from the initial set of ebXML deliverables. The
  +
working group that came to be known as UBL began in April 2001 as a discussion
  +
group sponsored by CommerceNet and was established as an OASIS Technical
  +
Committee in November 2001.</span>
 
</p>
 
</p>
-
<p>
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973726" title="_Toc262973726"></a><!--[if !supportLists]--><span><span>3.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>Where does UBL stand at this point?</span></h1>
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<p class="MsoNormal">
-
</span>Freight Status Reporting
+
<span>UBL 1.0 was released as an OASIS Standard
  +
on 8 November 2004 following three years of open development and public review.
  +
UBL 2.0, which expanded the scope of UBL to include the commercial
  +
collaborations of international trade, was approved in November 2006.</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>The current version, UBL 2.1 was
-
</span>Certification of Origin of Goods
+
approved as an OASIS Standard in November 2013 and extends the
  +
functionality of UBL 2.0 to include support for collaborative planning,
  +
forecasting, and replenishment; vendor managed inventory; utility billing;
  +
tendering; and intermodal freight management.</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>UBL 2.1 is fully backward compatible with
-
</span>Intermodal Freight Management
+
UBL 2.0. It is the intention of the UBL Technical Committee to stabilize on the
  +
UBL 2 for the foreseeable future so that subsequent releases of UBL will not
  +
affect the validity of any UBL 2.0 (and later) documents.  This means
  +
future releases will focus on further extensions to the functionality and will
  +
not require changes to existing UBL implementations.</span>
 
</p>
 
</p>
-
<p>
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973727" title="_Toc262973727"></a><!--[if !supportLists]--><span><span>4.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>Is UBL a ‘real’ global standard for electronic business?</span></h1>
-
And XML Schemas for the documents used in these processes:
+
<p class="MsoNormal">
  +
<span>Perhaps the clearest summary of what makes
  +
standards effective comes from a recent article published by the American
  +
National Standards Institute (ANSI).</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>“When it comes to international
-
</span>Application Response
+
standardization, good practices are measured against the World Trade
  +
Organization (WTO) Technical Barriers to Trade (TBT) Agreement Committee
  +
Decision<strong>[1]</strong>, which states that the global relevance of a standard is
  +
determined by how it was developed, not where. More specifically, the Decision
  +
states that the development of international standards must rely upon a number
  +
of principles, including openness, impartiality, consensus, transparency, and
  +
coherence, among others.</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>In other words, the global relevance of a
-
</span>Attached Document
+
standard cannot and should not be measured by which organization developed it.
  +
The degree to which a standard is used in the global marketplace is, in ANSI’s
  +
view, the best measure of an international standard.”<strong>[2]</strong></span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>Using this description we believe UBL
-
</span>Awarded Notification
+
qualifies as an international standard in compliance with the World Trade
  +
Organization (WTO) Technical Barriers to Trade (TBT) Agreement Committee
  +
Decision.</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>The strength of UBL (as with any standard)
-
</span>Bill of Lading
+
is that:</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Call for Tenders
+
it is an open global standard (from a recognized standards consortium)</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Catalogue
+
it exists (the technology works)</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Catalogue Deletion
+
it is stable (it has good governance)</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Catalogue Item Specification Update
+
it is proven to meet business requirements (it has market adoption). </span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>UBL has been developed within OASIS (a
-
</span>Catalogue Pricing Update
+
global standards development consortia) and OASIS has recently submitted UBL
  +
2.1 to the ISO-IEC Joint Technical Committee 1 (Information Technology) for
  +
publication as an ISO standard.  This will ensure that UBL is both
  +
recognized in public sector policies and will also provide additional layers of
  +
governance for the long-term sustainability of UBL.</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>In this way UBL is following a typical
-
</span>Catalogue Request
+
evolutionary path for effective global standards.</span>
 
</p>
 
</p>
-
<p>
+
<p style="padding-top: 0px; padding-right: 0px; padding-bottom: 10px; padding-left: 0px; margin: 0px" class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>[1] G/TBT/ 1/REV. 10. “Decision of the Committee on Principles for the Development of International Standards, Guides and Recommendations with Relation to Articles 2, 5 and Annex 3 of the Agreement”</span>
-
</span>Certificate of Origin
+
 
</p>
 
</p>
-
<p>
+
<p style="padding-top: 0px; padding-right: 0px; padding-bottom: 10px; padding-left: 0px; margin: 0px" class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>[2] ANSI Supports Continued Dialogue on Standards for EU-U.S. Transatlantic Trade and Investment Partnership<strong>, </strong>New York  October 11, 2013 (<a style="color: #000099; text-decoration: none" href="http://ansi.org/news_publications/news_story.aspx?menuid=7&amp;articleid=3754">http://ansi.org/news_publications/news_story.aspx?menuid=7&amp;articleid=3754</a>)</span> 
-
</span>Contract Award Notice
+
 
</p>
 
</p>
-
<p>
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973728" title="_Toc262973728"></a><!--[if !supportLists]--><span><span>5.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>How can I get the UBL 2.1 package, and what's in it?</span></h1>
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<p class="MsoNormal">
-
</span>Contract Notice
+
<span>UBL 2.1 can be downloaded as a single zip
  +
archive from</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span><a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip">http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip</a></span>
-
</span>Credit Note
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>The UBL 2.1 release package contains an
-
</span>Debit Note
+
overview of identified Business Processes:</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Despatch Advice
+
Tendering</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Document Status
+
Catalogue</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Document Status Request
+
Quotation</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Exception Criteria
+
Ordering</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Exception Notification
+
Fulfilment</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Forecast
+
Billing</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Forecast Revision
+
Freight Billing</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Forwarding Instructions
+
Utility Billing</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Freight Invoice
+
Payment Notification</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Fulfilment Cancellation
+
Report State of Accounts</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Goods Item Itinerary
+
Collaborative Planning, Forecasting, and Replenishment</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Guarantee Certificate
+
Vendor Managed Inventory</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Instruction for Returns
+
International Freight Management</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Inventory Report
+
Freight Status Reporting</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Invoice
+
Certification of Origin of Goods</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Item Information Request
+
Intermodal Freight Management</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>And XML Schemas for the documents used in
-
</span>Order
+
these processes:</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Order Cancellation
+
Application Response</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Order Change
+
Attached Document</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Order Response
+
Awarded Notification</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Order Response Simple
+
Bill of Lading</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Packing List
+
Call for Tenders</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Prior Information Notice
+
Catalogue</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Product Activity
+
Catalogue Deletion</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Quotation
+
Catalogue Item Specification Update</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Receipt Advice
+
Catalogue Pricing Update</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Reminder
+
Catalogue Request</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Remittance Advice
+
Certificate of Origin</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Request for Quotation
+
Contract Award Notice</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Retail Event
+
Contract Notice</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Self Billed Credit Note
+
Credit Note</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Self Billed Invoice
+
Debit Note</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Statement
+
Despatch Advice</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Stock Availability Report
+
Document Status</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Tender
+
Document Status Request</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Tender Receipt
+
Exception Criteria</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Tenderer Qualification
+
Exception Notification</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Tenderer Qualification Response
+
Forecast</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Trade Item Location Profile
+
Forecast Revision</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transport Execution Plan
+
Forwarding Instructions</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transport Execution Plan Request
+
Freight Invoice</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transport Progress Status
+
Fulfilment Cancellation</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transport Progress Status Request
+
Goods Item Itinerary</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transport Service Description
+
Guarantee Certificate</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transport Service Description Request
+
Instruction for Returns</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transportation Status
+
Inventory Report</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Transportation Status Request
+
Invoice</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Unawarded Notification
+
Item Information Request</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Utility Statement
+
Order</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<span>·        
-
</span>Waybill
+
Order Cancellation</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136264" title="_Toc262136264"></a>5.    
+
<p class="MsoNormal">
-
Where can I discuss UBL with other users?</h2>
+
<span>·        
-
<p>
+
Order Change</span>
-
For general discussions and exchanges of ideas there is a web site and wiki for the UBL user community at <a style="color: #000099; text-decoration: none" href="/">ubl.xml.org</a>.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
For specifc questions regarding UBL a publicly subscribable OASIS ubl-dev
+
<span>·        
-
list provides a free forum for questions regarding UBL. The ubl-dev
+
Order Response</span>
-
archive is located at:
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<a href="http://lists.oasis-open.org/archives/ubl-dev/">http://lists.oasis-open.org/archives/ubl-dev/</a>
+
<span>·        
  +
Order Response Simple</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Subscriptions to ubl-dev can be made through the OASIS list
+
<span>·        
-
manager at:
+
Packing List</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<a href="http://www.oasis-open.org/mlmanage/index.php">http://www.oasis-open.org/mlmanage/index.php</a>
+
<span>·        
  +
Prior Information Notice</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
&nbsp;
+
<span>·        
  +
Product Activity</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136265" title="_Toc262136265"></a>6.    
+
<p class="MsoNormal">
-
Who owns UBL?</h2>
+
<span>·        
-
<p>
+
Quotation</span>
-
UBL is owned by OASIS, a nonprofit organization dedicated to the
+
-
open development of public XML standards. UBL is maintained by an
+
-
OASIS Technical Committee made up of XML and business experts.
+
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136266" title="_Toc262136266"></a>7.    
+
<p class="MsoNormal">
-
How much will it cost to use UBL?</h2>
+
<span>·        
-
<p>
+
Receipt Advice</span>
-
The simple answer is that UBL is royalty-free. It can be used
+
-
without charge by anyone.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
More precisely, the UBL TC operates in the OASIS Intellectual
+
<span>·        
-
Property Rights (IPR) mode known as &quot;Royalty Free on Limited
+
Reminder</span>
-
Terms,&quot; which &quot;requires all Obligated Parties to license
+
-
their Essential Claims using the RF licensing elements described in
+
-
Sections 10.2.1 and 10.2.3&quot; of the OASIS IPR Policy, a copy of
+
-
which can be found at:
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<a href="http://www.oasis-open.org/who/intellectualproperty.php">http://www.oasis-open.org/who/intellectualproperty.php</a>
+
<span>·        
  +
Remittance Advice</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136267" title="_Toc262136267"></a>8.    
+
<p class="MsoNormal">
-
Can UBL be customized to meet specific business requirements?</h2>
+
<span>·        
-
<p>
+
Request for Quotation</span>
-
In many small-business environments, standard forms can satisfy
+
-
business requirements well enough to be used without modification.
+
-
The existence of standard paper forms such as the UN Layout Key
+
-
proves this. In these environments, UBL can work right out of the
+
-
box.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Customization is an activity undertaken by implementers of UBL to
+
<span>·        
-
apply additional business rules and information requirements to
+
Retail Event</span>
-
documents conforming to the standard UBL schema. UBL does not attempt
+
-
a complete solution to this problem but instead takes an extremely
+
-
pragmatic approach that should allow satisfactory solutions in the
+
-
great majority of real-world cases.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
For example, each UBL schema contains an optional extension area
+
<span>·        
-
in which trading partners may, by agreement, include any data not
+
Self Billed Credit Note</span>
-
already covered by the very extensive predefined UBL data structure.
+
-
Maintaining this extension area and coordinating its use is, of
+
-
course, the responsibility of the trading partners. But this simple
+
-
strategy allows nearly unlimited flexibility in individual trading
+
-
relationships without requiring modification of the standard UBL
+
-
schemas.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Implementers of UBL typically use customization techniques to
+
<span>·        
-
apply extensions, restrictions and other business rules to their
+
Self Billed Invoice</span>
-
documents. To assist in developing these, the UBL Guidelines for
+
-
Customization are available at:
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
<a href="http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf">http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf</a>
+
<span>·        
  +
Statement</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136268" title="_Toc262136268"></a>9.    
+
<p class="MsoNormal">
-
Has UBL been successful in real-world implementations?</h2>
+
<span>·        
-
<p>
+
Stock Availability Report</span>
-
Since UBL is publicly available and royalty-free it is impossible
+
-
to track implementations with any accuracy.  However, over the
+
-
past 10 years a number of UBL user communities have made themselves
+
-
known to the UBL Technical Committee.  Some of these are listed
+
-
below.  Many of these stakeholder communities have also
+
-
contributed to the ongoing development of UBL.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
From this we can confidently state that UBL has seen significant
+
<span>·        
-
large-scale, real-world adoption in public procurement programmes,
+
Tender</span>
-
initially in Europe and now in other regions across the public and
+
-
private sector.   
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
The first example of this was from Denmark.  Since February
+
<span>·        
-
2005, use of the UBL Invoice standard has been mandated by law for
+
Tender Receipt</span>
-
all public-sector business in Denmark. Several million UBL invoices
+
-
are currently exchanged in Denmark every month. The Danish Ministry
+
-
of Finance estimates savings to the government of 100 million euros
+
-
annually from use of this one document type. The introduction of
+
-
their wider-ranging <a href="http://www.oioubl.info/classes/en/index.html">OIOUBL
+
-
initiative</a> in 2010 affected almost all 440,000 businesses in
+
-
Denmark and established Denmark as a world leader in electronic
+
-
invoicing best practice.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
In 2008, the PEPPOL (Pan European eProcurement Online) initiative
+
<span>·        
-
scaled UBL adoption across 11 countries: Austria, Denmark, Finland,
+
Tenderer Qualification</span>
-
France, Germany, Greece, Italy, Norway, Portugal, Sweden, and the
+
-
United Kingdom.  In March 2014 the OpenPEPPOL association, set
+
-
up to ensure long term sustainability of PEPPOL had one hundred
+
-
member organisations from the public and private sector, from 18
+
-
European countries, including Russia and USA.  In April 2014,
+
-
the UK National Health Service, the world's largest publicly funded
+
-
health service and the world’s 5th largest employer, announced that
+
-
PEPPOL standards (including UBL) would be the basis of its new
+
-
eProcurement strategy.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Government adoption in this way has a stimulating effect on
+
<span>·        
-
adoption in other communities because government procurement touches
+
Tenderer Qualification Response</span>
-
on both commercial and policy issues.  In most economies it is
+
-
the largest procurement activity.  This means standards
+
-
introduced for public procurement have traction that encourages
+
-
adoption by other parts of the economy.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
The current implementations of UBL known to the UBL Technical
+
<span>·        
-
Committee are…
+
Trade Item Location Profile</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Public Procurement initiatives:
+
<span>·        
  +
Transport Execution Plan</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://www.peppol.eu/">PEPPOL</a> (Pan-European)
+
Transport Execution Plan Request</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://www.oioubl.info/classes/da/index.html">OIOUBL</a>
+
Transport Progress Status</span>
-
(Denmark)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://www.difi.no/artikkel/2012/11/papirfakturaens-tid-er-forbi">EHF</a>
+
Transport Progress Status Request</span>
-
(Norway)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://www.sfti.se/specifikationer/svefaktura">Svefaktura</a>
+
Transport Service Description</span>
-
(Sweden)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://www.icepro.is/Pages/NewsInfo.aspx?id=83">E-Invoicing</a>
+
Transport Service Description Request</span>
-
(Iceland)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://ec.europa.eu/dgs/informatics/supplier_portal/index_en.htm">ePrior</a>
+
Transportation Status</span>
-
(European Commission)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://www.efatura.gov.tr/anasayfa.html">E-Fatura</a>
+
Transportation Status Request</span>
-
(Turkey)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://orientacion.sunat.gob.pe/index.php?option=com_content&amp;view=article&amp;id=849&amp;Itemid=155">Factura
+
Unawarded Notification</span>
-
Electronica</a> (Peru)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="http://www.e-invoice-gateway.net/knowledgebase/countryrelated/compare?country1=332&amp;country2=332">E-Invoicing</a>
+
Utility Statement</span>
-
(Croatia)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>·        
-
</span><a href="https://www.gov.uk/government/publications/nhs-e-procurement-strategy">National
+
Waybill</span>
-
Health Service</a> (UK)
+
 
</p>
 
</p>
-
<p>
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973729" title="_Toc262973729"></a><!--[if !supportLists]--><span><span>6.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>How much will it cost to use UBL?</span></h1>
-
Trading Communities:
+
<p class="MsoNormal">
  +
<span>The simple answer is that UBL is
  +
royalty-free. It can be used without charge by anyone.</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>More precisely, the UBL TC operates in the
-
</span>Textile, Clothing and Footwear (<a href="http://ebiz-tcf.eu/">eBiz-TCF</a>)
+
OASIS Intellectual Property Rights (IPR) mode known as &quot;Royalty Free on
  +
Limited Terms,&quot; which &quot;requires all Obligated Parties to license
  +
their Essential Claims using the RF licensing elements described in Sections
  +
10.2.1 and 10.2.3&quot; of the OASIS IPR Policy, a copy of which can be found
  +
at:</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Service Providers:
+
<span><a href="http://www.oasis-open.org/who/intellectualproperty.php">http://www.oasis-open.org/who/intellectualproperty.php</a></span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973730" title="_Toc262973730"></a><!--[if !supportLists]--><span><span>7.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>Where can I discuss UBL with other users?</span></h1>
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<p class="MsoNormal">
-
</span>eInvoicing (<a href="http://tradeshift.com/">Tradeshift</a>,
+
<span>For general discussions and exchanges of
-
<a href="http://www.fundtech.com/products/cash-management/accountis-eipp/?redirect_source=accountis.com">Accountis</a>,
+
ideas there is a web site and wiki for the UBL user community at <a href="/">ubl.xml.org</a>.</span>
-
<a href="https://www.b2brouter.net/">B2BRouter</a>, <a href="http://www.simplerinvoicing.org/">SimplerInvoicing</a>)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>For specifc questions regarding UBL a
-
</span>Logistics Services (<a href="http://www.freightgate.com/">Freightgate</a>,
+
publicly subscribable OASIS ubl-dev list provides a free forum for questions
-
<a href="http://www.electra.se/">Electra</a>)
+
regarding UBL. The ubl-dev archive is located at:</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span><a href="http://lists.oasis-open.org/archives/ubl-dev/">http://lists.oasis-open.org/archives/ubl-dev/</a></span>
-
</span>ePurchasing (<a href="http://www.ozedi.com.au/">Ozedi</a>)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>Subscriptions to ubl-dev can be made
-
</span>Online Retailing (<a href="http://www.wehkamp.nl/">Wehkamp</a>)
+
through the OASIS list manager at:</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span><a href="http://www.oasis-open.org/mlmanage/index.php">http://www.oasis-open.org/mlmanage/index.php</a></span>
-
</span>Interoperability Services (<a href="http://www.eespa.eu/content/interoperability">European
+
-
eInvoice Service Providers Association</a>)
+
 
</p>
 
</p>
-
<p>
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973731" title="_Toc262973731"></a><!--[if !supportLists]--><span><span>8.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>Who owns UBL?</span></h1>
-
Freight Logistics and Transport initiatives:
+
<p class="MsoNormal">
  +
<span>UBL is owned by OASIS, a nonprofit
  +
organization dedicated to the open development of public XML standards. UBL is
  +
maintained by an OASIS Technical Committee made up of XML and business experts.</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973732" title="_Toc262973732"></a><a name="_Toc262970495" title="_Toc262970495"></a><span><!--[if !supportLists]--><span><span>9.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">   </span></span></span><!--[endif]--><span>Is the UBL effort still open to participation?</span></span></h1>
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<p class="MsoNormal">
-
</span><a href="http://www.efreightproject.eu/">eFreight</a>
+
<span>Yes! Anyone interested in the further
-
(European Commission, DG MOVE)
+
development of UBL should join OASIS and sign up for the UBL TC. OASIS
  +
memberships are available at the following URL:</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span><a href="http://www.oasis-open.org/join/">http://www.oasis-open.org/join/</a></span>
-
</span><a href="http://www.hk-dttn.com/home/english/home.html">DTTN</a>
+
-
(Port of Hong Kong)
+
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973733" title="_Toc262973733"></a><!--[if !supportLists]--><span><span>10.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
</span></span></span><!--[endif]--><span>Can UBL be customized to meet
-
</span><a href="https://www.certoforigin.com/tnlcoo/pfk/PfkMainServlet?pContents=/coo/CooWalkinUrl.jsp&amp;pPortalId=COO">CertOfOrigin</a>
+
specific business requirements?</span></h1>
-
(CrimsonLogic, Singapore)
+
<p class="MsoNormal">
  +
<span>In many small-business environments,
  +
standard forms can satisfy business requirements well enough to be used without
  +
modification. The existence of standard paper forms such as the UN Layout Key
  +
proves this. In these environments, UBL can work right out of the box.</span>
 
</p>
 
</p>
-
<p style="margin-left: 0.8in">
+
<p class="MsoNormal">
-
<span style="font-family: 'Courier New'">o</span><span style="font-family: 'Courier New'">      
+
<span>Customization is an activity undertaken by
-
</span><a href="http://www.its.dot.gov/efm/">Electronic Freight
+
implementers of UBL to apply additional business rules and information
-
Management</a> (US Dept of Transport)
+
requirements to documents conforming to the standard UBL schema. UBL does not
  +
attempt a complete solution to this problem but instead takes an extremely
  +
pragmatic approach that should allow satisfactory solutions in the great
  +
majority of real-world cases.</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136269" title="_Toc262136269"></a>10. Can I use UBL in
+
<p class="MsoNormal">
-
other contexts?</h2>
+
<span>For example, each UBL schema contains an
-
<p>
+
optional extension area in which trading partners may, by agreement, include
-
Yes. Many communities have successfully built their own XML schema
+
any data not already covered by the very extensive predefined UBL data
-
using UBL as a starting point. Some of these have subsequently been
+
structure. Maintaining this extension area and coordinating its use is, of
-
submitted to the UBL Technical Committee as candidates for inclusion
+
course, the responsibility of the trading partners. But this simple strategy
-
in the official UBL standard.
+
allows nearly unlimited flexibility in individual trading relationships without
  +
requiring modification of the standard UBL schemas.</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Others have used the UBL’s Naming and Design Rules to create
+
<span>Implementers of UBL typically use
-
completely new messages in domains such as healthcare, education and
+
customization techniques to apply extensions, restrictions and other business
-
customs.
+
rules to their documents. To assist in developing these, the UBL Guidelines for
  +
Customization are available at:</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136270" title="_Toc262136270"></a>11. Is the UBL effort
+
<p class="MsoNormal">
-
still open to participation?</h2>
+
<span><a href="http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf">http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf</a></span>
-
<p>
+
-
Yes! Anyone interested in the further development of UBL should
+
-
join OASIS and sign up for the UBL TC. OASIS memberships are
+
-
available at the following URL:
+
 
</p>
 
</p>
-
<p>
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973734" title="_Toc262973734"></a><!--[if !supportLists]--><span><span>11.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
-
<a href="http://www.oasis-open.org/join/">http://www.oasis-open.org/join/</a>
+
</span></span></span><!--[endif]--><span>Has UBL been successful in
  +
real-world implementations?</span></h1>
  +
<p class="MsoNormal">
  +
<span>Since UBL is publicly available and
  +
royalty-free it is impossible to track implementations with any accuracy. 
  +
However, over the past 10 years a number of UBL user communities have made
  +
themselves known to the UBL Technical Committee.  Some of these are listed
  +
below.  Many of these stakeholder communities have also contributed to the
  +
ongoing development of UBL.</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136271" title="_Toc262136271"></a>12. How does UBL
+
<p class="MsoNormal">
-
facilitate international trade?</h2>
+
<span>From this we can confidently state that UBL
-
<p>
+
has seen significant large-scale, real-world adoption in public procurement
-
<span>One of the challenges with </span>international
+
programmes, initially in Europe and now in other regions across the public and
-
trade in the digital era <span>is trust. When businesses
+
private sector.   </span>
-
seek to develop or improve their international supply chains their
+
-
primary consideration is trust in the complete trade system. Trust in
+
-
the security, reliability and authenticity of the processes and
+
-
partners they are dealing with.  Fundamental to establishing
+
-
this trust are standards.  Using standards creates certainty…
+
-
and certainty enables trust.</span>
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
UBL's contribution to ensuring trust in international trade lies
+
<span>The first example of this was from
-
in the definition of a standard set of XML documents that provide the
+
Denmark.  Since February 2005, use of the UBL Invoice standard has been
-
world with standards for the electronic versions of traditional
+
mandated by law for all public-sector business in Denmark. Several million UBL
-
business documents designed in a way that recognizes established
+
invoices are currently exchanged in Denmark every month. The Danish Ministry of
-
commercial and legal practices.
+
Finance estimates savings to the government of 100 million euros annually from
  +
use of this one document type. The introduction of their wider-ranging <a href="http://www.oioubl.info/classes/en/index.html">OIOUBL initiative</a> in
  +
2010 affected almost all 440,000 businesses in Denmark and established Denmark
  +
as a world leader in electronic invoicing best practice.</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
Exchanging standard UBL documents ensures that the structures and
+
<span>In 2008, the PEPPOL (Pan European
-
semantics of the information being exchanged are consistent and
+
eProcurement Online) initiative scaled UBL adoption across 11 countries:
-
interoperable with trading partners.
+
Austria, Denmark, Finland, France, Germany, Greece, Italy, Norway, Portugal,
  +
Sweden, and the United Kingdom.  In March 2014 the OpenPEPPOL association,
  +
set up to ensure long term sustainability of PEPPOL had one hundred member
  +
organisations from the public and private sector, from 18 European countries,
  +
including Russia and USA.  In April 2014, the UK National Health Service,
  +
the world's largest publicly funded health service and the world’s 5th largest
  +
employer, announced that PEPPOL standards (including UBL) would be the basis of
  +
its new eProcurement strategy.</span>
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136272" title="_Toc262136272"></a>13.  Can I use
+
<p class="MsoNormal">
-
UBL in a Single Window environment?</h2>
+
<span>Government adoption in this way has a
-
<p>
+
stimulating effect on adoption in other communities because government
-
The regulatory Single Window concept has been implemented in many
+
procurement touches on both commercial and policy issues.  In most
-
developing countries around the world as a major platform for
+
economies it is the largest procurement activity.  This means standards
-
collaboration and information exchange among different government
+
introduced for public procurement have traction that encourages adoption by
-
agencies involved in international trade. Recognized as effective
+
other parts of the economy.</span>
-
trade facilitation measures in the recent Bali Ministerial
+
-
Declaration and WTO Trade Facilitation Agreement, regulatory Single
+
-
Window systems are increasingly being adopted by developed and
+
-
developing countries.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
However, international trade transactions require a number of
+
<span>The current implementations of UBL known to
-
different business processes (not just regulatory) that need to be
+
the UBL Technical Committee are…</span>
-
coordinated.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
European projects such as PEPPOL and e-Freight have demonstrated
+
<span>Public Procurement initiatives:</span>
-
that UBL is a suitable standard for implementing the commercial,
+
-
transport and freight logistic documents required by processes that
+
-
complement regulatory Single Windows.
+
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136273" title="_Toc262136273"></a>14. Is UBL a ‘real’
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpFirst">
-
global standard for electronic business?</h2>
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
<p>
+
</span></span></span><!--[endif]--><span>     <a href="http://www.peppol.eu/">PEPPOL</a> (Pan-European)</span>
-
Perhaps the clearest summary of what makes standards effective
+
-
comes from a recent article published by the American National
+
-
Standards Institute (ANSI).
+
 
</p>
 
</p>
-
<p style="margin-right: 0.65in; margin-bottom: 0in">
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
“<em>When
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
it comes to international standardization, good practices are
+
</span></span></span><!--[endif]--><span>     <a href="http://www.oioubl.info/classes/da/index.html">OIOUBL</a> (Denmark)</span>
-
measured against the World Trade Organization (WTO) Technical
+
-
Barriers to Trade (TBT) Agreement Committee Decision</em><a name="_ftnref1" href="#_ftn1" title="_ftnref1"><span style="font-family: Cambria"><span style="font-size: small"><em><strong>[1]</strong></em></span></span></a><em>,
+
-
which states that the global relevance of a standard is determined by
+
-
how it was developed, not where. More specifically, the Decision
+
-
states that the development of international standards must rely upon
+
-
a number of principles, including openness, impartiality, consensus,
+
-
transparency, and coherence, among others.</em>
+
 
</p>
 
</p>
-
<p style="margin-right: 0.65in; margin-bottom: 0in">
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
<em>In other
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
words, the global relevance of a standard cannot and should not be
+
</span></span></span><!--[endif]--><span>     <a href="http://www.difi.no/artikkel/2012/11/papirfakturaens-tid-er-forbi">EHF</a>
-
measured by which organization developed it. The degree to which a
+
(Norway)</span>
-
standard is used in the global marketplace is, in ANSI’s view, the
+
-
best measure of an international standard.”</em><a name="_ftnref2" href="#_ftn2" title="_ftnref2"><span style="font-family: Cambria"><span style="font-size: small"><em><strong>[2]</strong></em></span></span></a>
+
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
Using this description we believe UBL qualifies as an
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
international standard in compliance with the World Trade
+
</span></span></span><!--[endif]--><span>     <a href="http://www.sfti.se/specifikationer/svefaktura">Svefaktura</a> (Sweden)</span>
-
Organization (WTO) Technical Barriers to Trade (TBT) Agreement
+
-
Committee Decision<em>.</em>
+
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
The strength of UBL (as with any standard) is that:
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
  +
</span></span></span><!--[endif]--><span>     <a href="http://www.icepro.is/Pages/NewsInfo.aspx?id=83">E-Invoicing</a> (Iceland)</span>
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
</span>it is an open global standard (from a recognized standards
+
</span></span></span><!--[endif]--><span>     <a href="http://ec.europa.eu/dgs/informatics/supplier_portal/index_en.htm">ePrior</a>
-
consortium)
+
(European Commission)</span>
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
</span>it exists (the technology works)
+
</span></span></span><!--[endif]--><span>     <a href="http://www.efatura.gov.tr/anasayfa.html">E-Fatura</a> (Turkey)</span>
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
</span>it is stable (it has good governance)
+
</span></span></span><!--[endif]--><span>     <a href="http://orientacion.sunat.gob.pe/index.php?option=com_content&amp;view=article&amp;id=849&amp;Itemid=155">Factura
  +
Electronica</a> (Peru)</span>
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
<span style="font-family: Symbol">·</span><span style="font-family: Symbol">        
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
</span>it is proven to meet business requirements (it has market
+
</span></span></span><!--[endif]--><span>     <a href="http://www.e-invoice-gateway.net/knowledgebase/countryrelated/compare?country1=332&amp;country2=332">E-Invoicing</a>
-
adoption). 
+
(Croatia)</span>
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpLast">
-
UBL has been developed within OASIS (a global standards
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
development consortia) and OASIS has recently submitted UBL 2.1 to
+
</span></span></span><!--[endif]--><span>     <a href="https://www.gov.uk/government/publications/nhs-e-procurement-strategy">National
-
the ISO-IEC Joint Technical Committee 1 (Information Technology) for
+
Health Service</a> (UK)</span>
-
publication as an ISO standard.  This will ensure that UBL is
+
-
both recognized in public sector policies and will also provide
+
-
additional layers of governance for the long-term sustainability of
+
-
UBL.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
In this way UBL is following a typical evolutionary path for
+
<span>Trading Communities:</span>
-
effective global standards.
+
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136274" title="_Toc262136274"></a>15. What is the
+
<p style="margin-left: 18pt; text-indent: -18pt" class="MsoListParagraph">
-
relationship of UBL to ebXML?</h2>
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
<p>
+
</span></span></span><!--[endif]--><span>Textile, Clothing and Footwear
-
The impetus to begin the UBL TC came from the desire of a number
+
(<a href="http://ebiz-tcf.eu/">eBiz-TCF</a>)</span>
-
of ebXML participants to define a standard XML payload format for
+
-
ebXML — that is, an XML counterpart to traditional EDI standards
+
-
such as ANSI X12 and UN/EDIFACT. The ebXML suite of specifications,
+
-
many of them now standardized as ISO 15000, provides a complete,
+
-
next-generation XML-based infrastructure that enables EDI
+
-
functionality over the free Internet.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
UBL provides a standard data format for the messages to be
+
<span>Service Providers:</span>
-
exchanged in such an infrastructure. However, UBL is designed to be
+
-
&quot;agnostic&quot; with respect to the infrastructure, and UBL
+
-
messages can be used in a very wide range of functional contexts,
+
-
from complex service-oriented architectures and cloud services to the
+
-
simple exchange of documents via email.
+
 
</p>
 
</p>
-
<h2 class="western"><a name="_Toc262136275" title="_Toc262136275"></a>16. What is the
+
<p style="margin-left: 18pt; text-indent: -18pt" class="MsoListParagraphCxSpFirst">
-
relationship of UBL to ebXML Core Components?</h2>
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
<p>
+
</span></span></span><!--[endif]--><span>eInvoicing (<a href="http://tradeshift.com/">Tradeshift</a>, <a href="http://www.fundtech.com/products/cash-management/accountis-eipp/?redirect_source=accountis.com">Accountis</a>,
-
UBL was the first published data format specification produced in
+
<a href="https://www.b2brouter.net/">B2BRouter</a>, <a href="http://www.simplerinvoicing.org/">SimplerInvoicing</a>)</span>
-
full conformance with UN/CEFACT's ebXML Core Components Technical
+
-
Specification (CCTS) Version 2.01 - ISO TS15000-5:2005.
+
 
</p>
 
</p>
-
<p>
+
<p style="margin-left: 18pt; text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
The UBL library consists of ebXML CCTS Business Information
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
Entities (BIEs). UBL XML schemas are defined through the application
+
</span></span></span><!--[endif]--><span>Logistics Services (<a href="http://www.freightgate.com/">Freightgate</a>, <a href="http://www.electra.se/">Electra</a>)</span>
-
of UBL Naming and Design Rules (NDRs) to an underlying data model
+
-
mapped to the Core Component types.
+
 
</p>
 
</p>
-
<p>
+
<p style="margin-left: 18pt; text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
For more information please see the UBL Committee Note on “UBL
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
Conformance to ebXML CCTS” at:
+
</span></span></span><!--[endif]--><span>ePurchasing (<a href="http://www.ozedi.com.au/">Ozedi</a>)</span>
 
</p>
 
</p>
-
<p>
+
<p style="margin-left: 18pt; text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
<a href="http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/cn01/UBL-conformance-to-CCTS-v1.0-cn01.html">http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/cn01/UBL-conformance-to-CCTS-v1.0-cn01.html</a>
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
  +
</span></span></span><!--[endif]--><span>Online Retailing (<a href="http://www.wehkamp.nl/">Wehkamp</a>)</span>
 
</p>
 
</p>
-
<h2 class="western">17. How does UBL
+
<p style="margin-left: 18pt; text-indent: -18pt" class="MsoListParagraphCxSpLast">
-
support the European electronic invoicing Directive?<a name="_Toc262136276" title="_Toc262136276"></a></h2>
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
<p>
+
</span></span></span><!--[endif]--><span>Industry Groups (<a href="http://www.eespa.eu/content/interoperability">European eInvoice Service
-
The European Directive on electronic invoicing in public
+
Providers Association</a>)</span>
-
procurement is a law enacted by the European parliament obliging
+
-
public authorities in all EU member states to receive electronic
+
-
invoices.  One aspect of this law is that a common European
+
-
standard for the semantic data model of the core elements of an
+
-
electronic invoice (the ‘European standard on electronic
+
-
invoicing’) will be developed over the next few years.  When
+
-
this is published, public sector contracting authorities will be
+
-
obliged to receive and process electronic invoices formatted using a
+
-
listed set of syntaxes that comply with the European semantic
+
-
standard.
+
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
The work of the CEN BII Workshop will be a key foundation for the
+
<span>Freight Logistics and Transport
-
European standard for electronic invoicing and we expect UBL will be
+
initiatives:</span>
-
one of the syntaxes identified.
+
 
</p>
 
</p>
-
<h3 class="western"><a name="_Toc262136278" title="_Toc262136278"></a>17.1.                   
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpFirst">
-
Will UBL be the standard European invoice format?</h3>
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
<p>
+
</span></span></span><!--[endif]--><span>     <a href="http://www.efreightproject.eu/">eFreight</a> (European Commission, DG
-
Yes (and no). There will not be a standard format or syntax for
+
MOVE)</span>
-
European invoices.  The European standard on electronic
+
-
invoicing will not dictate what syntax or format is to be used, only
+
-
the semantics of the required information.  
+
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
However, the semantic model of the CEN BII Post-award Profile will
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
be a key foundation of the European semantics and as the combination
+
</span></span></span><!--[endif]--><span>     <a href="http://www.hk-dttn.com/home/english/home.html">DTTN</a> (Port of Hong
-
of BII semantics and UBL format/syntax has been widely adopted in
+
Kong)</span>
-
Europe, the expectation is that the established BII user community
+
-
will be supported by the standard.  
+
 
</p>
 
</p>
-
<p>
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
-
While there will not be a European standard for invoice syntax, we
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
expect that market forces will determine that UBL syntax is the most
+
</span></span></span><!--[endif]--><span>     <a href="https://www.certoforigin.com/tnlcoo/pfk/PfkMainServlet?pContents=/coo/CooWalkinUrl.jsp&amp;pPortalId=COO">CertOfOrigin</a>
-
effective implementation of the European standard on electronic
+
(CrimsonLogic, Singapore)</span>
-
invoicing.
+
 
</p>
 
</p>
-
<h3 class="western"><a name="_Toc262136279" title="_Toc262136279"></a>17.2.                   
+
<p style="text-indent: -18pt" class="MsoListParagraphCxSpLast">
-
Isn’t this yet another standard?</h3>
+
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
-
<p>
+
</span></span></span><!--[endif]--><span>     <a href="http://www.its.dot.gov/efm/">Electronic Freight Management</a> (US Dept
-
No, fortunately this work is already well established and the
+
of Transport)</span>
-
formal standardization can be seen as the next stage on the natural
+
-
evolution of standards.  The obligation is for invoices to
+
-
contain core information elements.  Defining what is required as
+
-
core information is not a new piece of work.  These requirements
+
-
will be based on existing standardization activities by groups such
+
-
as the CEN BII Workshop and the semantic data model used in the BII
+
-
Profiles for post-award processes.
+
 
</p>
 
</p>
-
<h3 class="western"><a name="_Toc262136280" title="_Toc262136280"></a>17.3.                   
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973735" title="_Toc262973735"></a><!--[if !supportLists]--><span><span>12.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
-
What will a standard European electronic invoice look like?</h3>
+
</span></span></span><!--[endif]--><span>What is the UBL semantic data
-
<p>
+
model?</span></h1>
-
We expect that various subsets of the UBL Invoice will be
+
<p class="MsoNormal">
-
compliant to the new standard.  Valid subsets will contain the
+
<span>Since its inception in 2002, UBL has taken
-
core elements of information (the semantics) defined by the European
+
a data model approach to designing standardized business documents (that can be
-
standard on electronic invoicing.  
+
expressed in XML).  In fact, all UBL document types are made up of
  +
components from a common data model we call the Common Library.</span>
 
</p>
 
</p>
-
<h3 class="western"><a name="_Toc262136281" title="_Toc262136281"></a>17.4.                   
+
<p class="MsoNormal">
-
Should I delay my electronic invoicing programme until we see what
+
<span>Using a semantic data model to describe the
-
the European semantic standard is?</h3>
+
UBL Common Library has proven beneficial in several ways:</span>
-
<p>
+
-
Not at all. This is unnecessary and counter to the intention of
+
-
the Directive. The work of the CEN BII Workshop will be a key
+
-
foundation on which to develop the European standard for electronic
+
-
invoicing and UBL will be one of the syntaxes identified. Therefore,
+
-
the current CEN BII Post-award Profile offers a suitable placeholder
+
-
for the eventual European standard and so can be implemented with
+
-
some confidence that this will comply with the Directive.
+
 
</p>
 
</p>
-
<h2><a name="digsig" title="digsig"></a>18.   Can I use digital signatures to electronically sign UBL documents?</h2>
+
<ul style="margin-top: 0cm">
-
<p>
+
<li class="MsoNormal"><span>Business
-
The UBL 2.1 electronic signature extension is the first &quot;committee specified extension&quot; and it incorporates the use of the W3C digital signature XML structure. This extension also can be used with UBL 2.0 documents.
+
experts can work on the semantics of UBL business processes and their data
  +
requirements without needing to know XML technology.  This
  +
methodology is based on principles of business data analysis and modeling
  +
and uses the ebXML Core Component Technical Specification (ISO 15000-5)
  +
for its notation. </span></li>
  +
<li class="MsoNormal"><span>The
  +
common data model ensures that the common semantics of the components are
  +
not lost when they are re-used in different contexts.  This means a
  +
UBL Address is always the same component wherever it appears.</span></li>
  +
<li class="MsoNormal"><span>It is
  +
possible to automatically generate from the UBL data models not only XML
  +
representations of document types such as XML Schema and RelaxNG but also
  +
non-XML representations such as ASN.1. This effectively ‘future-proofs’
  +
UBL from changes in notations and syntaxes. </span></li>
  +
<li class="MsoNormal"><span>Because
  +
the UBL semantic data model is similar to a relational data model, some
  +
user communities also use this data model for their own internal data
  +
representations.  Why re-invent common data structures from scratch
  +
when UBL has already designed a useful starting point?</span></li>
  +
</ul>
  +
<p class="MsoNormal">
  +
<span>To aid in understanding the UBL semantic data
  +
model UML, HTML and spreadsheet views are provided.  For more details:</span>
 
</p>
 
</p>
-
<p>
+
<p class="MsoNormal">
-
The documentation of the electronic signature extension is found in the UBL 2.1 specification here:<br />
+
<span>OASIS UBL 2.1 specification Appendix C The
-
<br />
+
UBL 2.1 Data Model (<a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#A-THE-UBL-2.1-DATA-MODEL">http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#A-THE-UBL-2.1-DAT...</a>)</span>
-
<a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#S-UBL-DIGITAL-SIGNATURES">http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#S-UBL-DIGITAL-SIGNATURES<br />
+
</p>
-
<br />
+
<p class="MsoNormal">
-
</a>... where one reads:<br />
+
<span>Having a foundation based on a common
-
<br />
+
semantic data model provides long term sustainability for the growing number of
-
&quot;These include specific provisions to use extensions supporting <br />
+
communities who are implementing solutions based on UBL.  </span>
-
[XAdES], XML Advanced Electronic Signatures (ETSI TS 101 903), <br />
+
</p>
-
when the electronic signing of UBL documents is necessary to <br />
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973736" title="_Toc262973736"></a><!--[if !supportLists]--><span><span>13.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
-
satisfy legal and technical requirements.&quot;<br />
+
</span></span></span><!--[endif]--><span>Can I use UBL in other
-
<br />
+
contexts?</span></h1>
-
In essence, support for digital signatures is straightforward, thus ensuring a compliant implementation in OASIS UBL:  digital signature users embed in the W3C digital signature structure <a href="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/">http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/</a> all their information required for legal and technical requirements, and the UBL extension point scaffolding suitably embeds this W3C structure in any UBL instance providing full schema validation of the information.<br />
+
<p class="MsoNormal">
-
<br />
+
<span>Yes. Many communities have successfully
-
As with all XML documents, electronic signature validation is done outside of schema validation.  Examples of the use of electronic signatures in UBL are found in these digitally-signed UBL documents:<br />
+
built their own XML schema using UBL as a starting point. Some of these have
-
<br />
+
subsequently been submitted to the UBL Technical Committee as candidates for
-
<a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Enveloped.xml">http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Enveloped.xml</a><br />
+
inclusion in the official UBL standard.</span>
-
<a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached.xml">http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached.xml<br />
+
-
</a><a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached-Signature.xml">http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached-Signature.xml</a>
+
 
</p>
 
</p>
-
<p style="margin-bottom: 0in">
+
<p class="MsoNormal">
-
<br />
+
<span>Others have used the UBL’s Naming and
  +
Design Rules to create completely new messages in domains such as healthcare,
  +
education and customs.</span>
 
</p>
 
</p>
-
<hr />
+
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973737" title="_Toc262973737"></a><!--[if !supportLists]--><span><span>14.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
-
<div id="ftn1" dir="LTR">
+
</span></span></span><!--[endif]--><span>How does UBL facilitate
-
<p>
+
international trade?</span></h1>
-
<a name="_ftn1" href="#_ftnref1" title="_ftn1"><span style="font-family: Cambria"><span style="font-size: small">[1]</span></span></a>
+
<p class="MsoNormal">
-
<span style="font-size: x-small">G/TBT/ 1/REV. 10. “Decision of the Committee on
+
<span>One of the challenges with international
-
Principles for the Development of International Standards, Guides
+
trade in the digital era is trust. When businesses seek to develop or improve
-
and Recommendations with Relation to Articles 2, 5 and Annex 3 of
+
their international supply chains their primary consideration is trust in the
-
the Agreement”</span>
+
complete trade system. Trust in the security, reliability and authenticity of
  +
the processes and partners they are dealing with.  Fundamental to
  +
establishing this trust are standards.  Using standards creates certainty…
  +
and certainty enables trust.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>UBL's contribution to ensuring trust in
  +
international trade lies in the definition of a standard set of XML documents
  +
that provide the world with standards for the electronic versions of
  +
traditional business documents designed in a way that recognizes established
  +
commercial and legal practices.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>Exchanging standard UBL documents ensures
  +
that the structures and semantics of the information being exchanged are
  +
consistent and interoperable with trading partners.</span>
  +
</p>
  +
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973738" title="_Toc262973738"></a><!--[if !supportLists]--><span><span>15.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
  +
</span></span></span><!--[endif]--><span>Can I use UBL in a Single
  +
Window environment?</span></h1>
  +
<p class="MsoNormal">
  +
<span>The regulatory Single Window concept has
  +
been implemented in many developing countries around the world as a major
  +
platform for collaboration and information exchange among different government
  +
agencies involved in international trade. Recognized as effective trade facilitation
  +
measures in the recent Bali Ministerial Declaration and WTO Trade Facilitation
  +
Agreement, regulatory Single Window systems are increasingly being adopted by
  +
developed and developing countries.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>However, international trade transactions
  +
require a number of different business processes (not just regulatory) that
  +
need to be coordinated.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>European projects such as PEPPOL and
  +
e-Freight have demonstrated that UBL is a suitable standard for implementing
  +
the commercial, transport and freight logistic documents required by processes
  +
that complement regulatory Single Windows.</span>
  +
</p>
  +
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973739" title="_Toc262973739"></a><!--[if !supportLists]--><span><span>16.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
  +
</span></span></span><!--[endif]--><span>What is the relationship of UBL
  +
to ebXML?</span></h1>
  +
<p class="MsoNormal">
  +
<span>The impetus to begin the UBL TC came from
  +
the desire of a number of ebXML participants to define a standard XML payload
  +
format for ebXML — that is, an XML counterpart to traditional EDI standards
  +
such as ANSI X12 and UN/EDIFACT. The ebXML suite of specifications, many of
  +
them now standardized as ISO 15000, provides a complete, next-generation
  +
XML-based infrastructure that enables EDI functionality over the free Internet.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>UBL provides a standard data format for the
  +
messages to be exchanged in such an infrastructure. However, UBL is designed to
  +
be &quot;agnostic&quot; with respect to the infrastructure, and UBL messages
  +
can be used in a very wide range of functional contexts, from complex
  +
service-oriented architectures and cloud services to the simple exchange of
  +
documents via email.</span>
  +
</p>
  +
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973740" title="_Toc262973740"></a><!--[if !supportLists]--><span><span>17.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
  +
</span></span></span><!--[endif]--><span>What is the relationship of UBL
  +
to ebXML Core Components?</span></h1>
  +
<p class="MsoNormal">
  +
<span>UBL was the first published data format
  +
specification produced in full conformance with UN/CEFACT's ebXML Core
  +
Components Technical Specification (CCTS) Version 2.01 - ISO TS15000-5:2005.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>The UBL library consists of ebXML CCTS
  +
Business Information Entities (BIEs). UBL XML schemas are defined through the
  +
application of UBL Naming and Design Rules (NDRs) to an underlying data model
  +
mapped to the Core Component types.</span>
 
</p>
 
</p>
-
</div>
+
<p class="MsoNormal">
-
<div id="ftn2" dir="LTR">
+
<span>For more information please see the UBL
-
<p>
+
Committee Note on “UBL Conformance to ebXML CCTS” at:</span>
-
<a name="_ftn2" href="#_ftnref2" title="_ftn2"><span style="font-family: Cambria"><span style="font-size: small">[2]</span></span></a>
+
-
<span style="font-size: x-small">ANSI Supports Continued Dialogue on Standards for
+
-
EU-U.S. Transatlantic Trade and Investment Partnership</span><span style="font-size: x-small"><strong>,
+
-
</strong></span><span style="font-size: x-small">New York  October 11, 2013
+
-
(<a href="http://ansi.org/news_publications/news_story.aspx?menuid=7&amp;articleid=3754">http://ansi.org/news_publications/news_story.aspx?menuid=7&amp;articleid=3754</a>)</span>
+
 
</p>
 
</p>
-
</div>
+
<p class="MsoNormal">
-
<p style="margin-bottom: 0in">
+
<span><a href="http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/cn01/UBL-conformance-to-CCTS-v1.0-cn01.html">http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/cn01/UBL-conformance-to-CCTS-v1.0-cn01.html</a></span>
-
<br />
+
</p>
  +
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973741" title="_Toc262973741"></a><!--[if !supportLists]--><span><span>18.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
  +
</span></span></span><!--[endif]--><span>How does UBL support the
  +
European electronic invoicing Directive?</span></h1>
  +
<p class="MsoNormal">
  +
<span>The European Directive on electronic
  +
invoicing in public procurement is a law enacted by the European parliament
  +
obliging public authorities in all EU member states to receive electronic
  +
invoices.  One aspect of this law is that a common European standard for
  +
the semantic data model of the core elements of an electronic invoice (the
  +
‘European standard on electronic invoicing’) will be developed over the next
  +
few years.  When this is published, public sector contracting authorities
  +
will be obliged to receive and process electronic invoices formatted using a
  +
listed set of syntaxes that comply with the European semantic standard.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>The work of the CEN BII Workshop will be a
  +
key foundation for the European standard for electronic invoicing and we expect
  +
UBL will be one of the syntaxes identified.</span>
  +
</p>
  +
<h2><a name="_Toc262973742" title="_Toc262973742"></a><span>Will UBL be the standard European
  +
invoice format?</span></h2>
  +
<p class="MsoNormal">
  +
<span>Yes (and no). There will not be a standard
  +
format or syntax for European invoices.  The European standard on
  +
electronic invoicing will not dictate what syntax or format is to be used, only
  +
the semantics of the required information.  </span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>However, the semantic model of the CEN BII
  +
Post-award Profile will be a key foundation of the European semantics and as
  +
the combination of BII semantics and UBL format/syntax has been widely adopted
  +
in Europe, the expectation is that the established BII user community will be
  +
supported by the standard.  </span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>While there will not be a European standard
  +
for invoice syntax, we expect that market forces will determine that UBL syntax
  +
is the most effective implementation of the European standard on electronic
  +
invoicing.</span>
  +
</p>
  +
<h2><a name="_Toc262973743" title="_Toc262973743"></a><span>Is the Directive asking for yet
  +
another standard?</span></h2>
  +
<p class="MsoNormal">
  +
<span>No, fortunately this work is already well
  +
established and the formal standardization can be seen as the next stage on the
  +
natural evolution of standards.  The obligation is for invoices to contain
  +
core information elements.  Defining what is required as core information
  +
is not a new piece of work.  These requirements will be based on existing
  +
standardization activities by groups such as the CEN BII Workshop and the
  +
semantic data model used in the BII Profiles for post-award processes.</span>
  +
</p>
  +
<h2><a name="_Toc262973744" title="_Toc262973744"></a><span>What will a standard European
  +
electronic invoice look like?</span></h2>
  +
<p class="MsoNormal">
  +
<span>We expect that various subsets of the UBL
  +
Invoice will be compliant to the new standard.  Valid subsets will contain
  +
the core elements of information (the semantics) defined by the European
  +
standard on electronic invoicing.  </span>
  +
</p>
  +
<h2><a name="_Toc262973745" title="_Toc262973745"></a><span>Should I delay my electronic
  +
invoicing programme until we see what the European semantic standard is?</span></h2>
  +
<p class="MsoNormal">
  +
<span>Not at all. This is unnecessary and counter
  +
to the intention of the Directive. The work of the CEN BII Workshop will be a
  +
key foundation on which to develop the European standard for electronic
  +
invoicing and UBL will be one of the syntaxes identified. Therefore, the
  +
current CEN BII Post-award Profile offers a suitable placeholder for the
  +
eventual European standard and so can be implemented with some confidence that
  +
this will comply with the Directive.</span>
  +
</p>
  +
<h1 style="margin-left: 36pt; text-indent: -18pt"><a name="_Toc262973746" title="_Toc262973746"></a><!--[if !supportLists]--><span><span>19.<span style="font: normal normal normal 7pt/normal 'Times New Roman'">                
  +
</span></span></span><!--[endif]--><span>Can I use digital signatures to
  +
electronically sign UBL documents?</span></h1>
  +
<p class="MsoNormal">
  +
<span>The UBL 2.1 electronic signature extension
  +
is the first &quot;committee specified extension&quot; and it incorporates the
  +
use of the W3C digital signature XML structure. This extension also can be used
  +
with UBL 2.0 documents.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>The documentation of the electronic
  +
signature extension is found in the UBL 2.1 specification here:</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span><a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html%23S-UBL-DIGITAL-SIGNATURE">http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#S-UBL-DIGITAL-SIGNATURE</a>
  +
</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>... where one reads:</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>&quot;These include specific provisions to
  +
use extensions supporting [XAdES], XML Advanced Electronic Signatures (ETSI TS
  +
101 903), when the electronic signing of UBL documents is necessary to satisfy
  +
legal and technical requirements.”</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>In essence, support for digital signatures
  +
is straightforward, thus ensuring a compliant implementation in OASIS
  +
UBL:  digital signature users embed in the W3C digital signature structure
  +
<a href="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/">http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/</a>
  +
all their information required for legal and technical requirements, and the
  +
UBL extension point scaffolding suitably embeds this W3C structure in any UBL
  +
instance providing full schema validation of the information.</span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span>As with all XML documents, electronic
  +
signature validation is done outside of schema validation.  Examples of
  +
the use of electronic signatures in UBL are found in these digitally-signed UBL
  +
documents:</span>
  +
</p>
  +
<p style="text-indent: -18pt" class="MsoListParagraphCxSpFirst">
  +
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
  +
</span></span></span><!--[endif]--><span><a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Enveloped.xml">http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Enveloped.xml</a></span>
  +
</p>
  +
<p style="text-indent: -18pt" class="MsoListParagraphCxSpMiddle">
  +
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
  +
</span></span></span><!--[endif]--><span><a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached.xml">http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached.xml</a></span>
  +
</p>
  +
<p style="text-indent: -18pt" class="MsoListParagraphCxSpLast">
  +
<!--[if !supportLists]--><span style="font-family: Symbol"><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'">     
  +
</span></span></span><!--[endif]--><span><a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached-Signature.xml">http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached-Signature.xml</a></span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span> </span>
  +
</p>
  +
<p class="MsoNormal">
  +
<span> </span>
  +
</p>
  +
<p class="MsoNormal">
  +
&nbsp;
  +
</p>
  +
<!--EndFragment-->
  +
<p>
  +
&nbsp;
 
</p>
 
</p>
 
 
Revision of Thu, 2014-05-29 01:25:

UBL FAQ

<!--[if gte mso 9]> 0 0 1 4247 24210 Document Engineering Services 201 56 28401 14.0 <![endif]--> <!--[if gte mso 9]> Normal 0 false false false EN-AU JA X-NONE <![endif]--><!--[if gte mso 9]> <![endif]--> <!--[if gte mso 10]> <![endif]--> <!--StartFragment-->

<!--[if supportFields]> 

TOC \o "1-3" <![endif]-->1.    What is UBL?

2.    Where did UBL come from?

3.    Where does UBL stand at this point?

4.    Is UBL a ‘real’ global standard for electronic business?

5.    How can I get the UBL 2.1 package, and what's in it?

6.    How much will it cost to use UBL?

7.    Where can I discuss UBL with other users?

8.    Who owns UBL?

9.    Is the UBL effort still open to participation?

10. Can UBL be customized to meet specific business requirements?

11. Has UBL been successful in real-world implementations?

12. What is the UBL semantic data model? 

13. Can I use UBL in other contexts?

14. How does UBL facilitate international trade?

15. Can I use UBL in a Single Window environment?

16. What is the relationship of UBL to ebXML?

17. What is the relationship of UBL to ebXML Core Components?

18. How does UBL support the European electronic invoicing Directive?

Will UBL be the standard European invoice format?

Is the Directive asking for yet another standard?

What will a standard European electronic invoice look like?

Should I delay my electronic invoicing programme until we see what the European semantic standard is?

19. Can I use digital signatures to electronically sign UBL documents?

<!--[if supportFields]><![endif]--> 

<!--[if !supportLists]-->1.   <!--[endif]-->What is UBL?

UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices. Developed in an open and accountable OASIS Technical Committee with participation from a variety of industry data standards organizations, UBL is designed to plug directly into existing business, legal, auditing, and records management practices, eliminating the re-keying of data in existing fax- and paper-based supply chains and providing an entry point into electronic business for small and medium-sized businesses.

<!--[if !supportLists]-->2.   <!--[endif]-->Where did UBL come from?

The UBL initiative originated in efforts beginning in mid-1999 to create a set of standard XML "office documents" within OASIS. The work of the OASIS OfficeDoc TC under the leadership of Murray Altheim of Sun Microsystems was set aside when OASIS and UN/CEFACT began collaboration on ebXML in December 1999. Interest in the creation of a standard XML syntax for basic commercial documents revived again in May 2000 with the decision in ebXML to omit a standard XML "payload" syntax from the initial set of ebXML deliverables. The working group that came to be known as UBL began in April 2001 as a discussion group sponsored by CommerceNet and was established as an OASIS Technical Committee in November 2001.

<!--[if !supportLists]-->3.   <!--[endif]-->Where does UBL stand at this point?

UBL 1.0 was released as an OASIS Standard on 8 November 2004 following three years of open development and public review. UBL 2.0, which expanded the scope of UBL to include the commercial collaborations of international trade, was approved in November 2006.

The current version, UBL 2.1 was approved as an OASIS Standard in November 2013 and extends the functionality of UBL 2.0 to include support for collaborative planning, forecasting, and replenishment; vendor managed inventory; utility billing; tendering; and intermodal freight management.

UBL 2.1 is fully backward compatible with UBL 2.0. It is the intention of the UBL Technical Committee to stabilize on the UBL 2 for the foreseeable future so that subsequent releases of UBL will not affect the validity of any UBL 2.0 (and later) documents.  This means future releases will focus on further extensions to the functionality and will not require changes to existing UBL implementations.

<!--[if !supportLists]-->4.   <!--[endif]-->Is UBL a ‘real’ global standard for electronic business?

Perhaps the clearest summary of what makes standards effective comes from a recent article published by the American National Standards Institute (ANSI).

“When it comes to international standardization, good practices are measured against the World Trade Organization (WTO) Technical Barriers to Trade (TBT) Agreement Committee Decision[1], which states that the global relevance of a standard is determined by how it was developed, not where. More specifically, the Decision states that the development of international standards must rely upon a number of principles, including openness, impartiality, consensus, transparency, and coherence, among others.

In other words, the global relevance of a standard cannot and should not be measured by which organization developed it. The degree to which a standard is used in the global marketplace is, in ANSI’s view, the best measure of an international standard.”[2]

Using this description we believe UBL qualifies as an international standard in compliance with the World Trade Organization (WTO) Technical Barriers to Trade (TBT) Agreement Committee Decision.

The strength of UBL (as with any standard) is that:

·         it is an open global standard (from a recognized standards consortium)

·         it exists (the technology works)

·         it is stable (it has good governance)

·         it is proven to meet business requirements (it has market adoption). 

UBL has been developed within OASIS (a global standards development consortia) and OASIS has recently submitted UBL 2.1 to the ISO-IEC Joint Technical Committee 1 (Information Technology) for publication as an ISO standard.  This will ensure that UBL is both recognized in public sector policies and will also provide additional layers of governance for the long-term sustainability of UBL.

In this way UBL is following a typical evolutionary path for effective global standards.

[1] G/TBT/ 1/REV. 10. “Decision of the Committee on Principles for the Development of International Standards, Guides and Recommendations with Relation to Articles 2, 5 and Annex 3 of the Agreement”

[2] ANSI Supports Continued Dialogue on Standards for EU-U.S. Transatlantic Trade and Investment Partnership, New York  October 11, 2013 (http://ansi.org/news_publications/news_story.aspx?menuid=7&articleid=3754) 

<!--[if !supportLists]-->5.   <!--[endif]-->How can I get the UBL 2.1 package, and what's in it?

UBL 2.1 can be downloaded as a single zip archive from

http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip

The UBL 2.1 release package contains an overview of identified Business Processes:

·         Tendering

·         Catalogue

·         Quotation

·         Ordering

·         Fulfilment

·         Billing

·         Freight Billing

·         Utility Billing

·         Payment Notification

·         Report State of Accounts

·         Collaborative Planning, Forecasting, and Replenishment

·         Vendor Managed Inventory

·         International Freight Management

·         Freight Status Reporting

·         Certification of Origin of Goods

·         Intermodal Freight Management

And XML Schemas for the documents used in these processes:

·         Application Response

·         Attached Document

·         Awarded Notification

·         Bill of Lading

·         Call for Tenders

·         Catalogue

·         Catalogue Deletion

·         Catalogue Item Specification Update

·         Catalogue Pricing Update

·         Catalogue Request

·         Certificate of Origin

·         Contract Award Notice

·         Contract Notice

·         Credit Note

·         Debit Note

·         Despatch Advice

·         Document Status

·         Document Status Request

·         Exception Criteria

·         Exception Notification

·         Forecast

·         Forecast Revision

·         Forwarding Instructions

·         Freight Invoice

·         Fulfilment Cancellation

·         Goods Item Itinerary

·         Guarantee Certificate

·         Instruction for Returns

·         Inventory Report

·         Invoice

·         Item Information Request

·         Order

·         Order Cancellation

·         Order Change

·         Order Response

·         Order Response Simple

·         Packing List

·         Prior Information Notice

·         Product Activity

·         Quotation

·         Receipt Advice

·         Reminder

·         Remittance Advice

·         Request for Quotation

·         Retail Event

·         Self Billed Credit Note

·         Self Billed Invoice

·         Statement

·         Stock Availability Report

·         Tender

·         Tender Receipt

·         Tenderer Qualification

·         Tenderer Qualification Response

·         Trade Item Location Profile

·         Transport Execution Plan

·         Transport Execution Plan Request

·         Transport Progress Status

·         Transport Progress Status Request

·         Transport Service Description

·         Transport Service Description Request

·         Transportation Status

·         Transportation Status Request

·         Unawarded Notification

·         Utility Statement

·         Waybill

<!--[if !supportLists]-->6.   <!--[endif]-->How much will it cost to use UBL?

The simple answer is that UBL is royalty-free. It can be used without charge by anyone.

More precisely, the UBL TC operates in the OASIS Intellectual Property Rights (IPR) mode known as "Royalty Free on Limited Terms," which "requires all Obligated Parties to license their Essential Claims using the RF licensing elements described in Sections 10.2.1 and 10.2.3" of the OASIS IPR Policy, a copy of which can be found at:

http://www.oasis-open.org/who/intellectualproperty.php

<!--[if !supportLists]-->7.   <!--[endif]-->Where can I discuss UBL with other users?

For general discussions and exchanges of ideas there is a web site and wiki for the UBL user community at ubl.xml.org.

For specifc questions regarding UBL a publicly subscribable OASIS ubl-dev list provides a free forum for questions regarding UBL. The ubl-dev archive is located at:

http://lists.oasis-open.org/archives/ubl-dev/

Subscriptions to ubl-dev can be made through the OASIS list manager at:

http://www.oasis-open.org/mlmanage/index.php

<!--[if !supportLists]-->8.   <!--[endif]-->Who owns UBL?

UBL is owned by OASIS, a nonprofit organization dedicated to the open development of public XML standards. UBL is maintained by an OASIS Technical Committee made up of XML and business experts.

<!--[if !supportLists]-->9.   <!--[endif]-->Is the UBL effort still open to participation?

Yes! Anyone interested in the further development of UBL should join OASIS and sign up for the UBL TC. OASIS memberships are available at the following URL:

http://www.oasis-open.org/join/

<!--[if !supportLists]-->10.                 <!--[endif]-->Can UBL be customized to meet specific business requirements?

In many small-business environments, standard forms can satisfy business requirements well enough to be used without modification. The existence of standard paper forms such as the UN Layout Key proves this. In these environments, UBL can work right out of the box.

Customization is an activity undertaken by implementers of UBL to apply additional business rules and information requirements to documents conforming to the standard UBL schema. UBL does not attempt a complete solution to this problem but instead takes an extremely pragmatic approach that should allow satisfactory solutions in the great majority of real-world cases.

For example, each UBL schema contains an optional extension area in which trading partners may, by agreement, include any data not already covered by the very extensive predefined UBL data structure. Maintaining this extension area and coordinating its use is, of course, the responsibility of the trading partners. But this simple strategy allows nearly unlimited flexibility in individual trading relationships without requiring modification of the standard UBL schemas.

Implementers of UBL typically use customization techniques to apply extensions, restrictions and other business rules to their documents. To assist in developing these, the UBL Guidelines for Customization are available at:

http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf

<!--[if !supportLists]-->11.                 <!--[endif]-->Has UBL been successful in real-world implementations?

Since UBL is publicly available and royalty-free it is impossible to track implementations with any accuracy.  However, over the past 10 years a number of UBL user communities have made themselves known to the UBL Technical Committee.  Some of these are listed below.  Many of these stakeholder communities have also contributed to the ongoing development of UBL.

From this we can confidently state that UBL has seen significant large-scale, real-world adoption in public procurement programmes, initially in Europe and now in other regions across the public and private sector.   

The first example of this was from Denmark.  Since February 2005, use of the UBL Invoice standard has been mandated by law for all public-sector business in Denmark. Several million UBL invoices are currently exchanged in Denmark every month. The Danish Ministry of Finance estimates savings to the government of 100 million euros annually from use of this one document type. The introduction of their wider-ranging OIOUBL initiative in 2010 affected almost all 440,000 businesses in Denmark and established Denmark as a world leader in electronic invoicing best practice.

In 2008, the PEPPOL (Pan European eProcurement Online) initiative scaled UBL adoption across 11 countries: Austria, Denmark, Finland, France, Germany, Greece, Italy, Norway, Portugal, Sweden, and the United Kingdom.  In March 2014 the OpenPEPPOL association, set up to ensure long term sustainability of PEPPOL had one hundred member organisations from the public and private sector, from 18 European countries, including Russia and USA.  In April 2014, the UK National Health Service, the world's largest publicly funded health service and the world’s 5th largest employer, announced that PEPPOL standards (including UBL) would be the basis of its new eProcurement strategy.

Government adoption in this way has a stimulating effect on adoption in other communities because government procurement touches on both commercial and policy issues.  In most economies it is the largest procurement activity.  This means standards introduced for public procurement have traction that encourages adoption by other parts of the economy.

The current implementations of UBL known to the UBL Technical Committee are…

Public Procurement initiatives:

<!--[if !supportLists]-->·      <!--[endif]-->     PEPPOL (Pan-European)

<!--[if !supportLists]-->·      <!--[endif]-->     OIOUBL (Denmark)

<!--[if !supportLists]-->·      <!--[endif]-->     EHF (Norway)

<!--[if !supportLists]-->·      <!--[endif]-->     Svefaktura (Sweden)

<!--[if !supportLists]-->·      <!--[endif]-->     E-Invoicing (Iceland)

<!--[if !supportLists]-->·      <!--[endif]-->     ePrior (European Commission)

<!--[if !supportLists]-->·      <!--[endif]-->     E-Fatura (Turkey)

<!--[if !supportLists]-->·      <!--[endif]-->     Factura Electronica (Peru)

<!--[if !supportLists]-->·      <!--[endif]-->     E-Invoicing (Croatia)

<!--[if !supportLists]-->·      <!--[endif]-->     National Health Service (UK)

Trading Communities:

<!--[if !supportLists]-->·      <!--[endif]-->Textile, Clothing and Footwear (eBiz-TCF)

Service Providers:

<!--[if !supportLists]-->·      <!--[endif]-->eInvoicing (Tradeshift, Accountis, B2BRouter, SimplerInvoicing)

<!--[if !supportLists]-->·      <!--[endif]-->Logistics Services (Freightgate, Electra)

<!--[if !supportLists]-->·      <!--[endif]-->ePurchasing (Ozedi)

<!--[if !supportLists]-->·      <!--[endif]-->Online Retailing (Wehkamp)

<!--[if !supportLists]-->·      <!--[endif]-->Industry Groups (European eInvoice Service Providers Association)

Freight Logistics and Transport initiatives:

<!--[if !supportLists]-->·      <!--[endif]-->     eFreight (European Commission, DG MOVE)

<!--[if !supportLists]-->·      <!--[endif]-->     DTTN (Port of Hong Kong)

<!--[if !supportLists]-->·      <!--[endif]-->     CertOfOrigin (CrimsonLogic, Singapore)

<!--[if !supportLists]-->·      <!--[endif]-->     Electronic Freight Management (US Dept of Transport)

<!--[if !supportLists]-->12.                 <!--[endif]-->What is the UBL semantic data model?

Since its inception in 2002, UBL has taken a data model approach to designing standardized business documents (that can be expressed in XML).  In fact, all UBL document types are made up of components from a common data model we call the Common Library.

Using a semantic data model to describe the UBL Common Library has proven beneficial in several ways:

  • Business experts can work on the semantics of UBL business processes and their data requirements without needing to know XML technology.  This methodology is based on principles of business data analysis and modeling and uses the ebXML Core Component Technical Specification (ISO 15000-5) for its notation. 
  • The common data model ensures that the common semantics of the components are not lost when they are re-used in different contexts.  This means a UBL Address is always the same component wherever it appears.
  • It is possible to automatically generate from the UBL data models not only XML representations of document types such as XML Schema and RelaxNG but also non-XML representations such as ASN.1. This effectively ‘future-proofs’ UBL from changes in notations and syntaxes. 
  • Because the UBL semantic data model is similar to a relational data model, some user communities also use this data model for their own internal data representations.  Why re-invent common data structures from scratch when UBL has already designed a useful starting point?

To aid in understanding the UBL semantic data model UML, HTML and spreadsheet views are provided.  For more details:

OASIS UBL 2.1 specification Appendix C The UBL 2.1 Data Model (http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#A-THE-UBL-2.1-DAT...)

Having a foundation based on a common semantic data model provides long term sustainability for the growing number of communities who are implementing solutions based on UBL.  

<!--[if !supportLists]-->13.                 <!--[endif]-->Can I use UBL in other contexts?

Yes. Many communities have successfully built their own XML schema using UBL as a starting point. Some of these have subsequently been submitted to the UBL Technical Committee as candidates for inclusion in the official UBL standard.

Others have used the UBL’s Naming and Design Rules to create completely new messages in domains such as healthcare, education and customs.

<!--[if !supportLists]-->14.                 <!--[endif]-->How does UBL facilitate international trade?

One of the challenges with international trade in the digital era is trust. When businesses seek to develop or improve their international supply chains their primary consideration is trust in the complete trade system. Trust in the security, reliability and authenticity of the processes and partners they are dealing with.  Fundamental to establishing this trust are standards.  Using standards creates certainty… and certainty enables trust.

UBL's contribution to ensuring trust in international trade lies in the definition of a standard set of XML documents that provide the world with standards for the electronic versions of traditional business documents designed in a way that recognizes established commercial and legal practices.

Exchanging standard UBL documents ensures that the structures and semantics of the information being exchanged are consistent and interoperable with trading partners.

<!--[if !supportLists]-->15.                 <!--[endif]-->Can I use UBL in a Single Window environment?

The regulatory Single Window concept has been implemented in many developing countries around the world as a major platform for collaboration and information exchange among different government agencies involved in international trade. Recognized as effective trade facilitation measures in the recent Bali Ministerial Declaration and WTO Trade Facilitation Agreement, regulatory Single Window systems are increasingly being adopted by developed and developing countries.

However, international trade transactions require a number of different business processes (not just regulatory) that need to be coordinated.

European projects such as PEPPOL and e-Freight have demonstrated that UBL is a suitable standard for implementing the commercial, transport and freight logistic documents required by processes that complement regulatory Single Windows.

<!--[if !supportLists]-->16.                 <!--[endif]-->What is the relationship of UBL to ebXML?

The impetus to begin the UBL TC came from the desire of a number of ebXML participants to define a standard XML payload format for ebXML — that is, an XML counterpart to traditional EDI standards such as ANSI X12 and UN/EDIFACT. The ebXML suite of specifications, many of them now standardized as ISO 15000, provides a complete, next-generation XML-based infrastructure that enables EDI functionality over the free Internet.

UBL provides a standard data format for the messages to be exchanged in such an infrastructure. However, UBL is designed to be "agnostic" with respect to the infrastructure, and UBL messages can be used in a very wide range of functional contexts, from complex service-oriented architectures and cloud services to the simple exchange of documents via email.

<!--[if !supportLists]-->17.                 <!--[endif]-->What is the relationship of UBL to ebXML Core Components?

UBL was the first published data format specification produced in full conformance with UN/CEFACT's ebXML Core Components Technical Specification (CCTS) Version 2.01 - ISO TS15000-5:2005.

The UBL library consists of ebXML CCTS Business Information Entities (BIEs). UBL XML schemas are defined through the application of UBL Naming and Design Rules (NDRs) to an underlying data model mapped to the Core Component types.

For more information please see the UBL Committee Note on “UBL Conformance to ebXML CCTS” at:

http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/cn01/UBL-conformance-to-CCTS-v1.0-cn01.html

<!--[if !supportLists]-->18.                 <!--[endif]-->How does UBL support the European electronic invoicing Directive?

The European Directive on electronic invoicing in public procurement is a law enacted by the European parliament obliging public authorities in all EU member states to receive electronic invoices.  One aspect of this law is that a common European standard for the semantic data model of the core elements of an electronic invoice (the ‘European standard on electronic invoicing’) will be developed over the next few years.  When this is published, public sector contracting authorities will be obliged to receive and process electronic invoices formatted using a listed set of syntaxes that comply with the European semantic standard.

The work of the CEN BII Workshop will be a key foundation for the European standard for electronic invoicing and we expect UBL will be one of the syntaxes identified.

Will UBL be the standard European invoice format?

Yes (and no). There will not be a standard format or syntax for European invoices.  The European standard on electronic invoicing will not dictate what syntax or format is to be used, only the semantics of the required information.  

However, the semantic model of the CEN BII Post-award Profile will be a key foundation of the European semantics and as the combination of BII semantics and UBL format/syntax has been widely adopted in Europe, the expectation is that the established BII user community will be supported by the standard.  

While there will not be a European standard for invoice syntax, we expect that market forces will determine that UBL syntax is the most effective implementation of the European standard on electronic invoicing.

Is the Directive asking for yet another standard?

No, fortunately this work is already well established and the formal standardization can be seen as the next stage on the natural evolution of standards.  The obligation is for invoices to contain core information elements.  Defining what is required as core information is not a new piece of work.  These requirements will be based on existing standardization activities by groups such as the CEN BII Workshop and the semantic data model used in the BII Profiles for post-award processes.

What will a standard European electronic invoice look like?

We expect that various subsets of the UBL Invoice will be compliant to the new standard.  Valid subsets will contain the core elements of information (the semantics) defined by the European standard on electronic invoicing.  

Should I delay my electronic invoicing programme until we see what the European semantic standard is?

Not at all. This is unnecessary and counter to the intention of the Directive. The work of the CEN BII Workshop will be a key foundation on which to develop the European standard for electronic invoicing and UBL will be one of the syntaxes identified. Therefore, the current CEN BII Post-award Profile offers a suitable placeholder for the eventual European standard and so can be implemented with some confidence that this will comply with the Directive.

<!--[if !supportLists]-->19.                 <!--[endif]-->Can I use digital signatures to electronically sign UBL documents?

The UBL 2.1 electronic signature extension is the first "committee specified extension" and it incorporates the use of the W3C digital signature XML structure. This extension also can be used with UBL 2.0 documents.

The documentation of the electronic signature extension is found in the UBL 2.1 specification here:

http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#S-UBL-DIGITAL-SIGNATURE

... where one reads:

"These include specific provisions to use extensions supporting [XAdES], XML Advanced Electronic Signatures (ETSI TS 101 903), when the electronic signing of UBL documents is necessary to satisfy legal and technical requirements.”

In essence, support for digital signatures is straightforward, thus ensuring a compliant implementation in OASIS UBL:  digital signature users embed in the W3C digital signature structure http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/ all their information required for legal and technical requirements, and the UBL extension point scaffolding suitably embeds this W3C structure in any UBL instance providing full schema validation of the information.

As with all XML documents, electronic signature validation is done outside of schema validation.  Examples of the use of electronic signatures in UBL are found in these digitally-signed UBL documents:

<!--[if !supportLists]-->·      <!--[endif]-->http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Enveloped.xml

<!--[if !supportLists]-->·      <!--[endif]-->http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached.xml

<!--[if !supportLists]-->·      <!--[endif]-->http://docs.oasis-open.org/ubl/os-UBL-2.1/xml/UBL-Invoice-2.0-Detached-Signature.xml

 

 

 

<!--EndFragment-->

 

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

Hosted by:

OASIS