YeNotice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
DETAILED ACTION
1. This Office Action is in response to the amendment filed on 03/24/2026.
Claims 1, 17 and 19 have been amended.
Claims 1-20 are pending.
Response to Arguments
2. Applicant's arguments with respect to claims 1-20 have been considered but are moot in view of the new ground(s) of rejection.
Examiner's Note
3. Data lineage (According to Google): "Data lineage is the process of tracking, mapping,
and visualizing the entire lifecycle of data, from its origin, through all transformations (ETL/ELT
processes), to its final destination and consumption. It provides a detailed record of data
dependencies, enabling users to verify accuracy, audit compliance, troubleshoot errors, and
understand the impact of changes."
Data asset (According to Google): "A data asset is a managed collection of structured or
unstructured data-such as databases, files, or reports-that holds measurable economic or
operational value for an organization. These digital resources are used to drive decision-
making, improve processes, and provide competitive insights. They can include customer
records, sensor data, or intellectual property."
Gatchell et al, US 10,521,442, [Gatchell: Abstract and column 1, lines 29-46 ("provides
integrated technical metadata and business metadata for each of a plurality of the data assets of
the enterprise", i.e., 'shared data asset' and 'shared data asset object')] [Gatchell: Column 2,
lines 34-37 and Figure 6 ("FIG. 6 shows an example of an integrated workflow generated
utilizing a value-based governance architecture", i.e., 'shared data asset' and 'shared data asset
object')] [Gatchell: Column 12, lines 11-17 ("Metadata Integration. Integration combines
technical and business metadata as well as data lineage", i.e., 'data lineage' and 'shared data
asset')] [Gatchell: Column 2, lines 1-12 ("Governance issues relating to data assets from
multiple distinct data sources", i.e., distributed data system)] [Gatchell: Column 12, lines 31-44
("this figure illustrates an end-to-end integrated workflow from request to review to approval
and provisioning across multiple teams from including business and IT teams", i.e., data
approval)].
McCormick et al, US 11,906,950, [McCormick: Column 1, lines 35-52 (“In many cases, the asset data that hold the answers are scattered among different production sites and incompatible systems, formats and processes. Basic systems (e.g., data lakes) have been developed to collect, analyze, visualize and share time-series asset data generated from multiple sources to people and systems across all operations”)] [McCormick: Column 4, lines 18-23 (“With respect to deployment, some embodiments provide governance controls for industrial enterprise models and data. For example, some embodiments track data lineage (e.g., from data source to data sink), synchronize data and models across systems, and/or provide version control for the asset models”)] [McCormick: Column 5, lines 21-33 (“In some embodiments, the asset models 143 may include contextualized data templates, and the data pipeline 142 may transform the data into the form specified by the contextualized data templates. In this way, the data pipeline 142 and the ingress agents 141 may link the attributes of an asset model's template to the locations in the data sources 110 where the corresponding data are stored.”)] [McCormick: Column 6, lines 27-38 (“In some embodiments, the system 100 functions as a data hub addressing the asset data domain (e.g., assets, equipment, processes, and personnel), thereby enabling industrial companies to connect to data, manage their data models, digital representations of physical assets, and then share models and data across the enterprise”)].
Munuri et al, US 20230350862, [Munuri: Abstract and paragraphs 2 and 84(“to collecting data from a plurality of sources, and linking the collected data to derive information and knowledge. The method includes defining at least one data model and asset by including data models, vocabulary, data quality rules, data mapping rules for at least one of, a particular data industry, a data domain, or a data subject area, importing data from a plurality of data sources, performing de-duplication of the imported data and data profiling of the imported data, and creating linked data either by semantic mapping, or by curating the data.”, i.e., “derive information and knowledge” = ‘shared data asset’ or ‘derived data asset’)] [Mumuri: Paragraph 2 (“to collecting data from a plurality of sources, and linking the collected data to derive information and knowledge (i.e., providing a linked data intelligence via a knowledge graph) and providing a fully connected and interoperable data cloud available via open and community standards”, i.e., “derive information and knowledge” or “linked data intelligence” can be shared (“interoperable data cloud available via open and community standards”)] [Munuri: Paragraphs 29 and 36 (“collecting data from a plurality of sources and linking the collected data to derive information and knowledge”)] [Munuri: Paragraph 58 (“Once the linked data and the associated metadata is fully connected, enterprise micro applications such as, but are not limited to, linked Master Data Management (MDM), data quality observability, data lineage, data dictionaries, data vocabulary, data marketplace, and so on”)] [Munuri: Paragraph 64 (“In an embodiment, the data integration engine 202 may also be configured to provide an up-to-date canonical source of information in the form of linked data to the target entities 206, which can be trusted.”)].
Sim Tang, US 20200311294, [Sim Tang: Paragraph 25 (“FIG. 2 illustrates the structure of a Collaborative System for Data Asset Management, Secured Data Sharing, and Data Processing”)] [Sim Tang: Paragraphs 50-53 and 89 (“Dataset Data Lineage Service”)] [Sim Tang: Paragraph 97 (“In step 0863, the data user can set permissions for the collaborator to restrict what the collaborator can do to the dataset object. For example, is the collaborator allowed to make changes to metadata in the dataset object; can the collaborator share and publish information and data of the dataset object; can the collaborator read or write the data contents of the data item associates with the dataset object. If the collaborator is allowed to read or write data contents, then in step 0866 data user defines personalized security and privacy access control rules (e.g., 0360-x) to restrict the collaborator's access to the data content. This may be used for example to filter sensitive data. Sensitive data as used herein refers to data that may need to have access restricted for security and/or privacy control reasons. For example, the rules may specify which part of the content has to be masked, which part of the content has to be filtered out, and which part of the content needs to be transformed before sharing with the collaborator. In step 0868, the collaborator, the dataset object usage permissions, and the personalized security and privacy data content access control rules are written into the source dataset object (in this example it is R1). Then in step 0870, a new dataset object R2 is created in the collaborator's Data User Environment (e.g., 0312-a). The new data object R2 (e.g., 0330-x) is linked to its source dataset object R1 (e.g., 0330-a, 0330-b, or 0330-c)”)] [Sim Tang: Paragraphs 130-136 (“FIG. 18 begins with the Data Lineage Service (1540) receiving the reference to a dataset (say Dataset-A). A dataset reference may be an identifier, a name, or an address of the dataset. In step 1804, a new lineage map is created (refer to as Map) with only one node (Dataset-A).” , i.e., ‘includes links to the at least two source data assets’)].
Claim Rejections - 35 USC § 103
4. In the event the determination of the status of the application as subject to AIA 35 U.S.C.
102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the
statutory basis for the rejection will not be considered a new ground of rejection if the prior art
relied upon, and the rationale supporting the rejection, would be the same under either status.
5. The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness
rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
6. Claims 1-2, 4, 6-8, 10-14 and 17-20 are rejected under 35 U.S.C. 103 as being
unpatentable over Chu et al (US 20230007074), in view of Sim-Tang (US 20200311294).
Claim 1:
Chu suggests a computer-implemented method for providing sharing of electronic data
assets, the computer-implemented method comprising, by one or more hardware processors
executing program instructions: receiving, from a first user, a request to access a shared data
asset, wherein the shared data asset is associated with a shared data asset object [Chu: Title and
paragraphs 29, 40, 42 and 63 ("global data sharing" and "The private data exchange may
provide a centralized, managed hub for an entity to list internally or externally-shared data
assets, inspire data collaboration, and also to maintain data governance and to audit access")].
Chu suggests in response to receiving the request from the first user, generating a data access
request object including at least an identification of the first user and an identification of the
shared data asset object [Chu: Paragraphs 40, 45-47 and 49-50 ("The access controls 206 may
specify a class of users (members of a particular group or organization) that are allowed to
access the data and/or see the listing. The access controls 206 may specify that a "point-to-
point" share ")]. Chu suggests obtaining an approval of the request [Chu: Paragraphs 46 and
129 ("The access controls 206 may specify that a "point-to-point" share (see discussion of FIG.
4) in which users may request access but are only allowed access upon approval of the provider"
and "The data provider may approve or deny the request at 822. If approved, the private data
exchange may grant access to the listing at 823. The user may then begin consuming the data as
discussed above ")]. Chu suggests in response to obtaining the approval of the request, granting the first user access to the shared data asset associated with the shared data asset object [Chu: Paragraphs 46 and 129 ("The access controls 206 may specify that a "point-to-point" share (see
discussion of FIG. 4) in which users may request access but are only allowed access upon
approval of the provider" and "The data provider may approve or deny the request at 822. If
approved, the private data exchange may grant access to the listing at 823. The user may then
begin consuming the data as discussed above")]. Chu suggests wherein the shared data asset is a
derived data asset comprising a combination of at least two shared source data assets, and
wherein the shared data asset object identifies the shared data asset as derived [Chu: Paragraphs
30 and 108 ("In addition, a data provider may combine its own data with other data sets from,
e.g., a public data exchange, and create new listings using the combined data"). Paragraph 67
("manages the integration of shared data referenced by consumed shares"). Paragraph 131
("serve to combine the benefits of crowdsourced content")].
Sim Tang suggests indicating lineage data identifying the at least two source data assets
based on which the data asset is derived [Sim Tang: Paragraphs 13-15 ("IT administrators (0101) first process corporate data by going through extraction, cleaning, and transformation to create curated data. IT administrators then connect the curated data source (0102-a, 0102-b, 0102-c) to the platform for management purposes. In the platform, data source (0121-a, 0121-b, 0121-c) objects are logical entities created to manage the real data source (0102-a, 0102-b, 0102-c). IT administrators then build and manage a static data directory (also known as a data catalog 0105) which contains a list of all the data sources connected to the platform.", i.e., 'shared data asset' and 'shared data asset object')]
[Sim Tang: Paragraphs 72-76 ("Data users (0203-a, 0203-b, 0203-c) select data items from their data sources (0211-a, 0211-b, 0211-c) and register the data items as Datasets (0222-a, 0222-b, 0222-c) into their Data Processing Environment (0221-a, 0221-b, 0221-c). For example, a data user may select a table (a data item) from a database (a Data Source 0211-a, 0211-b, 0211-c) and register it as a Dataset (0222-a, 0222-b, 0222-c). In their Data Processing Environment (0221-a, 0221-b, 0221-c), data users can create Project Containers (0223-a, 0223-b, 0223-c). Each Data User Environment (0221-a, 0221-b, 0221-c) is isolated from all others. However, data users can share datasets and collaborate (0213) with one another on their projects. In such instances, only the shared datasets and Project Containers are visible to the selected collaborators. Personalized security and privacy access control rules are defined by the data owner for the collaborator while sharing is initiated”] [Sim Tang: Paragraphs 130-136 (“FIG. 18 begins with the Data Lineage Service (1540) receiving the reference to a dataset (say Dataset-A). A dataset reference may be an identifier, a name, or an address of the dataset. In step 1804, a new lineage map is created (refer to as Map) with only one node (Dataset-A).” , i.e., ‘includes links to the at least two source data assets’)].
Both references (Chu and Sim Tang) taught features that were directed to analogous art
and they were directed to the same field of endeavor, such as data processing and data
integration. It would have been obvious to one of ordinary skill in the art at the time the
invention was made, having the teachings of Chu and Sim Tang before him/her, to modify the
system of Chu with the teaching of Sim Tang in order to provide data integration and data
collaboration or sharing [Sim Tang: Paragraphs 72-76 and 130-136].
Claim 2:
The combined teachings of Chu and Sim Tang suggest wherein the shared data asset
object identifies at least a second user authorized to approve sharing of the shared data asset, and
wherein obtaining the approval of the request comprises: providing an indication of the data
access request object to the second user associated with the shared data asset object; and
receiving, from the second user, the approval of the request [Chu: Paragraphs 40, 45-46 and 129
("The access controls 206 may specify that a "point- to-point" share (see discussion of FIG. 4) in
which users may request access but are only allowed access upon approval of the provider" and
"The data provider may approve or deny the request at 822. If approved, the private data
exchange may grant access to the listing at 823. The user may then begin consuming the data as
discussed above ")].
Claim 4:
The combined teachings of Chu and Sim Tang suggest further comprising, by the one or
more hardware processors executing program instructions: further in response to receiving the
approval of the request from the second user: updating the data access request object to include at least an indication of the approval of the request [Chu: Paragraphs 3, 41 and 50 ("Databases
may include one or more tables that include or reference data that can be read, modified, or
deleted using queries" and "choose to expand the filters 208 to permit access to excluded users
or classes of excluded users ")].
Claim 6:
The combined teachings of Chu and Sim Tang suggest receiving one or more user inputs
to share a data asset; and in response to receiving the one or more user inputs, generating the
shared data asset object [Chu: Paragraphs 40, 45-47 and 49-50 ("The access controls 206 may
specify a class of users (members of a particular group or organization) that are allowed to
access the data and/or see the listing. The access controls 206 may specify that a "point-to-
point" share ")].
Claim 7:
The combined teachings of Chu and Sim Tang suggest wherein the shared data asset
object comprises metadata including at least one of: schema, update frequencies, owner, tag,
approver, column identifier, column description, derivation, or filtering [Chu: Paragraph 27
("owner of data")].
Claim 8:
The combined teachings of Chu and Sim Tang suggest wherein the data access request
object comprises metadata including at least one of: forms, conversations, updates, approvals, re-
approvals, statuses, or versions [Chu: Paragraphs 46 and 129 ("The access controls 206 may
specify that a "point-to-point" share (see discussion of FIG. 4) in which users may request
access but are only allowed access upon approval of the provider" and "The data provider may approve or deny the request at 822. If approved, the private data exchange may grant access to
the listing at 823. The user may then begin consuming the data as discussed above ")].
Claim 10:
The combined teachings of Chu and Sim Tang suggest receiving one or more user inputs
to share a data asset; and in response to receiving the one or more user inputs, generating the
shared data asset object, wherein the shared data asset is based on the data asset [Chu:
Paragraphs 46 and 129 ("The access controls 206 may specify that a "point-to-point" share (see
discussion of FIG. 4) in which users may request access but are only allowed access upon
approval of the provider" and "The data provider may approve or deny the request at 822. If
approved, the private data exchange may grant access to the listing at 823. The user may then
begin consuming the data as discussed above ")].
Claim 11:
The combined teachings of Chu and Sim Tang suggest wherein the shared data asset is
scoped or filtered from the data asset, and wherein the shared data asset object includes
information on the scoping or filtering of the data asset [Chu: Paragraph 50 "filtering ")].
Claim 12:
The combined teachings of Chu and Sim Tang suggest requesting, from the first user, a
justification with the request to access a shared data asset; and updating the data access request
object with the justification [Chu: Paragraphs 3, 41 and 50 ("Databases may include one or
more tables that include or reference data that can be read, modified, or deleted using queries" and "choose to expand the filters 208 to permit access to excluded users or classes of excluded
users")].
Claim 13:
The combined teachings of Chu and Sim Tang suggest wherein the shared data asset is
updated, and wherein the updates are propagated [Chu: Paragraphs 3, 41 and 50 ("Databases
may include one or more tables that include or reference data that can be read, modified, or deleted using queries" and "choose to expand the filters 208 to permit access to excluded users
or classes of excluded users")].
Claim 14:
The combined teachings of Chu and Sim Tang suggest wherein the data access request
object is versioned [Chu: Paragraphs 56 and 76 ("update version ")].
Claim 17:
Claim 17 is essentially the same as claim 1 except that it sets forth the claimed invention as a system rather than a method and rejected under the same reasons as applied above.
Claim 18:
Claim 18 is essentially the same as claim 2 except that it sets forth the claimed invention
as a system rather than a method and rejected under the same reasons as applied above.
Claim 19:
Claim 19 is essentially the same as claim 1 except that it sets forth the claimed invention
as a program product rather than a method and rejected under the same reasons as applied above.
Claim 20:
Claim 20 is essentially the same as claim 2 except that it sets forth the claimed invention
as a program product rather than a method and rejected under the same reasons as applied above.
Conclusion
7. Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the date of this final action.
8. Any inquiry concerning this communication or earlier communications from the examiner should be directed to [Hung D. Le], whose telephone number is [571-270-1404]. The examiner can normally be communicated on [Monday to Friday: 9:00 A.M. to 5:00 P.M.].
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Apu Mofiz can be reached on [571-272-4080]. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, contact [800-786-9199 (IN USA OR CANADA) or 571-272-1000].
Hung Le
06/08/2026
/HUNG D LE/Primary Examiner, Art Unit 2161
Prosecution Insights