[go: up one dir, main page]

WO2009007754A1 - Outil d'interface utilisateur graphique - Google Patents

Outil d'interface utilisateur graphique Download PDF

Info

Publication number
WO2009007754A1
WO2009007754A1 PCT/GB2008/050556 GB2008050556W WO2009007754A1 WO 2009007754 A1 WO2009007754 A1 WO 2009007754A1 GB 2008050556 W GB2008050556 W GB 2008050556W WO 2009007754 A1 WO2009007754 A1 WO 2009007754A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
user interface
graphical user
interface tool
meta
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.)
Ceased
Application number
PCT/GB2008/050556
Other languages
English (en)
Inventor
Olaitan Malomo
Gary Thompson
Tom Martin
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.)
Integra SP Ltd
Original Assignee
Integra SP Ltd
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 Integra SP Ltd filed Critical Integra SP Ltd
Publication of WO2009007754A1 publication Critical patent/WO2009007754A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • G06F16/9024—Graphs; Linked lists
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually

Definitions

  • Analysing the relationships in data without the use of a graphical interface which can display data in the form of a graph, is difficult to achieve. Analysing the data as a list of rows and columns, as in spreadsheet programs such as Microsoft (RTM) Excel (RTM) requires focused concentration on the part of the analyst and is tiring and time consuming. To overcome this, graphs are used to provide a graphical representation of a data relationship network. However, at present the market place does not offer a graphical user interface tool to bring together system integration for retrieving required data relationship network data and for the graphical viewing of the data relationship network.
  • a thick client application operates on a desktop personal computer (PC) provides the technology to visualise in a graph the data that has been developed in a specific manner for a specific business domain. This means that the data structure and how the graph can be interacted with cannot be utilised outside of the specific business domain.
  • Desktop PC clients introduce the issue of needing to be deployed and maintained on each client machine, and in a large corporation with many users the deployment and maintenance can be an expensive approach. Deployment and maintenance can also be expensive on a per user basis in smaller corporations.
  • Using a browser-based technology overcomes the issue of deployment. This involves users connecting to a Universal Resource Locator (URL) and the graph being displayed in the browser window using technologies such as Scalable Vector Graphics (SVG) or Macromedia Flash (RTM).
  • SVG Scalable Vector Graphics
  • RTM Macromedia Flash
  • SVG Scalable Vector Graphics
  • RTM Macromedia Flash
  • SVG Scalable Vector Graphics
  • RTM Macromedia Flash
  • both of these technologies overcome some of the visualisation issue they do not address how to retrieve the data from a disparate set of source repositories.
  • restricting data shown to the user will be performed through the use of database queries with roundtrips to the database taking place to retrieve new, filtered data. This provides a usability issue to the end users while they wait for retrieval of data leading to frustration and a lack of desire to use the system, especially where users wish to change the filters applied.
  • a graphical user interface tool is provided that is operable (i) to use meta-data associated with entities in a network by analysing that meta-data to extract relationships between some or all of the entities in the network and then (ii) to graphically depict or display the relationships.
  • the graphical user interface tool may be one in which the tool uses meta-data to describe attributes of the extracted relationships.
  • the graphical user interface tool may be one in which the data stored in the data cache is filtered without further interrogation of the database server.
  • the graphical user interface tool may be one in which push technology is used to provide real time updates to the data cache.
  • the graphical user interface tool may be one in which the relationship extraction is metadata driven such that the meta-data allows a data relationship network to be described in terms of Node Types, Link Types, Link Styles, Subset Effects and Filters.
  • the graphical user interface tool may be one in which Subset Effects may be configured.
  • the graphical user interface tool may be one in which relationship extraction analysis is performed using meta-data driven queries.
  • the graphical user interface tool may be one in which configurable and flexible user interface components are provided for mapping a network of relationships.
  • the graphical user interface tool may be one in which the tool operates in a web browser environment.
  • the graphical user interface tool may be one in which new database server queries can be quickly added to an existing set of database server queries.
  • the graphical user interface tool of may be one in which all sources of information can be merged together either in a single set of data passed to the presentation server and to the user work station, or as multiple data sets which can be merged on the presentation server and the user work station.
  • the graphical user interface tool may be one in which a Network Analyser is used to retrieve data from the database server.
  • the graphical user interface tool may be one in which the Network Analyser uses hardware network topology meta data to provide high performance and targeted analysis of the data stored within the database server.
  • the graphical user interface tool may be one in which the data can expose explicit relationships through the data itself.
  • the graphical user interface tool of may be one in which some or all the data can have implied relationships where the relationships in data are exposed as a consequence of the data structure.
  • the graphical user interface tool may be one in which the approach is to use a query language such as SQL, XPath or XQuery to provide the definitions of the data relationships.
  • the graphical user interface tool of may be one in which a Node Type is configured by editing a meta-data description of the Node Type directly.
  • the graphical user interface tool may be one in which a Link Type is that of an implied relationship.
  • the graphical user interface tool may be one in which a Link Type is that of an explicit relationship.
  • the graphical user interface tool may be one in which the Link Styles have implied attributes for handling values for two ends of a Link.
  • the graphical user interface tool may be one in which extracted relationships are defined in terms of Edges, Nodes and Relations.
  • the graphical user interface tool may be one in which the tool provides filtering for Edges, Links, and Activity.
  • the graphical user interface tool may be one in which a user may interact with the data relationship network map data by deleting nodes or by moving nodes.
  • the graphical user interface tool may be one in which a client database stores the data in an XML structure and queries are performed using the XPath query language.
  • the graphical user interface tool may be one in which an initial request to the database server populates the data cache with all data required by the user.
  • the graphical user interface tool may be one in which an initial request to the database server is followed by a response, followed by the detailed data pushed to the data cache by the database server when the data is available.
  • the graphical user interface tool may be one in which sources of data and the configuration of accessing the sources of data are stored as meta-data in configuration files.
  • the graphical user interface tool may be one in which meta-data can be maintained dynamically at runtime by inserting new meta-data.
  • the graphical user interface tool may be one in which the Network Analyser is implemented using a key to identify Node Types and from these Node Types a set of queries or service requests are assigned to determine the sources of data to be queried.
  • the graphical user interface tool may be one in which Relation Query Groups provide a mechanism to group a set of logic that uses a seed node to find related nodes or links to other nodes.
  • the graphical user interface tool may be one in which the data source is one or more of Web Service, Database, flat file, or HTTP.
  • a graphical user interface tool is provided which is operable with a hardware system including a database server, a presentation server and a user work station, the graphical user interface tool combining data processing at the presentation server and at the user work station to analyse relationships in data retrieved from the database server and stored in a data cache, thereby generating a data relationship network.
  • a computer program product running as a graphical user interface tool that is operable (i) to use meta-data associated with entities in a network by analysing that meta-data to extract relationships between some or all of the entities in the network and then (ii) to graphically depict or display the relationships.
  • the computer program product may be one in which the computer program product runs as a graphical user interface tool which is operable with a hardware system including a database server, a presentation server and a user work station, the graphical user interface tool combining data processing at the presentation server and at the user work station when extracting relationships in the analysis of meta-data retrieved from the database server and stored in a data cache, the extracted relationships forming a data relationship network.
  • a graphical user interface tool which is operable with a hardware system including a database server, a presentation server and a user work station, the graphical user interface tool combining data processing at the presentation server and at the user work station when extracting relationships in the analysis of meta-data retrieved from the database server and stored in a data cache, the extracted relationships forming a data relationship network.
  • the computer program product may be one in which the extracted relationships are rendered as a data relationship network map.
  • the computer program product may be contained on a data carrier.
  • a method of presenting information is provided, the method including the step of using a graphical user interface tool as described in this document.
  • Figure 1 shows the use of a graphical user interface tool which is an example of the invention.
  • Figure 2 shows the concepts of Nodes, Edges and Relationships for a set of customers in a financial environment
  • Figure 3 shows example data exposing explicit relations for a link between two nodes.
  • Figure 4 shows an example of where implied relationships occur, where the structure of the data provides the definition of the links between nodes.
  • Figure 5 shows a user interface for configuring the attributes of an Altio (RTM) Graph node.
  • Figure 6 shows a meta-data description which may be edited for configuring the attributes of an Altio (RTM) Graph node.
  • Figure 7 shows an example of where a customer node is linked to two purchase nodes.
  • Figure 8 shows a graph resulting from the explicit data relationship network using XML data and the definitions from Figures 31, 32 and 33. This graph has two nodes and a link between them.
  • Figure 9 shows the attributes in the designer, associated with Figure 8.
  • Figure 10 shows the configuration meta data, associated with Figures 8 and 9.
  • Figure 11 shows an example of Link Types attributes as used in Altio (RTM) Graph.
  • Figure 12 shows the meta-data that is saved to the configuration file in the case of Figure
  • Figure 13 shows an example of grouping by Link Style which provides the addition of totalling all values for links of different Link Types.
  • Figure 14 shows an example of how Subset Effects can be modified at run time through a user interface to provide dynamic visual effects on the displayed graph.
  • Figure 16 shows an example in which Node A has four Edges and thus four relations to related Nodes.
  • the values from the Edges accumulate on the node, and the Edge totals are an accumulation of the link values in the edge.
  • Figure 17 shows an example of how a Filter Type can be configured through the user interface.
  • Figure 18 shows an example of how a Filter Type can be configured through the metadata.
  • Figure 19 shows an example of how the Value of a filter can be changed at runtime and be applied immediately to the graph.
  • Figure 20 shows an example of a case in which for a data relationship network graph, the data has been retrieved and then transmitted to the user where it is displayed. Once data is available, typically the user will want to interact with that data by applying filters that affect what will be shown in the graph.
  • Figure 21 shows how in a typical web based system, data is retrieved on request. This will mean that details about a Node or Link will need to be retrieved each time a user interacts with the data. This imposes further latency due to the server roundtrip time.
  • Figure 24 shows a data relationship network for which the common practice is to use
  • Figure 25 shows an example of the logical relationship of a Query Group to Relation
  • Figure 26 shows a configuration for a class AdhocRelationQueryGroup.
  • Figure 27 shows the concrete class implementation of the configuration of Figure 26.
  • Figure 28 shows the configuration of a Relation Query object for a database query, where two configurations of the same class take place.
  • Figure 29 shows an example of XML and the XPath statement that can be used to identify a data source for a node.
  • FIG. 30 shows an example of where there is an implied relation from PURCHASE to
  • Figure 31 shows example XML in which explicit relations are defined between node elements and link elements. This continues in Figure 32.
  • Figure 32 shows example XMT, in which explicit relations are defined between node elements and link elements, continued from Figure 31. This continues in Figure 33.
  • Figure 33 shows example XML in which explicit relations are defined between node elements and link elements, continued from Figure 32.
  • Figure 34 shows in Java an example of an interface declaration for a Query Group.
  • Figure 35 shows a Java declaration for a query group which is the same as for the
  • Relation Query interface shown in Figure 25.
  • Figure 36 shows an example of a concrete class implementing a database query. The text continues in Figure 37.
  • Figure 37 shows an example of a concrete class implementing a database query, where the text continues from Figure 36.
  • the Altio (RTM) Graph graphical user interface tool which is used to represent a data relationship network visually to a user is described. Contained in the description is a high level architectural description of significant components.
  • the Altio (RTM) Graph tool is designed to provide a graphical representation of data. However, at present the market place does not offer a generic tool to bring together system integration for retrieving required data and for the graphical viewing of this data.
  • One feature of the Altio (RTM) Graph tool is that it overcomes this limitation.
  • the Altio (RTM) Graph control provides a means to graphically present relationships between data items to an end user.
  • Altio (RTM) Graph is not specific to a particular business domain (eg. inside one particular firm) and provides the following features in a generic framework:
  • Altio (RTM) Graph provides a flexible user interface and once the initial data has been loaded from source locations the data can be filtered using zero latency techniques that do not require further roundtrips to the data source location.
  • Zero latency data analysis allows users to apply filters to the information displayed in the graph and has the effect of the filter being applied instantly, or after a very short time period. It also allows the filter to be removed without the need to perform a request to the server. Retrieval of the initial network data is provided through a framework that enables new database queries to be quickly added to enhance the network data without the need for a large development cycle or for modification to existing code. It is also possible to use standard Altiolive integration features to connect to web services, message queues etc.
  • Name an identifier that provides a unique reference for the link between two nodes
  • Node B Type, Node B Foreign Key, Node B Primary Key operate the same except that they refer to the B end of the link.
  • a Link Style can be used by multiple Link Types. This means different Link Types can be visually grouped together. This grouping by Link Style provides the addition of totalling all values for links of different Link Types ( Figure 13).
  • Link Style By introducing the concept of a Link Style and having the ability to have multiple Link Types and thus Link Styles between nodes necessitates the need to handle multiple types of links between nodes. This is achieved by being able to configure a Multi Match Link Style for the graph as a whole.
  • Node/Link Type the object in the graph that the Subset Effect is applied to (NODE or LINK).
  • Exclude From Filters prevents Nodes or Links from being considered for filters and so they will never be removed from the graph, filters in Altio (RTM) Graph are discussed later in this document.
  • Altio (RTM) Graph provides filtering for Edges, Links, and Activity - total, in, out and middle.
  • An Edge filter applies to the number of Edges (unique relations) on a node, the filter works by counting the unique Edges on a node.
  • a Link filter is applied to a relation between two nodes, and works by counting the number of individual links in that relationship and applying a filter to it.
  • Activity filters apply to Nodes and the total value of a Node based upon the values provided by Links. Links can have inbound and outbound values and a value with no direction.
  • a Node value is the total of all the Links contained in an Edge associated with the node — there will be a total value for in, out and middle values in a relationship.
  • a Filter Type can be configured through the user interface ( Figure 17) or through the meta-data (Figure 18). To provide effective usability the Value of a filter can be changed at runtime and be applied immediately to the graph ( Figure 19). The immediacy of applying filters provides one feature of the zero latency interaction provided by Altio (RTM) Graph.
  • Typical features expected in a rich user interface for a data relationship network graph are: • ability to interact with data, opening new windows, popup windows providing summary information
  • Zero latency user interaction requires the data to be cached within the client environment. To achieve maximum flexibility it is important to be able to dynamically manipulate the data within the cache. The manipulation of the data occurs either through user interaction or server changes being propagated to the client, and feedback to the user is instantaneous, or it occurs in a very short period of time.
  • the client data cache is only a subset of the data available on the server and will be specific to the graph being displayed but this will provide the user with all the information required to perform their duties.
  • the graph control interacts with the client data cache by applying filters or to display further details not already displayed. Filters affect the data made available for visualisation and displaying details makes use of data which exists in the client cache - all achieved without further requests to the server.
  • the Altio (RTM) Graph client database stores the data in an XML structure and queries are performed using the XPath query language.
  • the simplest approach involves an initial request to the server that populates the client database cache with all data required by the user ( Figure 22).
  • This initial request returns the data relationship network data required to draw the data relationship network graph and this will be the one and only hardware network request to the server unless a different set of data relationship network data is required.
  • the approach of improving user satisfaction by delivering the data in multiple packets pushed from the server provides the means by which the user will be able to access details without the need to initiate a new request to the server.
  • the same push technology is used to provide real time updates to the data cache ensuring clients have the latest data available.
  • Predictive analysis involves making use of predefined queries and requests to other systems for the required data.
  • the locations of the data and the structure of the queries as well as parameters required to execute are all pre-determined. This provides a predictive approach to analysing the data and will result in a pre-determined set of relationship types and node types, and a consistent data set based upon the same seed point.
  • This approach to analysing the data is efficient and provides the fastest response time to the user. The major risk to performance is the source of the data not being optimised to return data as quickly as possible.
  • Altio (RTM) Graph makes use of server side components to integrate with databases, web services and message queues. The support for this is primarily provided through Altiolive but a specific component for querying databases for relationships is provided in a component called the Network Analyser.
  • the sources of data and the configuration of accessing the systems are stored as meta-data in configuration files. This meta-data can be maintained statically by editing the configuration file or dynamically at runtime by inserting new meta-data into the running system. Static edits of the configuration means the changes are only available on system restart.
  • a wrapper object around service requests and queries provides a consistent means to execute an individual item of work without the need for the calling system to know what is being executed.
  • the wrapper objects known as a Relation Query, and their contained logic are grouped into Query Groups and these query groups are executed based upon the type of data used to seed the execution.
  • the declaration of the method contains two parameters.
  • the first provides the seed point for performing the execution of queries or service requests: the Node.
  • the second parameter to the method/event is a name value pair of additional parameters that can be used during execution of queries.
  • the name value pair parameter provides means to pass loosely coupled parameters, ensuring flexibility in the use of the method/event when implemented by a concrete class.
  • This concrete class is an actual implementation of the interface the concrete class performs, for example, the task of querying a database or executing a request to a web service but is not limited to these execution types.
  • Shown in Figure 25 is the logical relationship of a Query Group to Relation Query objects.
  • the diagram has a sequence of three queries followed by a parallel group of queries.
  • the combinations of queries and how they are executed provides a very flexible means of executing Predictive data relationship network analysis.
  • the Relation Query interface has the same declaration as the query group as shown in the Java declaration shown in Figure 35.
  • FIG. 36 An example of a concrete class implementing a database query could be as shown in Figures 36 and 37, where the text runs from Figure 36 into Figure 37.
  • the important factor is the configuration that provides the means to combine Relation Query objects into groups.
  • Altio (RTM) Graph uses SpringFramework (www.springframework.com) to provide the configuration by means of dependency injection.
  • a configuration for a class AdhocRelationQueryGroup is shown in Figure 26 with the concrete class implementation shown in Figure 27.
  • the example Java code shown in Figure 27 demonstrates the execution of Query Objects in a loop as a sequence of executable steps.
  • a graphical user interface tool uses meta- data to describe the attributes of a data relationship network as well as having the ability to combine server side and client side processing to analyse relationships in data to produce a data relationship network. This data relationship network is then rendered as a graph.
  • its features may include:
  • database server can be a single database server or a set of database servers.
  • the “database server” can be one or more of a broad set of data sources e.g. Web Service, Database, flat file, HTTP.
  • Altiolive is a platform for building and deploying rich internet, thin client applications that offer real-time bi-directional interactivity with enterprise data. Further reference may be made to US 2004-0117439 and US 2004-0148375, the contents of which are incorporated by reference.
  • Altiolive is a best fit for the presentation of, and interaction with, data-intensive information where immediacy is critical. Based on proprietary technology and industry standards such as Java and XML, AltioLive uses a small yet highly efficient client to communicate with the server and render XML screen layouts as Swing windows within the web browser. As a result, the user can enjoy features such as secure live data delivery, drag and drop, filtering and sorting - all in the browser.
  • the AltioLive platform integrates easily with existing application environments. It is both easy to connect to sources of information and simple to deploy over a hardware network via a URL.
  • the Altiolive client is designed to run in as many different browsers on as many different operating systems as required, meaning the user's applications can be deployed as widely as possible. Further information is given at http://www.altio.com/AltioLive.aspx.
  • the Extensible Markup Language is a general-purpose specification for creating custom markup languages. It is classified as an extensible language because it allows its users to define their own elements. XML's primary purpose is to facilitate the sharing of structured data across different information systems, particularly via the Internet, and it is used both to encode documents and to serialize data.
  • Hypertext Transfer Protocol is a communications protocol for the transfer of information on the internet and the World Wide Web. Its original purpose was to provide a way to publish and retrieve hypertext pages over the Internet.
  • HTTPS Hypertext Transfer Protocol over Secure Socket Layer
  • HTTPS Hypertext Transfer Protocol over Secure Socket Layer
  • URI Uniform Resource Identifier
  • URL indicates that HTTP is to be used, but with a different default Transmission Control Protocol (TCP) port and an additional encryption/ authentication layer between the HTTP and TCP.
  • TCP Transmission Control Protocol
  • IDE Integrated Development Environment
  • an integrated development environment is a software application that provides comprehensive facilities to computer programmers for software development.
  • An IDE normally consists of a source code editor, a compiler and/or interpreter, build automation tools, and (usually) a debugger. Sometimes a version control system and various tools are integrated to simplify the construction of a graphical user interface (GUI).
  • GUI graphical user interface
  • Many modern IDEs also have a class browser, an object inspector, and a class hierarchy diagram, for use with object oriented software development. IDEs are designed to maximise programmer productivity by providing tightly-knit components with similar user interfaces. This should mean that the programmer has much less mode switching to do than when using discrete development programs.
  • JDBC Java Database Connectivity
  • JDBC Java Database Connectivity
  • API application programming interface
  • REST Representational state transfer
  • SQL Structured Query Language
  • SQL Structured Query Language
  • RDBMS relational database management systems
  • SQL database schema creation and modification
  • SQL is a standard interactive and programming language for querying and modifying data and managing databases.
  • the core of SQL is formed by a command language that allows the retrieval, insertion, updating, and deletion of data, and performing management and administrative functions.
  • SQL also includes a Call Level Interface (SQL/CLI) for accessing and managing data and databases remotely.
  • SQL/CLI Call Level Interface
  • a Web Service is defined by the World Wide Web Consortium as "a software system designed to support interoperable Machine to Machine interaction over a network.” Web services are frequently just Web APIs that can be accessed over a hardware network, such as the Internet, and executed on a remote system hosting the requested services.
  • XML Path Language is a language for selecting nodes from an XML document.
  • XPath may be used to compute values (strings, numbers, or boolean values) from the content of an XML document.
  • the XPath language is based on a tree representation of the XML document, and provides the ability to navigate around the tree, selecting nodes by a variety of criteria. In popular use, an XPath expression is often referred to simply as an "XPath".
  • XQuery is a query language (with some programming language features) that is designed to query collections of XML data. It is semantically similar to SQL. XQuery provides the means to extract and manipulate data from XMT, documents or any data source that can be viewed as XML, such as relational databases or office documents. XQuery uses XPath expression syntax to address specific parts of an XML document.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Library & Information Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

