OASIS ebXML Core (ebCore) TC Public Documents
OASIS ebXML Core (ebCore) TC (Showing 10 of 21) | ||||||
Document Name | # | Size | State | Submitter | Date | Action |
---|---|---|---|---|---|---|
0 |
4K |
Draft |
Pim van der Eijk |
2011-03-11 |
||
0 |
263K |
Draft |
Pim van der Eijk |
2010-09-30 |
||
2 |
262K |
Draft |
Pim van der Eijk |
2010-08-18 |
||
Updated version based on Mary/Kim comments. /////// Updated version of this document set fixes an annoying typo (9738 vs 9735). /////// This package contains ODF, PDF and XHTML versions of the specification voted Commitee Draft 03 on July 9 2010, packaged for second (short) Public Review. | ||||||
1 |
268K |
Draft |
Pim van der Eijk |
2010-07-28 |
||
Updated version of this document set fixes an annoying typo (9738 vs 9735). /////// This package contains ODF, PDF and XHTML versions of the specification voted Commitee Draft 03 on July 9 2010, packaged for second (short) Public Review. | ||||||
0 |
269K |
Draft |
Pim van der Eijk |
2010-07-09 |
||
This package contains ODF, PDF and XHTML versions of the specification voted Commitee Draft 03 on July 9 2010, packaged for second (short) Public Review. | ||||||
0 |
67K |
Draft |
Pim van der Eijk |
2010-06-19 |
||
ebCore-PartyIdType-1.0 (CD2 updated after PR) This document is a revision of CD 2: - There was a Public Review comment that proposes to generalize the use of the ebCore Party ID Type, which I propose to accept. There is a new section 2.7 to cover this. - I've revised the ISO 20022 section. Previously it covered only the ISO 200222 Data Source Schemes, now it also covers the regular ISO 20022 Party Id types, such as BIC. - I've added a (non-normative) XBRL example. - Minor editorial updates. | ||||||
1 |
61K |
Draft |
Pim van der Eijk |
2010-04-11 |
||
A mechanism for the identification of business partners in XML business documents and XML message headers based on URN-based identifier types is required in many electronic business exchanges. This specification specifies a formal URN-based mechanism for referencing party types from the ISO 6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace. Sample applications include (but are not limited to): ebXML message headers; ebXML collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents; and the UN/CEFACT SBDH. | ||||||
0 |
61K |
Draft |
Pim van der Eijk |
2010-04-03 |
||
A mechanism for the identification of business partners in XML business documents and XML message headers based on URN-based identifier types is required in many electronic business exchanges. This specification specifies a formal URN-based mechanism for referencing party types from the ISO 6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace. Sample applications include (but are not limited to): ebXML message headers; ebXML collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents; and the UN/CEFACT SBDH. | ||||||
2 |
62K |
Draft |
Pim van der Eijk |
2010-03-29 |
||
0 |
61K |
Draft |
Pim van der Eijk |
2010-03-29 |
||
A mechanism for the identification of business partners in XML business documents and XML message headers based on URN-based identifier types is required in many electronic business exchanges. This specification specifies a formal URN-based mechanism for referencing party types from the ISO 6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace. Sample applications include (but are not limited to) ebXML message headers; ebXML collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents; and the UN/CEFACT SBDH. |