# US 2018/0322151 A1 · Content management in a travel management system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0322151 A1 - Document ID: US20180322151A1 - Status: Published application - Kind: A1 - Application number: 16/038,412 - Filed: 2018-07-18 - Published: 2018-11-08 - Earliest claimed: 2014-05-30 - Assignees: Amadeus S.A.S. - Applicants: Amadeus S.A.S. - Inventors: Vanessa Fontebride; Christel Charrat; Ludovic Le Sinq; Marion Francois; Pierre Gadeyne - Web page: https://patentgrep.com/patent/US20180322151A1 ## CPC - G06F 16/22: Indexing; Data structures therefor; Storage structures - G06F 16/80: of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML (content-based retrieval of web data G06F16/95) - G06F 16/955: using information identifiers, e.g. uniform resource locators [URL] - G06Q 10/02: Reservations, e.g. for tickets, services or events - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Methods, apparatus, and computer program products for managing content in a travel management system. A standard data element and a non-standard data element comprising the content are received from one or more content providers. A first data container for the standard data element and a second data container for the non-standard data element are created in an extended record data structure. The first data container includes a common record identifier and first data values for first attributes corresponding to the standard data element. The second data container includes the common record identifier and second data values corresponding to second attributes for the non-standard data element. The travel management system manages access to the first container and the second container in the extended record data structure based on the common record identifier. ## Claims ### Claim 1 A method of managing content in a travel management system, the method comprising: receiving, from one or more content providers, a data element comprising the content; receiving, from the one or more content providers, a first XSD structure description file, wherein one or more first XML, tags complying with the first XSD structure description file describe an attribute structure of the data element and one or more second XML tags complying with the first XSD structure description file describe one or more auxiliary constraints associated with the data element; creating a first data container for the data element in an extended record data structure; applying, based at least in part on the one or more second XML tags, the one or more auxiliary constraints to the first data container; transforming, through XSLT transformation, the first XSD structure description file into a second XSD structure description file using predefined mapping rules, wherein the first XSD structure description file and the second XSD structure description file define corresponding attributes; and creating, based at least in part on the second XSD structure description file, a second data container for the data element. ### Claim 2 (depends on 1) The method of claim 1 wherein the second data container comprises a plurality of keys and a plurality of values, each key corresponding to one of the attributes. ### Claim 3 (depends on 2) The method of claim 2 wherein one of the keys of the second data container defines a type for the data element. ### Claim 4 (depends on 2) The method of claim 2 wherein the second data container is a business object model, the business object model being self-implemented. ### Claim 5 (depends on 4) The method of claim 4 wherein the second data container comprises a self-serialization mechanism for serializing itself into an application target format, and a library embedding serialization information for serializing or deserializing the second data container. ### Claim 6 (depends on 1) The method of claim 1 wherein the data element comprises a first data element obtained from a travel provider system or a second data element obtained from a source other than the travel provider system. ### Claim 7 (depends on 1) The method of claim 1 further comprising: providing an application access to the second data container by generating a generic container to which is assigned a unique generic type, the generic container containing the second data container. ### Claim 8 (depends on 7) The method of claim 7 further comprising: introspecting the data element to permit the application to access the unique generic type contained in the generic container. ### Claim 9 (depends on 7) The method of claim 7 further comprising: providing the application access to the first data container by converting the data element and adding the converted data element to the generic container. ### Claim 10 (depends on 1) The method of claim 1 wherein the content may be received by a plurality of chained applications at a content aggregator, the data element is transmitted between the chained applications through messages carrying self-serialization information, and the second data container is stored in the extended record data structure when triggered by one of the chained applications. ### Claim 11 An apparatus for managing content in a travel management system, the apparatus comprising: at least one processor; and a memory coupled to the at least one processor and including instructions that, when executed by the at least one processor, cause the apparatus to: receive, from one or more content providers, a data element comprising the content; receive, from the one or more content providers, a first XSD structure description file, wherein one or more first XML tags complying with the first XSD structure description file describe an attribute structure of the data element and one or more second XML tags complying with the first XSD structure description file describe one or more auxiliary constraints associated with the data element; create a first data container for the data element in an extended record data structure; apply, based at least in part on the one or more second XML tags, the one or more auxiliary constraints to the first data container; transform, through XSLT transformation, the first XSD structure description file into a second XSD structure description file using predefined mapping rules, wherein the first XSD structure description file and the second XSD structure description file define corresponding attributes; and create, based at least in part on the second XSD structure description file, a second data container for the data element. ### Claim 12 (depends on 11) The apparatus of claim 11 wherein the second data container comprises a plurality of keys and a plurality of values, each key corresponding to one of the attributes of the data element. ### Claim 13 (depends on 12) The apparatus of claim 12 wherein one of the keys of the second data container defines a type for the data element. ### Claim 14 (depends on 12) The apparatus of claim 12 wherein the second data container is a business object model, the business object model being self-implemented. ### Claim 15 (depends on 14) The apparatus of claim 14 wherein the second data container comprises a self-serialization mechanism for serializing itself into an application target format, and a library embedding serialization information for serializing or deserializing the second data container. ### Claim 16 (depends on 11) The apparatus of claim 11 wherein the data element comprises a first data element obtained from a travel provider system or a second data element obtained from a source other than the travel provider system. ### Claim 17 (depends on 11) The apparatus of claim 11 wherein the instructions, when executed by the at least one processor, further cause the apparatus to: provide an application access to the second data container by generating a generic container to which is assigned a unique generic type, the generic container containing the second data container. ### Claim 18 (depends on 17) The apparatus of claim 17 wherein the instructions, when executed by the at least one processor, further cause the apparatus to: introspect the data element to permit the application to access the unique generic type contained in the generic container. ### Claim 19 (depends on 17) The apparatus of claim 17 wherein the instructions, when executed by the at least one processor, further cause the apparatus to: provide the application access to the first data container by converting the data element and adding the converted data element to the generic container. ### Claim 20 (depends on 11) The apparatus of claim 11 wherein the content may be received by a plurality of chained applications at a content aggregator, the data element is transmitted between the chained applications through messages carrying self-serialization information, and the second data container is stored in the extended record data structure when triggered by one of the chained applications. ### Claim 21 A computer program product for managing content in a travel management system, the computer program product comprising: a non-transitory computer readable storage medium; and instructions stored on the non-transitory computer readable storage medium that, when executed by a processor, cause the processor to: receive, from one or more content providers, a data element comprising the content; receive, from the one or more content providers, a first XSD structure description file, wherein one or more first XML tags complying with the first XSD structure description file describe an attribute structure of the data element and one or more second XML tags complying with the first XSD structure description file describe one or more auxiliary constraints associated with the data element; create a first data container for the data element in an extended record data structure; apply, based at least in part on the one or more second XML tags, the one or more auxiliary constraints to the first data container; transform, through XSLT transformation, the first XSD structure description file into a second XSD structure description file using predefined mapping rules, wherein the first XSD structure description file and the second XSD structure description file define corresponding attributes; and create, based at least in part on the second XSD structure description file, a second data container for the data element.