Le domaine de l'invention concerne des outils d'interface utilisateur graphique, spécialement des outils d'interface utilisateur graphique qui récupèrent des données qui définissent la relation entre des entités dans un réseau. Le problème technique est d'analyser ces données pour générer des données qui définissent les relations de réseau et pour représenter ou afficher ensuite graphiquement ce réseau de relations de données pour former un graphe. La solution est de proposer un outil d'interface utilisateur graphique (i) pour utiliser des métadonnées associées à des entités dans un réseau par analyse de ces métadonnées pour extraire des relations entre certaines entités ou toutes les entités dans le réseau et, ensuite, (ii) pour représenter ou afficher graphiquement les relations.
PCT/GB2008/050556 2007-07-11 2008-07-09 Outil d'interface utilisateur graphique Ceased WO2009007754A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0713404.2 2007-07-11
GBGB0713404.2A GB0713404D0 (en) 2007-07-11 2007-07-11 Altio graph

Publications (1)

Publication Number Publication Date
WO2009007754A1 true WO2009007754A1 (fr) 2009-01-15

Family

ID=38461360

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2008/050556 Ceased WO2009007754A1 (fr) 2007-07-11 2008-07-09 Outil d'interface utilisateur graphique

Country Status (2)

Country Link
GB (2) GB0713404D0 (fr)
WO (1) WO2009007754A1 (fr)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8396867B2 (en) 2011-07-13 2013-03-12 Nimblecat, Inc. Identifying and ranking networked biographies and referral paths corresponding to selected qualifications
WO2013113028A1 (fr) * 2012-01-27 2013-08-01 Bottlenose, Inc. Orientation préférentielle de flux d'informations personnalisés regroupés et illustration graphique pluridimensionnelle associée
US8530173B2 (en) 2000-11-09 2013-09-10 The Brigham And Women's Hospital, Inc. Methods for treatment of cardiovascular disease
US8734769B2 (en) 2002-05-09 2014-05-27 The Brigham And Women's Hospital, Inc. 1L1RL-1 as a cardiovascular disease marker and therapeutic target
US8762302B1 (en) 2013-02-22 2014-06-24 Bottlenose, Inc. System and method for revealing correlations between data streams
US8832092B2 (en) 2012-02-17 2014-09-09 Bottlenose, Inc. Natural language processing optimized for micro content
GB2512574A (en) * 2012-01-27 2014-10-08 Bottlenose Inc Trending of aggregated personalized information streams and multi-dimensional graphical depiction thereof
US8990097B2 (en) 2012-07-31 2015-03-24 Bottlenose, Inc. Discovering and ranking trending links about topics
US9614807B2 (en) 2011-02-23 2017-04-04 Bottlenose, Inc. System and method for analyzing messages in a network or across networks
US9621428B1 (en) 2014-04-09 2017-04-11 Cisco Technology, Inc. Multi-tiered cloud application topology modeling tool
US9886553B2 (en) 2008-04-18 2018-02-06 Critical Care Diagnostics, Inc. Predicting risk of major adverse cardiac events
US10067146B2 (en) 2006-04-24 2018-09-04 Critical Care Diagnostics, Inc. Predicting mortality and detecting severe disease
US10203339B2 (en) 2006-05-01 2019-02-12 Critical Care Diagnostics, Inc. Diagnosis of cardiovascular disease

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1443396A2 (fr) * 2003-01-30 2004-08-04 Agilent Technologies, Inc. Systèmes et méthodes pour donner des visualisations de diagrammes de réseaux.
US20040239674A1 (en) * 2003-06-02 2004-12-02 Microsoft Corporation Modeling graphs as XML information sets and describing graphs with XML schema
US20070124291A1 (en) * 2005-11-29 2007-05-31 Hassan Hany M Method and system for extracting and visualizing graph-structured relations from unstructured text

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1443396A2 (fr) * 2003-01-30 2004-08-04 Agilent Technologies, Inc. Systèmes et méthodes pour donner des visualisations de diagrammes de réseaux.
US20040239674A1 (en) * 2003-06-02 2004-12-02 Microsoft Corporation Modeling graphs as XML information sets and describing graphs with XML schema
US20070124291A1 (en) * 2005-11-29 2007-05-31 Hassan Hany M Method and system for extracting and visualizing graph-structured relations from unstructured text

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MARC STREIT: "Interactive Visualizations of Complex Graphs", 23 April 2007 (2007-04-23), XP007905700, Retrieved from the Internet <URL:http://www.cescg.org/CESCG-2007/papers/Graz-Streit-Marc/Graz-Streit-Marc.pdf> [retrieved on 20080917] *
WENKE LEE: "Jadve: A Framework for Graph-Based Data Visualization Applications", 1999, XP007905718, Retrieved from the Internet <URL:http://www.cc.gatech.edu/~wenke/papers/Jadve.ps> [retrieved on 20080917] *

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9857379B2 (en) 2000-11-09 2018-01-02 The Brigham And Women's Hospital Inc. Methods for treatment of cardiovascular disease
US8871452B2 (en) 2000-11-09 2014-10-28 The Brigham And Women's Hospital, Inc. Methods for treatment of cardiovascular disease
US8530173B2 (en) 2000-11-09 2013-09-10 The Brigham And Women's Hospital, Inc. Methods for treatment of cardiovascular disease
US8748116B2 (en) 2002-05-09 2014-06-10 The Brigham And Women's Hospital, Inc. 1L1RL-1 as a cardiovascular disease marker and therapeutic target
US10788500B2 (en) 2002-05-09 2020-09-29 Brigham & Women's Hospital, Inc. IL1RL-1 as a cardiovascular disease marker and therapeutic target
US9851362B2 (en) 2002-05-09 2017-12-26 The Brigham & Women's Hosptial, Inc. 1L1RL-1 as a cardiovascular disease marker and therapeutic target
US8734769B2 (en) 2002-05-09 2014-05-27 The Brigham And Women's Hospital, Inc. 1L1RL-1 as a cardiovascular disease marker and therapeutic target
US10067146B2 (en) 2006-04-24 2018-09-04 Critical Care Diagnostics, Inc. Predicting mortality and detecting severe disease
US11016103B2 (en) 2006-04-24 2021-05-25 Critical Care Diagnostics, Inc. Predicting mortality and detecting severe disease
US10203339B2 (en) 2006-05-01 2019-02-12 Critical Care Diagnostics, Inc. Diagnosis of cardiovascular disease
US9886553B2 (en) 2008-04-18 2018-02-06 Critical Care Diagnostics, Inc. Predicting risk of major adverse cardiac events
US11170896B2 (en) 2008-04-18 2021-11-09 Critical Care Diagnostics, Inc. Predicting risk of major adverse cardiac events
US9614807B2 (en) 2011-02-23 2017-04-04 Bottlenose, Inc. System and method for analyzing messages in a network or across networks
US9876751B2 (en) 2011-02-23 2018-01-23 Blazent, Inc. System and method for analyzing messages in a network or across networks
US8396867B2 (en) 2011-07-13 2013-03-12 Nimblecat, Inc. Identifying and ranking networked biographies and referral paths corresponding to selected qualifications
WO2013113028A1 (fr) * 2012-01-27 2013-08-01 Bottlenose, Inc. Orientation préférentielle de flux d'informations personnalisés regroupés et illustration graphique pluridimensionnelle associée
GB2512574A (en) * 2012-01-27 2014-10-08 Bottlenose Inc Trending of aggregated personalized information streams and multi-dimensional graphical depiction thereof
US8832092B2 (en) 2012-02-17 2014-09-09 Bottlenose, Inc. Natural language processing optimized for micro content
US9304989B2 (en) 2012-02-17 2016-04-05 Bottlenose, Inc. Machine-based content analysis and user perception tracking of microcontent messages
US8938450B2 (en) 2012-02-17 2015-01-20 Bottlenose, Inc. Natural language processing optimized for micro content
US9009126B2 (en) 2012-07-31 2015-04-14 Bottlenose, Inc. Discovering and ranking trending links about topics
US8990097B2 (en) 2012-07-31 2015-03-24 Bottlenose, Inc. Discovering and ranking trending links about topics
US8909569B2 (en) 2013-02-22 2014-12-09 Bottlenose, Inc. System and method for revealing correlations between data streams
US8762302B1 (en) 2013-02-22 2014-06-24 Bottlenose, Inc. System and method for revealing correlations between data streams
US9621428B1 (en) 2014-04-09 2017-04-11 Cisco Technology, Inc. Multi-tiered cloud application topology modeling tool

