XMLandeBusiness.pptVIP

Analysis Resolve unknown elements with multiple standards Less human intervention and High flexibility on designing and processing documents Multilingual support A Lower barrier for trading partners with short-term relationships Miscellaneous conversions data format conversions MMddyyyy“ ? “yyyy/MM/dd” Conclusions The ReScUE XML/EDI model is implemented and works correctly File Systems ?? XML DB (ex. eXcelon) The maintenance of semantics in the metadata base can be greatly simplified Future Works RDF (Resource Description Framework) The complexity and the flexibility of using RDF requires further study * * * * * * * * * * * * * * * References Kammie Kayl, “ebXML: The Key Components”, /features/2001/09/ebxmlkey.html, 09/2001. David Webber and Anthony Dutton, “Understanding ebXML, UDDI, XML/EDI,” /feature_articles/2000_1107_miller.shtml, 10/2000. White papers from A ReScUE XML/EDI Model Eric Jui-Lin Lu and Chang-Chuan Wu Software-Practice Experience vol. 34, no. 3, Mar. 2004, pp. 315-338. Motivations To make EDI to work, we need pre-agreement on the format of interchanged data standard transaction sets 標準的訂定時間非常冗長 不適合變動快速的現代化商業環境 短期合作的組織（ex. outsourcing） pre-agreement is resource consuming. Motivations Latest EDI solutions a common data dictionary (ex. repository or ontology) a process of mapping between terms from the common data dictionary 以後，會有一個超級標準來”一統中原”？ Because XML allows organizations to design their own XML/EDI documents, it is common to receive XML/EDI documents with unknown elements. Also, language issue: ex. XML/EDI documents encoded in Bog5! Our Design Considered Factors many data dictionaries each element has metadata which can be associated with multiple data dictionaries encoding issue can be resolved practical semantic resolution scheme flexible and (semi-)automatic translation The ReScUE XML/EDI model Key Components Template repository The template repository is composed of reusable templates for document presentation and transformation. There