Method of externalizing legacy database in ASN.1-formatted data into XML format
AssigneeInternational Business Machines Corporation
InventorsCarl Binding, Stefan G. Hild, Daniela Bourges-Waldegg, Kjell Beisland, Andreas Schade
Life of this patent
Estimating the term…
Abstract
A computer-readable medium is encoded with a method of externalizing legacy data from a legacy database on a data resource into an Extensible Markup Language (“XML”)-compliant format where the format is specified by an automatically generated XML meta-description, thus enabling access and processing of legacy data by XML-compliant applications.
Claims26
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:
- for every COMPONENTS OF construct, creating an XML element which contains individual component elements, wherein the COMPONENTS OF optionally has an attribute that refers to the contained construct;
- and
- (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.
A method that automates the data format mapping between data in a legacy database on a data resource formatted according to an Abstract Syntax Notation (ASN.1) data model and Extensible Markup Language (“XML”)-compliant representations of that data, wherein the method comprises:
- (1) an exploration/adaptation step for exploration of the data resource, and
- (2) a mapping step for generation of XML data out of the legacy data wherein the data format mapping takes ASN.1 constructs, and performe the following 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:
- for every COMPONENTS OF construct, creating an XML element which contains individual component elements, wherein the COMPONENTS OF optionally has an attribute that refers to the contained construct;
- and
- (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.
A computer-readable medium encoded with 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 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:
- for every COMPONENTS OF construct, creating an XML element which contains individual component elements, wherein the COMPONENTS OF optionally has an attribute that refers to the contained construct;
- and
- (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.
A medium that automates the data format mapping between data in a legacy database on a data resource formatted according to an Abstract Syntax Notation data model and Extensible Markup Language (“XML”)-compliant representations of that data, wherein the method comprises:
- an exploration/adaptation step for exploration of the data resource, and
- a mapping step for generation of XML data out of the legacy data, and wherein the data format mapping takes ASN.1 constructs, and performe the following 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:
- for every COMPONENTS OF construct, creating an XML element which contains individual component elements, wherein the COMPONENTS OF optionally has an attribute that refers to the contained construct;
- and
- (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.
Dependencies are inferred from the claim text.