---xCBL---
* DTD/Schema definitions for a product catalogue
* compiled by CommerceOne
Oversimplified Document Summary
* CatalogHeader
Administrative information about the catalog including its provider, and suppliers and other trading partners present in the catalog
* CatalogSchema
Optional information about the structure of products in the catalog
* CatalogData
Container for instances of products
---cXML---
* compiled by Ariba
* XML specifications for:
--Catalogs
--PunchOuts (dynamic catalogs)
* PunchOut gives you an alternative to static catalog files.
* PunchOut sites are live, interactive catalogs running on your Website.
* For PunchOut sites, procurement applications display a button instead of product or pricing details. When users click this button, their Web browsers display pages from your local Website. Depending on how you implement your pages, users can browse product options, specify configurations, and select delivery methods. When users are done selecting items, they click a button that returns the order information to the pro-curement application. The fully configured products and their prices appear within users’ purchase requisitions.
--POs
---ebXML---
What is ebXML about?
* set of specifications that together enable a electronic business framework
* vision of ebXML is to enable a global electronic marketplace where companies of any size and anywhere can conduct business with each other
* ebXML is a joint initiative of the United Nations (UN/CEFACT) and OASIS
What is ebXML?
* A standard way to describe a Business Process.
* A mechanism for registering and storing your Business Process and meta data via ebXML CPP (Collaboration Protocol Profile).
* Businesses can search registry.
* Businesses can find out about another business':
--Business Processes
--Business Service Interfaces to support Business Processes
--Business Messages used by these Business Service Interfaces
--Transport, Security, and Encoding Protocols
* A mechanism for registering the above.
* A mechanism for describing the execution of a business arrangement which can be derived from their registration via ebXML CPA.
* A Messaging Service framework that allows for communication between partners.
* A mechanism for configuring the messaging services to engage in agreed upon Business Process.
Scenario
* Company A registers their Business Processes in the registry with our software.
* Company B finds Company A in registry with our software.
* Company B submits proposed business arrangment to Company A's software (ours) interface.
* Company A accepts.
* Company A and B are ready to do business electronically.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The important difference between cXML Punch Outs and cXML catalogues is NOT that Punch Outs are dynamic. Both can be updated so both are "dynamic". The key difference is that Punch Outs catalogues are hosted on the seller side, as opposed to having catalogues hosted on the procurement system proper.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
---xCBL---
* DTD/Schema definitions for a product catalogue
* compiled by CommerceOne
Oversimplified Document Summary
* CatalogHeader
Administrative information about the catalog including its provider, and suppliers and other trading partners present in the catalog
* CatalogSchema
Optional information about the structure of products in the catalog
* CatalogData
Container for instances of products
---cXML---
* compiled by Ariba
* XML specifications for:
--Catalogs
--PunchOuts (dynamic catalogs)
* PunchOut gives you an alternative to static catalog files.
* PunchOut sites are live, interactive catalogs running on your Website.
* For PunchOut sites, procurement applications display a button instead of product or pricing details. When users click this button, their Web browsers display pages from your local Website. Depending on how you implement your pages, users can browse product options, specify configurations, and select delivery methods. When users are done selecting items, they click a button that returns the order information to the pro-curement application. The fully configured products and their prices appear within users’ purchase requisitions.
--POs
---ebXML---
What is ebXML about?
* set of specifications that together enable a electronic business framework
* vision of ebXML is to enable a global electronic marketplace where companies of any size and anywhere can conduct business with each other
* ebXML is a joint initiative of the United Nations (UN/CEFACT) and OASIS
What is ebXML?
* A standard way to describe a Business Process.
* A mechanism for registering and storing your Business Process and meta data via ebXML CPP (Collaboration Protocol Profile).
* Businesses can search registry.
* Businesses can find out about another business':
--Business Processes
--Business Service Interfaces to support Business Processes
--Business Messages used by these Business Service Interfaces
--Transport, Security, and Encoding Protocols
* A mechanism for registering the above.
* A mechanism for describing the execution of a business arrangement which can be derived from their registration via ebXML CPA.
* A Messaging Service framework that allows for communication between partners.
* A mechanism for configuring the messaging services to engage in agreed upon Business Process.
Scenario
* Company A registers their Business Processes in the registry with our software.
* Company B finds Company A in registry with our software.
* Company B submits proposed business arrangment to Company A's software (ours) interface.
* Company A accepts.
* Company A and B are ready to do business electronically.
The important difference between cXML Punch Outs and cXML catalogues is NOT that Punch Outs are dynamic. Both can be updated so both are "dynamic". The key difference is that Punch Outs catalogues are hosted on the seller side, as opposed to having catalogues hosted on the procurement system proper.