Patent Grant
11755602
Various embodiments relate generally to data science and data analysis, computer software and systems, and data-driven control systems and algorithms based on graph-based data arrangements, among other things, and, more specifically, to a computing platform configured to receive or analyze datasets in parallel by implementing, for example, parallel computing processor systems to correlate subsets of parallelized data from disparately-formatted data sources to identify entity data and to aggregate graph data portions, among other things.
Advances in computing hardware and software have ignited exponential growth in the generation of vast amounts of data due to increased computations and analyses in numerous areas, such as in the various scientific and engineering disciplines. Also, advances in conventional data storage technologies provide an ability to store an increasing amounts of generated data. Moreover, different computing platforms and systems, different database technologies, and different data formats give rise to “data silos” that inherently segregate and isolate datasets.
While conventional approaches are functional, various approaches are not well-suited to significantly overcome the difficulties of data silos. Organizations, including enterprises, continue strive to understand, manage, and productively use large amounts of enterprise data. For example, consumers of enterprise organizations have different levels of skill and experience in using analytic data tools. Data scientists typically create complex data models using sophisticated analysis application tools, whereas other individuals, such as executives, marketing personnel, product managers, etc., have varying levels of skill, roles, and responsibilities in an organization. The disparities in various analytic data tools, reporting tools, visualization tools, etc., continue to frustrate efforts to improve interoperability and usage of large amounts of data.
Further, various data management and analysis applications, such as query programming language applications and data analytic applications, may not be compatible for use in a distributed data architecture, such as a “cloud”-based computing platform. Hence, data practitioners generally may be required to intervene manually to apply derived formulaic data models to datasets, such as using local computing resources, which requires a burden to update and maintain data terms and definitions as well as storing relatively large amounts of data relying on a particular data format and database schema (e.g., relying on relational databases and relational table data formats).
Thus, what is needed is a solution for facilitating techniques to optimize data operations applied to datasets, without the limitations of conventional techniques.
Various embodiments or examples (“examples”) of the invention are disclosed in the following detailed description and the accompanying drawings:
Various embodiments or examples may be implemented in numerous ways, including as a system, a process, an apparatus, a user interface, or a series of program instructions on a computer readable medium such as a computer readable storage medium or a computer network where the program instructions are sent over optical, electronic, or wireless communication links. In general, operations of disclosed processes may be performed in any arbitrary order, unless otherwise provided in the claims.
A detailed description of one or more examples is provided below along with accompanying figures. The detailed description is provided in connection with such examples, but is not limited to any particular example. The scope is limited only by the claims, and numerous alternatives, modifications, and equivalents thereof. Numerous specific details are set forth in the following description in order to provide a thorough understanding. These details are provided for the purpose of example and the described techniques may be practiced according to the claims without some or all of these specific details. For clarity, technical material that is known in the technical fields related to the examples has not been described in detail to avoid unnecessarily obscuring the description or providing unnecessary details that may be already known to those of ordinary skill in the art.
As used herein, “system” may refer to or include the description of a computer, network, or distributed computing system, topology, or architecture implementing hardware or software, or both, using various computing resources that are configured to provide computing features, functions, processes, elements, components, or parts, without any particular limitation as to the type, make, manufacturer, developer, provider, configuration, programming or formatting language, service, class, resource, specification, protocol, or other computing or network attributes. As used herein, “software” or “application” may also be used interchangeably or synonymously with, or refer to, a computer program, software, program, firmware, or any other term that may be used to describe, reference, or refer to a logical set of instructions that, when executed, performs a function or set of functions in association with a computing system or machine, regardless of whether physical, logical, or virtual and without restriction or limitation to any particular implementation, design, configuration, instance, or state. Further, “platform” may refer to any type of computer hardware (hereafter “hardware”) or software, or any combination thereof, that may use one or more local, remote, distributed, networked, or computing cloud (hereafter “cloud”)-based computing resources (e.g., computers, clients, servers, tablets, notebooks, smart phones, cell phones, mobile computing platforms or tablets, and the like) to provide an application, operating system, or other computing environment, such as those described herein, without restriction or limitation to any particular implementation, design, configuration, instance, or state. Distributed resources such as cloud computing networks (also referred to interchangeably as “computing clouds,” “storage clouds,” “cloud networks,” or, simply, “clouds,” without restriction or limitation to any particular implementation, design, configuration, instance, or state) may be used for processing and/or storage of varying quantities, types, structures, and formats of data, without restriction or limitation to any particular implementation, design, or configuration.
As used herein, data may be stored in various types of data structures including, but not limited to databases, data repositories, data warehouses, data stores, or other data structures or memory configured to store data in various computer programming languages and formats in accordance with various types of structured and unstructured database schemas such as SQL, MySQL, NoSQL, DynamoDB™, etc. Also applicable are computer programming languages and formats similar or equivalent to those developed by data facility and computing providers such as Amazon® Web Services, Inc. of Seattle, Wash., FMP, Oracle®, Salesforce.com, Inc., or others, without limitation or restriction to any particular instance or implementation. DynamoDB™, Amazon Elasticsearch Service, Amazon Kinesis Data Streams (“KDS”)™, Amazon Kinesis Data Analytics, and the like, are examples of suitable technologies provide by Amazon Web Services (“AWS”). Another example of cloud computing services include the Google® cloud platform that may implement a publisher-subscriber messaging service (e.g., Google® pub/sub architecture). Yet in another example, cloud computing and messaging services may include Apache Kafka, Apache Spark, and any other Apache software application and platforms, which are developed and maintained by Apache Software Foundation of Wilmington, Del., U.S.A.
Further, references to databases, data structures, memory, or any type of data storage facility may include any embodiment as a local, remote, distributed, networked, cloud-based, or combined implementation thereof. For example, social networks and social media (e.g., “social media”) using different types of devices may generate (i.e., in the form of posts (which is to be distinguished from a POST request or call over HTTP) on social networks and social media) data in different forms, formats, layouts, data transfer protocols, and data storage schema for presentation on different types of devices that use, modify, or store data for purposes such as electronic messaging, audio or video rendering (e.g., user-generated content, such as deployed on YouTube®), content sharing, or like purposes. Data may be generated in various formats such as text, audio, video (including three dimensional, augmented reality (“AR”), and virtual reality (“VR”)), or others, without limitation, as electronic messages for use on social networks, social media, and social applications (e.g., “social media”) such as Twitter® of San Francisco, Calif., Snapchat® as developed by Snap® of Venice, Calif., Messenger as developed by Facebook®, WhatsApp®, or Instagram® of Menlo Park, Calif., Pinterest® of San Francisco, Calif., LinkedIn® of Mountain View, Calif., and others, without limitation or restriction. In various embodiments, the term “content” may refer to, for example, one or more of executable instructions (e.g., of an application, a program, or any other code compatible with a programming language), textual data, image data, video data, audio data, or any other data.
In some examples, data may be formatted and transmitted via electronic messaging channels (i.e., transferred over one or more data communication protocols) between computing resources using various types of data communication and transfer protocols such as Hypertext Transfer Protocol (“HTTP”), Transmission Control Protocol (“TCP”)/Internet Protocol (“IP”), Internet Relay Chat (“IRC”), SMS, text messaging, instant messaging (“TM”), File Transfer Protocol (“FTP”), or others, without limitation. As described herein, disclosed processes implemented as software may be programmed using Java®, JavaScript®, Scala, Python™, XML, HTML, and other data formats and programs, without limitation. Disclosed processes herein may also implement software such as Streaming SQL applications, browser applications (e.g., Firefox™) and/or web applications, among others. In some example, a browser application may implement a JavaScript framework, such as Ember.js, Meteor.js, ExtJS, AngularJS, and the like. References to various layers of an application architecture (e.g., application layer or data layer) may refer to a stacked layer application architecture such as the Open Systems Interconnect (“OSI”) model or others. As described herein, a distributed data file may include executable instructions as described above (e.g., JavaScript® or the like) or any data constituting content (e.g., text data, video data, audio data, etc.), or both.
In some examples, systems, software, platforms, and computing clouds, or any combination thereof, may be implemented to facilitate online distribution of subsets of units of any data, content, postings, electronic messages, and the like. In some cases, units of content, electronic postings, electronic messages, and the like may originate at social networks, social media, and social applications, or any other source of content.
Data sources 190, whether stored locally or remotely, may be accessed to provide any type of data in any format, such as structured data (e.g., data stored as data tables in relational databases accessible via, for example, SQL or other structured database languages), semi-structured data (e.g., XML-formatted data, metadata, spreadsheet data, etc.), and unstructured data (e.g., PDF documents, GitHub™ Jupyter Notebook data, text document data, email document data, website data, etc.).
In the example shown, collaborative dataset consolidation system 150 may be configured to include any combination of hardware and software to analyze, deduplicate, format, and resolve data representing identities of entities, the data being received from data sources 190 as parallelized data 110. In at least one instance, collaborative dataset consolidation system 150 may be configured to process data from data resources 190 in parallel (or substantially in parallel), for example, in real-time or near real-time. Collaborative dataset consolidation system 150 may include logic as hardware (e.g., multiple processors such as more than 200 to 1,600 core processors) and software, or any combination thereof, that may be configured to “massively parallel process” parallelized data 110 to analyze, deduplicate, format, and/or resolve data representing identities of entities as each of parallelized data streams 101a to 101n. In a non-limiting example, consider that collaborative dataset consolidation system 150 may be configured to access data with more than one thousand data sources 190 to identify 50 billion or more subsets of observation data (or units of observation data) during a time interval (e.g., 24 hours or less). Parallelized processing of data (e.g., raw data) from data sources 190 facilitates rapid and expeditious deduplication and consolidation of data to form units of observation data with which to resolve to identify unique entities, according to some examples. In one example, logic configured to implement dataset ingestion controller 130 and dataset attribute manager 141 may be replicated (not shown) to process each of parallelized data streams 101a to 101n in parallel, or substantially in parallel.
In the example shown, collaborative dataset consolidation system 150 may include a dataset ingestion controller 130 configured to remediate (e.g., “clean” and “prepare”) parallelized data 110 prior to conversion into another data format (e.g., a graph data structure) that may be stored locally or remotely such as a graph data node referring to an external data source, such as one of data sources 190. As shown, dataset ingestion controller 130 may also include a dataset analyzer 132 and a format converter 137. Also shown, dataset analyzer 130 may include an inference engine 134, which may include a data classifier 134a and a data enhancement manager 134b. Further to diagram 100, collaborative dataset consolidation system 150 is shown also to include a dataset attribute manager 141, which includes an attribute correlator 142 and a data derivation calculator 143. Dataset ingestion controller 130 and dataset attribute manager 141 may be communicatively coupled to exchange dataset-related data 147a and enrichment data 147b, whereby any of dataset ingestion controller 130 and dataset attribute manager 141 may exchange data from a number of sources (e.g., external data sources) that may include dataset metadata 103a (e.g., descriptor data or information specifying dataset attributes), dataset data 103b (e.g., reference data stored locally or remotely to access data in any local or remote data storage, such as data in data sources 190), schema data 103c (e.g., sources, such as schema.org, that may provide various types and vocabularies, glossaries, data dictionaries, and the like), and ontology data 103d from any suitable ontology and any other suitable types of data sources.
Diagram 100 depicts an example of a classifier 124a configured to classify any portion of parallelized data stream 101a to 101n as including a unit of observation data 102 associated with one or more attributes and data values, such as attribute data 104 and attribute 105. Observation data, or a unit thereof, can be data that may be classified as being associated with an entity, a concept, a topic, or a classification of data (e.g., a “class” of data), such as a “person” associated with attributes including a name, an address, etc., or a “product” associated with attributes including a product name, a manufacturer, a stock-keeping unit (“SKU”), etc., or a “service” associated with attributes including a name of purveyor of such services, etc., or any other entity. As an example, an “observation” or a unit of observation data may be refer to a data record that may include data representing attributes identifying a name, an address, a phone number, an email address, a customer number, a familial relationship, a gender, or any other attribute or characteristic of an object or individual entity. A unit of observation data 102 may be correlatable to (or matched to) any number of attributes, such as attributes 104 and 105 as well as other attributes and/or data values.
According to some examples, data representing a unit of observation data 102 may be computed to be associated with a hash value referring to a content-addressed node of a graph data arrangement, whereby similar or equivalent hash values may be implemented to consolidate (e.g., collapse, integrate, or deduplicate) multiple data representations of entities into graph data representing an entity. In some cases, observation data 102 may be referred to as an “observation fingerprint” (e.g., an electronically digital fingerprint, or a portion thereof) associated with an entity, whereby each grouping of observation data 102 and attributes 104 and 105 may be considered as a subset of data representing an entity—that when aggregated or clustered with other equivalent observation fingerprints—provides enriched graph data that may be used to describe or identify a particular entity (e.g., uniquely identifying a specific person). Note that the term “attribute” may refer to, or may interchangeable with, the term “property.”
Dataset ingestion controller 130 or dataset enrichment manager 134b may be configured to generate a content graph 106 (or a portion thereof) based on one or more subsets of observation data 102 and attribute data 104 and 105. In one example, content graph 106 may include at least one node representing observation data 102 and one or more other nodes each representing a data value (e.g., as attributes 104 and 105, or any other attribute or data value). In some examples, dataset enrichment manager 134b may be configured to correlate or predictively match groupings of content graph portions 106 to deduplicate redundant data and to consolidate attribute data to comprehensively generate enriched graph data that represents an entity. Hence, dataset enrichment manager 134b may be configured to consolidate datasets and portions thereof.
Further, any of dataset attribute manager 141 and attribute correlator 142 may be configured to correlate attribute data 104 and 105 of observation data 102 to correlate or match with other subsets of attribute data to form correlated subsets of parallelized data 110, each of which may be used to aggregate or cluster groups of observation data 102 to generate content graph 106 to characterize and identify an entity. Parallelized data 110 or observation data 102 with attribute data 104 and 105 may be transmitted to dataset attribute manager 141. As shown, dataset attribute manager 141 and attribute correlator 142 may be configured to correlate a first data value as attribute data 151 (“John Smith”) to a second data value as attribute data 153 (“Smith, J.”). Correlated attribute data 151 and 153 may be transmitted as enrichment data 147b to facilitate aggregating or clustering of content graph portions 106 at dataset enrichment manager 134b to form or modify at least a portion of enriched arrangement of graph data 160. Dataset attribute manager 141 and attribute correlator 142 may be configured to electronically interact to aggregate or cluster content graph portions 106 to identify an individual entity (e.g., a person or a product), and may be further configured to aggregate or cluster aggregated content graph portions 106 to identify a hierarchical entity to which individual entities may be associated (e.g., a household or a manufacturer). In some examples, dataset attribute manager 141 and attribute correlator 142 may be configured to electronically interact to correlate or match data representing observation fingerprints to derive a calculated identify of an entity from relatively large amounts (e.g., 50 Billion or more) of units of observation data 102.
According to some examples, dataset analyzer 132 and any of its components, including inference engine 134, may be configured to analyze datasets of parallelized data 110 to detect or determine whether ingested data has an anomaly relating to data (e.g., improper or unexpected data formats, types or values) or to a structure of a data arrangement in which the data is disposed. For example, inference engine 134 may be configured to analyze parallelized data 110 to identify tentative anomalies and to determine (e.g., infer or predict) one or more corrective actions. In some cases, inference engine 134 may predict a most-likely solution relative to other solutions for automatic resolution to clean and prepare data. In some examples, dataset analyzer 132 may be configured to correct an anomaly (e.g., to correct or confirm data, such as data that might refer to a U.S. state name, such as “Texas,” rather than “TX”). Dataset analyzer 132 and any of its components may be configured to perform an action based on any of a number of statistical computations, including Bayesian techniques, linear regression, natural language processing (“NLP”) techniques, machine-learning techniques, deep-learning techniques, etc. In some other examples, dataset analyzer 132 may be configured to identify and correct or quarantine invalid data values or outlier data values (e.g., out-of-range data values). Therefore, dataset analyzer 132 may facilitate corrections to observation data 102 or content graph data 106 “in-situ” or “in-line” (e.g., in real time or near real time) to enhance accuracy of atomized dataset generation (e.g., including triples) during the dataset ingestion and/or graph formation processes to form graph arrangement 160. In some cases, collaborative dataset consolidation system 150 may be configured to construct a repair graph including invalid or quarantined data to remediate the anomalous data for use in graph arrangement 160.
Subsequent or in parallel to performing corrective actions to remediate automatically issues related to datasets and data embodied in parallelized data 100, classifier 134a may be configured to identify and classify data as observation data 102, which may be linked to attribute data 104 and 105. Data enrichment manager 134b may be configured to generate and aggregate content graph portions 106 to identify an entity. Format converter 137 may be configured to convert any portion of parallelized data from data source 190 to graph-based data as observation data 102 and content graph data 106 at any time during ingestion, analyzation, identification, and deduplication of data. Format converter 137 may be configured to generate other graph-based data, such as ancillary data or descriptor data (e.g., metadata) that may describe other attributes associated with each unit of observation data 102. Ancillary or descriptor data can include data elements describing attributes of a unit of data, such as, for example, a label or annotation (e.g., header name) for a column, an index or column number, a data type associated with the data in a column, etc. In some examples, a unit of data may refer to data disposed at a particular row and column of a tabular arrangement.
In various examples, attribute correlator 142 may be configured to correlate inferred or implicit (as well as explicit) attributes with a dataset having attributes 151 and 153 to other attributes of other observation data 102, which may be implemented to join, aggregate, or cluster data to enrich an ingested dataset to form graph data 160. For example, attribute correlator 1763 can detect patterns in datasets in parallelized data streams 101a to 101n to correlate or match attributes to identify subsets of observation data 102 that may be correlatable to an identity of an entity. Attribute correlator 142 may be configured to analyze the data to detect patterns or data classifications that may resolve an issue, by “learning” or probabilistically predicting a dataset attribute through the use of Bayesian networks, clustering analysis, as well as other known machine learning techniques, deep-learning techniques, and the like. In some cases, data derivation calculator 143 may be configured to derive data computationally and/or predictively to add links among graph-based data nodes to enhance graph arrangement 160. In some examples, data derivation calculator 143 may be configured to enrich individual entity data by linking attributes imported from external feeds and calculating derived attributes algorithmically.
In one or more examples, one or more structural and/or functional elements described in
In view of the foregoing, structures and/or functionalities depicted in
One or more state classifiers 244a to 244n may be configured to determine a “state” or “class” associated with portions of data received as parallelized data 210 to determine a state, type, or class of observation data. One or more state classifiers 244a to 244n may be configured to implement any number of statistical analytic programs, machine-learning applications, deep-learning applications, and the like. For example, state classifier 244a may include any number of predictive data modeling algorithms 290a to 290c that may be configured to perform pattern recognition and probabilistic data computations. For example, predictive data modeling algorithms 290a to 290c may apply “k-means clustering,” or any other clustering data identification techniques to form clustered sets of data that may be analyzed to determine or learn optimal classifications of observation data and associated attributes and supplemental data (e.g., metadata) related thereto. In some examples, data classifier 234a and its components may be configured to detect patterns or classifications among datasets through the use of Bayesian networks, clustering analysis, as well as other known machine learning techniques or deep-learning techniques (e.g., including any known artificial intelligence techniques, or any of k-NN algorithms, linear support vector machine (“SVM”) algorithm, regression and variants thereof (e.g., linear regression, non-linear regression, etc.), Bayesian inferences and the like, including classification algorithms, such as Naïve Bayes classifiers, or any other statistical, empirical, or heuristic technique). In other examples, predictive data modeling algorithms 290a to 290c may include any algorithm configured to extract features and/or attributes based on classifying data or identifying patterns of data, as well as any other process to characterize subsets of data
As shown, predictive data model 290a may be configured to implement one of any type of neural networks (or any other predictive algorithm) as neural network model 290a, which may include a set of inputs 281 and any number of “hidden” or intermediate computational nodes 282 and 283, whereby one or more weights 287 may be implemented and adjusted (e.g., in response to training). Also shown, is a set of predicted outputs 284, such as terms defining a type of observation data. Predictive data model 290a may be configured to predict a class of “observation data,” whereby one or more of any output A1, . . . , Ax, Ay, . . . An may represent a class of observation data, such as a “name” (e.g., a person's name), an “address,” a “customer number,” a “date of birth,” an “email address,” a “telephone number,” or any other class of observation data that may be associated with attributes. In some examples, attributes may be input into inputs 281 to derive a class or type of observation data. As an example, data representing an address and a name may be applied to inputs 281 to identify an identity of an entity, such as a unique identity of a person.
As another example, inputs into state classifier 244b may determine affinity data that may indicate a degree of affiliation with another entity. For example, predictive data modeling algorithms 291a to 291c may be configured to predict whether an individual entity (e.g., a unique person, a unique product, etc.) is associated or affiliated with another entity. As such, inputs into predictive data modeling algorithms 291a to 291c may be configured to predict whether multiple entities, such as multiple people belong to the same household (or as a living unit) or multiple products originate from a common retailer or manufacturer. Output B1 may indicate a relatively high probability of association (e.g., a familial relationship exists) and output B2 may indicate a relatively low probability of association (e.g., a familial relationship does not exist). Other state classifiers, such as state classifier 244n, may generate data representing characterizations of parallelized data 210, including metadata, to determine a “context” in which observation data and associated attributes are modeled. A predicted context may facilitate enhanced accuracy in determining and resolving identities of entities.
Data outputs from state classifiers 244 and parallelized data 210 may be transmitted to dataset enrichment manager 234b, which may be configured to analyze ingested data relative to dataset-related data to determine correlations among dataset attributes of ingested data and other datasets 103b of
Referring back to
Further to diagram 200, dataset enrichment manager 234b is shown to include a content graph constructor 236 that is configured to form a content graph (or a portion thereof) that builds upon similar or equivalent units of observation data and subsets of attributes that may be correlatable (e.g., correlatable or matched to a threshold degree). In some examples, content graph constructor 236 may be configured to form a portion of graph data 260 (e.g., a sub-graph) based on correlated and deduplicated subsets of observation fingerprint data. As an example, observation fingerprint data may include data representing one or more attributes such as a first name, a first initial, a last name, a residential address, an email address, a customer number, etc. Enrichment data 247b may include data specifying matched or correlated attribute data with which to merge or cluster content graphs to form a comprehensive graph that includes data regarding an entity (e.g., a person, a product, a service, etc.). According to some implementations, content graph constructor 236 may be configured to cluster various units of observation data to form a cluster of data representing an identifiable entity.
Format converter 237 may be configured to convert data generated by data classifier 234a and dataset enrichment manager 236b into a graph-based data format. Also, format converter 237 may be configured to convert one or more of parallelized data 210, dataset-related data 247a, and enrichment data 247b into a graph-based data format compatible with enriched arrangement of graph data 260. In view of the foregoing, structures and/or functionalities depicted in
Feature extraction controller 322 may be configured to extract features as data representing correlated data 302 (e.g., as matched attribute data values). In at least one example, feature extraction controller 322 may include any number of natural language processing (“NLP”) algorithms configured to correlate attribute data, such as matching or correlating names of entities (e.g., names of persons, products, services, etc.) to determine an identity of an entity. Natural language processor algorithms 321a to 321c may be configured, for example, to tokenize sentences and words, perform word stemming, filter out stop or irrelevant words, or implement any other natural language processing operation to determine text-related features to correlate attribute data, such as text data.
In some examples, feature extraction controller 322 may include any number of predictive data modeling algorithms 390a to 390c that may be configured to perform pattern recognition and probabilistic data computations. For example, predictive data modeling algorithms 390a to 390c may apply “k-means clustering,” or any other clustering data identification techniques to form clustered sets of data that may be analyzed to determine or learn optimal correlation or matching of attribute data. In some examples, feature extraction controller 322 maybe configured to detect patterns or classifications among datasets through the use of Bayesian networks, clustering analysis, as well as other known machine learning techniques or deep-learning techniques (e.g., including any known artificial intelligence techniques, or any of k-NN algorithms, linear support vector machine (“SVM”) algorithm, regression and variants thereof (e.g., linear regression, non-linear regression, etc.), Bayesian inferences and the like, including classification algorithms, such as Naïve Bayes classifiers, or any other statistical, empirical, or heuristic technique). In other examples, predictive data modeling algorithms 390a to 390c may include any algorithm configured to extract features and/or attributes based on identifying patterns of attribute data, as well as any other process to characterize subsets of data.
In the example shown, feature extraction controller 322 may be configured to implement any number of statistical analytic programs, machine-learning applications, deep-learning applications, and the like. Feature extraction controller 322 is shown to have access to any number of predictive models, such as predictive models 390a, 390b, and 390c, among others. As shown, predictive data model 390a may be configured to implement one of any type of neural networks to similar or equivalent data representations of attributes. For example, as predictive models 390a, 390b, and 390c may be configured to identity or match names associated with observation data, as well as matching addresses (or any other attribute) associated with a name to identify an individual entity. A neural network model 390a may include a set of inputs 391 and any number of “hidden” or intermediate computational nodes 392, whereby one or more weights 397 may be implemented and adjusted (e.g., in response to training). Also shown is a set of predicted outputs 393, such as text terms defining a match among attribute values (e.g., matched names, matched addressed, matched SKUs, etc.), among any other types of outputs.
Feature extraction controller 322 may include a neural network data model configured to predict (e.g., extract) contextual or related text terms based on generation of vectors (e.g., word vectors) with which to determine degrees of similarity (e.g., magnitudes of cosine similarity) to, for example, establish compatibility between attribute data (to indicate a degree of equivalency), at least in some examples. In at least one example, feature extraction controller 322 may be configured to implement a “word2vec” natural language processing algorithm or any other natural language process that may or may not transform, for example, text data into numerical data (e.g., data representing a vector space).
According to some examples, feature extraction controller 322 may include algorithms configured to detect a degree of similarity between, for example, strings of texts to match names, addresses, etc. In some implementations, feature extraction controller 322 may be configured to implement edit distance algorithms and/or phonetic encoding algorithms, among others, to identify matched attribute values. For example, feature extraction controller 322 may implement an algorithm configured to determine the Levenshtein Distance to calculate a difference between data representing strings of alphanumeric text (e.g., to determine similarity or equivalency). In another example, a phonetic algorithm, such as a Soundex algorithm, may be implemented to detect a degree to which text strings or alphanumeric text strings may be similar or equivalent. In yet other examples, a Jaro-Winkler distance algorithm may be implemented to detect a degree of equivalency between or among text strings.
Thus, feature extraction controller 322 may be configured to identify correlated data 302 and generate extracted feature data 303, which may include one or more groups of data units 371 to 374, whereby each group of data units 371 to 374 may be associated with a unit of observations data or a unit of attribute data, or both. As example, consider that feature extraction controller 322 may be configured to identity correlatable data units 371 to 374 as attribute data that may match with other attribute data values. Here, data unit 371 may specify a “person” as a class of data indicative of a unit of predicted observation data 355a. Also, data units 372 to 374 may describe attribute values “name,” “address,” and “phone number” as entity attributes 355b.
In view of the foregoing, attribute correlator 342 may be configured to generate electronic messages including correlated data 302 and extracted feature data 303 that may be transmitted as enrichment data 247b to a content graph constructor, such as depicted in
Application stack 401 may include a collaborative dataset consolidation system application layer 450 upon application layer 440, which, in turn, may be disposed upon any number of lower layers (e.g., layers 403a to 403d). Collaborative dataset consolidation system application layer 450 may be configured to correlate subsets of parallelized data from disparately-formatted data sources to identify entity data and to aggregate graph data portions, as described herein. Further, collaborative dataset consolidation system application layer 450 and application layer 440 may be disposed on data exchange layer 403d, which may implemented using any programming language, such as HTML, JSON, XML, etc., or any other format to effect generation and communication of requests and responses among computing devices and computational resources constituting an enterprise, an entity, and/or a platform configured to correlate data and information expeditiously, such as information regarding products or services aligned with data in targeted data sources compatible with data integration. Data exchange layer 403d may be disposed on a service layer 403c, which may provide a transfer protocol or architecture for exchanging data among networked applications. For example, service layer 403c may provide for a RESTful-compliant architecture and attendant web services to facilitate GET, PUT, POST, DELETE, and other methods or operations. In other examples, service layer 403c may provide, as an example, SOAP web services based on remote procedure calls (“RPCs”), or any other like services or protocols (e.g., APIs, such as REST APIs, etc.). Service layer 403c may be disposed on a transport layer 403b, which may include protocols to provide host-to-host communications for applications via an HTTP or HTTPS protocol, in at least this example. Transport layer 403b may be disposed on a network layer 403a, which, in at least this example, may include TCP/IP protocols and the like.
As shown, collaborative dataset consolidation system application layer 450 may include (or may be layered upon) an application layer 440 that includes logic constituting a data catalog application layer 441, which is optional and referenced in
Any of the described layers of
At 502, parallelized data may be received from multiple disparate data sources in a computing system that includes multiple processors configured to facilitate massively parallel processing to extract attribute data to analyze and correlate data values associated with various units of attribute data in parallel. Further, raw data that may be ingested as parallelized data may be modified to remediate (e.g., “clean” and “prepare”) ingested data to be formatted or referenced as graph-based data in an arrangement of graph data, such as a knowledge graph. Remediation of data may be performed in accordance with rules or a set of predictively compliant data thresholds to identify valid data. As an example, data representing a state of Texas may be modified or normalized to reflect an alternative representation of TX. Further, data issues can be detected and corrected based on a lexical structure. Examples may include trimming quotes and leading/trailing whitespace(s), and correcting field misuse errors, such as modifying data fields first name and last name to correct for an invalid last name. For example, data fields {firstName: “John Smith” and lastName: “‘OCCUPANT”} may be modified to reflect data fields {firstName: “‘John” and lastName: “Smith”}, thereby removing “occupant” as an erroneous last name of an entity.
At 504, data representing a subset of parallelized data may be classified to identify observation data, such as a class or type of observation data. In some examples, data that may not comply with rules (e.g., based on conformance to an ontology, semantic-defined data, a data dictionary, a glossary, etc.) to determine noncompliant data or outlier data, which may be quarantined for further processing to, for example, generate a repair graph with which to integrate subsequently with a data arrangement on an enriched graph. In some examples, data records of individual entities may be quarantined if data includes (1) an absence of a first name and a last name, (2) addresses that do not conform postal standards (e.g., invalid zip codes and state identifiers), (3) email addresses that do not conform to an “id@domain.tld” format, (4) telephone numbers that do not conform with a country's standards (e.g., a U.S. phone number that does not include 10 digits), (5) blacklisted data references, and (6) other non-compliant data. Further at 504, overly-matched or overly-correlated data may be deemed as outliers that may complicate resolution of an identity of an entity, and thus may be quarantined or discarded. For example, residential addresses, email addresses, phone number and customer numbers that are linked to a large number of observation fingerprints, such as 1,000 instances, may be refer to an organization or a group of individual entities. Hence, such data may be of little or negligible value to determine an identity of a specific entity, such as an individual person, and may be quarantined or discarded (e.g., into a repair graph to receive subsequent processing to determine whether the associated data may be included to enrich an arrangement of graph data).
At 506, one or more content graphs in a graph data format may be constructed based on, for example, a class of observation data and one or more entity attributes, such as a name, an address, and other attribute data. A unit of observation data may be referred to as “observation fingerprint,” which may be an electronically digital fingerprint, or a portion thereof, associated with an entity.
At 508, data representing one or more entity attributes associated with observation data may be identified based on any number of sources. For example, a predictive data classifier or an attribute correlator may be configured to identify a set of terms (e.g., in a data dictionary) with which to search parallelized data or converted graph-based data. Identified attribute data may be linked or otherwise associated with a unit of observation data.
At 510, a subset of parallelized data may be correlated to other subsets of the parallelized data associated with a class or unit of observation data to form correlated subsets of parallelized data. For example, each data value associated with a corresponding attribute may be used to correlate, match, or otherwise detect equivalent units of attribute data associated with other units of observation data (e.g., other digital observation fingerprints). Data values of attribute data may be matched against other data values of other attribute data by an attribute correlator configured to identify and correlate patterns of data. According to some examples, correlation of subsets of parallelized data or associated attribute data values may include forming adjacency nodes linked to units of attributes in a content graph (e.g., a sub-graph). Multiple adjacency nodes may be linked together to cluster or aggregate similar or equivalent attribute data values that may constitute or relate to an individual entity. An adjacency node may be a portion of constructed content graph that connects or links an attribute (e.g., a name) and other indicator values (e.g., other attribute values) to capture data relationships comprehensively.
At 512, one or more units of observation data (and correlated attribute data) may be classified as an individual entity. For example, multiple units of observation data may be clustered together to form an enriched content graph that describes an individual entity, such as a person, a product, a service, or any other entity. In some implementations, correlated subsets of parallelized data may be clustered to identify an individual entity using data representing multiple adjacency node data linked together.
At 514, data representing multiple individual entities may be aggregated or clustered to form a set of entities based on correlated subsets of parallelized data. An individual entity may be aggregated or clustered with data representing other individual entities to form a group of clustered individual entities. For example, multiple individual entities may represent multiple persons having a familial relationship or a common geographic location (e.g., a household, a living unit, or a common residential address at which the entities reside).
In view of the foregoing, flow 500 may be configured to modify a graph data arrangement to enrich data stored in association with, for example, a knowledge graph.
Diagram 1050 depicts aggregation or clustering of observation data 1002 and 1004. For example, a dataset analyzer and/or an attribute correlator (or any other component of a collaborative dataset consolidation system) may be configured to form an association 1080 to specify that digital fingerprints of units of observation data 1002 and 1004 may resolve to represent an individual entity, such as a uniquely-identifiable person.
Diagram 1300 also depicts collaborative dataset consolidation system 1350 including or being configured to access data associated with data catalog controller logic 1352 to access, manage, and use a data catalog (e.g., an enterprise data catalog). Collaborative dataset consolation system 1350 may include or may be configured to access data associated with knowledge graph controller logic 1356 to access, manage, and use a knowledge graph data arrangement 1342. Thus, knowledge graph data arrangement 1342 may be implemented as a knowledge graph-as-a-service (e.g., “KGaas”). In some non-limiting examples, knowledge graph data arrangement 1342 may interact electronically with data catalog controller logic 1352 to form a network of concepts and semantic relationships describing data and metadata associated with the knowledge graph. Further, knowledge graph data arrangement 1342 may be configured to integrate knowledge, information, and data at a relatively large scale as a graph data mode, whereby knowledge graph data arrangement 1342 may include nodes representing tables, columns, dashboards, reports, business terms, users, etc.
Collaborative dataset consolation system 1350 may access data locally or remotely at any data source, such as data sources 1302 that may be accessible via APIs 1320. Examples of such data may include dataset metadata 1303a (e.g., descriptor data or information specifying dataset attributes), dataset data 1303b (e.g., reference data stored locally or remotely to access data in any local or remote data storage, such as data in data sources 1302), schema data 1303c (e.g., sources, such as schema.org, that may provide various types and vocabularies, glossaries, data dictionaries, and the like), and ontology data 1303d from any suitable ontology and any other suitable types of data source. Elements depicted in diagram 1300 may include structures and/or functions as similarly-named or similarly-numbered elements depicted in other drawings.
Data sources 1302 may be configured to provide (e.g., external data) as data assets 1310. Data sources 1302 may include any data storage or data arrangement, such as a data warehouse or a data lake 1304, one or more cloud services 1305, one or more data files and metadata files 1306, and any other external data or analytic data 1307. Data assets 1310 may include tabular data 1311, any type of file data 1312, dashboard and/or visualization data 1313, document data 1314 (e.g., a PDF document), code data 1315 (e.g., a portion of Python code or code-generated data, or JSON code), workbooks and/or notebook data 1316 (e.g., a Jupyter notebook, etc.), terminology data 1317, and any other data assets 1318.
Collaborative dataset consolation system 1350 may include a data project controller 1331 may be configured to provision and control a data project interface (not shown) as a computerized tools, or as controls for implementing computerized tools to procure, generate, manipulate, and share datasets, as well as to share query results and insights (e.g., conclusions or subsidiary conclusions) among any number of collaborative computing systems (and collaborative users of system 1350). In some examples, data project controller 1331 may be configured to provide computerized tools (or access thereto) to establish a data project, as well as invite collaboration and provide real-time (or near real-time) information as to insights to data analysis (e.g., conclusions) relating to a dataset or data project, as well as a data dictionary or glossary that may constitute at least a portion of data catalog 1355. Data project controller 1331 may be configured to identify a potential resolution, aim, goal, or hypothesis through, for example, application one or more queries against a dataset (e.g., canonical dataset). Data project controller 1331 may be configured to provide computerized tools (or access thereto) to provide an electronic “workspace” in which multiple datasets may be aggregated, analyzed (e.g., queried), and summarized through generation and publication of insights that may be integrated into knowledge graph data arrangement 1342. In view of the above, data project controller 1331 may be configured to control components of collaborative dataset consolidation system 1350 to provision computerized tools to facilitate interoperability of datasets (e.g., canonical datasets) with other datasets in different formats or with various external computerized analysis tools (e.g., via APIs 1322 and 1320), whereby external computerized analysis tools may be disposed external to collaborative dataset consolidation system 1350.
Examples of external computerized analysis tools include external statistical and visualization applications, such as Tableau®, that may be accessible as external data and visualization logic 1380. Further, data project controller 1331 may be configured to access, manage, build, and use data representing a data dictionary 1353 (e.g., a composite data dictionary), which may be managed electronically by data catalog controller logic 1352. In some examples, data representing data dictionary 1353 may be a subset of data representing a data catalog 1355. As data catalog 1355 may be disposed in a cloud-based computing system, data catalog may be referred to as a “data catalog-as-a-service,” at least in some examples. In some non-limiting examples, a data catalog 1355 and/or a data dictionary 1353 may include data or code, or both, that may be configured to create (e.g., automatically), manage, modify, use descriptor data that may identify metadata associated with datasets that can be implemented to enrich a graph-based data arrangement (e.g., knowledge graph data arrangement 1342). An example of a data dictionary may be implemented as described in U.S. patent application Ser. No. 15/985,702, filed on May 22, 2018, now U.S. Pat. No. 11,068,475 and titled “COMPUTERIZED TOOLS TO DEVELOP AND MANAGE DATA-DRIVEN PROJECTS COLLABORATIVELY VIA A NETWORKED COMPUTING PLATFORM AND COLLABORATIVE DATASETS,” which is hereby incorporated by reference.
Dataset query engine 1339 may be configured to receive a query (e.g., from computing device 1394b) to apply against a combined dataset, which may include at least a portion of knowledge graph data arrangement 1342. In some examples, a query may be implemented as either a relational-based query (e.g., in an SQL-equivalent query language) or a graph-based query (e.g., in a SPARQL-equivalent query language). Further, a query may be implemented as either an implicit federated query or an explicit federated query.
According to some examples, dataset query engine 1339 may be configured to access data associated with knowledge graph data arrangement 1342 as atomized datasets that may be formed as triples compliant with an RDF specification. Further, knowledge graph data arrangement 1342 may be stored in one or more repositories, at least one of which may be a database storage device formed as a “triplestore.” Note that in some cases, data referenced to knowledge graph data arrangement 1342 may also be of any data format, such as CSV, JSON, XML, XLS, MySQL, binary, RDF, or other similar or suitable data formats.
In some cases, computing platform 1500 or any portion (e.g., any structural or functional portion) can be disposed in any device, such as a computing device 1590a, mobile computing device 1590b, and/or a processing circuit in association with initiating any of the functionalities described herein, via user interfaces and user interface elements, according to various examples.
Computing platform 1500 includes a bus 1502 or other communication mechanism for communicating information, which interconnects subsystems and devices, such as processor 1504, system memory 1506 (e.g., RAM, etc.), storage device 1508 (e.g., ROM, etc.), an in-memory cache (which may be implemented in RAM 1506 or other portions of computing platform 1500), a communication interface 1513 (e.g., an
Ethernet or wireless controller, a Bluetooth controller, NFC logic, etc.) to facilitate communications via a port on communication link 1521 to communicate, for example, with a computing device, including mobile computing and/or communication devices with processors, including database devices (e.g., storage devices configured to store atomized datasets, including, but not limited to triplestores, etc.). Processor 1504 can be implemented as one or more graphics processing units (“GPUs”), as one or more central processing units (“CPUs”), such as those manufactured by Intel® Corporation, or as one or more virtual processors, as well as any combination of CPUs and virtual processors. Computing platform 1500 exchanges data representing inputs and outputs via input-and-output devices 1501, including, but not limited to, keyboards, mice, audio inputs (e.g., speech-to-text driven devices), user interfaces, displays, monitors, cursors, touch-sensitive displays, touch-sensitive input and outputs (e.g., touch pads), LCD or LED displays, and other I/O-related devices.
Note that in some examples, input-and-output devices 1501 may be implemented as, or otherwise substituted with, a user interface in a computing device associated with, for example, a user account identifier in accordance with the various examples described herein.
According to some examples, computing platform 1500 performs specific operations by processor 1504 executing one or more sequences of one or more instructions stored in system memory 1506, and computing platform 1500 can be implemented in a client-server arrangement, peer-to-peer arrangement, or as any mobile computing device, including smart phones and the like. Such instructions or data may be read into system memory 1506 from another computer readable medium, such as storage device 1508. In some examples, hard-wired circuitry may be used in place of or in combination with software instructions for implementation. Instructions may be embedded in software or firmware. The term “computer readable medium” refers to any tangible medium that participates in providing instructions to processor 1504 for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks and the like. Volatile media includes dynamic memory, such as system memory 1506.
Known forms of computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can access data. Instructions may further be transmitted or received using a transmission medium. The term “transmission medium” may include any tangible or intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 1502 for transmitting a computer data signal.
In some examples, execution of the sequences of instructions may be performed by computing platform 1500. According to some examples, computing platform 1500 can be coupled by communication link 1521 (e.g., a wired network, such as LAN, PSTN, or any wireless network, including WiFi of various standards and protocols, Bluetooth®, NFC, Zig-Bee, etc.) to any other processor to perform the sequence of instructions in coordination with (or asynchronous to) one another. Computing platform 1500 may transmit and receive messages, data, and instructions, including program code (e.g., application code) through communication link 1521 and communication interface 1513. Received program code may be executed by processor 1504 as it is received, and/or stored in memory 1506 or other non-volatile storage for later execution.
In the example shown, system memory 1506 can include various modules that include executable instructions to implement functionalities described herein. System memory 1506 may include an operating system (“O/S”) 1532, as well as an application 1536 and/or logic module(s) 1559. In the example shown in
The structures and/or functions of any of the above-described features can be implemented in software, hardware, firmware, circuitry, or a combination thereof. Note that the structures and constituent elements above, as well as their functionality, may be aggregated with one or more other structures or elements. Alternatively, the elements and their functionality may be subdivided into constituent sub-elements, if any. As software, the above-described techniques may be implemented using various types of programming or formatting languages, frameworks, syntax, applications, protocols, objects, or techniques. These can be varied and are not limited to the examples or descriptions provided.
In some embodiments, modules 1559 of
In some cases, a mobile device, or any networked computing device (not shown) in communication with one or more modules 1559 or one or more of its/their components (or any process or device described herein), can provide at least some of the structures and/or functions of any of the features described herein. As depicted in the above-described figures, the structures and/or functions of any of the above-described features can be implemented in software, hardware, firmware, circuitry, or any combination thereof. Note that the structures and constituent elements above, as well as their functionality, may be aggregated or combined with one or more other structures or elements. Alternatively, the elements and their functionality may be subdivided into constituent sub-elements, if any. As software, at least some of the above-described techniques may be implemented using various types of programming or formatting languages, frameworks, syntax, applications, protocols, objects, or techniques. For example, at least one of the elements depicted in any of the figures can represent one or more algorithms. Or, at least one of the elements can represent a portion of logic including a portion of hardware configured to provide constituent structures and/or functionalities.
For example, modules 1559 or one or more of its/their components, or any process or device described herein, can be implemented in one or more computing devices (i.e., any mobile computing device, such as a wearable device, such as a hat or headband, or mobile phone, whether worn or carried) that include one or more processors configured to execute one or more algorithms in memory. Thus, at least some of the elements in the above-described figures can represent one or more algorithms. Or, at least one of the elements can represent a portion of logic including a portion of hardware configured to provide constituent structures and/or functionalities. These can be varied and are not limited to the examples or descriptions provided.
As hardware and/or firmware, the above-described structures and techniques can be implemented using various types of programming or integrated circuit design languages, including hardware description languages, such as any register transfer language (“RTL”) configured to design field-programmable gate arrays (“FPGAs”), application-specific integrated circuits (“ASICs”), multi-chip modules, or any other type of integrated circuit. For example, modules 1559 or one or more of its/their components, or any process or device described herein, can be implemented in one or more computing devices that include one or more circuits. Thus, at least one of the elements in the above-described figures can represent one or more components of hardware. Or, at least one of the elements can represent a portion of logic including a portion of a circuit configured to provide constituent structures and/or functionalities.
According to some embodiments, the term “circuit” can refer, for example, to any system including a number of components through which current flows to perform one or more functions, the components including discrete and complex components. Examples of discrete components include transistors, resistors, capacitors, inductors, diodes, and the like, and examples of complex components include memory, processors, analog circuits, digital circuits, and the like, including field-programmable gate arrays (“FPGAs”), application-specific integrated circuits (“ASICs”). Therefore, a circuit can include a system of electronic components and logic components (e.g., logic configured to execute instructions, such that a group of executable instructions of an algorithm, for example, and, thus, is a component of a circuit). According to some embodiments, the term “module” can refer, for example, to an algorithm or a portion thereof, and/or logic implemented in either hardware circuitry or software, or a combination thereof (i.e., a module can be implemented as a circuit). In some embodiments, algorithms and/or the memory in which the algorithms are stored are “components” of a circuit. Thus, the term “circuit” can also refer, for example, to a system of components, including algorithms. These can be varied and are not limited to the examples or descriptions provided.
Although the foregoing examples have been described in some detail for purposes of clarity of understanding, the above-described inventive techniques are not limited to the details provided. There are many alternative ways of implementing the above-described invention techniques. The disclosed examples are illustrative and not restrictive.
This nonprovisional application is a continuation-in-part application of co-pending U.S. patent application Ser. No. 17/037,005, filed Sep. 29, 2020, and entitled “COLLABORATIVE DATASET CONSOLIDATION VIA DISTRIBUTED COMPUTER NETWORKS;”' U.S. patent application Ser. No. 17/037,005 is a continuation application of U.S. patent application Ser. No. 16,120,057, filed Aug. 31, 2018, now U.S. Pat. No. 10,853,376, and entitled, “COLLABORATIVE DATASET CONSOLIDATION VIA DISTRIBUTED COMPUTER NETWORKS;” U.S. patent application Ser. No. 16/120,057 is a continuation application of U.S. patent application Ser. No. 15/186,514, filed Jun. 19, 2016, now U.S. Pat. No. 10,102,258 and entitled, “COLLABORATIVE DATASET CONSOLIDATION VIA DISTRIBUTED COMPUTER NETWORKS;” THIS nonprovisional application is a —Continuation-In-Part—application of co-pending U.S. patent application Ser. No. 16/457,766 filed Jun. 28, 2019, and entitled “COMPUTERIZED TOOLS TO DISCOVER, FORM, AND ANALYZE DATASET INTERRELATIONS AMONG A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;”' U.S. patent application Ser. No. 16/457,766 is a continuation of U.S. patent application Ser. No. 15/454,923, filed on Mar. 9, 2017, now U.S. Pat. No. 10,353,911, and titled “COMPUTERIZED TOOLS TO DISCOVER, FORM, AND ANALYZE DATASET INTERRELATIONS AMONG A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 15/454,923 is a continuation-in-part application of U.S. patent application Ser. No. 15/186,514, filed on Jun. 19, 2016, now U.S. Pat. No. 10,102,258 and titled “COLLABORATIVE DATASET CONSOLIDATION VIA DISTRIBUTED COMPUTER NETWORKS;” THIS nonprovisional application is a —Continuation-In-Part—application of co-pending U.S. patent application Ser. No. 17/332,354 filed May 27, 2021 and titled, “EXTENDED COMPUTERIZED QUERY LANGUAGE SYNTAX FOR ANALYZING MULTIPLE TABULAR DATA ARRANGEMENTS IN DATA-DRIVEN COLLABORATIVE PROJECTS;” U.S. patent application Ser. No. 17/332,354 is a continuation application of U.S. patent application Ser. No. 16/036,834, filed Jul. 16, 2018, now U.S. Pat. No. 11,042,560, and titled, “EXTENDED COMPUTERIZED QUERY LANGUAGE SYNTAX FOR ANALYZING MULTIPLE TABULAR DATA ARRANGEMENTS IN DATA-DRIVEN COLLABORATIVE PROJECTS;” U.S. patent application Ser. No. 16/036,834 is a continuation-in-part application of U.S. patent application Ser. No. 15/186,514, filed on Jun. 19, 2016, now U.S. Pat. No. 10,102,258 and titled “COLLABORATIVE DATASET CONSOLIDATION VIA DISTRIBUTED COMPUTER NETWORKS;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/186,516, filed on Jun. 19, 2016, now U.S. Pat. No. 10,452,677 and titled “DATASET ANALYSIS AND DATASET ATTRIBUTE INFERENCING TO FORM COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/454,923, filed on Mar. 9, 2017, now U.S. Pat. No. 10,353,911 and titled “COMPUTERIZED TOOLS TO DISCOVER, FORM, AND ANALYZE DATASET INTERRELATIONS AMONG A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/926,999, filed on Mar. 20, 2018, now U.S. Pat. No. 11,016,931 and titled “DATA INGESTION TO GENERATE LAYERED DATASET INTERRELATIONS TO FORM A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/927,004, filed on Mar. 20, 2018, now U.S. Pat. No. 11,036,716 and titled “LAYERED DATA GENERATION AND DATA REMEDIATION TO FACILITATE FORMATION OF INTERRELATED DATA IN A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/439,908, filed on Feb. 22, 2017, now U.S. Pat. No. 10,452,975 and titled “PLATFORM MANAGEMENT OF INTEGRATED ACCESS OF PUBLIC AND PRIVATELY-ACCESSIBLE DATASETS UTILIZING FEDERATED QUERY GENERATION AND QUERY SCHEMA REWRITING OPTIMIZATION;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/985,702, filed on May 22, 2018, now U.S. Pat. No. 11,068,475, and titled “COMPUTERIZED TOOLS TO DEVELOP AND MANAGE DATA-DRIVEN PROJECTS COLLABORATIVELY VIA A NETWORKED COMPUTING PLATFORM AND COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/985,704, filed on May 22, 2018, now U.S. Pat. No. 11,068,847, and titled “COMPUTERIZED TOOLS TO FACILITATE DATA PROJECT DEVELOPMENT VIA DATA ACCESS LAYERING LOGIC IN A NETWORKED COMPUTING PLATFORM INCLUDING COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,834 is also a continuation-in-part application of U.S. patent application Ser. No. 15/985,705, filed on May 22, 2018, now U.S. Pat. No. 11,086,896, and titled “DYNAMIC COMPOSITE DATA DICTIONARY TO FACILITATE DATA OPERATIONS VIA COMPUTERIZED TOOLS CONFIGURED TO ACCESS COLLABORATIVE DATASETS IN A NETWORKED COMPUTING PLATFORM;” U.S. patent application Ser. No. 17/332,354 is also a continuation of U.S. patent application Ser. No. 16/036,836, filed Jul. 16, 2018, now U.S. Pat. No. 11,042,556, and titled, “LOCALIZED LINK FORMATION TO PERFORM IMPLICITLY FEDERATED QUERIES USING EXTENDED COMPUTERIZED QUERY LANGUAGE SYNTAX;” U.S. patent application Ser. No. 16/036,836 is a continuation-in-part application of U.S. patent application Ser. No. 15/186,514, filed on Jun. 19, 2016, now U.S. Pat. No. 10,102,258 and titled “COLLABORATIVE DATASET CONSOLIDATION VIA DISTRIBUTED COMPUTER NETWORKS;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/186,516, filed on Jun. 19, 2016, now U.S. Pat. No. 10,452,677 and titled “DATASET ANALYSIS AND DATASET ATTRIBUTE INFERENCING TO FORM COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/454,923, filed on Mar. 9, 2017, now U.S. Pat. No. 10,353,911 and titled “COMPUTERIZED TOOLS TO DISCOVER, FORM, AND ANALYZE DATASET INTERRELATIONS AMONG A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/926,999, filed on Mar. 20, 2018, now U.S. Pat. No. 11,016,931 and titled “DATA INGESTION TO GENERATE LAYERED DATASET INTERRELATIONS TO FORM A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/927,004, filed on Mar. 20, 2018, now U.S. Pat. No. 11,036,716, and titled “LAYERED DATA GENERATION AND DATA REMEDIATION TO FACILITATE FORMATION OF INTERRELATED DATA IN A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/439,908, filed on Feb. 22, 2017, now U.S. Pat. No. 10,452,975 and titled “PLATFORM MANAGEMENT OF INTEGRATED ACCESS OF PUBLIC AND PRIVATELY-ACCESSIBLE DATASETS UTILIZING FEDERATED QUERY GENERATION AND QUERY SCHEMA REWRITING OPTIMIZATION;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/985,702, filed on May 22, 2018, now U.S. Pat. No. 11,068,475, and titled “COMPUTERIZED TOOLS TO DEVELOP AND MANAGE DATA-DRIVEN PROJECTS COLLABORATIVELY VIA A NETWORKED COMPUTING PLATFORM AND COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/985,704, filed on May 22, 2018, now U.S. Pat. No. 11,068,847, and titled “COMPUTERIZED TOOLS TO FACILITATE DATA PROJECT DEVELOPMENT VIA DATA ACCESS LAYERING LOGIC IN A NETWORKED COMPUTING PLATFORM INCLUDING COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 16/036,836 is also a continuation-in-part application of U.S. patent application Ser. No. 15/985,705, filed on May 22, 2018, now U.S. Pat. No. 11,086,896, and titled “DYNAMIC COMPOSITE DATA DICTIONARY TO FACILITATE DATA OPERATIONS VIA COMPUTERIZED TOOLS CONFIGURED TO ACCESS COLLABORATIVE DATASETS IN A NETWORKED COMPUTING PLATFORM;” THIS nonprovisional application is a —Continuation-In-Part—application of co-pending U.S. patent application Ser. No. 17/333,914 filed May 28, 2021 and titled, “COMPUTERIZED TOOLS TO DEVELOP AND MANAGE DATA-DRIVEN PROJECTS COLLABORATIVELY VIA A NETWORKED COMPUTING PLATFORM AND COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 17/333,914 is a continuation-in-part application of U.S. patent application Ser. No. 15/186,514, filed on Jun. 19, 2016, now U.S. Pat. No. 10,102,258, and titled “COLLABORATIVE DATASET CONSOLIDATION VIA DISTRIBUTED COMPUTER NETWORKS,” U.S. patent application Ser. No. 17/333,914 is a continuation-in-part application of U.S. patent application Ser. No. 15/186,516, filed on Jun. 19, 2016, now U.S. Pat. No. 10,452,677, and titled “DATASET ANALYSIS AND DATASET ATTRIBUTE INFERENCING TO FORM COLLABORATIVE DATASETS,” U.S. patent application Ser. No. 17/333,914 is a continuation-in-part application of U.S. patent application Ser. No. 15/454,923, filed on Mar. 9, 2017, now U.S. Pat. No. 10,353,911, and titled “COMPUTERIZED TOOLS TO DISCOVER, FORM, AND ANALYZE DATASET INTERRELATIONS AMONG A SYSTEM OF NETWORKED COLLABORATIVE DATASETS,” U.S. patent application Ser. No. 17/333,914 is a continuation-in-part application of U.S. patent application Ser. No. 15/926,999, filed on Mar. 20, 2018, now U.S. Pat. No. 11,016,931, and titled “DATA INGESTION TO GENERATE LAYERED DATASET INTERRELATIONS TO FORM A SYSTEM OF NETWORKED COLLABORATIVE DATASETS,” and U.S. patent application Ser. No. 17/333,914 is a continuation-in-part application of U.S. patent application Ser. No. 15/927,004, filed on Mar. 20, 2018, now U.S. Pat. No. 11,036,716, titled “LAYERED DATA GENERATION AND DATA REMEDIATION TO FACILITATE FORMATION OF INTERRELATED DATA IN A SYSTEM OF NETWORKED COLLABORATIVE DATASETS;” THIS nonprovisional application is a —Continuation-In-Part—application of co-pending U.S. patent application Ser. No. 17/004,570 filed Aug. 27, 2020 and titled, “MATCHING SUBSETS OF TABULAR DATA ARRANGEMENTS TO SUBSETS OF GRAPHICAL DATA ARRANGEMENTS AT INGESTION INTO DATA-DRIVEN COLLABORATIVE DATASETS;” U.S. patent application Ser. No. 17/004,570 is a continuation application of U.S. patent application Ser. No. 16/137,292 filed on Sep. 20, 2018, now U.S. Pat. No. 10,824,637, and titled, “Matching Subsets of Tabular Data Arrangements to Subsets of Graphical Data Arrangements at Ingestion into Data Driven Collaborative Datasets,” U.S. patent application Ser. No. 16/137,292 is a continuation-in-part application of U.S. patent application Ser. No. 15/454,923, filed on Mar. 9, 2017, now U.S. Pat. No. 10,353,911, and titled “Computerized Tools To Discover, Form, And Analyze Dataset Interrelations Among A System Of Networked Collaborative Datasets,” U.S. patent application Ser. No. 16/137,292 is also a continuation application of U.S. patent application Ser. No. 15/926,999, filed on Mar. 20, 2018, now U.S. Pat. No. 11,016,931, and titled “Data Ingestion To Generate Layered Dataset Interrelations To Form A System Of Networked Collaborative Datasets,” U.S. patent application Ser. No. 16/137,292 is also a continuation application of U.S. patent application Ser. No. 15/927,004, filed on Mar. 20, 2018, now U.S. Pat. No. 11,036,716, and titled “Layered Data Generation And Data Remediation To Facilitate Formation Of Interrelated Data In A System Of Networked Collaborative Datasets,” U.S. patent application Ser. No. 16/137,292 is also a continuation application of U.S. patent application Ser. No. 15/985,702, filed on May 22, 2018, now U.S. Pat. No. 11,068,475, and titled “Computerized Tools To Develop And Manage Data-Driven Projects Collaboratively Via A Networked Computing Platform And Collaborative Datasets,” U.S. patent application of Ser. No. 16/137,292 is also a continuation application of U.S. patent application Ser. No. 15/985,704, filed on May 22, 2018, now U.S. Pat. No. 11,068,847, and titled “Computerized Tools To Facilitate Data Project Development Via Data Access Layering Logic In A Networked Computing Platform Including Collaborative Datasets;” all of which are herein incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5845285 | Klein | Dec 1998 | A |
| 6144962 | Weinberg et al. | Nov 2000 | A |
| 6317752 | Lee et al. | Nov 2001 | B1 |
| 6466933 | Huang | Oct 2002 | B1 |
| 6529909 | Bowman-Amuah | Mar 2003 | B1 |
| 6768986 | Cras et al. | Jul 2004 | B2 |
| 6961728 | Wynblatt et al. | Nov 2005 | B2 |
| 7080090 | Shah et al. | Jul 2006 | B2 |
| 7143046 | Babu et al. | Nov 2006 | B2 |
| 7146375 | Egilsson et al. | Dec 2006 | B2 |
| 7680862 | Chong et al. | Mar 2010 | B2 |
| 7702639 | Stanley et al. | Apr 2010 | B2 |
| 7761407 | Stern | Jul 2010 | B1 |
| 7818352 | Krishnamoorthy et al. | Oct 2010 | B2 |
| 7836063 | Salazar et al. | Nov 2010 | B2 |
| 7853081 | Thint | Dec 2010 | B2 |
| 7856416 | Hoffman et al. | Dec 2010 | B2 |
| 7877350 | Stanfill et al. | Jan 2011 | B2 |
| 7953695 | Roller et al. | May 2011 | B2 |
| 7987179 | Ma et al. | Jul 2011 | B2 |
| 8037108 | Chang | Oct 2011 | B1 |
| 8060472 | Itai et al. | Nov 2011 | B2 |
| 8099382 | Liu et al. | Jan 2012 | B2 |
| 8170981 | Tewksbary | May 2012 | B1 |
| 8275784 | Cao et al. | Sep 2012 | B2 |
| 8296200 | Mangipudi et al. | Oct 2012 | B2 |
| 8312389 | Crawford et al. | Nov 2012 | B2 |
| 8429179 | Mirhaji | Apr 2013 | B1 |
| 8521565 | Faulkner et al. | Aug 2013 | B2 |
| 8538985 | Betawadkar-Norwood et al. | Sep 2013 | B2 |
| 8583631 | Ganapathi et al. | Nov 2013 | B1 |
| 8616443 | Butt et al. | Dec 2013 | B2 |
| 8640056 | Helfman et al. | Jan 2014 | B2 |
| 8719252 | Miranker et al. | May 2014 | B2 |
| 8762160 | Lulla | Jun 2014 | B2 |
| 8799240 | Stowe et al. | Aug 2014 | B2 |
| 8831070 | Huang et al. | Sep 2014 | B2 |
| 8843502 | Elson et al. | Sep 2014 | B2 |
| 8849783 | Abramovitz | Sep 2014 | B2 |
| 8849784 | Alber | Sep 2014 | B2 |
| 8856643 | Drieschner | Oct 2014 | B2 |
| 8892513 | Forsythe | Nov 2014 | B2 |
| 8930337 | Studer | Jan 2015 | B2 |
| 8935272 | Ganti et al. | Jan 2015 | B2 |
| 8943313 | Glew et al. | Jan 2015 | B2 |
| 8965915 | Ganti et al. | Feb 2015 | B2 |
| 8990236 | Mizrahy et al. | Mar 2015 | B2 |
| 8996492 | Paradies | Mar 2015 | B2 |
| 8996559 | Ganti et al. | Mar 2015 | B2 |
| 8996978 | Richstein et al. | Mar 2015 | B2 |
| 9002860 | Ghemawat | Apr 2015 | B1 |
| 9020921 | Alber | Apr 2015 | B2 |
| 9171077 | Balmin et al. | Oct 2015 | B2 |
| 9218365 | Irani et al. | Dec 2015 | B2 |
| 9244952 | Ganti et al. | Jan 2016 | B2 |
| 9268820 | Henry | Feb 2016 | B2 |
| 9268950 | Gkoulalas-Divanis et al. | Feb 2016 | B2 |
| 9396283 | Miranker et al. | Jul 2016 | B2 |
| 9454611 | Henry | Sep 2016 | B2 |
| 9495429 | Miranker | Nov 2016 | B2 |
| 9560026 | Worsley | Jan 2017 | B1 |
| 9607042 | Long | Mar 2017 | B2 |
| 9613152 | Kucera | Apr 2017 | B2 |
| 9659081 | Ghodsi et al. | May 2017 | B1 |
| 9690792 | Bartlett et al. | Jun 2017 | B2 |
| 9696981 | Martin et al. | Jul 2017 | B2 |
| 9710526 | Couris et al. | Jul 2017 | B2 |
| 9710568 | Srinivasan et al. | Jul 2017 | B2 |
| 9720958 | Bagehorn et al. | Aug 2017 | B2 |
| 9760602 | Ghodsi et al. | Sep 2017 | B1 |
| 9769032 | Ghodsi et al. | Sep 2017 | B1 |
| 9798737 | Palmer | Oct 2017 | B2 |
| 9836302 | Hunter et al. | Dec 2017 | B1 |
| 9959337 | Ghodsi et al. | May 2018 | B2 |
| 9990230 | Stoica et al. | Jun 2018 | B1 |
| 10095735 | Ghodsi et al. | Oct 2018 | B2 |
| 10102258 | Jacob et al. | Oct 2018 | B2 |
| 10176234 | Gould et al. | Jan 2019 | B2 |
| 10216860 | Miranker et al. | Feb 2019 | B2 |
| 10248297 | Beechuk et al. | Apr 2019 | B2 |
| 10296329 | Hunter et al. | May 2019 | B2 |
| 10318567 | Henry | Jun 2019 | B2 |
| 10324925 | Jacob et al. | Jun 2019 | B2 |
| 10346429 | Jacob et al. | Jul 2019 | B2 |
| 10353911 | Reynolds et al. | Jul 2019 | B2 |
| 10361928 | Ghodsi et al. | Jul 2019 | B2 |
| 10438013 | Jacob et al. | Oct 2019 | B2 |
| 10452677 | Jacob et al. | Oct 2019 | B2 |
| 10452975 | Jacob et al. | Oct 2019 | B2 |
| 10474501 | Ghodsi et al. | Nov 2019 | B2 |
| 10474736 | Stoica et al. | Nov 2019 | B1 |
| 10545986 | Tappan et al. | Jan 2020 | B2 |
| 10546001 | Nguyen et al. | Jan 2020 | B1 |
| D876454 | Knowles et al. | Feb 2020 | S |
| 10558664 | Armbrust et al. | Feb 2020 | B2 |
| D877167 | Knowles et al. | Mar 2020 | S |
| D879112 | Hejazi et al. | Mar 2020 | S |
| 10606675 | Luszczak et al. | Mar 2020 | B1 |
| 10645548 | Reynolds et al. | May 2020 | B2 |
| 10664509 | Reeves et al. | May 2020 | B1 |
| 10673887 | Crabtree et al. | Jun 2020 | B2 |
| 10678536 | Hunter et al. | Jun 2020 | B2 |
| 10691299 | Broek et al. | Jun 2020 | B2 |
| 10691433 | Shankar et al. | Jun 2020 | B2 |
| 10713314 | Yan et al. | Jul 2020 | B2 |
| 10769130 | Armbrust et al. | Sep 2020 | B1 |
| 10769535 | Lindsley | Sep 2020 | B2 |
| 10810051 | Shankar et al. | Oct 2020 | B1 |
| 10922308 | Griffith | Feb 2021 | B2 |
| 10984008 | Jacob et al. | Apr 2021 | B2 |
| 11042556 | Griffith et al. | Jun 2021 | B2 |
| 11042560 | Griffith et al. | Jun 2021 | B2 |
| 11068453 | Griffith | Jul 2021 | B2 |
| 11068475 | Boutros et al. | Jul 2021 | B2 |
| 11068847 | Boutros et al. | Jul 2021 | B2 |
| 11093539 | Henry | Aug 2021 | B2 |
| 11294972 | George et al. | Apr 2022 | B2 |
| 11327991 | Reynolds et al. | May 2022 | B2 |
| 11468049 | Griffith | Oct 2022 | B2 |
| 11500831 | Griffith et al. | Nov 2022 | B2 |
| 20020133476 | Reinhardt | Sep 2002 | A1 |
| 20020143755 | Wynblatt et al. | Oct 2002 | A1 |
| 20030093597 | Marshak et al. | May 2003 | A1 |
| 20030120681 | Baclawski | Jun 2003 | A1 |
| 20030208506 | Greenfield et al. | Nov 2003 | A1 |
| 20040064456 | Fong et al. | Apr 2004 | A1 |
| 20050004888 | McCrady et al. | Jan 2005 | A1 |
| 20050010550 | Potter et al. | Jan 2005 | A1 |
| 20050010566 | Cushing et al. | Jan 2005 | A1 |
| 20050234957 | Olson et al. | Oct 2005 | A1 |
| 20050246357 | Geary et al. | Nov 2005 | A1 |
| 20050278139 | Glaenzer et al. | Dec 2005 | A1 |
| 20060100995 | Albornoz et al. | May 2006 | A1 |
| 20060117057 | Legault et al. | Jun 2006 | A1 |
| 20060129605 | Doshi | Jun 2006 | A1 |
| 20060161545 | Pura | Jul 2006 | A1 |
| 20060168002 | Chesley | Jul 2006 | A1 |
| 20060218024 | Lulla | Sep 2006 | A1 |
| 20060235837 | Chong et al. | Oct 2006 | A1 |
| 20070027904 | Chow et al. | Feb 2007 | A1 |
| 20070055662 | Edelman et al. | Mar 2007 | A1 |
| 20070139227 | Speirs et al. | Jun 2007 | A1 |
| 20070179760 | Smith | Aug 2007 | A1 |
| 20070203933 | Iversen et al. | Aug 2007 | A1 |
| 20070271604 | Webster et al. | Nov 2007 | A1 |
| 20070276875 | Brunswig et al. | Nov 2007 | A1 |
| 20080046427 | Lee et al. | Feb 2008 | A1 |
| 20080091634 | Seeman | Apr 2008 | A1 |
| 20080140609 | Werner et al. | Jun 2008 | A1 |
| 20080162550 | Fey | Jul 2008 | A1 |
| 20080162999 | Schlueter et al. | Jul 2008 | A1 |
| 20080216060 | Vargas | Sep 2008 | A1 |
| 20080240566 | Thint | Oct 2008 | A1 |
| 20080256026 | Hays | Oct 2008 | A1 |
| 20080294996 | Hunt et al. | Nov 2008 | A1 |
| 20080319829 | Hunt et al. | Dec 2008 | A1 |
| 20090006156 | Hunt et al. | Jan 2009 | A1 |
| 20090013281 | Helfman et al. | Jan 2009 | A1 |
| 20090018996 | Hunt et al. | Jan 2009 | A1 |
| 20090064053 | Crawford et al. | Mar 2009 | A1 |
| 20090094416 | Baeza-Yates et al. | Apr 2009 | A1 |
| 20090106734 | Riesen et al. | Apr 2009 | A1 |
| 20090119254 | Cross et al. | May 2009 | A1 |
| 20090132474 | Ma et al. | May 2009 | A1 |
| 20090132503 | Sun et al. | May 2009 | A1 |
| 20090138437 | Krishnamoorthy et al. | May 2009 | A1 |
| 20090150313 | Heilper et al. | Jun 2009 | A1 |
| 20090157630 | Yuan | Jun 2009 | A1 |
| 20090182710 | Short et al. | Jul 2009 | A1 |
| 20090198693 | Pura | Aug 2009 | A1 |
| 20090234799 | Betawadkar-Norwood et al. | Sep 2009 | A1 |
| 20090248714 | Liu | Oct 2009 | A1 |
| 20090300054 | Fisher et al. | Dec 2009 | A1 |
| 20100114885 | Bowers et al. | May 2010 | A1 |
| 20100138388 | Wakeling et al. | Jun 2010 | A1 |
| 20100223266 | Balmin et al. | Sep 2010 | A1 |
| 20100235384 | Itai et al. | Sep 2010 | A1 |
| 20100241644 | Jackson et al. | Sep 2010 | A1 |
| 20100250576 | Bowers et al. | Sep 2010 | A1 |
| 20100250577 | Cao et al. | Sep 2010 | A1 |
| 20100268722 | Yalamanchi et al. | Oct 2010 | A1 |
| 20100306240 | Berce | Dec 2010 | A1 |
| 20100332453 | Prahlad et al. | Dec 2010 | A1 |
| 20110093467 | Sharp | Apr 2011 | A1 |
| 20110153047 | Cameron et al. | Jun 2011 | A1 |
| 20110202560 | Bowers et al. | Aug 2011 | A1 |
| 20110283231 | Richstein et al. | Nov 2011 | A1 |
| 20110298804 | Hao et al. | Dec 2011 | A1 |
| 20120016895 | Butt et al. | Jan 2012 | A1 |
| 20120036162 | Gimbel | Feb 2012 | A1 |
| 20120102022 | Miranker et al. | Apr 2012 | A1 |
| 20120154633 | Rodriguez | Jun 2012 | A1 |
| 20120179644 | Miranker | Jul 2012 | A1 |
| 20120190386 | Anderson | Jul 2012 | A1 |
| 20120254192 | Gelbard | Oct 2012 | A1 |
| 20120278902 | Martin et al. | Nov 2012 | A1 |
| 20120284301 | Mizrahy et al. | Nov 2012 | A1 |
| 20120310674 | Faulkner et al. | Dec 2012 | A1 |
| 20120330908 | Stowe et al. | Dec 2012 | A1 |
| 20120330979 | Elson et al. | Dec 2012 | A1 |
| 20130031208 | Linton et al. | Jan 2013 | A1 |
| 20130031364 | Glew et al. | Jan 2013 | A1 |
| 20130041893 | Strike | Feb 2013 | A1 |
| 20130054517 | Beechuk et al. | Feb 2013 | A1 |
| 20130086022 | Black, III | Apr 2013 | A1 |
| 20130110775 | Forsythe | May 2013 | A1 |
| 20130110825 | Henry | May 2013 | A1 |
| 20130114645 | Huang et al. | May 2013 | A1 |
| 20130138681 | Abrams et al. | May 2013 | A1 |
| 20130156348 | Irani et al. | Jun 2013 | A1 |
| 20130238667 | Carvalho et al. | Sep 2013 | A1 |
| 20130262443 | Leida et al. | Oct 2013 | A1 |
| 20130263019 | Castellanos et al. | Oct 2013 | A1 |
| 20130318062 | Studer | Nov 2013 | A1 |
| 20130318070 | Wu et al. | Nov 2013 | A1 |
| 20130321458 | Miserendino et al. | Dec 2013 | A1 |
| 20140006448 | McCall | Jan 2014 | A1 |
| 20140019426 | Palmer | Jan 2014 | A1 |
| 20140067762 | Carvalho | Mar 2014 | A1 |
| 20140113638 | Zhang et al. | Apr 2014 | A1 |
| 20140115013 | Anderson | Apr 2014 | A1 |
| 20140119611 | Prevrhal et al. | May 2014 | A1 |
| 20140164431 | Tolbert | Jun 2014 | A1 |
| 20140172810 | Paradies | Jun 2014 | A1 |
| 20140198097 | Evans | Jul 2014 | A1 |
| 20140214857 | Srinivasan et al. | Jul 2014 | A1 |
| 20140229869 | Chiantera et al. | Aug 2014 | A1 |
| 20140236914 | Okamura | Aug 2014 | A1 |
| 20140236933 | Schoenbach et al. | Aug 2014 | A1 |
| 20140244623 | King | Aug 2014 | A1 |
| 20140279640 | Moreno et al. | Sep 2014 | A1 |
| 20140279845 | Ganti et al. | Sep 2014 | A1 |
| 20140280067 | Ganti et al. | Sep 2014 | A1 |
| 20140280286 | Ganti et al. | Sep 2014 | A1 |
| 20140280287 | Ganti et al. | Sep 2014 | A1 |
| 20140337331 | Hassanzadeh et al. | Nov 2014 | A1 |
| 20140337436 | Hoagland et al. | Nov 2014 | A1 |
| 20140372434 | Smith et al. | Dec 2014 | A1 |
| 20150046547 | Vohra et al. | Feb 2015 | A1 |
| 20150052125 | Ellis et al. | Feb 2015 | A1 |
| 20150052134 | Bornea et al. | Feb 2015 | A1 |
| 20150066387 | Yamada et al. | Mar 2015 | A1 |
| 20150081666 | Long | Mar 2015 | A1 |
| 20150095391 | Gajjar et al. | Apr 2015 | A1 |
| 20150120643 | Dantressangle et al. | Apr 2015 | A1 |
| 20150142829 | Lee et al. | May 2015 | A1 |
| 20150143248 | Beechuk et al. | May 2015 | A1 |
| 20150149879 | Miller et al. | May 2015 | A1 |
| 20150186653 | Gkoulalas-Divanis et al. | Jul 2015 | A1 |
| 20150213109 | Kassko et al. | Jul 2015 | A1 |
| 20150234884 | Henriksen | Aug 2015 | A1 |
| 20150242867 | Prendergast et al. | Aug 2015 | A1 |
| 20150269223 | Miranker et al. | Sep 2015 | A1 |
| 20150277725 | Masterson et al. | Oct 2015 | A1 |
| 20150278273 | Wigington et al. | Oct 2015 | A1 |
| 20150278335 | Opitz et al. | Oct 2015 | A1 |
| 20150339572 | Achin et al. | Nov 2015 | A1 |
| 20150356144 | Chawla et al. | Dec 2015 | A1 |
| 20150372915 | Shen et al. | Dec 2015 | A1 |
| 20150379079 | Kota | Dec 2015 | A1 |
| 20160004820 | Moore | Jan 2016 | A1 |
| 20160012059 | Balmin et al. | Jan 2016 | A1 |
| 20160019091 | Leber et al. | Jan 2016 | A1 |
| 20160055184 | Fokoue-Nkoutche et al. | Feb 2016 | A1 |
| 20160055261 | Reinhardt et al. | Feb 2016 | A1 |
| 20160063017 | Bartlett et al. | Mar 2016 | A1 |
| 20160063271 | Bartlett et al. | Mar 2016 | A1 |
| 20160092090 | Stojanovic et al. | Mar 2016 | A1 |
| 20160092474 | Stojanovic et al. | Mar 2016 | A1 |
| 20160092475 | Stojanovic et al. | Mar 2016 | A1 |
| 20160092476 | Stojanovic et al. | Mar 2016 | A1 |
| 20160092527 | Kang et al. | Mar 2016 | A1 |
| 20160098418 | Dakshinamurthy et al. | Apr 2016 | A1 |
| 20160100009 | Zoldi et al. | Apr 2016 | A1 |
| 20160103908 | Fletcher et al. | Apr 2016 | A1 |
| 20160117358 | Schmid et al. | Apr 2016 | A1 |
| 20160117362 | Bagehorn et al. | Apr 2016 | A1 |
| 20160125057 | Gould et al. | May 2016 | A1 |
| 20160132572 | Chang et al. | May 2016 | A1 |
| 20160132608 | Rathod | May 2016 | A1 |
| 20160132787 | Drevo et al. | May 2016 | A1 |
| 20160147837 | Nguyen et al. | May 2016 | A1 |
| 20160162785 | Grobman | Jun 2016 | A1 |
| 20160171380 | Kennel et al. | Jun 2016 | A1 |
| 20160173338 | Wolting | Jun 2016 | A1 |
| 20160188789 | Kisiel et al. | Jun 2016 | A1 |
| 20160203196 | Schnall-Levin et al. | Jul 2016 | A1 |
| 20160210364 | Henry | Jul 2016 | A1 |
| 20160225271 | Robichaud et al. | Aug 2016 | A1 |
| 20160232457 | Gray et al. | Aug 2016 | A1 |
| 20160275204 | Miranker et al. | Sep 2016 | A1 |
| 20160283551 | Fokoue-Nkoutche et al. | Sep 2016 | A1 |
| 20160292206 | Velazquez et al. | Oct 2016 | A1 |
| 20160314143 | Hiroshige | Oct 2016 | A1 |
| 20160321316 | Pennefather et al. | Nov 2016 | A1 |
| 20160322082 | Davis et al. | Nov 2016 | A1 |
| 20160350414 | Henry | Dec 2016 | A1 |
| 20160352592 | Sasaki et al. | Dec 2016 | A1 |
| 20160358102 | Bowers et al. | Dec 2016 | A1 |
| 20160358103 | Bowers et al. | Dec 2016 | A1 |
| 20160371288 | Biannic et al. | Dec 2016 | A1 |
| 20160371355 | Massari et al. | Dec 2016 | A1 |
| 20170017537 | Razin et al. | Jan 2017 | A1 |
| 20170032259 | Goranson et al. | Feb 2017 | A1 |
| 20170053130 | Hughes et al. | Feb 2017 | A1 |
| 20170075973 | Miranker | Mar 2017 | A1 |
| 20170132401 | Gopi et al. | May 2017 | A1 |
| 20170161323 | Simitsis et al. | Jun 2017 | A1 |
| 20170161341 | Hrabovsky et al. | Jun 2017 | A1 |
| 20170177729 | Duke et al. | Jun 2017 | A1 |
| 20170213004 | Fox et al. | Jul 2017 | A1 |
| 20170220615 | Bendig et al. | Aug 2017 | A1 |
| 20170220667 | Ghodsi et al. | Aug 2017 | A1 |
| 20170228405 | Ward et al. | Aug 2017 | A1 |
| 20170236060 | Ignatyev | Aug 2017 | A1 |
| 20170316070 | Krishnan et al. | Nov 2017 | A1 |
| 20170318020 | Kamath et al. | Nov 2017 | A1 |
| 20170357653 | Bicer et al. | Dec 2017 | A1 |
| 20170364538 | Jacob et al. | Dec 2017 | A1 |
| 20170364539 | Jacob et al. | Dec 2017 | A1 |
| 20170364553 | Jacob et al. | Dec 2017 | A1 |
| 20170364564 | Jacob et al. | Dec 2017 | A1 |
| 20170364568 | Reynolds et al. | Dec 2017 | A1 |
| 20170364569 | Jacob et al. | Dec 2017 | A1 |
| 20170364570 | Jacob et al. | Dec 2017 | A1 |
| 20170364694 | Jacob et al. | Dec 2017 | A1 |
| 20170364703 | Jacob et al. | Dec 2017 | A1 |
| 20170371881 | Reynolds et al. | Dec 2017 | A1 |
| 20170371926 | Shiran et al. | Dec 2017 | A1 |
| 20180025027 | Palmer | Jan 2018 | A1 |
| 20180025307 | Hui et al. | Jan 2018 | A1 |
| 20180031703 | Ngai et al. | Feb 2018 | A1 |
| 20180032327 | Adami et al. | Feb 2018 | A1 |
| 20180040077 | Smith et al. | Feb 2018 | A1 |
| 20180046668 | Ghodsi et al. | Feb 2018 | A1 |
| 20180048536 | Ghodsi et al. | Feb 2018 | A1 |
| 20180075115 | Murray et al. | Mar 2018 | A1 |
| 20180121194 | Hunter et al. | May 2018 | A1 |
| 20180210936 | Reynolds et al. | Jul 2018 | A1 |
| 20180262864 | Reynolds et al. | Sep 2018 | A1 |
| 20180300354 | Liang et al. | Oct 2018 | A1 |
| 20180300494 | Avidan et al. | Oct 2018 | A1 |
| 20180314556 | Ghodsi et al. | Nov 2018 | A1 |
| 20180314705 | Griffith et al. | Nov 2018 | A1 |
| 20180314732 | Armbrust et al. | Nov 2018 | A1 |
| 20180330111 | Käbisch et al. | Nov 2018 | A1 |
| 20190005104 | Prabhu et al. | Jan 2019 | A1 |
| 20190034491 | Griffith et al. | Jan 2019 | A1 |
| 20190042606 | Griffith et al. | Feb 2019 | A1 |
| 20190050445 | Griffith et al. | Feb 2019 | A1 |
| 20190050459 | Griffith et al. | Feb 2019 | A1 |
| 20190057107 | Bartlett et al. | Feb 2019 | A1 |
| 20190065567 | Griffith et al. | Feb 2019 | A1 |
| 20190065569 | Boutros et al. | Feb 2019 | A1 |
| 20190066052 | Boutros et al. | Feb 2019 | A1 |
| 20190079968 | Griffith et al. | Mar 2019 | A1 |
| 20190095472 | Griffith | Mar 2019 | A1 |
| 20190121807 | Boutros et al. | Apr 2019 | A1 |
| 20190138538 | Stojanovic et al. | May 2019 | A1 |
| 20190155852 | Miranker et al. | May 2019 | A1 |
| 20190258479 | Hunter et al. | Aug 2019 | A1 |
| 20190266155 | Jacob et al. | Aug 2019 | A1 |
| 20190272279 | Jacob et al. | Sep 2019 | A1 |
| 20190278793 | Henry | Sep 2019 | A1 |
| 20190286617 | Abu-Abed et al. | Sep 2019 | A1 |
| 20190295296 | Gove, Jr. | Sep 2019 | A1 |
| 20190317961 | Brener et al. | Oct 2019 | A1 |
| 20190332606 | Kee et al. | Oct 2019 | A1 |
| 20190347244 | Jacob et al. | Nov 2019 | A1 |
| 20190347258 | Jacob et al. | Nov 2019 | A1 |
| 20190347259 | Jacob et al. | Nov 2019 | A1 |
| 20190347268 | Griffith | Nov 2019 | A1 |
| 20190347347 | Griffith | Nov 2019 | A1 |
| 20190370230 | Jacob et al. | Dec 2019 | A1 |
| 20190370262 | Reynolds et al. | Dec 2019 | A1 |
| 20190370266 | Jacob et al. | Dec 2019 | A1 |
| 20190370481 | Jacob et al. | Dec 2019 | A1 |
| 20190384571 | Oberbreckling et al. | Dec 2019 | A1 |
| 20200073644 | Shankar et al. | Mar 2020 | A1 |
| 20200073865 | Jacob et al. | Mar 2020 | A1 |
| 20200074298 | Jacob et al. | Mar 2020 | A1 |
| 20200097504 | Sequeda et al. | Mar 2020 | A1 |
| 20200117665 | Jacob et al. | Apr 2020 | A1 |
| 20200117688 | Sequeda et al. | Apr 2020 | A1 |
| 20200175012 | Jacob et al. | Jun 2020 | A1 |
| 20200175013 | Jacob et al. | Jun 2020 | A1 |
| 20200201854 | Miller | Jun 2020 | A1 |
| 20200218723 | Jacob et al. | Jul 2020 | A1 |
| 20200241950 | Luszczak et al. | Jul 2020 | A1 |
| 20200252766 | Reynolds et al. | Aug 2020 | A1 |
| 20200252767 | Reynolds et al. | Aug 2020 | A1 |
| 20200257689 | Armbrust et al. | Aug 2020 | A1 |
| 20200301684 | Shankar et al. | Sep 2020 | A1 |
| 20200380009 | Reynolds et al. | Dec 2020 | A1 |
| 20200409768 | Shankar et al. | Dec 2020 | A1 |
| 20210011901 | Armbrust et al. | Jan 2021 | A1 |
| 20210019327 | Reynolds et al. | Jan 2021 | A1 |
| 20210042299 | Migliori | Feb 2021 | A1 |
| 20210081414 | Jacob et al. | Mar 2021 | A1 |
| 20210109629 | Reynolds et al. | Apr 2021 | A1 |
| 20210173848 | Jacob et al. | Jun 2021 | A1 |
| 20210224250 | Griffith | Jul 2021 | A1 |
| 20210224330 | Miranker et al. | Jul 2021 | A1 |
| 20210294465 | Reynolds et al. | Sep 2021 | A1 |
| 20210374134 | He et al. | Dec 2021 | A1 |
| 20210374171 | Henry | Dec 2021 | A1 |
| 20210374555 | Beguerisse-Díaz et al. | Dec 2021 | A1 |
| 20210390098 | Reynolds et al. | Dec 2021 | A1 |
| 20210390141 | Jacob et al. | Dec 2021 | A1 |
| 20210390507 | Reynolds et al. | Dec 2021 | A1 |
| 20210397589 | Griffith et al. | Dec 2021 | A1 |
| 20210397611 | Boutres et al. | Dec 2021 | A1 |
| 20210397626 | Griffith et al. | Dec 2021 | A1 |
| 20220229838 | Jacob et al. | Jul 2022 | A1 |
| 20220229847 | Jacob et al. | Jul 2022 | A1 |
| 20220261411 | Reynolds et al. | Aug 2022 | A1 |
| 20220277004 | Griffith | Sep 2022 | A1 |
| 20220327119 | Gasper et al. | Oct 2022 | A1 |
| 20220337978 | Reynolds et al. | Oct 2022 | A1 |
| 20230105459 | Griffith | Apr 2023 | A1 |
| 20230109821 | Griffith | Apr 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 2012289936 | Feb 2014 | AU |
| 2820994 | Jan 2014 | CA |
| 103425734 | Jun 2017 | CN |
| 2631817 | Aug 2013 | EP |
| 2631819 | Aug 2013 | EP |
| 2685394 | Jun 2017 | EP |
| 2740053 | Jun 2019 | EP |
| 2519779 | May 2015 | GB |
| 2013175181 | Sep 2013 | JP |
| 2013246828 | Dec 2013 | JP |
| 2014524124 | Sep 2014 | JP |
| 2012054860 | Apr 2012 | WO |
| 2013020084 | Feb 2013 | WO |
| 2017190153 | Nov 2017 | WO |
| 2017222927 | Dec 2017 | WO |
| 2018156551 | Aug 2018 | WO |
| 2018164971 | Sep 2018 | WO |
| 2021252805 | Dec 2021 | WO |
| Entry |
|---|
| “Data.World Comes Out of Stealth to Make Open Data Easier.” Americaninno.com, AustinInno, Jul. 11, 2016, Retrieved from the Internet; URL: www.americaninno.com/austin/open-data-tech-brett-hurts-startup-data-world-launches/ [retrieved Jan. 27, 2020]. |
| Alaoui et al., “SQL to SPARQL Mapping for RDF querying based on a new Efficient Schema Conversion Technique,” International Journal of Engineering Research & Technology (IJERT); ISSN: 2278-0181; vol. 4 Issue 10, Oct. 1, 2015, Retrieved from internet: https://www.ijert.org/research/sql-to-sparql-mapping-for-rdf-querying-based-on-a-new-efficient-schema-conversion-technique-IJERTV4IS1--1-5.pdf. Retrieved on Oct. 6, 2020. |
| Angles, R., Gutierrez. C., “The Expressive Power of SPARQL,” Proceedings of the 7th International Semantic Web Conference (ISWC2008). 2008. |
| Arenas, M., et al., “A Direct Mapping of Relational Data to RDF,” W3C Recommendation, Sep. 27, 2012, Retrieved from the Internet; URL: https://www.w3.org/TR/rdb-direct-mapping/ [retrieved Mar. 7, 2019]. |
| Beckett, D., Berners-Lee, T., “Turtle—Terse RDF Triple Language,” W3C Team Submission, Jan. 14, 2008, Retrieved from the Internet URL: https://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114/ [retrieved Mar. 7, 2019]. |
| Beckett, D., Broekstra, J., “SPARQL Query Results XML Format,” W3C Recommendation, Jan. 15, 2008, Retrieved from the Internet URL: https://www.w3.org/TR/2008/REC-rdf-sparql/XMLres-20080115/ [retrieved Mar. 7, 2019]. |
| Beckett, Dave, “RDF/XML Syntax Specification (Revised),” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/ [retrieved Mar. 7, 2019]. |
| Berners-Lee, Tim, “Notation 3,” 2006, Retrieved from the Internet; URL: https://www.w3.org/DesignIssues/Notation3.html [retrieved on Mar. 7, 2019]. |
| Berners-Lee, Tim, “Linked Data,” 2009, Retrieved from the Internet; URL: https://www.w3.org/DesignIssues/LinkedData.html [retrieved on Mar. 7, 2019]. |
| Boutros et al., “Computerized Tools to Develop and Manage Data-Driven Projects Collaboratively via a Networked Computing Platform and Collaborative Datasets,” U.S. Appl. No. 15/985,702, filed May 22, 2018. |
| Boutros et al., “Computerized Tools to Facilitate Data Project Development via Data Access Layering Logic in a Networked Computing Platform Including Collaborative Datasets,” U.S. Appl. No. 15/985,704, filed May 22, 2018. |
| Boutros et al., “Dynamic Composite Data Dictionary to Facilitate Data Operations via Computerized Tools Configured to Access Collaborative Datasets in a Networked Computing Platform,” U.S. Appl. No. 15/985,705, filed May 22, 2018. |
| Boutros et al., “Graphical User Interface for a Display Screen or Portion Thereof,” U.S. Appl. No. 29/648,465, filed May 22, 2018. |
| Boutros et al., “Graphical User Interface for a Display Screen or Portion Thereof,” U.S. Appl. No. 29/648,466, filed May 22, 2018. |
| Boutros et al., “Graphical User Interface for a Display Screen or Portion Thereof,” U.S. Appl. No. 29/648,467, filed May 22, 2018. |
| Brener et al., “Computerized Tools Configured to Determine Subsets of Graph Data Arrangements for Linking Relevant Data to Enrich Datasets Associated With a Data-Driven Collaborative Dataset Platform,” U.S. Appl. No. 16/395,036, filed Apr. 25, 2019. |
| Brickley, D., Guha, R.V., “RDF Vocabulary Description Language 1.0: RDF Schema,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-rdf-schema-2004/0210/[retrieved Mar. 7, 2019]. |
| Buche et al., “Flexible SPARQL Querying of Web Data Tables Driven by an Ontology,” FQAS 2009, LNAI 5822, Springer, 2009, pp. 345-357. |
| Bullock, Joshua, Final Office Action dated Jan. 22, 2019 for U.S. Appl. No. 15/439,908. |
| Bullock, Joshua, Final Office Action dated Jan. 22, 2019 for U.S. Appl. No. 15/439,911. |
| Bullock, Joshua, Final Office Action dated Oct. 30, 2018 for U.S. Appl. No. 15/186,517. |
| Bullock, Joshua, Non-Final Office Action dated Dec. 20, 2021 for U.S. Appl. No. 16/457,759. |
| Bullock, Joshua, Non-Final Office Action dated Dec. 7, 2021 for U.S. Appl. No. 16/457,750. |
| Bullock, Joshua, Non-Final Office Action dated Jul. 12, 2018 for U.S. Appl. No. 15/186,517. |
| Bullock, Joshua, Non-Final Office Action dated Jun. 28, 2018 for U.S. Appl. No. 15/439,908. |
| Bullock, Joshua, Non-Final Office Action dated Jun. 28, 2018 for U.S. Appl. No. 15/439,911. |
| Bullock, Joshua, Notice of Allowance and Fee(s) Due dated Dec. 22, 2021 for U.S. Appl. No. 16/395,049. |
| Bullock, Joshua, Notice of Allowance and Fee(s) Due dated Feb. 23, 2022 for U.S. Appl. No. 16/457,750. |
| Caiado, Antonio J., Non-Final Office Action dated Sep. 16, 2022 for U.S. Appl. No. 17/365,214. |
| Clark, K., Feigenbaum, L., Torres, E., “SPARQL Protocol for RDF,” W3C Recommendation, Jan. 15, 2008, Retrieved from the Internet; URL: https://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115/ [retrieved Mar. 7, 2019]. |
| Copenheaver, Blaine R., Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Jul. 5, 2017 for International Patent Application No. PCT/US2017/030474. |
| Czajkowski, K., et al., “Grid Information Services for Distributed Resource Sharing,” 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181-184. IEEE Press, New York (2001). |
| Dean, M., Schreiber, G., “OWL Web Ontology Language Reference,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-owl-ref-20040210/ [retrieved Mar. 7, 2019]. |
| Doung, Hien, Non-Final Office Action dated Dec. 9, 2020 for U.S. Appl. No. 16/899,544. |
| Duong, Hien Luongvan, Non-Final Office Action dated May 5, 2022 for U.S. Appl. No. 17/185,917. |
| Duong, Hien, Notice of Allowance and Fee(s) Due dated Oct. 27, 2022 for U.S. Appl. No. 17/185,917. |
| Dwivedi, Mahesh H., Non-Final Office Action dated Jan. 30, 2020 for U.S. Appl. No. 15/454,955. |
| Ellis, Matthew J., Non-Final Office Action dated Sep. 25, 2020 for U.S. Appl. No. 16/139,374. |
| European Patent Office, Extended European Search Report for European Patent Application No. 18757122.9 dated Oct. 15, 2020. |
| European Patent Office, Extended European Search Report for European Patent Application No. 18763855.6 dated Sep. 28, 2020. |
| Feigenbaum, L., et al., “Semantic Web in Action,” Scientific American, pp. 90-97, Dec. 2007. |
| Fernandez, J., et al., “Lightweighting the Web of Data through Compact RDF/HDT,” Lozano J.A., Moreno J.A. (eds) Advances in Artificial Intelligence. CAEPIA 2011. Lecture Notes in Computer Science, vol. 7023. Springer, Berlin, Hidelberg. |
| Foster, I., Kesselman, C., “The Grid: Blueprint for a New Computing Infrastructure,” Morgan Kaufmann, San Francisco (1999). |
| Foster, I., Kesselman, C., Nick, J., Tuecke, S., “The Physiology of the Grid: An Open Grid Services Architecture for Distributed Systems Integration,” Technical Report, Global Grid Forum (2002). |
| Ganti et al., U.S. Appl. No. 61/802,743, filed Mar. 18, 2013 and entitled, “Creating a Data Catalog by Mining Queries.” |
| Ganti et al., U.S. Appl. No. 61/802,744, filed Mar. 18, 2013 and entitled, “Autocompletion of Queries With Data Object Names and Data Profiles.” |
| Garay, Peter, Examination Report No. 1 for Standard Patent Application for Australia Patent Application No. 2017282656 dated Jul. 21, 2021, Intellectual Property Office of Australia. |
| Garcia-Molina, H., Ullman, J., Widom, J., Database Systems: The Complete Book. Editorial Pearson Prentice Hall. Second Edition. Published Jan. 11, 2011. (Year: 2011). |
| Gawinecki, Maciej, “How schema mapping can help in data integration?—integrating the relational databases with ontologies,” ITC School, Computer Science, XXIII Cycle DII, University of Modena and Reggio Emilia, Italy, 2008. |
| Gillin, Paul, “Neo4j Connector Integrates Graph Data With Business Intelligence Tools,” SiliconANGLE, Published Mar. 24, 2020, Retrieved from https://siliconangle.com/2020/03/24/neo4j-connector-integrates-graph-data-business-intelligence-tools/ on Mar. 25, 2020. |
| Girma, Anteneh B., Final Office Action for U.S. Appl. No. 13/278,907, dated Apr. 18, 2013. |
| Girma, Anteneh B., Non-Final Office Action for U.S. Appl. No. 13/278,907, dated Jul. 25, 2012. |
| Grant, J., Beckett, D., “RDF Test Cases,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet URL: https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/ [retrieved Mar. 7, 2019]. |
| Griffith et al., “Aggregation of Ancillary Data Associated With Source Data in a System of Networked Collaborative Datasets,” U.S. Appl. No. 15/927,006, filed Mar. 20, 2018. |
| Griffith et al., “Data Ingestion to Generate Layered Dataset Interrelations to Form a System of Networked Collaborative Datasets,” U.S. Appl. No. 15/926,999, filed Mar. 20, 2018. |
| Griffith et al., “Extended Computerized Query Language Syntax for Analyzing Multiple Tabular Data Arrangements in Data-Driven Collaborative Projects,” U.S. Appl. No. 16/036,834, filed Jul. 16, 2018. |
| Griffith et al., “Layered Data Generation and Data Remediation to Facilitate Formation of Interrelated Data in a System of Networked Collaborative Datasets,” U.S. Appl. No. 15/927,004, filed Mar. 20, 2018. |
| Griffith et al., “Link-Formative Auxiliary Queries Applied at Data Ingestion to Facilitate Data Operations in a System of Networked Collaborative Datasets,” U.S. Appl. No. 15/943,633, filed Apr. 2, 2018. |
| Griffith et al., “Localized Link Formation to Perform Implicitly Federated Queries Using Extended Computerized Query Language Syntax,” U.S. Appl. No. 16/036,836, filed Jul. 16, 2018. |
| Griffith et al., “Transmuting Data Associations Among Data Arrangements to Facilitate Data Operations in a System of Networked Collaborative Datasets,” U.S. Appl. No. 15/943,629, filed Apr. 2, 2018. |
| Griffith, David Lee, “Determining a Degree of Similarity of a Subset of Tabular Data Arrangements to Subsets of Graph Data Arrangements at Ingestion Into a Data-Driven Collaborative Dataset Platform,” U.S. Appl. No. 16/137,297, filed Sep. 20, 2018. |
| Griffith, David Lee, “Matching Subsets of Tabular Data Arrangements to Subsets of Graphical Data Arrangements at Ingestion Into Data Driven Collaborative Datasets,” U.S. Appl. No. 16/137,292, filed Sep. 20, 2018. |
| Griffith, David Lee, “Predictive Determination of Constraint Data for Application With Linked Data in Graph-Based Datasets Associated With a Data-Driven Collaborative Dataset Platform,” U.S. Appl. No. 16/139,374, filed Sep. 24, 2018. |
| Haveliwala et al., “Evaluating Strategies for Similarity Search on the Web,” Proceedings of the 11th international conference on World Wide Web, May 7-11, 2002, Honolulu, Hawaii, USA (ACM), p. 432-442. |
| Hayes, Patrick, “RDF Semantics,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-rdf-mt-20040210/ [retrieved Mar. 7, 2019]. |
| Heflin, J., “OWL Web Ontology Language Use Cases and Requirements,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-webnot-req-20040210 [retrieved Mar. 7, 2019]. |
| Henry, Jerome William, U.S. Appl. No. 61/515,305, filed Aug. 4, 2011 entitled, “Apparatus and Method for Supplying Search Results With a Knowledge Card.” |
| Hoang, Hau Hai, Final Office Action dated Jul. 30, 2019 for U.S. Appl. No. 15/186,515. |
| Hoang, Hau Hai, Final Office Action dated Nov. 26, 2018 for U.S. Appl. No. 15/186,515. |
| Hoang, Hau Hai, Non-Final Office Action dated Apr. 16, 2019 for U.S. Appl. No. 15/186,515. |
| Hoang, Hau Hai, Non-Final Office Action dated May 3, 2018 for U.S. Appl. No. 15/186,515. |
| Hoang, Hau Hai, Notice of Allowance and Fee(s) Due dated Aug. 19, 2021 for U.S. Appl. No. 16/697,132. |
| Htay, Lin Lin M., Non-Final Office Action dated Sep. 14, 2018 for U.S. Appl. No. 15/186,516. |
| Htay, Lin Lin M., Notice of Allowance and Fee(s) Due and Notice of Allowability for U.S. Appl. No. 15/186,516, dated Jan. 25, 2019. |
| Hu, Xiaoqin, Final Office Action dated Apr. 5, 2019 for U.S. Appl. No. 15/454,969. |
| Hu, Xiaoqin, Final Office Action dated Apr. 5, 2019 for U.S. Appl. No. 15/454,981. |
| Hu, Xiaoqin, Final Office Action dated Oct. 31, 2019 for U.S. Appl. No. 15/454,969. |
| Hu, Xiaoqin, Final Office Action dated Sep. 24, 2019 for U.S. Appl. No. 15/454,981. |
| Hu, Xiaoqin, Non-Final Office Action for U.S. Appl. No. 15/454,969 dated Dec. 7, 2018. |
| Hu, Xiaoqin, Non-Final Office Action for U.S. Appl. No. 15/454,981 dated Dec. 12, 2018. |
| Hu, Xiaoqin, Non-Final Office Action dated Aug. 1, 2019 for U.S. Appl. No. 15/454,981. |
| Hu, Xiaoqin, Non-Final Office Action dated Jul. 26, 2019 for U.S. Appl. No. 15/454,969. |
| Hu, Xiaoqin, Non-Final Office Action dated Jul. 30, 2021 for U.S. Appl. No. 16/732,261. |
| Hu, Xiaoqin, Non-Final Office Action dated Sep. 2, 2021 for U.S. Appl. No. 16/732,263. |
| J. Perez, M. Arenas, C. Gutierrez, “Semantics and Complexity of SPARQL,” ACM Transactions on Database Systems (TODS), Vo. 34, No. 3, Article 16, Publication Date: Aug. 2009. |
| Jacob et al., “Collaborative Dataset Consolidation via Distributed Computer Networks,” U.S. Appl. No. 16/120,057, filed Aug. 31, 2018. |
| Jacob et al., “Collaborative Dataset Consolidation via Distributed Computer Networks,” U.S. Appl. No. 16/287,967, filed Feb. 27, 2019. |
| Jacob et al., “Dataset Analysis and Dataset Attribute Inferencing to Form Collaborative Datasets,” U.S. Appl. No. 16/271,263, filed Feb. 8, 2019. |
| Joshi, Amit Krishna et al., “Alignment-based Querying of Linked Open Data,” Lecture Notes in Computer Science, 7566, 807-824, 2012. |
| Kahn, Yasar et al., “SAFE: Policy Aware SPARQL Query Federation Over RDF Data Cubes,” Proceedings of the 7th International Workshop on Semantic Web Applications and Tools for Life Sciences, Berlin, Germany, Dec. 9-11, 2014. |
| Khong, Alexander, Non-Final Office Action for U.S. Appl. No. 15/165,775, dated Jun. 14, 2018. |
| Kim, Harry C., Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, dated Sep. 28, 2021 for International Application No. PCT/US2021/036880. |
| Klyne, G., Carroll, J., “Resource Description Framework (RDF): Concepts and Abstract Syntax,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-rdf-concepts-20040210 [retrieved Mar. 7, 2019]. |
| Konda et al., Magellan: Toward Building Entity Matching Management Systems over Data Science Stacks, Proceedings of the VLDB Endowment, vol. 9, No. 13, (2016), pp. 1581-1584; URL: http://cpcp.wisc.edu/images/resources/magellan-vldb16.pdf, Date retrieved: Aug. 30, 2021. |
| Konda, Pradap, Magellan: Toward Building Entity Matching Management Systems, Presentation dated Feb. 27, 2018. |
| Krishnan et al., U.S. Appl. No. 15/583,966, filed May 1, 2017 and titled “Automatic Generation of Structured Data from Semi-Structured Data.” |
| Langedgger, Andreas, “XL Wrap—Spreadsheet-to-RDF Wrapper,” 2009, Retrieved from the Internet URL: http://xlwrap.sourceforge.net [retrieved Mar. 7, 2019]. |
| Lee, Mark B., Non-Final Office Action for U.S. Appl. No. 13/180,444 dated Jul. 2, 2012. |
| Lenz, H.J., Shoshani, A., “Summarizability in OLAP and Statistical Data Bases,” Proceedings of the Ninth International Conference on Scientific and Statistical Database Management, 1997. |
| Manola, F., Miller, E., “RDF Primer,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-rdf-primer-20040210/ [retrieved Mar. 7, 2019]. |
| Martin et al., U.S. Appl. No. 13/457,925, filed Apr. 27, 2012 and titled “Incremental Deployment of Computer Software Program Logic.” |
| Martin et al., U.S. Appl. No. 61/479,621, filed Apr. 27, 2011 and titled “Incremental Deployment of Computer Software Program Logic.” |
| May, P., Ehrlich, H.C., Steinke, T., “ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services,” In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148-1158. Springer, Heidelberg (2006). |
| McGuiness, D., Van Harmelen, F., “OWL Web Ontology Language Overview,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-owl-features-20040210/ [retrieved Mar. 7, 2019]. |
| Mian, Muhammad U., Notice of Allowance and Fee(s) Due dated Jun. 6, 2022 for U.S. Appl. No. 17/246,359. |
| Mian, Umar, Non-Final Office Action dated Apr. 8, 2022 for U.S. Appl. No. 17/246,359. |
| Miranker, Daniel Paul, “Accessing Relational Databases as Resource Description Framework Databases,” U.S. Appl. No. 61/406,021, filed Oct. 22, 2010. |
| Miranker, Daniel Paul, “Automatic Synthesis and Presentation of OLAP Cubes from Semantically Enriched Data Sources,” U.S. Appl. No. 61/362,781, filed Jul. 9, 2010. |
| National Center for Biotechnology Information, Website, Retrieved from the Internet; URL: https://www.ncbi.nlm.nih.gov/ [retrieved Mar. 7, 2019]. |
| Nguyen, Bao-Yen Thi, Restriction Requirement dated Jun. 29, 2021 for Design U.S. Appl. No. 29/648,466. |
| Nguyen, Kim T., Non-Final Office Action dated Apr. 25, 2022 for U.S. Appl. No. 17/163,287. |
| Nguyen, Kim T., Non-Final Office Action dated Aug. 31, 2021 for U.S. Appl. No. 16/899,549. |
| Nguyen, Kim T., Non-Final Office Action dated Aug. 31, 2022 for U.S. Appl. No. 17/332,354. |
| Nguyen, Kim T., Non-Final Office Action dated Aug. 31, 2022 for U.S. Appl. No. 17/333,914. |
| Nguyen, Kim T., Non-Final Office Action dated Dec. 10, 2020 for U.S. Appl. No. 16/137,297. |
| Nguyen, Kim T., Non-Final Office Action dated Dec. 8, 2020 for U.S. Appl. No. 15/985,704. |
| Nguyen, Kim T., Non-Final Office Action dated Jun. 14, 2018 for U.S. Appl. No. 15/186,514. |
| Nguyen, Kim T., Non-Final Office Action dated Jun. 7, 2021 for U.S. Appl. No. 16/457,766. |
| Nguyen, Kim T., Non-Final Office Action dated Mar. 20, 2019 for U.S. Appl. No. 15/454,923. |
| Nguyen, Kim T., Non-Final Office Action dated May 11, 2021 for U.S. Appl. No. 16/395,036. |
| Nguyen, Kim T., Non-Final Office Action dated Nov. 24, 2020 for U.S. Appl. No. 16/036,834. |
| Nguyen, Kim T., Non-Final Office Action dated Nov. 24, 2020 for U.S. Appl. No. 16/036,836. |
| Nguyen, Kim T., Non-Final Office Action dated Nov. 27, 2020 for U.S. Appl. No. 15/985,705. |
| Nguyen, Kim T., Non-Final Office Action dated Oct. 14, 2020 for U.S. Appl. No. 15/943,629. |
| Nguyen, Kim T., Non-Final Office Action dated Oct. 14, 2020 for U.S. Appl. No. 15/943,633. |
| Nguyen, Kim T., Non-Final Office Action dated Oct. 27, 2020 for U.S. Appl. No. 15/985,702. |
| Nguyen, Kim T., Non-Final Office Action dated Oct. 5, 2020 for U.S. Appl. No. 15/927,004. |
| Nguyen, Kim T., Non-Final Office Action dated Oct. 5, 2020 for U.S. Appl. No. 15/927,006. |
| Nguyen, Kim T., Non-Final Office Action dated Sep. 21, 2020 for U.S. Appl. No. 15/926,999. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Nov. 21, 2022 for U.S. Appl. No. 17/332,354. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Apr. 14, 2022 for U.S. Appl. No. 17/037,005. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Aug. 17, 2021 for U.S. Appl. No. 16/428,915. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Sep. 28, 2022 for U.S. Appl. No. 17/163,287. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due, dated May 15, 2019 for U.S. Appl. No. 15/454,923. |
| Niinimaki et al., “An ETL Process for OLAP Using RDF/OWL Ontologies,” Journal on Data Semantics XIII, LNCS 5530, Springer, pp. 97-119, Aug. 12, 2009. |
| Noy et al., “Tracking Changes During Ontology Evolution.” International Semantic Web Conference. Springer, Berlin, Heidelberg, 2004 (Year: 2004). |
| Pandit et al., “Using Ontology Design Patterns to Define SHACL Shapes,” CEUR Workshop Proceedings, Proceedings of the 9th Workshop on Ontology Design and Patterns (WOP 2018), Monterey, USA, Oct. 9, 2018. |
| Parashar et al., U.S. Appl. No. 62/329,982, filed Apr. 29, 2016 and titled “Automatic Parsing of Semi-Structured Data and Identification of Missing Delimiters.” |
| Patel-Schneider, P., Hayes, P., Horrocks, I., “OWL Web Ontology Language Semantics and Abstract Syntax,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-owl-semantics-20040210 [retrieved Mar. 7, 2019]. |
| Perez, J., Arenas, M., Gutierrez, C., “Semantics and Complexity of SPARQL,” In Proceedings of the International Semantic Web Conference (ISWC2006). 2006. |
| Prud'hommeaux, E., Seaborne, A., “SPARQL Query Language for RDF,” W3C Recommendation, Jan. 15, 2008, Retrieved from the Internet; URL: https://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/ [retrieved Mar. 7, 2019]. |
| Raab, Christopher J., Non-Final Office Action dated Jul. 24, 2020 for U.S. Appl. No. 16/271,687. |
| Raab, Christopher J., Non-Final Office Action dated Jun. 28, 2018 for U.S. Appl. No. 15/186,520. |
| Raab, Christopher J., Non-Final Office Action dated Oct. 16, 2020 for U.S. Appl. No. 16/287,967. |
| Raab, Christopher J., Notice of Allowance and Fee(s) Due and Notice of Allowability for U.S. Appl. No. 15/186,520, dated Jan. 2, 2019. |
| Rachapalli et al., “RETRO: A Framework for Semantics Preserving SQL-to-SPARQL Translation,” The University of Texas at Dallas; Sep. 18, 2011, XP055737294, Retrieved from internet: http://iswc2011.semanticweb.org/fileadmin/iswc/Papers/Workshope/EvoDyn/evodyn_3.pdf. Retrieved on Oct. 6, 2020. |
| RDB2RDF Working Group Charter, Sep. 2009, Retrieved from the Internet; URL: https://www.w3.org/2009/08/Ydb2rdf-charter [retrieved Mar. 7, 2019]. |
| Reynolds et al., “Computerized Tool Implementation of Layered Data Files to Discover, Form, or Analyze Dataset Interrelations of Networked Collaborative Datasets,” U.S. Appl. No. 15/454,981, filed Mar. 9, 2017. |
| Reynolds et al., “Computerized Tools to Discover, Form, and Analyze Dataset Interrelations Among a System of Networked Collaborative Datasets,” International Patent Application No. PCT/US2018/020812 filed with the Receiving Office of the USPTO dated Mar. 3, 2018. |
| Reynolds et al., “Interactive Interfaces to Present Data Arrangement Overviews and Summarized Dataset Attributes for Collaborative Datasets,” U.S. Appl. No. 15/454,969, filed Mar. 9, 2017. |
| Sahoo, S., et al., “A Survey of Current Approaches for Mapping of Relational Databases to RDF,” W3C RDB2RDF XG Report, Incubator Group, URL: http://www.w3.org/2005/Incubator/rdb2rdf/RDB2RDF_Survey_Report_01082009.pdf Published Jan. 8, 2009. |
| Sequeda, J., Depena, R., Miranker. D., “Ultrawrap: Using SQL Views for RDB2RDF,” Poster in the 8th International Semantic Web Conference (ISWC2009), Washington DC, US, 2009. |
| Sequeda, J., et al., “Direct Mapping SQL Databases to the Semantic Web,” Technical Report 09-04. The University of Texas at Austin, Department of Computer Sciences. 2009. |
| Sequeda, J., et al., “Ultrawrap: SPARQL Execution on Relational Data,” Technical Report. The University of Texas at Austin, Department of Computer Sciences. 2012. |
| Sequeda, J., Tirmizi, S., Miranker, D., “SQL Databases are a Moving Target,” Position Paper for W3C Workshop on RDF Access to Relational Databases, Cambridge, MA, USA, 2007. |
| Skevakis, Giannis et al., Metadata management, interoperability and Linked Data publishing support for Natural History Museums, Int J Digit Libr (2014), published online: Apr. 11, 2014; Springer-Verlag Berlin Heidelberg. |
| Slawski, Bill, Google Knowledge Cards Improve Search Engine Experiences, SEO by the Sea, Published Mar. 18, 2015, URL: https://www.seobythesea.com/2015/03/googles-knowledge-cards/, Retrieved Sep. 15, 2021. |
| Smith, M., Welty, C., McGuiness, D., “OWL Web Ontology Language Guide,” W3C Recommendation, Feb. 10, 2004, Retrieved from the Internet; URL: https://www.w3.org/TR/2004/REC-owl-guide-20040210/ [retrieved Mar. 7, 2019]. |
| Smith, T.F., Waterman, M.S., “Identification of Common Molecular Subsequences,” J. Mol. Biol. 147, 195-197 (1981). |
| Spieler, William, Advisory Action dated Nov. 22, 2021 for U.S. Appl. No. 16/435,196. |
| Spieler, William, Final Office Action dated Mar. 15, 2021 for U.S. Appl. No. 16/435,196. |
| Spieler, William, Non-Final Office Action dated Dec. 31, 2020 for U.S. Appl. No. 16/435,196. |
| Spieler, William, Non-Final Office Action dated Feb. 25, 2021 for U.S. Appl. No. 16/558,076. |
| Spieler, William, Non-Final Office Action dated Jul. 9, 2021 for U.S. Appl. No. 16/435,196. |
| Tirmizi, S., Sequeda, J., Miranker, D., “Translating SQL Applications to the Semantic Web,” In Proceedings of the 19th International Databases and Expert Systems Application Conference (DEXA2008). Turin, Italy. 2008. |
| U.S. Appl. No. 16/251,408, filed Jan. 18, 2019. |
| Uddin, MD I, Non-Final Office Action dated May 13, 2021 for U.S. Appl. No. 16/404,113. |
| Uddin, MD I., Final Office Action dated Jan. 1, 2021 for U.S. Appl. No. 16/404,113. |
| Uddin, MD I., Non-Final Office Action dated Oct. 6, 2020 for U.S. Appl. No. 16/404,113. |
| Ultrawrap Mapper, U.S. Appl. No. 62/169,268, filed Jun. 1, 2015 (Expired). |
| Vu, Bai Duc, Notice of Allowance and Fee(s) Due dated Aug. 22, 2022 for U.S. Appl. No. 16/899,551. |
| Vy, Hung T., Final Office Action for U.S. Appl. No. 13/180,444 dated Dec. 3, 2014. |
| Vy, Hung T., Final Office Action for U.S. Appl. No. 13/180,444 dated Dec. 9, 2015. |
| Vy, Hung T., Final Office Action for U.S. Appl. No. 13/180,444 dated Feb. 22, 2013. |
| Vy, Hung T., Non-Final Office Action for U.S. Appl. No. 13/180,444 dated Jun. 18, 2015. |
| Vy, Hung T., Non-Final Office Action for U.S. Appl. No. 13/180,444 dated Mar. 26, 2014. |
| Yen, Syling, Final Office Action dated Apr. 10, 2019 for U.S. Appl. No. 15/186,519. |
| Yen, Syling, Final Office Action dated Oct. 25, 2019 for U.S. Appl. No. 15/186,519. |
| Yen, Syling, Non-Final Office Action dated Feb. 8, 2019 for U.S. Appl. No. 15/186,519. |
| Yen, Syling, Non-Final Office Action dated Sep. 12, 2019 for U.S. Appl. No. 15/186,519. |
| Yotova, Polina, European Patent Office Examination Report, Communication Pursuant to Article 94(3) EPC for European Patent Application No. 17815970.3 dated Oct. 5, 2021. |
| Yotova, Polina, Supplementary European Search Report and Examiner Search Opinion for European Patent Application No. 17815970.3, dated Feb. 21, 2020. |
| Young, Lee W., International Searching Authority, Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2017/037846, dated Nov. 9, 2017. |
| Young, Lee W., International Searching Authority, Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2018/020812, dated Aug. 8, 2018. |
| Young, Lee W., Invitation to Pay Additional Fees and, Where Applicable, Protest Fee, dated Jun. 14, 2018 for International Application No. PCT/US2018/020812. |
| Young, Lee W., Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated May 29, 2018 for International Patent Application No. PCT/US2018/018906. |
| Young, Lee W., Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/057334, dated Mar. 22, 2012. |
| Ganti et al., U.S. Appl. No. 14/058,184, filed Oct. 18, 2013 and entitled, “Assisted Query Formation, Validation, and Result Previewing in a Database Having a Complex Schema.” |
| Ganti et al., U.S. Appl. No. 14/058,189, filed Oct. 18, 2013 and entitled, “Assisted Query Formation, Validation, and Result Previewing in a Database Having a Complex Schema.” |
| Ganti et al., U.S. Appl. No. 14/058,206, filed Oct. 18, 2013 and entitled, “Curated Answers Community Automatically Populated Through User Query Monitoring.” |
| Ganti et al., U.S. Appl. No. 14/058,208, filed Oct. 18, 2013 and entitled, “Editable and Searchable Markup Pages Automatically Populated Through User Query Monitoring.” |
| Ganti et al., U.S. Appl. No. 61/802,716, filed Mar. 17, 2013 and entitled, “Data Profile Driven Query Builder.” |
| Ganti et al., U.S. Appl. No. 61/802,742, filed Mar. 18, 2013 and entitled, “Developing a Social Data Catalog by Crowd-Sourcing.” |
| Jacob et al., “Dataset Analysis and Dataset Attribute Inferencing to Form Collaborative Datasets,” U.S. Appl. No. 16/292,120, filed Mar. 4, 2019. |
| Jacob et al., “Management of Collaborative Datasets via Distributed Computer Networks,” U.S. Appl. No. 16/271,687, filed Feb. 8, 2019. |
| Jacob et al., “Management of Collaborative Datasets via Distributed Computer Networks,” U.S. Appl. No. 16/292,135, filed Mar. 4, 2019. |
| Jacob et al., “Query Generation for Collaborative Datasets,” U.S. Appl. No. 16/395,043, filed Apr. 25, 2019. |
| Jacob et al., “Query Generation for Collaborative Datasets,” U.S. Appl. No. 16/395,049, filed Apr. 25, 2019. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Aug. 3, 2021 for U.S. Appl. No. 16/457,766. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Jul. 11, 2022 for U.S. Appl. No. 17/332,368. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Mar. 16, 2021 for U.S. Appl. No. 15/985,702. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Mar. 16, 2021 for U.S. Appl. No. 16/137,297. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Mar. 17, 2021 for U.S. Appl. No. 15/985,704. |
| Nguyen, Kim T., Notice of Allowance and Fee(s) Due dated Mar. 31, 2021 for U.S. Appl. No. 15/985,705. |
| Vy, Hung T., Non-Final Office Action for U.S. Appl. No. 15/273,930 dated Dec. 20, 2017. |
| Willis, Amanda Lynn, Final Office Action dated Apr. 18, 2022 for U.S. Appl. No. 16/899,547. |
| Willis, Amanda Lynn, Non-Final Office Action dated Feb. 8, 2022 for U.S. Appl. No. 16/899,547. |
| Willis, Amanda Lynn, Non-Final Office Action dated Sep. 8, 2022 for U.S. Appl. No. 16/899,547. |
| Woo, Isaac M., Non-Final Office Action dated Jul. 28, 2022 for U.S. Appl. No. 17/004,570. |
| Woo, Isaac M., Non-Final Office Action dated May 5, 2020 for U.S. Appl. No. 16/137,292. |
| Number | Date | Country | |
|---|---|---|---|
| 20220058193 A1 | Feb 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16120057 | Aug 2018 | US |
| Child | 17037005 | US | |
| Parent | 15186514 | Jun 2016 | US |
| Child | 16120057 | US | |
| Parent | 17461982 | Aug 2021 | US |
| Child | 16120057 | US | |
| Parent | 15454923 | Mar 2017 | US |
| Child | 16457766 | US | |
| Parent | 16036834 | Jul 2018 | US |
| Child | 17332354 | US | |
| Parent | 16036836 | Jul 2018 | US |
| Child | 17332354 | May 2021 | US |
| Parent | 15985702 | May 2018 | US |
| Child | 17333914 | US | |
| Parent | 16137292 | Sep 2018 | US |
| Child | 17004570 | US | |
| Parent | 15926999 | Mar 2018 | US |
| Child | 15454923 | US | |
| Parent | 15927004 | Mar 2018 | US |
| Child | 15926999 | US | |
| Parent | 15985702 | May 2018 | US |
| Child | 15927004 | US | |
| Parent | 15985704 | May 2018 | US |
| Child | 15985702 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17037005 | Sep 2020 | US |
| Child | 17461982 | US | |
| Parent | 16457766 | Jun 2019 | US |
| Child | 17461982 | US | |
| Parent | 15186514 | Jun 2016 | US |
| Child | 15454923 | US | |
| Parent | 17461982 | Aug 2021 | US |
| Child | 15454923 | US | |
| Parent | 17332354 | May 2021 | US |
| Child | 17461982 | US | |
| Parent | 15186514 | Jun 2016 | US |
| Child | 16036834 | US | |
| Parent | 15186516 | Jun 2016 | US |
| Child | 15186514 | US | |
| Parent | 15454923 | Mar 2017 | US |
| Child | 15186516 | US | |
| Parent | 15926999 | Mar 2018 | US |
| Child | 15454923 | US | |
| Parent | 15927004 | Mar 2018 | US |
| Child | 15926999 | US | |
| Parent | 15439908 | Feb 2017 | US |
| Child | 15927004 | US | |
| Parent | 15985702 | May 2018 | US |
| Child | 15439908 | US | |
| Parent | 15985704 | May 2018 | US |
| Child | 15985702 | US | |
| Parent | 15985705 | May 2018 | US |
| Child | 15985704 | US | |
| Parent | 15186514 | Jun 2016 | US |
| Child | 16036836 | US | |
| Parent | 15186516 | Jun 2016 | US |
| Child | 15186514 | US | |
| Parent | 15454923 | Mar 2017 | US |
| Child | 15186516 | US | |
| Parent | 15926999 | Mar 2018 | US |
| Child | 15454923 | US | |
| Parent | 15927004 | Mar 2018 | US |
| Child | 15926999 | US | |
| Parent | 15439908 | Feb 2017 | US |
| Child | 15927004 | US | |
| Parent | 15985702 | May 2018 | US |
| Child | 15439908 | US | |
| Parent | 15985704 | May 2018 | US |
| Child | 15985702 | US | |
| Parent | 15985705 | May 2018 | US |
| Child | 15985704 | US | |
| Parent | 17469982 | Aug 2021 | US |
| Child | 15985704 | US | |
| Parent | 17333914 | May 2021 | US |
| Child | 17469982 | US | |
| Parent | 15186514 | Jun 2016 | US |
| Child | 15985702 | US | |
| Parent | 15186516 | Jun 2016 | US |
| Child | 15186514 | US | |
| Parent | 15454923 | Mar 2017 | US |
| Child | 15186516 | US | |
| Parent | 15926999 | Mar 2018 | US |
| Child | 15454923 | US | |
| Parent | 15927004 | Mar 2018 | US |
| Child | 15926999 | US | |
| Parent | 17461982 | Aug 2021 | US |
| Child | 15926999 | US | |
| Parent | 17004570 | Aug 2020 | US |
| Child | 17461982 | US | |
| Parent | 15454923 | Mar 2017 | US |
| Child | 16137292 | US |