Also Published As

Publication number Publication date
GB2450989A (en) 2009-01-14
GB0812547D0 (en) 2008-08-13
GB0713404D0 (en) 2007-08-22

Similar Documents

Publication Publication Date Title
WO2009007754A1 (fr) Outil d&#39;interface utilisateur graphique
US12164568B2 (en) Tool to build and store a data model and queries for a graph database
JP5864583B2 (ja) 複合イベント処理におけるパラメータ化されたクエリ／ビューへのサポート
US8700988B2 (en) Selectively interpreted portal page layout template
US8805834B2 (en) Extensible system and method for information extraction in a data processing system
US9052908B2 (en) Web application development framework
US9495429B2 (en) Automatic synthesis and presentation of OLAP cubes from semantically enriched data sources
US10296657B2 (en) Accessing objects in a service registry and repository
JP2009543166A (ja) ページによってページ・レイアウトを定義するためのコンピュータで実行される方法、コンピュータ・プログラム、およびデータ処理システム
JP2009543167A (ja) ページに関するページ・レイアウトを継承するためのコンピュータで実行される方法、コンピュータ・プログラム、およびデータ処理システム
CN103189866B (zh) 复杂事件处理中对于参数化的查询/视图的支持
WO2022146714A9 (fr) Système et procédé de création, de distribution et d&#39;utilisation dynamiques en temps réel d&#39;applications web personnalisables
Furche et al. Oxpath: A language for scalable, memory-efficient data extraction from web applications
AU2022203755B2 (en) Storage structure for pattern mining
Wu et al. Diel: Interactive visualization beyond the here and now
CN114860218A (zh) 一种低代码开发方法和装置
US20220236968A1 (en) Optimized data resolution for web components
US20130218893A1 (en) Executing in-database data mining processes
Liu et al. An XML-enabled data extraction toolkit for web sources
Kohn et al. DashQL--Complete Analysis Workflows with SQL
Čechák Using GraphQL for content delivery in Kentico Cloud
Steinkamp et al. HyDash: A dashboard for real-time business intelligence based on the hyPer Main memory database system
CA3160892C (fr) Structure de memoire pour l&#39;exploration de formes
Zdravković et al. Model-based, client-side integration of heterogeneous data from REST services
US11467860B2 (en) Optimized data resolution for web components

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08776191

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08776191

Country of ref document: EP

Kind code of ref document: A1