Please use this identifier to cite or link to this item:
http://dspace.mediu.edu.my:8181/xmlui/handle/1721.1/7398Full metadata record
| DC Field | Value | Language |
|---|---|---|
| dc.creator | Tu, Steven | - |
| dc.creator | Madnick, Stuart | - |
| dc.creator | Wu, Luis | - |
| dc.date | 2004-12-10T19:15:42Z | - |
| dc.date | 2004-12-10T19:15:42Z | - |
| dc.date | 2004-12-10T19:15:42Z | - |
| dc.date.accessioned | 2013-10-09T02:39:47Z | - |
| dc.date.available | 2013-10-09T02:39:47Z | - |
| dc.date.issued | 2013-10-09 | - |
| dc.identifier | http://hdl.handle.net/1721.1/7398 | - |
| dc.identifier.uri | http://koha.mediu.edu.my:8181/xmlui/handle/1721 | - |
| dc.description | UccNet is a globally centralized B2B electronic data platform for storing trading product item information and hosted by the non-profit international standardization institute EAN-UCC. It is an emerging B2B data communication standard for the retail industry with significant potential impact. Many US retailers are requesting their international suppliers for compulsory subscription by the year-end of either 2004 or 2005 and many major IT software providers and consulting firms specialized in supply chain management are preparing packaged services/solutions for this imminent demand. In light of the increasing importance of UccNet on both the technology and application sides, this paper attempts to advance the following argument: Though UccNet establishes an architectural framework to resolve the many-to-many connectivity issue and data synchronization issue through a centralized product database and a uniform numbering system (i.e., Global Trade Item Numbering), there are context discrepancy issues remaining to be addressed. We show with a real case study that context discrepancy is inherent in the international trading applications where UccNet is intended to be used. Naturally, international trading partners tend to define and describe product item information differently. That difference, either due to the culture or the geographical location, is not considered in the original design of UccNet. As an example, the attribute "width" contained in the database schema of UccNet would be filled by a China-based supplier in 'meter' and yet be interpreted as 'feet' by the US retail buyer. We show how the Context Interchange Framework, operating under the rationale of local autonomy and speaking to the resolution of context mediation issue, can be nicely incorporated into the existing UccNet framework to constitute theoretically a more complete technical solution and practically a more useful B2B supply chain business solution. | - |
| dc.format | 364514 bytes | - |
| dc.format | application/pdf | - |
| dc.language | en_US | - |
| dc.relation | MIT Sloan School of Management Working Paper;4478-04 | - |
| dc.subject | B2B | - |
| dc.subject | Retail Supply-Chain | - |
| dc.subject | UccNet | - |
| dc.subject | Data Connectivity and Synchronization | - |
| dc.subject | Context Interchange | - |
| dc.subject | Data Semantics | - |
| dc.title | Improving UccNet-compliant B2B Supply-chain Applications Using a Context Interchange Framework | - |
| dc.type | Working Paper | - |
| Appears in Collections: | MIT Items | |
Files in This Item:
There are no files associated with this item.
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.