EP2087416A2 - Système et procédé permettant de générer des comptes-rendus personnalisés - Google Patents

Système et procédé permettant de générer des comptes-rendus personnalisés

Info

Publication number
EP2087416A2
EP2087416A2 EP06838045A EP06838045A EP2087416A2 EP 2087416 A2 EP2087416 A2 EP 2087416A2 EP 06838045 A EP06838045 A EP 06838045A EP 06838045 A EP06838045 A EP 06838045A EP 2087416 A2 EP2087416 A2 EP 2087416A2
Authority
EP
European Patent Office
Prior art keywords
report
data
file
format
reports
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP06838045A
Other languages
German (de)
English (en)
Other versions
EP2087416A4 (fr
Inventor
Dharmendra Etwaru
Dennis Rossi Jr.
Jacob Friedman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Barclays Capital Inc
Original Assignee
Barclays Capital Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Barclays Capital Inc filed Critical Barclays Capital Inc
Publication of EP2087416A2 publication Critical patent/EP2087416A2/fr
Publication of EP2087416A4 publication Critical patent/EP2087416A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/06—Asset management; Financial planning or analysis

Definitions

  • the present invention relates to generating customized reports.
  • the present invention is directed to a system and method for generating customized reports.
  • Data is retrieved from one or more repositories.
  • the data is consolidated to form a data file.
  • Configuration information from a template file is applied to the data file to produce a report file.
  • One or more customized reports are generated based on the report file.
  • Fig. 1 is an exemplary mark-up language report
  • Fig. 2A illustrates an exemplary schema for report data
  • Fig. 2B illustrates an exemplary schema for style data
  • Fig. 3 illustrates exemplary schemas for report data
  • Fig. 4 is a flow diagram of a process of an exemplary embodiment of the present invention
  • Figs. 5 A and 5B are pages of an exemplary report generated in accordance with the present invention.
  • Fig. 6 illustrates an overview of a preferred embodiment of the inventive process
  • Fig. 7 illustrates an exemplary hierarchy for a business data file used in connection with an exemplary embodiment of the present invention
  • Fig. 8 illustrates an exemplary hierarchy for a report template file used in connection with an exemplary embodiment of the present invention
  • Fig. 9 provides an illustration of an embodiment of a data consolidator used in connection with an exemplary embodiment of the present invention
  • Fig. 10 provides an illustration of an embodiment of a report assembler used in connection with an embodiment of the present invention.
  • Fig. 11 is a flow chart illustrating a preferred embodiment of a method of the present invention.
  • a report markup language is used, based upon XML in the preferred embodiment, to fully describe a report and all the elements that make up a report (e.g., different sections, and the components that comprise each section, down to the level of each individual element). This language is also used to describe the different ways in which a report can be structured and formatted. Specifying each element of a report in XML, with the ability to easily manipulate it with XSLT, results in a report structure that is extensible and flexible.
  • the reporting engine can accept data from any data provider, and data providers can export information to any downstream system, as a result of the standard created. Because this standard is based on XML in the preferred embodiment, the data can be easily transported and manipulated, and the structure can be easily checked and enforced.
  • a business schema which describes the raw business data.
  • This schema drives the remainder of the process, through multiple steps of transformations of the business data, through to the actual rendering of reports.
  • the transformations include, e.g., addition of styles, labels, data types etc.
  • sub-schemas which are all driven by the business schema and describe how to add attributes to elements in the business schema. Transforming the business data in this way is extendable to any number of transformations in view of the fact that the system described herein provides a platform and a vocabulary to insert data points.
  • Report Header information 10 An exemplary report mark-up language is shown in Figure 1.
  • Report sections 15 and report components 20 are shown.
  • Reports that can be generated into a PDF can be considered to be made up of two main parts — the report data and the report configuration files. Each is defined by an XSD schema.
  • Figure 2A shows an exemplary XSD schema for report data
  • Figure 2B shows an exemplary XSD schema for style (i.e., one component of configuration) data. Any data sent to and used by the system should be validated against the data schema.
  • the schema for the report data accommodates and includes all the structures that are necessary to define a report, in the preferred embodiment.
  • Report configurations files, defined and stored in XML in accordance with its own schema, define the way in which a report will look and feel.
  • the style XML file defines items such as font size, font family, font color, and numerical format, for each of the elements in a report, which also has its own schema.
  • the layout XML file defines, in accordance with its own schema, items such as the sections that appear in a report, the order of each section, and the components that are available in each section.
  • the configuration XML file defines the configuration changes that a client may specify for a particular report. These would include, by way of example, the inclusion of a graph and type of graph, the number of columns to show in a section, the specific periods to show in a table, and whether to show or not show a carve out section.
  • a report template is a set of customized report configuration files.
  • a series of standard report templates are available to firm representatives, who have the option to choose from any of these templates from which to generate a report and, within each template, have the option to change some configuration settings.
  • XML data can be, e.g., easily consumed by other applications using .Net or Java, transported through http, stored in databases such as UDB or SQL Server, and manipulated and transformed through XSLT or XSL-FO.
  • any individual element can be formatted, transformed, manipulated and modified.
  • fonts can be changed, or the font size modified, and sections can be rearranged, simply by changing the XML file. Changes can be made at each stage of the report definition to provide complete flexibility.
  • labels can be changed for internationalization; data types can be changed for currency accommodation; and font sizes and colors can be edited on the fly for individual clients to accommodate the visibly impaired.
  • An individual firm representative can specify changes to a particular template.
  • a new template can be created and made available to all the firm representatives.
  • the report schema itself can be changed to incorporate and include new and future reporting sections, or new configuration options.
  • the data from those systems in order for the system to accept data from existing firm systems, the data from those systems must be transformed into a format and a schema that conforms to the report data defined schema using a data adapter.
  • a data adapter takes data from a spreadsheet and through a series of XSLT transformations, thereby creating an XML report data document that conforms to the defined schema.
  • Different Data Adapters i.e., unification platforms
  • One embodiment of the system includes a data combiner, which accepts data feeds from multiple sources and combines them into an XML data document.
  • the data for each section of a report may come from different data sources.
  • the data combiner takes the data for each section, keeps track of the data, and combines it into one XML data document, fully compliant with the defined XML data schema.
  • An embodiment of the system may also include a consolidator/pre-renderer to prepare the report data XML for rendering, and apply the report configuration XML files to it.
  • a consolidator/pre-renderer to prepare the report data XML for rendering, and apply the report configuration XML files to it.
  • the configuration files for that report template are applied to the XML data file. This means that the data file is transformed by applying each of the configuration files to it (style, layout, configuration files). However, the data itself is not changed; instead, style, layout and configuration information is attached to each element. This prepares the report file for rendering into, e.g., PDF format.
  • a report validator may be included to provide a mechanism for report validation. Before the xml document is sent to be rendered into a PDF, the report validator may run a series of checks on that file, which can include business logic, intra-report, or options checks. The validator can cross-foot totals and portfolio positions, by way of example, for consistency checks. Thus, the validator can programmatically inspect the data for visible inconsistencies, which is typically a human function. The streamlining that is yielded by engaging the XSD schemas makes this possible in large volumes as the customizations are not an impediment given that they are compliant to the master (i.e., report schema). When a data XML document ready to be rendered, a final transformation occurs.
  • a template is applied to the data document.
  • the data document is transformed by the template into an XSL-FO document, in the preferred embodiment.
  • This template is designed to transform an XML document that conforms to a specific schema.
  • This template is extensible and flexible to accommodate all current and future report sections, and all configuration options.
  • the XSL-FO document generated by the template and is transformed into a PDF document.
  • the system can be used to produce reports on an ad hoc or a batch basis.
  • data is delivered in aggregated data files.
  • An aggregated data file, or data file with data for multiple reports, is processed and rendered to produce reports in batch.
  • step 101 of the process data 100 retrieved from a number of different repositories is consolidated.
  • data comprises raw business data associated with an account.
  • An XML vocabulary file 102 is developed to describe each item of data and provide structure to the same.
  • Figures 5 A and 5B show a portion of an exemplary report that may be generated using the invention. While this report shows the final result of the process, it is used for purposes of identifying the raw business data elements and values.
  • “Asset Allocation” is a data element, which has four attributes associated with it (i.e., "Cash & Cash Equivalent”, “Fixed Income”, “Equity”, and "Hedge Fund”).
  • attributes e.g., "Market Value”
  • numerical values e.g., "27506”
  • numerical value "27506” is not associated with any formatting (e.g., dollar signs or commas) at this point in the process.
  • headings such as “Allocation” and “Performance (net of fee returns)", as shown in Figure 5 A, are not part of the business data 100 and, instead, are part of the template inserted at a later stage of the process.
  • step 201 of the process package, template and client configuration information 200 are added.
  • package information introduces the concept of an account and ownership of that account.
  • this data may describe the number of recipients of the report, and the name and address of the account owner.
  • Each client's package points to a particular template.
  • a template is a collection of instances of mark-up language driver files that dictate how the report is to be laid out.
  • a template defines the sections that are in the report (e.g., a page) and which components are in those sections (e.g., with reference to Figure 5B, "Investment Results", "Asset Allocation").
  • Configuration information is also implemented at this step of the process, allowing for even further detailed customization. Such information comprises a more granular list of choices that result from a given template. Configuration information may include instructions, e.g., to show only two periods of performance history; include a larger font size; round off amounts to nearest dollar; and only include dollar signs with totals.
  • a client relationship manager who knows each of his clients, and the manner in which such clients would want their reports rendered, can specify the same in connection with generating reports.
  • a client relationship manager who knows each of his clients, and the manner in which such clients would want their reports rendered, can specify the same in connection with generating reports.
  • style/layout/forniat components 300 are added.
  • Vocabularies 302 are defined to call out aspects of the data such as font, color, data format, and page breaks, by way of example. These components are interjected into an instance of the business data as it works its way through the assembly line.
  • the output 400 is comprised of an XML document that contains the business data 100, the package and configuration information 200, and the style/layout/format components 300.
  • the XML document is then rendered into an industry standard format (e.g., PDF), using commercially available software packages such as Assentis, as will be known to those skilled in the art.
  • Report configuration file 310 contains Report Options and Section Structure information.
  • Display configuration file 311 contains display configuration information such as styles, labels, and data types.
  • a Report Template file 313 is associated with each Sub Package file 312 and is composed of report configuration and display configuration information.
  • the Package 314 contains all the information necessary to generate a report and serves as the driver for the process.
  • Each Package 314 may contain multiple Sub Packages files 312.
  • Portfolios file 315 contains the list of accounts for each portfolio in a package.
  • the Process Controller 316 retrieves the Package 314 and then calls each of the sub components, starting with the Data Consolidator 317, to create a report.
  • Data consolidator 317 retrieves data from one or more Adapters 318, using information from Portfolios file 319, and combines all the data into a Business Data file 320. Each adapter is configured to retrieve data from a given system.
  • the Report Assembler 312 applies Report Configuration file 310 and Display Configuration file 311 information from the Report Template file 313 to the Business Data file 320 to produce a Report file 324.
  • Report Renderer 325 uses the Report file 324 to produce a Report PDF 326.
  • FIG 7 illustrates an exemplary hierarchy for the Business Data file 320 of Figure 6.
  • a Business Data file 320 is the unit at which reports are aggregated and delivered to clients.
  • a Business data file 320 is comprised of one or more Portfolio Report business data files 411 as shown in Package 314 and Portfolios file 315 of Figure 6.
  • Each Portfolio Report business data file is comprised of one or more different Report Sections 412 (e.g., Overview, Performance, Investment Results and Special Investments).
  • Figure 8 illustrates an exemplary hierarchy for the Report Template file 313 of Figure 6.
  • a Report Template file 313 contains the information necessary to customize a Portfolio Report as shown in Package 314 and Portfolios file 315 of Figure 6. It includes Report Configuration file 310 and Display Configuration file 311.
  • Report Configuration file 310 includes the report option and structure information. Options determine which report configuration options to use, such as which columns or periods to show, what type of graph to use, and which benchmark to show, by way of example. The options for each report section are stored in accordance with a report section/component hierarchy. Sections determine which report sections and components are to be included and in what order.
  • Display Configuration file 311 contains display and "look and feel" information, such as styles, data types, and labels, by way of example.
  • FIG 9 provides a more detailed illustration of a preferred embodiment of the Data Consolidator 317 of Figure 6.
  • Sub Package Definition file 611 is the driver file used by the Data Consolidator 317. It contains all the information necessary for the Data Consolidator 317 to retrieve data from different Data Adapters 318 and combine them into a Sub Package Business Data file 320
  • Sub Package Definition files 611 are typically comprised of multiple portfolios as shown in Portfolios file 315 of Figure 6, each with multiple accounts.
  • Each Data Adapter 318 retrieves data from a different Data Source 610.
  • the Data Consolidator 317 retrieves the Report Section business data 412 of Figure 7 and combines it into one Sub Package Business Data file 320, in the correct schema.
  • FIG 10 provides a more detailed illustration of a preferred embodiment of the Report Assembler 321 of Figure 6.
  • Each Sub Package Definition file 611 is associated with a Report Template file 313, which defines the styles and configuration options for a portfolio report.
  • the Sub Package Business Data file 320 contains the business data necessary to generate all the reports in a sub package.
  • the Report Template file 313 contains the customization information on a portfolio report level, to set report options, as well as report styles, formatting and labels, by way of example.
  • the Sub Package Report file 324 contains both the business data and the configuration and style information necessary to generate all the reports in a sub package.
  • Figure 11 is a flow chart illustrating a preferred embodiment of a method of the present invention for generating customized reports.
  • One or more standards for describing one or more of a structure of a report, report data and a style of a report are established in step 1100.
  • Data is retrieved from one or more repositories in step 1101.
  • the data is consolidated to form a data file in step 1102 using the standards.
  • Configuration information from a template file is applied to the data file to produce a report file in step 1103.
  • One or more customized reports are generated based on the report file in step 1104.
  • the report file is rendered to produce one or more reports in one or more of PDF format, HTML format, RTF format, MS Word format or SVG format, by way of example.
  • One or more of the foregoing steps may be performed by software running on a data processing apparatus.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un système et un procédé de génération de compte-rendu personnalisé. Les données sont récupérées dans un ou plusieurs référentiels. Les données sont consolidées pour former un fichier de données. Les informations de configuration provenant d'un fichier de modèles sont appliquées au fichier de données pour produire un fichier de compte-rendu. Des comptes-rendus personnalisés sont générés sur la base du fichier de compte-rendu.
EP06838045A 2006-11-17 2006-11-17 Système et procédé permettant de générer des comptes-rendus personnalisés Withdrawn EP2087416A4 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2006/044869 WO2008063164A2 (fr) 2006-11-17 2006-11-17 Système et procédé permettant de générer des comptes-rendus personnalisés

Publications (2)

Publication Number Publication Date
EP2087416A2 true EP2087416A2 (fr) 2009-08-12
EP2087416A4 EP2087416A4 (fr) 2011-02-23

Family

ID=39430205

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06838045A Withdrawn EP2087416A4 (fr) 2006-11-17 2006-11-17 Système et procédé permettant de générer des comptes-rendus personnalisés

Country Status (3)

Country Link
EP (1) EP2087416A4 (fr)
JP (1) JP2010510570A (fr)
WO (1) WO2008063164A2 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6090681B2 (ja) * 2012-04-13 2017-03-08 ゴールドマン，サックス アンド カンパニー スケーラブルな構造化データ配布のためのシステム及び方法
GB2507722A (en) * 2012-09-28 2014-05-14 Barclays Bank Plc Document management system taking actions based on extracted data
JP2015103007A (ja) * 2013-11-25 2015-06-04 株式会社野村総合研究所 運用レポート管理システムおよび運用レポート管理プログラム
US10467697B2 (en) 2016-04-18 2019-11-05 Laurent Bensemana Method and system for building an enhanced investment portfolio

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10042601A1 (de) * 1999-09-20 2001-05-10 Dell Products Lp Sprache für XML-Server-Seiten
WO2001084299A1 (fr) * 2000-05-01 2001-11-08 Avery Dennison Corporation Formulaires de personnalisation bases sur les parametres d'un modele
US20010051962A1 (en) * 2000-06-08 2001-12-13 Robert Plotkin Presentation customization
US20030018481A1 (en) * 2001-03-15 2003-01-23 Cheng Zhou Method and apparatus for generating configurable documents
WO2003010676A1 (fr) * 2001-07-24 2003-02-06 Avery Dennison Corporation Systeme et procede de production de documents personnalises et/ou individualises
GB2381340A (en) * 2001-10-27 2003-04-30 Hewlett Packard Co Document generation in a distributed information network
US20030144982A1 (en) * 2002-01-30 2003-07-31 Benefitnation Document component management and publishing system
WO2003075191A1 (fr) * 2002-03-01 2003-09-12 Speedlegal Holdings Inc Systeme d'assemblage de documents
US6763343B1 (en) * 1999-09-20 2004-07-13 David M. Brooke Preventing duplication of the data in reference resource for XML page generation
US20040187080A1 (en) * 1999-09-20 2004-09-23 Dell Products L.P. XML server pages language
US20050050444A1 (en) * 2003-09-03 2005-03-03 Vasey Philip E. Cross-reference generation
US20060020886A1 (en) * 2004-07-15 2006-01-26 Agrawal Subodh K System and method for the structured capture of information and the generation of semantically rich reports
US20060064428A1 (en) * 2004-09-17 2006-03-23 Actuate Corporation Methods and apparatus for mapping a hierarchical data structure to a flat data structure for use in generating a report
US20060242569A1 (en) * 2005-04-21 2006-10-26 Omega Blue, Inc. Automatic authoring and publishing system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003076676A (ja) * 2001-06-22 2003-03-14 Toyo Eng Corp 報告書作成を支援する装置、プログラムおよび方法
US20050114308A1 (en) * 2003-11-24 2005-05-26 International Business Machines Corporation User customizable reporting
US20050234886A1 (en) * 2004-04-16 2005-10-20 Karim Mohraz Report designer tool and method
US7613688B2 (en) * 2005-02-28 2009-11-03 Sap Ag Generating business warehouse reports
JP4819391B2 (ja) * 2005-04-27 2011-11-24 Ｎｅｃフィールディング株式会社 文書合成システム、文書合成方法、及びプログラム

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6763343B1 (en) * 1999-09-20 2004-07-13 David M. Brooke Preventing duplication of the data in reference resource for XML page generation
DE10042601A1 (de) * 1999-09-20 2001-05-10 Dell Products Lp Sprache für XML-Server-Seiten
US20040187080A1 (en) * 1999-09-20 2004-09-23 Dell Products L.P. XML server pages language
WO2001084299A1 (fr) * 2000-05-01 2001-11-08 Avery Dennison Corporation Formulaires de personnalisation bases sur les parametres d'un modele
US20010051962A1 (en) * 2000-06-08 2001-12-13 Robert Plotkin Presentation customization
US20030018481A1 (en) * 2001-03-15 2003-01-23 Cheng Zhou Method and apparatus for generating configurable documents
WO2003010676A1 (fr) * 2001-07-24 2003-02-06 Avery Dennison Corporation Systeme et procede de production de documents personnalises et/ou individualises
GB2381340A (en) * 2001-10-27 2003-04-30 Hewlett Packard Co Document generation in a distributed information network
US20030144982A1 (en) * 2002-01-30 2003-07-31 Benefitnation Document component management and publishing system
WO2003075191A1 (fr) * 2002-03-01 2003-09-12 Speedlegal Holdings Inc Systeme d'assemblage de documents
US20060036612A1 (en) * 2002-03-01 2006-02-16 Harrop Jason B Document assembly system
US20050050444A1 (en) * 2003-09-03 2005-03-03 Vasey Philip E. Cross-reference generation
GB2405730A (en) * 2003-09-03 2005-03-09 Business Integrity Ltd Cross-reference generation
US20060020886A1 (en) * 2004-07-15 2006-01-26 Agrawal Subodh K System and method for the structured capture of information and the generation of semantically rich reports
US20060064428A1 (en) * 2004-09-17 2006-03-23 Actuate Corporation Methods and apparatus for mapping a hierarchical data structure to a flat data structure for use in generating a report
US20060242569A1 (en) * 2005-04-21 2006-10-26 Omega Blue, Inc. Automatic authoring and publishing system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2008063164A2 *

Also Published As

Publication number Publication date
WO2008063164A3 (fr) 2009-05-07
WO2008063164A2 (fr) 2008-05-29
JP2010510570A (ja) 2010-04-02
EP2087416A4 (fr) 2011-02-23

Similar Documents

Publication Publication Date Title
US20080120323A1 (en) System and method for generating customized reports
US10423708B2 (en) RDX enhancement of system and method for implementing reusable data markup language (RDL)
US7415482B2 (en) XBRL enabler for business documents
CA2488477C (fr) Systeme et methode de traitement de la paie
AU2002257192B2 (en) Method and system for reporting XML data based on precomputed context and a document object model
US7836394B2 (en) Interactive, customizable display and analysis of electronically tagged financial information
US6850950B1 (en) Method facilitating data stream parsing for use with electronic commerce
US8307012B2 (en) Schema mapping and data transformation on the basis of a conceptual model
US20070078877A1 (en) XBRL data conversion
US20020184213A1 (en) Data instance transformation tool for transforming a source instance to a target instance
US20070203922A1 (en) Schema mapping and data transformation on the basis of layout and content
US20050080808A1 (en) Document creation system and method using knowledge base, precedence, and integrated rules
WO2007114938A2 (fr) Système et procédé de rendu de données financières
KR20050056123A (ko) 소프트웨어 애플리케이션에서의 네임스페이스 또는 스키마라이브러리 지원을 위한 프로그램 가능한 객체 모델
AU2002257192A1 (en) Method and system for reporting XML data based on precomputed context and a document object model
US20180077299A1 (en) Document output processing
US20100257443A1 (en) System and Process for Producing a Two-Layer Document, and a Two-Layer Document Produced Accordingly
Emmerich et al. Tigra-an architectural style for enterprise application integration
EP2087416A2 (fr) Système et procédé permettant de générer des comptes-rendus personnalisés
Ðurović et al. TOWARDS FULL DIGITIZATION OF THE FINANCIAL REPORTING–OVERVIEW OF THE FINANCIAL REPORTING LANGUAGES
Ryan et al. Package ‘quantmod’
CA2364295C (fr) Systeme d'analyse de donnees destine au commerce electronique
US20090024405A1 (en) System and method for controlling the generation and distribution of publications
Kreulich Publishing Workflows with XSL-FO
Board College of Arts and Sciences An Investigation of XML and XML Tools in Java

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20090507

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1133936

Country of ref document: HK

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20110124

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 17/00 20060101ALI20110118BHEP

Ipc: G06F 7/00 20060101AFI20080611BHEP

Ipc: G06F 17/30 20060101ALI20110118BHEP

17Q First examination report despatched

Effective date: 20110929

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: BARCLAYS CAPITAL INC.

REG Reference to a national code

Ref country code: HK

Ref legal event code: WD

Ref document number: 1133936

Country of ref document: HK

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20160601