Patent ID: 7024413
Filing Date: 2006-04-04
Classification: G06F,Y10S

Abstract:
1. A method of mapping data formatted according to an Abstract Syntax Notation (“ASN.1”) data model into an Extensible Markup Language (“XML”) compliant data format, the method including an exploration/adaptation step for exploration of legacy data in a legacy database on a data resource, and a production step for generation of XML data out of the legacy data, wherein the method performs data format mapping between the legacy database and an XML-compliant representation of that data, and wherein the data format mapping takes ASN.1 constructs, and performs the following a steps; (a) mapping primitive ASN.1 types onto XML entities containing character data, wherein, for each primitive ASN.1 type, one entity is defined; (b) redefining fields of ASN.1 constructs, which are of a primitive ASN.1 type, as XML elements with an attribute of the corresponding entity; (c) mapping the ASN.1 ANY type onto an XML entity containing uninterpreted data; (d) mapping ASN.1 constants onto XML entities; (e) mapping the ASN.1 SEQUENCE construct onto an XML element containing individual elements of the SEQUENCE as an XML sequence, wherein the XML “?” operator is applied to optional ASN.1 elements; (f) mapping the ASN.1 SEQUENCE OF construct onto the XML repetition construct of ELEMENTS “*”; (g) mapping the ASN.1 SET construct onto the XML CHOICE construct, wherein the XML “?” operator is applied to optional ASN.1 elements in a SET; (h) mapping the ASN.1 SET OF construct onto the XML repetition construct of “*”; (i) mapping the ASN.1 CHOICE construct onto an XML element containing individual elements of the CHOICE as XML alternatives by using the “|” operator; (j) mapping the ASN.1 COMPONENTS OF construct as follows: (k) mapping each ASN.1 module having certain contents onto a specific XML Document Type Description by recursively applying the above rules to the module's contents, wherein each Document Type Description forms a separate name space and the ASN.1 constructs IMPORT and EXPORT are then modeled using qualified names for imported/exported XML elements, thus creating an XML specification.