2010
DOI: 10.1145/1670679.1670681
|View full text |Cite
|
Sign up to set email alerts
|

A survey and analysis of electronic business document standards

Abstract: No document standard is sufficient for all purposes because the requirements significantly differ among businesses, industries, and geopolitical regions. On the other hand, the ultimate aim of business document interoperability is to exchange business data among partners without any prior agreements related to the document syntax and semantics. Therefore, an important characteristic of a document standard is its ability to adapt to different contexts, its extensibility, and its customization. The UN/CEFACT Cor… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
13
0

Year Published

2011
2011
2023
2023

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 28 publications
(13 citation statements)
references
References 6 publications
0
13
0
Order By: Relevance
“…The Object Management Group (OMG) in its Model-Driven Architecture (MDA) defines ''computation-independent'', ''platform-independent'', and ''platform-dependent'' as abstraction levels (OMG ORMS 2001). From a data modeling point of view, instantiations of the level of abstraction are ''conceptual '', ''logical'', and ''physical'' (Hoberman 2005;Jardine 1977). A conceptual model is typically directed at business users, since it clarifies the meaning of the most relevant objects, their attributes, and the relations of the business stakeholders given, such as department, organization, or industry (Hoberman et al 2009).…”
Section: Basic Conceptsmentioning
confidence: 99%
See 1 more Smart Citation
“…The Object Management Group (OMG) in its Model-Driven Architecture (MDA) defines ''computation-independent'', ''platform-independent'', and ''platform-dependent'' as abstraction levels (OMG ORMS 2001). From a data modeling point of view, instantiations of the level of abstraction are ''conceptual '', ''logical'', and ''physical'' (Hoberman 2005;Jardine 1977). A conceptual model is typically directed at business users, since it clarifies the meaning of the most relevant objects, their attributes, and the relations of the business stakeholders given, such as department, organization, or industry (Hoberman et al 2009).…”
Section: Basic Conceptsmentioning
confidence: 99%
“…In particular, the Reference Model Analysis Grid by Pawlowski and Kozlov is a methodology for assessing standards, with the broader Little research has been done so far on actually comparing different Semantic IS Standards. One of the few contributions is proposed by Kabak and Dogac (2010) who analyzed a number of Semantic IS Standards, among which are UN/EDIFACT, UBL 2.0, 5 and OAGIS BOD 9.0. 6 Overall, existing literature comprises valuable work regarding Semantic IS Standards.…”
Section: Framework For Semantic Is Standardsmentioning
confidence: 99%
“…The latter has specifically initiated the concept of core components, elements that can be used as the core and starting point of vertical semantic standards that make use of these core components (Folmer, Hinderer, & Otto, 2003;Van Blommestein, 2007 A horizontal case study dealing with collaborative planning, forecasting, and replenishment (CPFR) based on a standards point of view (amongst others) is present in current literature (Markus & Gelinas Jr., 2008). The survey and analysis of horizontal standards (Kabak & Dogac, 2010) included EDI, UN/CEFACT CCL, UBL 2.0, OAGIS BOD 9.0 and GS1 XML and with the exception of EDI, they all use the CCTS in some (different) way. Other differences between these standards include the document artifacts, the use of code lists, the use of name spaces, and the naming and design rules used (Kabak & Dogac, 2010).…”
Section: Horizontalsmentioning
confidence: 99%
“…The survey and analysis of horizontal standards (Kabak & Dogac, 2010) included EDI, UN/CEFACT CCL, UBL 2.0, OAGIS BOD 9.0 and GS1 XML and with the exception of EDI, they all use the CCTS in some (different) way. Other differences between these standards include the document artifacts, the use of code lists, the use of name spaces, and the naming and design rules used (Kabak & Dogac, 2010). Also important is the fact that there are major differences in how these standards do accommodate customization and extensibility.…”
Section: Horizontalsmentioning
confidence: 99%
See 1 more Smart Citation